A review round is your opportunity to inspect completed work and ask for changes before the project moves forward. Your quotation states how many rounds are included.
The cycle
- We deliver work on staging and tell you what is ready to review and what is not.
- You review within the agreed window, usually a few working days.
- You send one consolidated set of feedback.
- We apply it and deliver the revised version. That closes the round.
Where rounds happen
Typically at design approval and again after content is populated on staging. Larger projects may have a round per module.
Consolidate before you send
Collect feedback from everyone on your side and resolve conflicts internally first. Two people asking for opposite things stops the work while we ask who decides. Sending feedback in five separate messages over two weeks costs the same round but takes five times as long.
Write feedback we can act on
Reference the page and the section, state what should change, and where possible state what it should become. "Services page, third card, change the heading to Managed Hosting" is immediately actionable. "The services page needs work" is not.
What is inside a round
Text edits, image swaps, colour and spacing adjustments, section reordering on an existing page, and anything that does not match what was approved. Corrections to our mistakes are always free and never consume a round.
What is not
New pages, new features, a fresh design direction after approval, or restructuring the navigation. These are change requests and are quoted separately.
The review clock
While work sits with you for review, the project schedule pauses. A review that runs two weeks past its window moves your launch date by two weeks.
If you need longer
Tell us in advance and we will adjust the plan. What causes problems is silence followed by a late burst of feedback.
Unsure whether a request is a revision or a change? Ask on your project thread or write to [email protected] before sending it.
