What the handoff does not include
A handoff from E31 Consulting leaves out a copy held by the practice, a path back in, a managed service, and anything outside the named scope. Knowing the edges makes the first morning after easier.
· 4 min read
IN SHORT
An E31 Consulting handoff does not include a copy of the work held by the practice, a path back into the customer's network, a managed service for the use case, the platform documentation for Substrate and Agency, certification of the site team, or anything outside the scope that was named at the start. Each omission exists so the site does not depend on anyone outside it.
It is worth being as precise about what a handoff from E31 Consulting leaves out as about what it includes. A site that expects the wrong things will find the first ordinary morning after the engagement confusing. A site that knows the edges can plan for them.
It does not include a copy held by the practice
Nothing built during the engagement is retained by E31 Consulting. The versions, the adapters, the corpora, the run record, the notes: all of it is on the customer's appliance and nowhere else. The engineers do not take a backup home. There is no copy in a vendor's cloud, because the work was never there.
This is sometimes a surprise to customers who expect a consultancy to keep a reference build. The practice does not, for the plain reason that keeping one would be a path out of the building, and engineers who leave no path out cannot also keep a copy.
It does not include a path back in
When the engagement ends, the engineers' access ends with it. On a forward-deployed engagement the accounts, the segment access, and any supervised sessions are closed as part of the handoff, not after it. On a connected site nothing is left open to the practice. On an air-gapped site there was never anything to close.
If the site wants the practice back for a next version, that is a new engagement with new access granted by the customer, inside whatever posture the customer sets then. Access is never a standing arrangement.
It does not include a managed service
The practice does not operate the use case after handoff. The site team does. That is why the engagement cannot end until the team can publish a version on their own, as described in training the site team to change it. A handoff to a team that still needs the engineers is not a handoff.
Operating the appliance itself, the sealed Czar in the rack, is a separate matter covered by the appliance subscription and is not something the practice takes on.
It does not include the platform documentation
The notes handed over describe this use case on this site. They do not replace the documentation for Substrate and Agency, which the customer has by virtue of the appliance. The engineers will point to the right parts of it during training, but they do not rewrite it, and the notes assume the operators can reach it.
It does not include certification of the site team
Training the site team makes them able to change what they own. It does not make them E31-certified engineers. Certification is Element 31's assessment of its own practitioners, and it is not something a customer team receives through an engagement. See what a certified engineer is.
It does not include anything outside the scope that was named
An engagement begins by naming what done means, and the handoff is measured against that. A desk that drafts and waits is handed back as a desk that drafts and waits. If the site decides during the work that the same agent should also serve a second desk, that is a new scope and a new version, not an unwritten extra.
This is not rigidity for its own sake. A scope that stays fixed is the only way the operators can be trained on a stable thing and the record can describe one behaviour. Changes are welcome; they go through publishing like every other change.
What is left, by contrast
Everything the site needs to run and change the use case: the published version and its history, the operating picture inside each version, the corpus and adapters, the run record, the notes, and a team that has done each ordinary change at least once with their own hands. The full list is in what the customer keeps. The things the handoff does not include are the things that would have made the site depend on someone outside it.
Questions this raises
- If the practice keeps no copy, what happens if we lose the version?
- The version history, the corpus, the adapters, and the record are on the customer's appliance, and the appliance's own sustainment covers the hardware and platform under its subscription. Keeping what is built is part of what the customer owns; the practice holding a copy would be a path out of the building.
- Can the engineers come back if we need them?
- Yes, as a new engagement with access granted again by the customer under whatever conditions IT sets at that time. Nothing from the earlier engagement remains open to the practice in the meantime.
- Does the handoff include running the appliance itself?
- No. The sealed Czar in the rack is covered by its subscription, which includes sustainment of hardware and platform. The practice builds the use case on it; it does not operate the appliance.
KEEP READING