Review a delivery with useful feedback
Keep feedback specific, respectful and connected to the accepted terms.
Compare delivery with the Agreement
Start with the accepted scope, schedule, deliverables, usage and included revisions. Point to the file, frame, format or requirement that needs attention. If something is missing, explain the impact and the next action instead of assuming intent.
A review window and handoff method help both people know when feedback is expected. Keep technical notes, creative direction and personal reactions distinct so a practical fix stays possible.
- Reference the accepted requirement.
- Identify the exact file or change.
- State the next action and review timing.
Recognize a scope change
A request for more hours, new deliverables, another channel, a different creative direction or extra revision can be valid while still being new scope. Say so plainly and propose an amendment or new Agreement version before work continues.
Do not hide an expanded request inside a delivery comment. Keeping the change visible protects the contributor from unpaid or uncredited work and gives the requester a clear decision to make.
Close the checkpoint carefully
Completion records that the participants consider the Production work complete. It does not publish files, create verified credit or force anyone to leave a review. If a review is written, keep it tied to the completed project and describe observable collaboration details.
When feedback concerns safety, rights or a material unresolved problem, pause normal closure and use the project issue route where available. Preserve the relevant context instead of deleting the conversation.