Client sign-off on every deliverable, with its versions
A deliverable is submitted on its task, reviewed by the client and accepted or returned with comments. Every version is kept, so everyone knows which file was accepted.
The client says they never accepted version 3. Your team says they did, in an email thread nobody can find. Scope creep often starts exactly here: work accepted informally, then disputed.
How it works in ApprovedFlow
- 1
Submit on the task
The team member uploads the deliverable on the task that produces it and sends it for review.
- 2
The client reviews
The client contact reviews it in the client portal, or acts on the request straight from the email link.
- 3
Returned with comments, or accepted
A rejection goes back to the team with the client's comments. The next upload is a new version of the same deliverable.
- 4
The decision on record
The accepted version, who accepted it and when stay on the task, next to every earlier version.
Questions
Does the client have to sign in?
Not necessarily. The client contact can act on the review request from the email link; signing in gives them the client portal with all their open items.
Are earlier versions kept?
Yes. Each upload is stored as a new version of the same document, with who uploaded it and when.
Where does the team see the client's comments?
On the task, beside the deliverable and its versions, where the project manager and the people on the task see them.
Checklist
- Each deliverable sits on the task that produces it
- The client contact who reviews is named on the project
- Comments come back on the task, not in a side email
- Every new upload is a new version
- The accepted version is recorded before invoicing