AI governance for integrators

Industry · Automation agencies and AI integrators

Give your client a way to continue the work after you leave

Agencies and integration teams know how to build agents and organise their workflows. At the end of the engagement, the client team also needs to understand the work still in progress: which cases are complete, which actions await approval and which outcomes need checking.

A useful handover combines workflow documentation with the state of the missions running through it. It makes decisions and the information needed to continue accessible, including when the consultant who knew the project is no longer available.

In brief

The question and the useful result.

Question
What should you hand over so the client can continue the missions after you leave?
Useful result
A handover checklist and four questions for the client team to answer.

AI governance for integrators

One workflow, three cases to hand over

Consider an agent that drafts meeting summaries and proposes updates to customer records. At handover, three cases have different outcomes: one update is confirmed, another awaits the owner's approval, and a third request has been acknowledged by the receiving system without confirmation of the result.

The workflow diagram explains the intended steps. The incoming team also needs to know where each case stands. Marking all three as “processed” would remove information they need to decide what comes next.

This is an illustrative handover scenario. It does not describe a CRM connector available in DUBSAR.

AI governance for integrators

What the client team needs to receive

Prepare a handover view that points to the following information in the tools and documents agreed with the client.

ItemWhat the incoming team should be able to find
Mission and scopeThe expected outcome, relevant cases, workflow version and boundaries of the assigned work.
State at handoverCompleted steps, pending actions, known failures and outcomes that remain uncertain.
Applicable authorisationsPermitted actions, conditions, authorised reviewers and changes in access that need attention.
Human decisionsThe action reviewed, the decision and any conditions, together with the information presented for review.
Results and referencesLinks to available confirmations tied to the right cases; acknowledgements distinguished from confirmed effects.
Work still to doOutstanding checks and decisions, with a named person responsible for each.

Review the departing consultant's permissions and those of the incoming team explicitly. Transferring a history does not by itself authorise every action recorded in it to continue.

AI governance for integrators

Check that another person can take over

Ask a client team member who did not build the workflow to review a few representative cases. They should be able to answer four questions:

  • What outcome was expected, and where does this mission stand?
  • What action can still be taken, and under which conditions?
  • What evidence confirms the work that actually completed?
  • Who needs to resolve the next decision or missing information?

Where an answer still depends on the consultant's memory, complete the handover record. This review can reveal missing links without triggering fresh business operations.

AI governance for integrators

Where DUBSAR is intended to help

DUBSAR is developing a governance foundation that connects durable mission state, authorisations, human decisions and execution evidence. The aim is to maintain continuity beyond a model conversation.

Connecting an existing workflow requires a clear account of where its useful records live, which actions are in scope and how their outcomes will be established. Automation tools and business systems retain their own roles in that process.

To check the capabilities of the tools you use, consult the official n8n documentation and Make AI Agent documentation.

AI governance for integrators

Frequently asked questions

Is a workflow export enough for a handover?

It helps explain how the workflow is organised. It needs to be accompanied by the state of ongoing missions, applicable decisions and references that allow results to be checked. The format depends on the tool and the work involved.

Can we reuse the same handover package for several clients?

You can reuse its structure. Scope, access, decisions and evidence need to remain specific to each client. A rule approved for one client establishes no authorisation for another.

What should we hand over when an outcome is still unknown?

Identify the request, the available evidence and the check still needed. Name the person who will handle it. Keep that part of the case open: missing confirmation alone does not establish either success or failure.

AI governance for integrators

Current project status

DUBSAR is in development. Selected workflows have been tested; end-to-end validation for B2B use is still underway. Pilots are not currently open.