Workshop wall with an abstract process diagram and two colleagues

Implementation

Four to six weeks to a matter your team runs without us in the room.

We do not arrive with a generic rollout plan and a slide about change management. We sit with the coordinator who currently chases the list, and we replace that list.

The rollout, week by week

Week 1 · Scope

Name the matter types and the people who sign

We agree which checklists are in scope first. Usually one: a buyer’s review, a property acquisition, or a supplier panel. We write down who may open a matter, who may mark a point queried, and who may sign. If those names are unclear, we stop and resolve that before any configuration.

Week 1–2 · Map

Lift the request list you already trust

Your current spreadsheet, playbook or precedent list is the source. We do not throw it away. Items are grouped into workstreams, given the source class they need, and marked mandatory or optional. You approve the list before it is used on a live file.

Week 2 · Intake

Match the way documents already arrive

Most teams begin with a structured export from the data room they already pay for, plus a named drop for documents that arrive by email. We do not insist on a live connection to every vendor on day one. A reliable intake beats a fragile integration.

Week 3–4 · Pilot

Run one real or recently closed matter

A live matter is better, because the gaps show up. A recently closed matter is acceptable if a live file would put a counterparty at risk. We load a sample of requests and documents, and your reviewers try to close three points using only the workspace. Where they reach for the old spreadsheet, we change the workspace.

Week 4–5 · Training

Separate sessions for coordinators and reviewers

Coordinators need the request list, the chase view and the export. Reviewers need the source register and the sign-off states. Partners need a twenty-minute path to the open issues. We do not put all three in one long demonstration and call it training.

Week 5–6 · Hypercare

Stay through the next completion, then step back

For the following matter we are on a named channel during UK business hours, fixing checklist wording and permissions rather than presenting. At the end you have the export of registers, the activity log and an administrator on your side. If you stop using Acheataya, that export is yours.

Who we need from you

A deal or file coordinator, one reviewer who will actually sign points, and a sponsor who can decide scope. IT is involved when access and retention rules need to match your own policy.

Who we are in the room

An implementation lead from the Penryn studio and, where the checklist is specialised, a practitioner who has run that matter type. We do not staff the project with people who have only seen a demonstration.

What you keep

Request lists, source registers, issue logs and the activity export. Your documents remain yours. Leaving does not require us to “release” your file.