How many revisions should we offer?
There is no single number for every job. Agree deliverables, feedback rounds and the approval owner before starting, and record them consistently with your existing agreement and proposal.
HOKUSH / Brief and revision guide
Brief and revision management: clarify expectations before work starts.
A brief aligns the work and delivery criteria. A revision record makes the affected version, scope and decision owner clear.
What should a useful brief answer?
A useful brief explains the purpose, audience, deliverables, required resources, responsibilities, target date and approval criteria. The team should be able to start from it and identify gaps before delivery.
A brief template to copy and complete
Job title: Purpose: Target audience: Deliverables and formats: Out of scope: Source files / current version: Responsible person / team: Feedback and approval owner: Target date and time, if needed: Acceptance criteria: Missing details / open questions:
Revision or a scope change?
A revision changes an agreed deliverable. A new deliverable, channel or audience may change the scope. Compare the requested change with the brief’s deliverables and acceptance criteria instead of relying on the phrase ‘small change’.
A concrete example
If the brief specifies one social media visual, correcting its headline can be treated as a revision. Adding a video and three language versions may introduce new deliverables. The team and client should separately agree timing, price and whether a new job is needed.
An example template and process suggestion, not a customer success result or delivery guarantee.Write a clear revision note
Affected version / file: Requested change: Reason for the change: Areas to keep unchanged: Feedback / approval owner: Agreed target date: Result and approval note:
Before-delivery checklist
- Are all briefed deliverables ready?
- Are the correct files and versions being shared?
- Has the latest feedback been addressed?
- Are any questions or approvals still open?
- Have client-visible files and conversations been checked?
Where can you keep this information in Hokush?
Keep the brief in the job description, related files with the work and revision decisions in the appropriate conversation. Responsibilities and target dates support follow-up. The template here is a text example, not a promise of a separate automated brief or revision module.
Frequently asked questions
What if several people give conflicting feedback?
Identify the decision owner, resolve conflicting notes and agree the changes to apply. Do not expect the designer to guess which feedback takes priority.
Does Hokush approve revisions automatically?
This guide does not claim automatic approval, file version comparison or AI decisions. The described decisions and checks are performed by your team.