How to Give Feedback
Good feedback is the single biggest factor in how quickly a project moves and how good the final result is. Here's how to make it count.
Where to leave feedback
Comment directly on the task in your portal. This is the best way. It keeps feedback tied to the deliverable, creates a record, and makes sure nothing gets lost.
Avoid sending feedback through text, email, or phone unless it's something that doesn't relate to a specific deliverable. Scattered feedback across multiple channels is the #1 cause of things getting missed.
What good feedback looks like
Be specific
| Instead of this | Try this |
|---|---|
| "I don't love the homepage" | "The hero section feels too busy. Can we simplify it to just the headline and one CTA?" |
| "The colors are off" | "The blue on the services page is too dark. Can we lighten it to match the logo?" |
| "Can you fix the copy?" | "On the About page, second paragraph, change 'we provide solutions' to 'we build systems'" |
Be consolidated
One detailed comment covering everything is better than 10 separate messages sent over a few days. Take the time to review the full deliverable, write up all your notes, and submit them together.
Reference specifics
- Name the page
- Point to the section
- Quote the exact text you want changed
- Include a screenshot if it helps
Revision rounds
Most projects include revision rounds (the number is in your proposal). A revision round is one consolidated set of feedback covering adjustments within the approved scope.
What counts as a revision:
- Layout adjustments
- Copy edits
- Color or font updates
- Image swaps
- Content reordering
- Pipeline and automation tweaks (CRM projects)
What's outside a revision round:
- New pages or sections
- Complete rewrites
- New functionality
- Additional systems or integrations
Work outside the original scope is quoted separately. See Scope & Additional Work.