Useful things / Decision sheet
Keep a private office moving without forwarding everything.
Plan private-office handoffs, approvals and AI-assisted briefs without forwarding confidential information to everyone.
A decision you can take with you
Hand over the responsibility.
What is moving between people?
Send a decision note.
State the decision required, relevant facts, options, deadline and authorised decision maker. Exclude unrelated history.
Send the next action and completion condition.
Name the owner, input, due date, dependency and what counts as done. Give access only to the material needed.
Create a continuity record.
List recurring obligations, approved contacts, access owners, open decisions and where the current records live.
Your next steps
0 / 6 completeYour answers stay in this tab. Download them before leaving. Use the sheet to plan the checks and conversations that follow.
Read the practical guide Examples, context and things to check
Start with a visible next action, a named coordinator and an explicit approver. Keep the sensitive material in its appropriate system. Most handoff problems do not require everyone to see everything.
The deputy needs a decision, not your entire inbox.
Our owner workspaces separate a routine action from an exception that needs approval. The useful record is small: what changed, when it was checked, what someone proposes and the limit of their authority.
For example, a coordinator may move an existing appointment within its agreed terms. A change to price, access or a commitment waits for the named approver. If that person cannot reply, the current arrangement remains in place and the deputy is told what to do next. Try the operating handover with one decision from your own week.
Separate coordination from authority.
A principal may approve spending, an assistant may arrange the work, and a specialist may need to review a document. Those are three different permissions. Copying all three into every email is a distribution habit, not an access model.
- Coordinator
- Keeps the request moving, confirms what is missing and sees the next action.
- Approver
- Makes a defined decision within an agreed limit. Absence does not imply approval.
- Contributor
- Provides the necessary work or advice and sees only what is relevant to it.
One person may hold more than one role. Write that down rather than letting the software guess. Give a temporary delegate an end date and name the person who removes that access.
The assistant knows. That does not mean every system should.
Use a small request record.
A useful record can travel without carrying the entire conversation. For example, a room booking might need a date, an approximate group size, a coordinator, a decision deadline and a link to the restricted brief. It rarely needs a family contact list in the subject line.
| Field | Purpose | Example |
|---|---|---|
| Reference | Find the request without naming private people. | Event 24 |
| Next action | State one observable step. | Confirm access to the room. |
| Owner | Identify who acts next. | Office coordinator |
| Approver | Identify who may authorize the decision. | Named principal or delegate |
| Due and time zone | Make the deadline unambiguous. | Thursday, 14:00 Vancouver time |
| Status | Distinguish waiting from completion. | Waiting for venue confirmation |
| Restricted link | Keep documents in the right system. | Access-controlled brief |
Acknowledge receipt separately from acceptance. “Received” means that a request arrived. “Approved” should name the decision, person and time. “Booked” should require actual confirmation from the system or person responsible for the booking.
Design the awkward Tuesday.
The normal route is the easy part. Try the process with an absent approver, a supplier cancellation, a changed budget, a duplicate request and a deadline that moves across time zones.
- Absent approver: route to an already authorized delegate or keep the item waiting. Do not quietly widen access.
- Changed scope: show what changed and request a new decision where needed. An old approval should not cover a different purchase.
- Duplicate request: preserve one reference and link the duplicate instead of booking twice.
- Failed connection: show that the action has not been confirmed. Assign someone to reconcile it before trying again.
- Person leaving: reassign open work, revoke access and verify that the remaining team can recover the records.
The group chat is excellent at choosing lunch. Give final approvals a more permanent address.
Use AI to prepare a decision.
Start with one repeated task: turning an approved brief into a draft status note. Keep the original record beside the draft so a reviewer can check it. In a private office, a useful note might contain the requested decision, the options, the cost, the deadline and what is still unknown. A law office may use the same shape for an administrative handoff without putting client matter details into an unapproved tool.
- Facts: link each figure or commitment to its current source. A fluent summary is not evidence.
- Open questions: keep missing dates, uncertain costs and conflicting instructions visible.
- Authority: record who must approve spending, access or publication. A suggested next step remains a suggestion.
Try ten ordinary notes with the person who handles them today. Count corrections, time spent checking and any detail they still had to find elsewhere. Keep the existing approval route until the new process earns its place. BDC's guide to administrative AI describes drafting and document tasks with human review.
Run five ordinary requests first.
Use your existing task system or a restricted worksheet. Record how often someone must ask “Who has this?” or forward the same details again. Try one deliberately awkward request. If the confusion remains, clarify the roles before automating the process.
A small custom tool may help when the same missing ability causes repeated work: different views for coordinators and approvers, a clear waiting state, or a reliable handoff between existing systems. The scope should also include recovery, access removal, ownership and support. Software cannot settle an authority question nobody has answered.
Use these examples to plan operations. Your own legal, privacy and professional requirements still determine what information may be collected, retained and shared.