Revisions, files, and rights

Standalone guides in this hub

• Revision rounds in the contract
• Source files not included
• Usage rights vs buyout

Feedback and review window

Set a calendar window after each delivery for the client to accept or send one consolidated feedback batch.

For example, five business days. If there is no written reply by the deadline, you may treat the round as accepted so the project can move.

This pairs with revision rounds. A window is when feedback is due. A round cap is how many times you revise.

Extra stakeholders and approvers

Default to one named approver who sends one consolidated set of feedback per round.

A new sign-off person mid-project — a partner, boss, or new hire who can block launch — is a scope event. Price the restart or the new round as a change order.

Sample line: Feedback comes from one named approver. Additional approvers who restart a round are billed as a change order.

Client-supplied content and assets

Unless the SOW lists copy, photography, or brand design as deliverables, the client provides usable content.

Say what “final” means — for example, approved copy in a shared doc, images at print resolution, and brand files in vector format.

Late assets are a timeline issue. Keep the supply rule in the SOW, and use a change order if you create the content instead.

Warranty and bug-fix window

After handoff, name a short window where you fix defects that fail the agreed specification at no charge.

For example, fourteen days after delivery. A defect is not a new feature. New work goes through a change order.

Sample line: For fourteen days after delivery, defects against the agreed specification are fixed at no charge. New features are change-order work.

Related pages

SOW exclusions · How to write a change order · All guides

Not legal advice. Match your contract and local rules. This is a process aid, not a lawyer.