An approval that survives the next handoff

Agree the boundaries before work begins

Record the intended result and the actions already authorized. Ordinary, reversible work can proceed within that scope. If the owner has explicitly requested publication of a particular result, that request is part of the authority already given. Asking for the same permission again adds little clarity.

Identify separate boundaries for spending, access, production changes and user data. An architect can investigate a question and prepare options. A handoff alone does not give that role the owner's authority, and an elapsed timer cannot supply the owner's answer.

Bring a concrete result to the decision

Complete the preparation that is already authorized before asking. Show the proposed change, relevant checks and material limitations. The owner should be able to tell exactly what will happen after approval, to which object and in which environment.

1. Name the action and its target, such as publishing the reviewed change to a staging site.
2. Link to the result and evidence for the specific revision you propose to apply.
3. Explain the consequences and offer a clear choice: perform that step or return the result for changes.

“May I continue?” leaves the decision undefined. “Publish the reviewed change to staging; keep production unchanged” establishes a boundary someone can check later.

Preserve the scope through changes

Approval applies to the described action and its boundaries. If the revision, destination, cost or data changes, compare the new proposal with that record. A material expansion needs another decision; correcting a typo in the explanation should not erase valid approval.

While waiting, preserve the prepared result and context. Continue independent, authorized work where possible. Keep the important question accessible after a brief visual cue disappears. Repeating the same notification on every screen refresh does not make the decision easier.

Verify execution after the answer

Before execution, check that the question remains current and its revision and target still match. Then record what was applied, where it can be inspected and what remains incomplete. If the attempt fails, preserve what already happened and explain the next concrete step. Approval does not turn a failed attempt into completed work.

A familiar tracker or text file can hold this record. Start with one important decision and check whether another person can reconstruct it without retelling the entire conversation.