Feature Request Tracker: How to Organize Incoming Requests

Once requests start arriving from more than one place, "I'll remember it" stops working. A feature request tracker is the structure that keeps incoming ideas from becoming a pile you're afraid to look at. Done right, nothing gets lost, duplicates collapse into one, and the next thing to build is always visible. Here's how to set one up.

What a tracker actually needs

A tracker doesn't need to be complicated. It needs a small, consistent structure applied to every request:

A single title that states the request in one line, so it's scannable and votable. A status — typically new, planned, in progress, shipped (and sometimes "won't do") — so everyone knows where each item stands. A demand signal — votes or a count of how many people asked — so priority isn't guesswork. And a source so you know where it came from (support, a sales call, the public board).

That's the whole skeleton. Everything else is optional detail you can add per request.

The statuses that matter

Statuses are the backbone of a tracker because they turn a flat list into a pipeline. Keep them few and meaningful:

• New — captured, not yet reviewed.
• Planned — you've decided to do it.
• In progress — actively being built.
• Shipped — live, and time to tell whoever asked.
• Won't do (optional) — a clear, respectful "no," which is kinder than silence.

Resist the urge to add ten sub-statuses. The more granular you get, the less anyone keeps them updated.

Two ways to run a tracker

A spreadsheet works to start: columns for title, status, votes, source. It's free and flexible — but it's private, so users can't see it, can't vote, and duplicates pile up because nobody knows what's already been asked. You also have to maintain it by hand.

A public feedback board is a tracker that maintains itself. Users post directly, vote to supply the demand signal, and see statuses update — which means fewer duplicates and far less manual work for you. On FeatureRequest, the board is the tracker: requests auto-rank by votes and carry status, so organizing happens as a side effect of people using it. For the bigger picture, see what a feature request board is.

Keep it honest

A tracker only works if it reflects reality. Two habits keep it honest: merge duplicates as they come in, so votes concentrate on the real request instead of scattering; and update statuses promptly, especially "shipped," because a tracker full of stale "in progress" items quietly loses everyone's trust. For scaling this across channels, see how to track feature requests across systems.

Start organized

The best time to set up a tracker is before you're buried — but the second-best time is now. Create a free board on FeatureRequest and let your tracker organize itself as requests come in.