Revisions are where a website project either builds momentum or loses it. Design work arrives, the owner responds, and what happens next depends on how well both sides understand the process they are in. Teams offering web design in san francisco run revision stages in structured ways, and owners who know that structure contribute more clearly, receive better results, and avoid the frustration of changes circling without landing. Three aspects of the revision process deserve clear expectation-setting before the first design arrives.
What are the first designs?
First designs show the layout structure of key pages, the colour direction chosen for the brand, the typography selected for headings and body text, and the way sections get ordered to reflect the content priorities agreed during planning. These elements appear together for the first time at this stage, so both sides can confirm the design is heading in the right direction before detailed work begins on top of that foundation.
First designs do not show finished copy, final photography, precise icon sizing, or pixel-level spacing, because applying that level of detail before the direction is confirmed means reworking it if the direction changes. Agencies share early screens specifically to get confirmation that the layout, colour, and structure are correct, so the feedback at this stage needs to cover those three areas and nothing below them in the design hierarchy.
Rounds narrow toward approval
Each revision round opens with the agency sharing updated designs based on the feedback received and closes with the owner returning written notes by the date the schedule sets. The agency applies those notes, and the next round begins, with each exchange producing a version closer to the approved design than the one before it.
- Round one confirms layout, colour direction, typography, and section order across key pages.
- Round two applies detailed adjustments to the confirmed direction across all pages in the project.
- Round three, where the proposal includes it, handles final corrections before both sides sign off.
Owners who direct round one feedback at layout and direction, then save detailed feedback for round two, move through this sequence without needing additional rounds that fall outside the agreed project scope and extend the schedule.
Scope stays separate from revisions
A revision round covers changes to designs that fall within the scope agreed upon before the project started. A request to add a feature not included in that scope, build a page not listed in the sitemap, or introduce a section not discussed during planning sits outside the revision round and needs separate assessment before anyone can confirm whether it joins the current project or follows after launch.
Agencies record these requests separately from revision feedback and assess each one against the existing schedule and build plan before responding. Owners who raise new ideas as separate requests rather than revision comments keep the current round moving at the pace the schedule requires, while owners who include new requests inside feedback comments create delays that affect every remaining stage of the project from that point forward.
Revision stages run most smoothly when owners arrive knowing what each round is for and where the boundary between revision and new scope sits. That knowledge turns what many owners find stressful into the phase where the site comes closest to what they originally imagined, without friction from mismatched expectations.
