Systems and records
Creative client feedback disagreement: who decides between reviewers
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
When two client reviewers ask for opposite changes, the person with decision authority settles it, and the record should show where that authority came from. Log both requests against the same version, find the named approver in the brief or proofing workflow, put one written question to that person, then record the answer, the new version and its sign-off. That chain is what makes revision history useful data.
License terms
Creative client feedback
Key takeaways
- Opposite reviewer requests are settled by whoever the brief or workflow names as decision maker, not by the last comment.
- Both requests must cite the same asset version, or the case is a sequence of edits rather than a conflict.
- Proofing tools record roles and decisions but rarely record why a conflicting note was overruled.
- The conflict type tells you where authority sits: legal and rights conflicts are not creative calls.
- A final approval is necessary for delivery but does not clear rights the client or agency never had.
- Access to a proofing system is not a right to license what is inside it.
Who settles it when two client reviewers ask for opposite changes?
The person with decision authority settles it, and the record should show where that authority came from. In practice that is the reviewer named as final approver in the brief or statement of work, or the decision maker configured in the proofing workflow. If nobody was named, the conflict goes back to the client's project owner as a single written question. The studio should never quietly pick a side or blend both notes into a compromise nobody asked for.
The practical sequence is short. Log both requests against the same asset version, so nobody argues later about which draft they saw. Classify the conflict. Find the authority source. Send one question to the decision maker that quotes both requests. Record the answer, the version it produced and who signed off on that version.
For anyone building training data from creative operations, that sequence is the valuable part. A revision history without the authority trail teaches a model that the last comment wins, which is how studios end up redoing work for the wrong stakeholder.
The same discipline helps the studio before any data question comes up. Teams that log conflicts this way spend less time relitigating old rounds, because the record shows who asked for what, on which version, and who chose.
What proofing and approval tools record about authority
Proofing tools capture more of the authority structure than most teams realize, but none of them captures why a conflicting note was overruled. Adobe Workfront's documentation, as read on October 18, 2026, is a useful reference because it spells out the mechanics.
In Workfront, a proof role decides what each person can do on that proof: a Reviewer can add markups and comments but cannot approve or reject. Decisions include Approved, Approved with changes, Changes required and Not relevant, and administrators can rename, reorder or hide decisions and require a reason. A stage can name a primary decision maker whose decision makes the other decisions on that stage unnecessary, and stages can be made private so an agency's internal review is not visible to the client. When several people decide on one proof, Workfront Proof shows the overall status as the most restrictive decision; its example is two accepted decisions and one rejected, which displays as rejected.
Asana's help center, read the same day, describes a looser approach. An approval task ends as Approved, Changes requested or Rejected, and the help center notes that anyone can complete an approval unless the project is set to comment-only. Email threads and meeting notes, where many creative decisions actually happen, record no authority at all unless someone writes it down.
When you extract cases, pull the full decision history for each proof rather than the current status, and keep the workflow configuration that was live at the time: which stages existed, who held which role and whether a primary decision maker was set. A configuration exported a year later may describe a different team. If the configuration is gone, the brief or statement of work becomes the only authority source, and the case should say so.
| Where the decision lives | What it records | Authority signal | What the annotator must add |
|---|---|---|---|
| Workfront proof with stages | Markups, comments, decisions per reviewer and stage, decision reasons if configured | Proof role, primary decision maker per stage | Why a conflicting comment was not followed |
| Workfront Proof overall status | One status derived from all decisions | Most restrictive decision wins the display | Whether the restrictive decision came from someone with authority |
| Asana approval task | Approved, Changes requested or Rejected, plus comments | Weak unless the project is comment-only | Who was entitled to approve under the brief |
| Email and meeting notes | Free-text requests and replies | None by default | The authority source and the asset version referred to |
| Brief or statement of work | Scope, deliverables, named approver | Strongest written source | Version of the brief in force when the conflict arose |
The authority and revision resolution annotation guide
The guide is the asset: one row per field an annotator fills for each conflict, with allowed values, required evidence and the rule that decides the label. A conflict is two or more requests on the same asset version that cannot all be carried out.
Keep identities out. Reviewers are labeled by role (brand lead, legal reviewer, regional marketing, executive sponsor), never by name, and client names are replaced with a stable pseudonym.
Run two checks before a case enters a dataset. First, have a second annotator label a sample of cases independently and compare the conflict type and authority source fields; disagreement there usually means the allowed values need sharper definitions, not that the annotators are careless. Second, confirm that every resolution label points to a written answer from the decision maker. A resolution inferred from what the next version happened to contain is a guess, and it should be labeled as unknown rather than adopted.
| Field | Allowed values | Evidence required | Labeling rule |
|---|---|---|---|
| Conflict ID and asset version | Stable ID, asset type, version number | Proof or file version history | Both requests must cite the same version or the case is not a conflict |
| Requests in conflict | Request A and request B, quoted, with reviewer role and time | Comments, markups or emails | Quote the request; do not paraphrase intent |
| Conflict type | Contradiction, brand or guideline, legal or claims, scope, regional adaptation, rights-limited | The requests plus the brief | One primary type; add a secondary only if it changes who decides |
| Authority source | Brief named approver, statement of work, workflow decision maker, client escalation, none found | Brief version, workflow configuration, escalation email | None found means the case cannot be graded on outcome |
| Resolution | Request A adopted, request B adopted, merged by decision maker, both withdrawn, escalated without answer | Written answer from the decision maker | Merged only when the decision maker chose the merge |
| Resulting version and sign-off | New version number, approval decision, approver role, date | Proof decision history | The approval must be on the version that implements the resolution |
| Rights status at delivery | Cleared, cleared with restriction, blocked, unknown | License, release or contract terms for each third-party element | Unknown blocks reuse labels; it does not block the case |
| Outcome | Delivered as approved, revised again, cancelled, unknown | Delivery record or later version | Outcome comes from a record after sign-off, not from the proof status |
Five kinds of reviewer conflict and the evidence each needs
Not every disagreement is decided the same way, so the conflict type is worth labeling carefully. The type tells a model where to look for authority before it looks at the content of the notes.
When a conflict fits two types, choose the one that changes who decides. A contradiction about the size of a legally required statement is a legal conflict first, because the regulatory reviewer outranks taste on that element, even if the notes read like a layout preference.
- Plain contradiction: one reviewer wants the headline larger, another wants it smaller. Evidence needed: the named approver or workflow decision maker. Without one, the case is escalated, not resolved.
- Brand or guideline conflict: a stakeholder asks for a color or type treatment outside the brand guide. Evidence needed: the guideline version in force. The brand owner usually decides, and the record should cite the guideline section.
- Legal or claims conflict: marketing wants a stronger product claim, the client's legal reviewer strikes it. Evidence needed: the legal reviewer's written decision. The creative team does not arbitrate; it records the legal decision as final for that version.
- Scope conflict: one reviewer adds a deliverable the brief does not include. Evidence needed: the statement of work. The resolution is often a change request rather than a revision, and it should be labeled that way.
- Rights-limited conflict: a reviewer asks to swap in an image, font or music track whose license does not cover the territory or medium. Evidence needed: the license terms. The decision maker can choose, but only among options the rights allow.
Approval, element rights and ownership: three separate gates on reuse
Three things change what may be delivered or reused: the final approval on a specific version, the rights attached to each element in that version, and the agreement that says who owns the finished work. They are separate questions, and a dataset should keep them in separate fields.
Approval is version-specific. Workfront lets a reviewer change or remove a decision while the proof is active, which means an approval read from a live system today may not be the approval that existed at delivery. Capture the decision history, not just the current state.
Ownership of the finished work depends on the contract. The U.S. Copyright Office explains in Circular 30 that a specially commissioned work is a work made for hire only if it falls into one of nine statutory categories and the parties expressly agree in a written instrument signed by both that it is a work made for hire. If any requirement is missing, it is not a work made for hire, and ownership then turns on what the contract assigns. A studio's revision files may therefore include work it owns, work the client owns and third-party elements under license.
None of that is the same as permission to use the records for AI. Comments and approvals can contain client confidential information, and the client agreement may limit how project files are used. Being able to open the proofing system is access, not a right to license what is inside it; counsel reviews the client contracts before any of it leaves the studio.
Worked example: a packaging label with two contradictory notes (illustrative)
This example is invented to show the guide in use. The client, roles and counts are illustrative, not drawn from real records.
The labels below preserve one point worth noticing: the regional lead was not wrong to ask; the request simply lost to a higher authority on a regulated element. A model trained on the case learns to route required label text to the regulatory reviewer, not that regional marketing requests are bad.
- Starting state: version 4 of a food packaging label is in a two-stage proof. Stage 1 is the agency's private internal review; stage 2 is the client, with the brand director set as primary decision maker.
- Request A, from the client's regional marketing lead: move the allergen statement below the nutrition panel to free space for a promotional burst.
- Request B, from the client's regulatory reviewer: keep the allergen statement where it is and enlarge it.
- Conflict type: legal or claims, with a secondary scope note because the promotional burst was not in the brief.
- Authority source: the brief names the brand director as final approver, and the regulatory reviewer's sign-off is listed as a prerequisite for anything touching required label text.
- Resolution: the agency sends one message quoting both requests. The brand director adopts request B and drops the promotional burst. The regulatory reviewer confirms in writing.
- Resulting version: version 5 implements request B. The brand director approves version 5; the regional lead's earlier changes-required decision on version 4 stays in the history.
- Rights status: cleared; all artwork elements were created by the agency under the client agreement.
- Outcome: version 5 goes to print, confirmed by the printer's proof approval record dated after sign-off. Labeled outcome: delivered as approved.
The exception: an authorized approval that rights cannot support
Sometimes the person with authority approves something the rights do not allow. The annotation should record both facts rather than let one overwrite the other.
Illustrative case: on a retail campaign, the executive sponsor, who is the stage decision maker, approves a version that uses a stock photo licensed for one country only, while the campaign runs in three. The approval is valid as an approval. The rights status is blocked for two territories. The correct labels are resolution adopted, sign-off present, rights status cleared with restriction, and outcome revised again, because the agency had to replace the image before delivery.
This is the case a model most needs to see. It shows that authority over creative choices does not extend to rights the client or agency never had, and that a final approval is a necessary condition for delivery but not a sufficient one.
In practice this means the rights status field is filled from license and release documents, never from the approval record. An annotator who sees an approval and assumes clearance has merged two decisions that different people own.
Conflicts an annotator should flag rather than resolve
Some conflicts are outside what an annotation guide should decide. Mark them and route them to the right reviewer instead of forcing a label.
- Product claims, required label statements, disclosures and regulated wording: the client's legal or regulatory reviewer decides; the annotator records that decision and nothing more.
- Disputes about who owns the finished work or a third-party element: a rights reviewer or counsel decides, using the contracts.
- Comments that name or describe individuals, such as talent, customers or employees: remove or generalize them, and leave the case out if the request cannot be understood without them.
- Cases where the authority source cannot be found: keep the requests and versions, label the authority source as none found and leave the case out of outcome grading.
- Client confidential strategy, unreleased products and pricing discussions in comment threads: remove them, or exclude the project if removal would gut the record.
Licensing creative revision and approval histories
Creative revision histories with a clear authority trail are rare, and they teach something preference data alone does not: how a decision gets made when the people giving feedback disagree. Agencies, studios and in-house creative teams that can assemble them with the fields above hold unusual material for AI developers.
An agency that wants to offer such histories can do it through SourceX, which locates and qualifies the records, checks the rights, writes the contract, prepares and delivers the files and pays the agency. Buyers generally prefer a couple of years or more of consistent records and volume in the tens of thousands within one system, though specialist work can qualify with less, and each dataset is reviewed separately.
Proof histories stay with the agency until it has accepted the scope and terms in a signed agreement, and the opening step is a brief assessment of the studio that involves no file upload.
Frequently asked questions
How do you handle conflicting feedback from two client reviewers?
Log both requests against the same version, check who the brief or workflow names as decision maker, and send that person one written question quoting both requests. Implement their answer in a new version and record who approved it.
Who has final say on creative revisions?
Whoever the brief, statement of work or proofing workflow names as final approver. If nobody is named, the client's project owner decides, and the team should ask for that in writing rather than infer it from seniority.
Should a designer merge two opposite requests into a compromise?
Only if the decision maker chooses the merge. A compromise nobody requested satisfies neither reviewer and leaves no record of who decided, which makes the next round of changes harder.
What does approved with changes mean in a proofing workflow?
In Adobe Workfront it means the proof needs some changes but the reviewer does not need to see the revision before it moves to the next stage. Changes required means the reviewer wants to see another version first.
Does approving a creative asset clear the rights to use it?
No. Approval is a creative and business decision on a version; rights depend on the licenses for each element and the agreement on ownership of the finished work. An approved asset can still be blocked for a territory or medium.
Can an agency use client revision histories to train AI?
Only if its agreements allow it. Revision files mix agency-owned work, client-owned work, licensed elements and confidential comments, so counsel reviews the client contracts before any of it is licensed or reused.
Sources
- Adobe Workfront lists the proof decisions Approved, Approved with changes, Changes required and Not relevant, and explains what each means for the next workflow stage. Source
- Workfront proof roles set what each person can do on a proof; a Reviewer can add markups and comments but cannot approve or deny. Source
- A Workfront automated workflow stage can name a primary decision maker whose decision makes the stage's other decisions unnecessary. Source
- Workfront proof stages can be made private, for example so an agency's internal comments are not visible to the client. Source
- Workfront Proof derives a proof's status from the most restrictive decision, so one rejection over two acceptances shows as rejected. Source
- Workfront Proof administrators can rename, reorder and hide decisions and can require reviewers to choose a decision reason. Source
- In Workfront, a reviewer can change or remove a decision while the proof is active. Source
- Asana approval tasks end as Approved, Changes requested or Rejected, and anyone can complete an approval unless the project is comment-only. Source
- The U.S. Copyright Office explains that a commissioned work is a work made for hire only if it is in a statutory category and the parties agree so in a written instrument both sign. Source
See if your company qualifies
A short company assessment. No data uploads are needed.