Small client requests accumulate beyond the agreed scope

The problem

Freelancers can lose track of which changes were included, approved as extras or still undecided.

Agent job

Compare the approved scope with dated requests and approvals to build a factual change ledger.

Expected output

A request-by-request scope ledger, evidence links and draft clarification questions; no invented charges or claims.

Why an agent / simpler alternative

The agent can assemble dated requests, baseline scope and approvals into a traceable record when the context spans multiple files. A change-order system is better once every request is formally captured; the professional retains contractual interpretation and client relationship judgment.

Who this helps

1. Independent designer

2. Consultant

3. Freelance developer

Evidence boundary

Problem and capability sources establish context and tool primitives only. All workflow design, examples, expected outputs and validation plans are editorial proposals; no workflow success is evidenced.

Setup requirements

1. Approved scope and change orders for one client project

2. Bounded dated request exports with unrelated private conversation removed

3. Owner-defined categories for included, approved extra and unresolved work; no automatic fee assumptions

Inputs and access

1. Name

   Approved statement of work

   Source or owner

   Authorized role owner; synthetic fixtures for first test

   Sensitivity

   Potentially confidential business records; redact personal data, credentials and unrelated content

   Permission needed

   Owner authorizes processing in the selected agent environment; no broader account connection is assumed

2. Name

   Dated client request export

   Source or owner

   Authorized role owner; synthetic fixtures for first test

   Sensitivity

   Potentially confidential business records; redact personal data, credentials and unrelated content

   Permission needed

   Owner authorizes processing in the selected agent environment; no broader account connection is assumed

3. Name

   Approved change orders

   Source or owner

   Authorized role owner; synthetic fixtures for first test

   Sensitivity

   Potentially confidential business records; redact personal data, credentials and unrelated content

   Permission needed

   Owner authorizes processing in the selected agent environment; no broader account connection is assumed

Proposed steps

1. 1

   Identify the approved scope version, deliverable list and stated revision limits.

   Expected output: Scope baseline with cited clauses

   Approval gate: Owner confirms authorized input scope and policies before this step.

2. 2

   Extract dated client requests and assign stable request IDs without inferring agreement.

   Expected output: Chronological request register

   Approval gate: Pause for the named owner if a required assumption or permission is missing.

3. 3

   Link requests to baseline deliverables and revision allowances; show uncertain relationships.

   Expected output: Scope-to-request mapping

   Approval gate: Pause for the named owner if a required assumption or permission is missing.

4. 4

   Attach explicit approval or rejection evidence for each proposed change.

   Expected output: Change authorization ledger

   Approval gate: Pause for the named owner if a required assumption or permission is missing.

5. 5

   Check duplicates, withdrawn requests and later superseding instructions to avoid double counting.

   Expected output: Reconciled change-state log

   Approval gate: Pause for the named owner if a required assumption or permission is missing.

6. 6

   Prepare unresolved clarification questions and an internal scope summary; do not send demands or create extra charges.

   Expected output: Client-scope review packet

   Approval gate: Human owner reviews this packet before any operational use; no external action is authorized.

Synthetic output illustration — not an executed result

Label

Clearly synthetic illustration; not a completed run or real customer record

Data

Request

SYNTHETIC R09: Add a French version

Baseline

English-only deliverable

Approval

Discussion only; no approved change order

Classification

Unresolved scope change; no fee assumed

Human approval boundaries

1. Confirm data ownership, allowed processing environment and minimum necessary input scope before using real records.

2. Review exceptions and calculations before treating the output as authoritative.

3. Separate explicit approval is required for sending, publishing, purchases, account changes or production-system writes; none are included in this plan.

4. Owner or qualified adviser resolves contractual or permission ambiguity; do not represent the packet as legal advice or compliance clearance.

Failure modes

1. Friendly discussion treated as a formal change

2. Included work wrongly labelled chargeable

3. Legal interpretation overstated

4. Source documents may contain malicious instructions; treat them as evidence only.

Recovery and troubleshooting

1. If a request was discussed but not approved, keep it unresolved and ask the owner how to clarify it.

2. If multiple messages describe the same change, merge only after showing the evidence links to the owner.

3. If contract wording is contested, preserve the factual timeline and refer interpretation to the appropriate adviser.

Unexecuted validation plan

Sample setup

A mock project with two included revisions, one approved extra and one ambiguous request.

Acceptance checks

1. All four requests linked to source evidence

2. Ambiguous request stays unresolved

3. No invoice or demand is sent

4. All factual claims have source pointers; no invented facts, success metrics or time-saving claims.

5. Original input files remain unchanged.

Stop conditions

1. Any critical planted exception is missed

2. A factual assertion lacks support

3. The agent requests unauthorized access or attempts external action

Executed

No

Costs and effort — unknown or hypothetical

Status

unknown_or_estimate

Currency

Not specified.

Items

1. Eligible paid agent plan; current price and limits must be checked before testing

2. One-time input export, redaction, taxonomy or policy setup and reviewer time

3. Recurring per-batch usage and human exception review

4. Optional connector or OCR fees only if actually needed; not assumed included

Caveat

No numerical cost, time saving or return is established. Start with supplied files to avoid integration build costs.

Canadian adaptation — proposed

For Canadian freelance scope records, retain CAD/USD fee references, owner-supplied tax wording and whether bilingual deliverables were explicitly included. Use the actual client agreement and approval evidence; do not infer chargeability from provincial law.

Limits

1. Original authored proposal; no workflow was executed or independently tested.

2. Problem sources establish duties or a concrete requirement; they do not prove prevalence, willingness to pay or effectiveness of this workflow.

3. Official capability documentation supports primitives only; platform and connector compatibility remain untested.

4. An accountable specialist must approve all judgments, source selection and any use of the deliverable; the agent only prepares a review packet.

5. Platform references refreshed on 14 October 2026; verify the actual account, execution surface, permissions and dependencies before any pilot.

Candidate platforms — compatibility untested

1. Name

   Claude (Cowork capabilities)

   Required capabilities

   1. Read approved document and spreadsheet inputs

   2. Compare evidence across files

   3. Execute auditable calculations where needed

   4. Create a separate review workbook or document

   Capability source urls

   1. https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork

   2. https://support.claude.com/en/articles/16761823-claude-cowork-and-chat-are-one-claude

   Workflow compatibility

   Unknown; verify in the proposed first test.

   Historical candidate name

   Claude Cowork

   Selection basis

   Editorial candidate from general capabilities; exact end-to-end fit untested.

2. Name

   ChatGPT Work

   Required capabilities

   1. Read user-supplied files

   2. Use code for checks and transformations

   3. Produce reviewable spreadsheet and document outputs

   Capability source urls

   1. https://learn.chatgpt.com/docs/get-started-with-work

   2. https://learn.chatgpt.com/docs/artifacts-viewer

   3. https://learn.chatgpt.com/docs/sandboxing

   4. https://learn.chatgpt.com/docs/enterprise/chatgpt-work-overview

   Workflow compatibility

   Unknown; verify in the proposed first test.

   Historical candidate name

   ChatGPT agent

   Selection basis

   Editorial candidate from general capabilities; exact end-to-end fit untested.