A feature request in web projects is a suggestion from a client, reviewer, or team member for a change, addition, or improvement to a website. During review rounds, these requests often arrive as pinned comments on specific elements—"Can we add a testimonial carousel here?" or "This section needs a video embed."
Why capturing requests matters
Requests buried in email threads or Slack messages get lost. When requests are tied to the exact page element they reference, developers know precisely what's being asked and where.
Common sources of feature requests
- Client review sessions: Stakeholders browsing staging sites and leaving notes
- QA testing: Testers flagging missing functionality
- Design handoff: Designers noting interactive behaviors
- Post-launch feedback: Users reporting desired improvements
Handling requests during website reviews
- Capture in context: Pin requests to the element they affect
- Distinguish from bugs: Separate "not working" from "would be nice"
- Scope for the current round: Decide what's in scope vs. future phase
- Assign ownership: Make it clear who's responsible for each item
- Track status: Mark as open, in progress, or resolved
Managing requests with Huddlekit
Huddlekit lets reviewers pin feature requests directly on your live site. Each request stays attached to the element it references, with device context and status tracking built in. No more spreadsheets or ticket-shuffling.
