Your copy. Your pace.

Engagement scope change control

Use a staff request for work outside an existing engagement to create an approved change record linked to a revised engagement. The design keeps source references, uncertain matches, and approval decisions visible to the responsible accountant. It coordinates an administrative handoff with version checks and an exception queue. New work must not begin solely because an AI summary labels it in scope.

Planning workbook. This file helps you document a process. It does not connect to accounts, read records, send messages, or complete external actions. It works offline and sends no entries anywhere. Entries are not saved automatically; export or print a copy before closing. Avoid entering sensitive information.

1. Define the starting point

Start with a staff request for work outside an existing engagement. A successful handoff produces an approved change record linked to a revised engagement. Define the accountable owner before connecting systems. New work must not begin solely because an AI summary labels it in scope. A source event is a request to evaluate the current state; it is not permission to make an irreversible change.

Process owner and backup rolesWhat will count as complete?

Current handling time and exceptions

2. Walk through the process

1. Capture the request

Record the requested deliverable, client engagement ID, requester, and supporting reference.

We have defined the owner, required information, and completion check for this step.Step 1 working notes

2. Compare the signed scope

Show the relevant existing engagement sections and flag uncertain boundaries for professional review.

We have defined the owner, required information, and completion check for this step.Step 2 working notes

3. Prepare a change proposal

Draft the additional work, exclusions, fee basis, and schedule using an approved template.

We have defined the owner, required information, and completion check for this step.Step 3 working notes

4. Approve and obtain agreement

An authorized professional checks the change and records required client agreement.

We have defined the owner, required information, and completion check for this step.Step 4 working notes

5. Update delivery instructions

Release revised tasks only after the approved scope version is linked to the engagement.

We have defined the owner, required information, and completion check for this step.Step 5 working notes

3. Check the information

Use invented references in this worksheet. Keep real documents and personal records in an appropriate private system.

Reference field	Working record	Check
engagement_id	engagement_id	Resolve the stable source reference in the correct client, entity, and engagement.
scope_version	scope_version	Bind approval to this exact source version; changes require review.
change_request_id	change_request_id	Resolve the stable source reference in the correct client, entity, and engagement.
client_agreement_ref	client_agreement_ref	Resolve the stable source reference in the correct client, entity, and engagement.

Source of truth and access boundaries

4. Verify the process

Use synthetic examples. Mark a check only after recording what actually happened.

Unsigned changes remain pending.A superseded engagement version cannot authorize new tasks.A repeated source event creates only one current review task.A changed source version invalidates an earlier approval.A named person can resolve an unclear or incorrect result.Work stops when the task is complete, withdrawn, or outside the agreed scope.A duplicate or interrupted handoff can be recovered without repeating a consequential action.Expected result, observed result, and recovery notes

5. Decide the next step

Your smallest reversible pilotReview date and decision

Retain qualified professional review for legal, accounting, tax, medical, financial, or other consequential decisions. This workbook does not certify compliance or guarantee results.