Reset authority before production
A stakeholder change often creates a decision problem before it creates a production problem. Confirm who can approve the combined response before estimating competing sets of edits.
Example: an executive changes positioning
If the delivered copy matches the approved brief but a new executive changes the audience, record the new audience as a brief change. If the copy omitted a required product fact, treat that omission under the existing correction obligations.
Copy-and-customize preview
Free editable sample
No purchase or email required.
STAKEHOLDER RESET — [Project] Previously approved version / date: [reference] Original approver: [name] New stakeholder and authority: [name / role] Requested departure from approved brief: [difference] Corrections within existing acceptance criteria: [items] Preference changes or new requirements: [items] Single consolidated feedback owner: [name] Rework estimate and revised milestone: [fee / date] Decision required: approve rework, preserve approval, or defer change Written approval record: [name / date / version]
| Field | Why it matters | Example |
|---|---|---|
| Prior approval | Preserves the decision history. | Homepage v3 approved by the marketing lead. |
| Classification | Avoids charging twice for an owed correction. | New positioning is a brief change; broken navigation is a correction. |
| Feedback authority | Prevents competing instructions. | One owner consolidates executive and marketing comments. |
Use it in four steps
- Locate the approved version and criteria
- Classify corrections separately from preference changes
- Name one authorized feedback owner
- Approve the rework estimate and replace the decision baseline
Customization checklist
- Do not assume the new stakeholder has contractual authority
- Record which decisions remain approved
- Keep superseded feedback for the project record
Common mistakes to avoid
- Accepting contradictory directions from several people
- Discarding the old approval record
- Billing all feedback as new work without checking the brief
Frequently asked questions
- Does a new stakeholder automatically mean an extra fee?
- No. Estimate only the work that changes the agreed requirements or exceeds included review. Correct nonconforming work under the existing agreement.
- Can I keep the old delivery date?
- Only if the rework and approval schedule make it achievable. Otherwise present the revised milestone before work resumes.
Continue with the next decision
New Stakeholder Feedback After Approval: Client Script
Treat late stakeholder direction as a change decision: preserve the approved version, estimate the rework, and reset approval before proceeding.
Free editable artifactFreelance Change Order Form Template
A freelance change-order form records the original agreement, requested difference, added and removed work, price adjustment, revised milestones, dependencies, and authorized approval. Give each change an identifier so the client can approve a specific version.
Publisher comparisonRevision vs Scope Change: How to Tell the Difference
A revision refines an included deliverable against the approved brief. A scope change alters the brief, quantity, direction, format, audience, or other agreed requirements. Corrections needed to meet existing acceptance criteria should not automatically be treated as new billable scope.