Start with the right question
A project can expand through small messages that never become a clear revised agreement. A scope record helps both sides identify what was requested, what was approved, and what remains disputed. It should not rewrite ambiguous conversations as definite consent.
Work through the checks
Preserve the baseline brief
Keep the accepted proposal, deliverable list, schedule, revision terms, and price. Identify the version agreed at the start. A later project board can reflect changes without proving their approval.
Track each change request
Record the requested revision, its source, and whether it changes an existing deliverable or adds a new one. Keep examples and attachments so the request can be understood in context.
Separate price approval
Save any estimate for extra work and the response. Distinguish approval of a design direction from agreement to an additional fee. Mark unanswered proposals rather than treating silence as confirmed acceptance.
Match delivery and billing
Link completed work to delivery dates, feedback, and invoice lines. Record credits and partial payments. Keep ownership or license questions separate from the arithmetic of the invoice.
A record you can use
- Original deliverable
- Requested change
- Price or timing proposal
- Approval record
- Delivery and invoice reference
Keep this record locally. Use document references rather than publishing account numbers or other people's personal details. An empty field means the information is still missing; it should not be filled with an AI guess.
Worked example
A fictional designer is hired for a logo and later asked for a social-media kit. The record identifies the kit as a proposed additional deliverable, preserves the fee discussion, and notes that approval is disputed. It does not assume a positive comment about the logo approved every later charge.
This example is fictional and illustrates the method, not a real case result.
Limits and next steps
This page does not determine contract formation, payment obligations, or ownership of creative work. Informal messages can require legal interpretation. Do not withhold access or publish client work without checking the consequences.
Use a concise change table to ask for clarification or prepare for advice. Keep the actual files and communications available so a reviewer can assess the disputed scope.