Intake field
Current scope
What written task, volume, tool, approval boundary, and service rule apply now?
Active provider change
Pause a changed provider task long enough to check the boundary.
Use this brief when an active provider takes on a new task, volume, data type, tool, action, or customer effect. Record the written request, the owner decision, and the first safe test before the new work becomes routine.
This is a coordination record, not legal, contract, privacy, security, financial-control, or regulatory advice. It does not grant access, amend terms, approve a charge, or authorize a customer commitment. The provider's written terms and authorized business owners control.
Ten fields
Write down what changed before someone acts on it.
Keep one requested change in each record. If a price, service, staffing, or access effect is not in a written source, mark it for clarification.
Intake field
Requested change
What new task, volume, data, tool, action, or customer effect is being requested?
Intake field
Reason and source
Why is it needed, and which dated request, task, report, or written provider note supports it?
Intake field
Access impact
Does the request need a new account, permission, data category, or action? Record the least access needed or mark it for review.
Intake field
Quality check
What one low-risk sample, source record, reviewer, and finished-result check would test the changed work?
Intake field
Commercial effect
What price, staffing, coverage, service, or contract effect has the provider confirmed in writing? Mark it clarify when no written answer exists.
Intake field
Business owner
Which authorized business owner can approve, decline, or return the request?
Intake field
Status
Is the request draft, under review, approved in writing, declined, or on hold?
Intake field
Effective date
When may the changed work begin after written approval and any required access or commercial review?
Intake field
Review date
When will the owner inspect the first sample or reconsider the changed boundary?
Fictional examples
Two small changes that need different owner checks.
Every company, person, date, and work example below is fictional. These are examples, not benchmarks or contract terms. On smaller screens, scroll the table horizontally to see all ten fields.
| Current scope | Requested change | Reason and source | Access impact | Quality check | Commercial effect | Business owner | Status | Effective date | Review date |
|---|---|---|---|---|---|---|---|---|---|
| Fictional provider labels order-status tickets and prepares reply drafts during the agreed weekday window | Provider also prepares a weekly order-delay trend report from the helpdesk export | Fictional support-manager request, 2026-08-14; weekly queue review notes | Read-only export access proposed; no permission to change ticket fields or send customer messages | Buyer checks one report against the saved export and the approved metric list before it repeats | Provider written answer pending; do not assume the report is included in the current fee | Buyer support manager | Under review; provider clarification open | Not set until written scope and commercial review are complete | First approved sample, then 2026-09-14 |
| Fictional provider prepares a weekly CRM cleanup batch from approved duplicate rules | Provider flags possible duplicate records and prepares a merge recommendation with source links | Fictional CRM-owner request, 2026-08-14; duplicate-review queue | Existing read-only source access stays; merge action remains with the buyer CRM owner | Buyer reviews one five-record sample and confirms each source link before any routine recommendation work | No effect stated in writing; clarify staffing and service impact with the provider | Buyer CRM owner | Approved for one low-risk sample only | After the buyer assigns the sample and confirms the written task note | At sample review before any recurring batch is assigned |
Copy-ready brief
Start with the current written scope.
Use safe links or document references. Do not copy credentials, customer records, payment details, or full confidential terms into this brief.
PROVIDER SCOPE-CHANGE INTAKE BRIEF CHANGE CONTROL Provider: Service or work lane: Request reference and date: Business owner: Provider contact: Current written scope reference: CURRENT SCOPE REQUESTED CHANGE REASON AND SOURCE ACCESS IMPACT QUALITY CHECK COMMERCIAL EFFECT BUSINESS OWNER STATUS EFFECTIVE DATE REVIEW DATE [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] [Enter value] DECISION NOTES Written provider clarification needed: Authorized decision and date: Approved preparation only: Commercial, contract, privacy, security, finance, legal, or regulatory review needed: First sample owner and result: Instruction or SOP location to update: Next review owner and date: Use safe references to approved records. Do not paste credentials, customer records, payment details, or full confidential terms into this brief. Completing this brief does not approve a change, grant access, amend a contract, or authorize a customer commitment. The provider's written terms and authorized business owners control.
The full brief stays visible and selectable. Nothing is uploaded or saved.
Review steps
Make the changed task clear before it repeats.
A brief can show where the old instruction stops. It cannot replace a decision from the person who owns the risk.
- Start with the written current scope, not a memory of how the work has been handled.
- Describe one requested change and attach a safe reference to its source record.
- Check whether the request changes data, tools, access, authority, customer effect, volume, coverage, or price.
- Name the business owner and keep the final approval, contract review, access decision, and customer commitment with the right authorized person.
- Ask the provider for written clarification when the price, service, staffing, or effective-date effect is not stated.
- Test a low-risk sample after written approval, record the result, and update the instruction before the changed work repeats.
Stop and clarify
Do not treat scope drift as a small favor.
An extra request can change access, authority, customer impact, service terms, or the risk of the next action.
- The request says it is only a small extra task but adds a new data type, tool, permission, or customer effect.
- The provider or buyer assumes a fee, staffing, coverage, or contract effect without a written confirmation.
- The same person requests, approves, and reviews a change that affects a payment, permission, customer promise, or contract term.
- The task asks the provider to send, merge, delete, publish, approve, or change access when the written scope only allows preparation.
- The first test uses a live, urgent, high-value, or hard-to-reverse item.
- The changed instruction lives only in a private chat or a personal drive.
Next provider step
Keep the decision and the written record together.
If the change affects a written offer or agreement, update the assumptions record. If it changes a service promise, review the evidence, exception, owner, and escalation rule before the work expands.