AI execution layer

Can you leave your AI workspace? Run an export and handover test

An AI workspace exit plan should prove that a colleague can continue one unfinished job outside the workspace. Downloading a ZIP file is a useful first step. The real test is finding the accepted version, its owner and the next commitment after the original operator signs out.

Open filing drawer containing organised document folders
Photo by Maksym Kaharlytskyi on Unsplash

Part of our guide to What is an AI execution layer? A plain-English guide for operators

On this page · 6 sections
  1. Pick a project with a history worth recovering
  2. Inventory the objects that carry a decision
  3. Run a timed recovery with a second colleague
  4. Identify the work that lives outside the export
  5. Turn a failed recovery into a purchasing condition
  6. Frequently asked questions

Use a completed or invented project that has all the awkward pieces: an initial brief, two revisions, a customer approval, an attachment and a follow-up due after delivery. Include one decision made in chat and one made in a document. Write the correct answers on paper before exporting. The person recovering the work should be able to identify the accepted version without the author telling them what happened.

Pick a project with a history worth recovering

Choose ordinary staff permissions for the recovery exercise. An administrator might be able to inspect everything in the original tenant, while the relief worker who has to deliver the follow-up cannot. Record whether each step depends on an administrator, an active paid seat, the original owner's sign-in or a supplier support request. These dependencies belong in the renewal discussion.

Pick a realistic reason for leaving. Moving a client account to a partner, changing a supplier and winding down a small business create different needs. A successor may need editable files and current obligations. An archive custodian may need stable records they can read years later. A customer may only be entitled to their own material. Do not bundle unrelated client files into a convenient test export.

Inventory the objects that carry a decision

Start with the question “what tells us that this version was accepted?” It may be a signed attachment, a named approval in a thread or a CRM record with a reference to the final document. If the export preserves three drafts but drops the one approval that distinguishes them, the future owner faces a choice between guessing and interrupting the customer.

ObjectQuestion after exportA useful recovery note
Document with revisionsWhich version did the customer accept?Filename or identifier, acceptance date and source of approval
Task with an ownerWho promised to call on Monday?Assignee, due date, customer reference and status at export
External attachmentCan the receiver open the actual file?Local copy or tested independent route with the right access
Agent-produced recommendationWhich input justified the suggestion?Permitted source and the human decision that followed

A hyperlink inside a downloaded PDF might still point back into the platform you plan to leave. Open the file from a clean browser that has no active session in the trial workspace. If the link requests a login, record what is missing and how the successor can get an authorised copy. Keep the original access policy intact. Opening the whole folder to the public to make an export easier would defeat the exercise.

Run a timed recovery with a second colleague

Give the successor the export, a brief description of the job and the contact details of the person sponsoring the transfer. Do not supply a narrated tour. Ask the successor to find the accepted price, the pending question and the next date promised to the customer. Let them describe the path they took. Record each point at which two records seem equally plausible.

A good exercise includes one item deliberately marked superseded. The successor should be able to explain why it is old. Imagine two drawings both called final, stored in separate threads a week apart. A chronological listing might be enough if the later file includes a clear acceptance note. Without that note, a neat export can still leave a field crew holding the wrong specification.

Have the successor complete a small change in the destination tool. They might add a new due date to the open task or produce a revised copy of a document. Can the manager tell which source material they used? Can the new owner attach the change to the right record without altering the historical decision? The answer helps distinguish a searchable archive from a practical migration.

Identify the work that lives outside the export

Connected tools can retain files, bookings, messages and access grants independently of the workspace. Draw a line between material owned by the platform and material referenced from another service. A chat might contain a task recap while the actual job remains in CRM. Conversely, CRM might contain only a link to an assistant's working file. Inspect a sample of both directions.

Write a row for recurring jobs. Who owns the scheduled weekly brief? What will happen to next Monday's draft when you cancel a seat? Which account has permission to prepare it in the replacement tool? During a rehearsal, use a disposable schedule or a documented simulation. Avoid turning off a live process just to discover who receives its output.

Consider the recipient of the exported material. Removing one client's access to the old workspace does not erase a previously downloaded copy. Agree on where the handover package lives, who can read it and who decides when it can be disposed of. This is a business-record decision. Ask the appropriate records owner to define retention for the actual material involved.

Turn a failed recovery into a purchasing condition

Use precise wording. “The export is poor” invites a general sales response. “The exported task list omits assignees, and the relief coordinator cannot identify who owes the client a call” gives the vendor a test it can demonstrate. Attach an invented example and the acceptance condition. Ask whether the fix exists in the intended plan or requires paid implementation.

Estimate the effort per project to reconstruct a missing part. A five-minute manual export for an annual job might be acceptable. The same intervention for every client thread could dominate the switching cost. Multiply only after sampling projects of different sizes and ages. Keep the assumptions visible so the purchasing team can decide whether the cost belongs in the budget.

Put a copy of the successful recovery instructions under an account the business controls. Name an owner and a review date. Rehearse again after changes to document storage, permission policies or the workflow that records approvals. An assistant can help assemble the packet, but a human successor should actually perform the recovery. For the role of agents across tools, see the Cortex platform.

Related guides: What is an AI execution layer? A plain-English guide for operators · AI vendor lock-in: the kill-switch risk when your agents run on one vendor · Can one AI subscription replace 20 SaaS tools? The honest maths.

Frequently asked questions

What if the supplier offers an export only on cancellation?

Ask for a representative sample and a written description of what the selected plan provides. If you cannot test the actual recovery before commitment, record that uncertainty in the purchase decision and keep critical decisions in a system you can already export.

Must every comment move into the new tool?

Decide which comments explain commitments, unresolved decisions or acceptance. A searchable archive may satisfy that need even if old comments cannot be edited. Get the project owner to approve the distinction using one real example.

Who should sign off the exit rehearsal?

The person who would inherit the work should demonstrate the recovery. The information owner should confirm the package contains only material the recipient is entitled to receive. Keep both decisions with the test result for the next renewal.