Delegation & oversight

Handing a client project between people and AI in a shared workspace

A client workspace handover succeeds when the incoming lead can answer a customer, prepare the right deliverable and recognise which decision still needs approval. Try the following exercise with a fictional print job before transferring responsibility for a live account.

Man presenting data on a large screen to colleagues
Photo by Vitaly Gariev on Unsplash

Part of our guide to How to delegate work to AI agents: tasks, autonomy levels and review loops

On this page · 6 sections
  1. Give the incoming lead a job to finish on Monday
  2. Write a handover brief small enough to inspect
  3. Open the evidence from the incoming person's account
  4. Let a late customer reply change the handover
  5. Ask for an acceptance message that names the next action
  6. Frequently asked questions

Imagine a design studio producing wayfinding signs for a venue. Jo, the account lead, is leaving for a fortnight. Casey takes over on Monday. The printer needs an approved proof by Tuesday at noon Sydney time to hold a production slot. The venue manager has just requested a different entrance arrow. Someone needs to decide whether that change applies to all signs or only to the sign beside the accessible entrance.

Give the incoming lead a job to finish on Monday

Give the outgoing lead, incoming lead and assistant different responsibilities. Jo assembles the records that explain the job. The assistant drafts a note from those records and identifies conflicting instructions. Casey checks the draft, owns the next client conversation and records the customer's decision. The printer receives an instruction only after the studio's normal release approval. Use invented material so participants can make mistakes without affecting a customer.

Build five small pieces of evidence. Create an accepted estimate for twelve signs, an approved artwork proof labelled revision B, an email asking about the arrow and a printer booking with the deadline. Add a revision C drawing that a designer prepared while waiting for a reply. Give that drawing the most recent timestamp. Casey's job is to work out which artwork can presently be released and what would have to happen before that changes.

Write a handover brief small enough to inspect

Ask the assistant to prepare a one-page note with the job reference, customer commitment, current approved revision, pending request, decision owner and next contact time. Require a reference to the original item for each statement affecting money, scope or delivery. A link to a folder of fifty files gives the incoming lead another search task. A reference to the accepted estimate and its relevant line gives them something they can check during a call.

Sample instruction: “For job V12, prepare Casey's Monday handover from the five supplied items. Identify the proof the venue has approved and explain how you know. Quote the printer's deadline with its time zone. Draft one question for the customer about the entrance arrow. Leave sending, booking changes and release with Casey and the studio approver.”

Handover entryEvidence Casey opensDecision Casey can make
Twelve signs agreedAccepted estimate for job V12Check whether a new request changes quantity or scope
Revision B approvedCustomer acceptance referring to that drawingIdentify the last version cleared by the customer
Arrow change unresolvedCustomer message and draft revision CRequest confirmation of the affected sign
Printer deadline approachingBooking with date, time and supplier contactDecide when to escalate if approval is outstanding

Ask Jo to remove any line that merely repeats information without helping Casey make a decision. Then ask Casey which fact they would need first if the printer rang now. Move that fact to the top. A handover for a live production deadline may reasonably lead with the outstanding approval, even if the team's usual template starts with background about the client.

Open the evidence from the incoming person's account

Have Casey follow the links from their normal account while Jo stays silent. One useful variation is to make the proof readable from a shared project area and put the customer's approval in a folder owned by the outgoing worker. Casey may see a polished summary while being unable to check its most important claim. Record which source failed, who owns it and what access the recipient genuinely needs.

Move or share the relevant evidence using the team's approved process. Preserve the original dates and ownership information where they matter. Grant access to the project material Casey needs without opening an entire customer mailbox or every project the outgoing employee has touched. Give the assistant a separately defined set of sources. The colleague inheriting a commercial relationship may be entitled to read material unnecessary for preparing a routine print handover.

For organisations using Google Workspace, a shared drive can provide a team-owned home for project files. Google explains that material in a shared drive stays with the team when a member leaves. Choose the location based on who should hold the file and test access with the intended reader. Google's shared drive guidance.

Let a late customer reply change the handover

Once Casey accepts the first handover, introduce a sixth item. The venue manager confirms the arrow change applies only to the accessible entrance and asks whether Tuesday's slot is still available. Give Casey a second message from the printer saying they can hold the slot until noon if the final proof is approved. Neither message supplies approval of the revised artwork itself.

Ask Casey to update the project record and prepare two separate drafts. The customer draft should identify the affected sign and ask them to approve the revised proof. The printer draft should describe the actual state of approval and request confirmation of any changed timing. The studio approver can then decide which message is ready for dispatch. Someone reading the record later should see the difference between a requested amendment, approval of the artwork and the production booking.

Check that revision B remains traceable after the change. A colleague covering the desk needs to understand why C exists and whether B is still authorised for any part of the job. Ask the designer to label the superseded drawing when the new version is approved and preserve the reason for the change. Use the studio's normal versioning convention so the record makes sense to staff who missed the exercise.

Ask for an acceptance message that names the next action

Give Casey two minutes to write back to Jo in their own words. A useful receipt might read: “I have V12. I can open the accepted estimate and proof B. The venue wants the entrance sign changed. I will send the revised proof for approval once our reviewer checks it. I own the call to the printer before noon Tuesday if approval is still outstanding.” The reply reveals whether responsibility has moved as well as information.

Track three observations during the rehearsal. How long did it take Casey to identify the last approved proof? How many times did they need Jo to interpret a private note? Could they explain the outstanding action and its owner to the person answering the office phone? Use the answers to adjust the handover entry with the greatest practical consequence before applying the exercise to another client.

Fulcrum Sessions coordinates work between people and specialist assistants. A suitable first job is assembling the evidence note for Casey to review. Keep the customer decision and release authority with the people named in the project. Record corrections against the underlying files so the next person opening the workspace inherits the current facts.

Related guides: How to delegate work to AI agents: tasks, autonomy levels and review loops · How to write instructions for AI agents (with a definition of done) · The daily exception report: what your AI agents should tell you each morning.

Frequently asked questions

What belongs in the shared workspace if the client gives an instruction by phone?

Record who spoke, the date, the instruction as understood and any detail still awaiting confirmation. Link the note to the affected deliverable. Follow the team's normal process for obtaining written approval when a change alters scope, price or release.

How can a solo operator practise a handover?

Give a trusted colleague an invented project and one specific question to answer from its records. Observe where they need context only you remember. That missing detail is a good candidate for a short project note.

When should the outgoing lead consider the transfer complete?

Ask the incoming lead to open the evidence, identify the authorised version, name the pending decision and accept ownership of the next contact. If they cannot perform one of those steps, record the outstanding item and its owner before closing the transfer.

Sources

  1. Google's shared drive guidance

General information only, not legal, financial or professional advice. Check the source for your circumstances.