Operating continuity, with the gaps in view.

Prepared by Axeron AI · Relay for the managing director

A colleague is away. A committee pack is due. The procedure register names an owner, but the backup is missing. A separate note gives a different review date. Before asking a team to act, the managing director needs a reliable picture of who does what, which instructions apply and what still needs a decision.

Continuity is a practical concern for family offices. In its 2026 Global Family Office Report, UBS reported that 35% of surveyed offices had a defined succession plan for the family office. The research covered 307 UBS client family offices across more than 30 markets. It describes that surveyed group; it does not measure Relay's results or every family office. Read the research and its methodology.

Begin with a process people already recognize

This recorded example uses an authored operating packet for three recurring routines: committee-pack preparation, document-register updates and procedure review. The requested output is specific. For each routine, identify its owner, backup, inputs, output, approval requirement and next due date. Link every factual entry to its source.

Relay's team has three roles. A Process Mapper extracts the routines. A Control Reviewer challenges the evidence. A Handover Editor prepares the working documents. The operator reviews the proposed tasks before starting the run. Defining these responsibilities makes the method inspectable and gives each role a concrete question to answer.

The rules also say what to do when the packet is incomplete. A missing backup remains “Not provided.” Two conflicting dates remain visible until an authorized decision resolves them. The team is preparing a handover for review; it is not granting operating authority.

Make a correction without rewriting the history

The original packet gives both 15 and 22 September for procedure review. During the recorded workflow, the operator supplies a dated demonstration decision confirming 22 September. Relay reuses the saved team for a focused repair: update the documents, then have a separate reviewer check the saved content against the complete packet.

The revised handover cites that new decision. It also preserves both earlier date claims as history. This distinction helps a reviewer understand why the current date changed, rather than discovering that one source quietly disappeared.

The remaining backup question stays open. The action register asks which role is the approved backup for the document register and what authoritative record establishes that designation. A suggested follow-up owner is explicitly a proposal. No colleague, deadline or approval is invented to make the document appear finished.

Judge the result by whether someone can use it

The resulting handover separates responsibilities, required information and approval gates. The action register distinguishes the unresolved gap, the new decision and the earlier conflict. A managing director can review those records with the people responsible for the process and decide what evidence is still needed.

The film is an edited walkthrough of the actual recorded steps and revised draft. It does not represent an uninterrupted autonomous release. Independent checks of the downloaded Markdown confirmed the demonstrated fields. The working documents remain subject to human review; the demonstration does not certify a completed independent release check or the correctness of every export format.

Start with one recurring process. Compare the effort to prepare its handover, the number of corrections and the questions a backup colleague still has. Those observations can establish whether the method is useful in your office. This example provides no measured savings claim, customer performance result or permission to carry out the underlying work.