One client reviewer says to shorten the homepage. Another asks for more detail. Both comments are recorded, but the work still lacks a clear direction.
This guide adds a clarification process to your existing feedback tracker. Its purpose is to preserve the disagreement and identify the decision needed before execution.
1. Keep the original feedback records
Do not overwrite the first comment with the second. Preserve each source, its date, the relevant deliverable and the version reviewed.
If you need a starting structure, use the client feedback tracker guide. Add this process to that register rather than maintaining a competing list.
2. Describe the conflict as a question
Use one clarification record or page for the unresolved issue. In its body, link the original feedback records and quote only the relevant instruction accurately.
A useful question is: For homepage copy v3, should the services section prioritize a short overview or detailed explanations?
“Client feedback is confusing” does not identify the decision someone must make.
3. Record the next clarification action
| Field | Purpose |
|---|---|
| Issue | Specific decision needed |
| Project | Existing project connection |
| Clarification Owner | Person responsible for obtaining an answer |
| Next Check | When that person should check again |
| Resolution Status | Open or Resolved |
Use existing properties if they already express these meanings. The clarification owner is not automatically the person authorized to approve the client’s direction.
4. Work through a small example
| Source | Instruction | Context |
|---|---|---|
| Reviewer A’s email | Reduce the services section to a short summary | Homepage copy v3 |
| Reviewer B’s document comment | Add an explanation under each service | Homepage copy v3 |
First check whether both people reviewed the same version and section. If they did, identify the authorized decision-maker through the agreed client process.
The next action might be: “Ask the project contact to confirm one direction for the services section, including whether both reviewers agree.” Do not infer approval from which message arrived last.
5. Build an open-clarification view
Create a Table view filtered to Resolution Status is Open. Show Issue, Project, Clarification Owner and Next Check. Sort Next Check ascending.
Keep a separate check for Open AND Next Check is empty, so an unscheduled question remains visible. Review missing owners too.
When work depends on that answer, record the dependency using the waiting-on-client workflow. Continue independent work whose requirements are already settled.
6. Record the answer before closing
- Confirm the answer resolves the specific conflict.
- Record who provided it, the source and the version it applies to.
- State the chosen direction in plain language.
- Link the decision back to both feedback records.
- Update the next production action.
- Mark the clarification Resolved and clear obsolete reminders.
“Please discuss internally” is a response, but it is not yet a production direction. Keep the issue open if the required decision remains outstanding.
7. Review changes to agreed work separately
A clear answer can still introduce extra work. Resolve what the client wants, then assess its effect on scope, timing and effort.
Use the scope-change tracker when the direction changes the agreed deliverable. Clarification and authorization of extra work are separate decisions.
Common mistakes
- Erasing earlier comments to make the register look consistent.
- Treating the latest response as approval without checking authority.
- Closing the issue after a reply that does not resolve the conflict.
- Rebuilding work around an unconfirmed interpretation.
Frequently asked questions
Should I merge contradictory comments into one instruction?
Preserve the original comments and create a separate clarification question. Record the agreed direction after it is resolved.
Who should resolve the disagreement?
Use the authorized decision-maker identified by your client’s agreed process. The person tracking the issue does not automatically hold that authority.
What if the reviewers saw different versions?
Identify the versions first and obtain feedback on the intended reference before treating the comments as a direct conflict.
Can independent work continue?
Yes, when it does not depend on an assumption about the unresolved direction.
Does a resolved clarification authorize extra work?
Not automatically. Assess any change to scope, timing or effort through the separate approval process.
Explore the wider workflow
This process can sit alongside your existing projects. For a broader client and project workspace, explore Freelancer CRM and compare its structure with how you work.