Carrying context from one department to the next

A request that crosses three teams is really three separate stories, each starting from whatever fitted in the subject line. The reason a decision was made in the first team almost never survives into the third.

By the time somebody asks why, the answer is spread across an inbox, a ticket, a spreadsheet and one person's memory of a call. Here is what gets lost at each handoff, what it costs, and how we design the history in.

What a case has to carry

A system that crosses departments has to carry the case, not just the record. Every team that touches it sees the same history, while each person still works in the tools they already use.

Every case we design carries four things from one team to the next:

• The request travels as the client made it, with every document that came with it, from the first email to the signed form.
• The findings travel with it: what each team checked, in which system of record, and what it found there. They can be read by each person or shared with the whole team.
• The rule that was applied travels too, with who approved it, so the next team does not re-decide what was already decided.
• The handoff note tells the next team what it needs to know, drafted by the system and checked by a person.

Each team still sees only what it is entitled to see. Permissions follow the record, not the system, so a case can cross departments without opening every file to everyone.

Teams also work the case where they already are. The system writes into the platforms each team already uses, so nobody has a new place to look, and the history travels with the work rather than beside it.

What gets dropped, and what it costs

Context is lost the same way in every industry we work in. Here are four handoffs we have rebuilt, from insurance, construction, energy and financial services.

Underwriting to Claims

At a multinational insurer, a policy is written by underwriting and claimed against months later. The claims team used to start from the policy number and little else, and the broker was asked again for what underwriting already knew.

Now the reasoning travels with the policy: the referral notes, the exclusions the underwriter discussed with the broker, and the exposure at the time of writing. Each morning, the claims desk sees what changed overnight, with a draft next step for each person, held for their approval.

The second team no longer re-asks the client what the first team already established. As people rotate on and off an account, the record keeps the decisions and the reasons for them, and a new adjuster gets up to speed from the case itself rather than from a colleague's memory.

The same insurer's exposure is repriced every morning against currency moves, and the result reaches underwriting, claims and finance with the same working attached, so three departments argue about one number.

“We used to reconcile three systems by hand before anyone could answer a broker. Now the case arrives with its history, the rule that was applied and who approved it. Nobody re-asks the client, and when an auditor asks why a claim went the way it did, the answer is already in the record.”

Estimating to the Site

At a national contractor, a job is priced by the estimating desk and built by a site team that was not in the room. The system follows the job from the estimate into the project's own tools, carries the assumption behind each line, and flags the ones a site team needs to see.

We taught the system the contractor's own handoff, as its estimators described it: what a site team needs before mobilising, when to go back to the estimator, and what evidence a change order needs before it is priced. It reports progress and open questions where the teams already talk.

The estimators review every change it proposes. A change order now arrives with the original assumption it changes, so the site and the estimating desk argue about the same number, with the same history in front of them.

Land to Engineering

At a geothermal developer, a site is chosen from satellite imagery, land records and permits long before an engineer is involved. The reasons a site was chosen used to stay with the team that chose it.

We gave the system the developer's own selection criteria and the documents behind each shortlisted site. When engineering opens a site, it sees why it was chosen, what was ruled out, and which permit conditions apply, without waiting for a meeting with the land team.

When a condition changes, the system carries the change from land to engineering and posts it for sign-off where both teams already work. Anyone on either team can see what changed and why, and every change goes through the same review before it is accepted.

“The reasons we chose a site used to live in three people's heads. Now engineering opens a site and the shortlist, the imagery and the permit conditions come with it, in the order we decided them.”

Treasury to Reporting

In financial services, a reconciliation team answers dozens of questions a day about why two records disagree. The answers used to live in one analyst's notes and nowhere else.

The system reads the ledger and the bank records with read-only access, scoped per system. It writes its findings into the platforms the reporting team already uses.

The team had spent years building rules for matching more than 45,000 accounts. We wrote those rules into the blueprint, including the exceptions nobody had documented, and the system remembers each correction an analyst makes to its matches, so what one person teaches it improves the answer it gives everyone.

One record, written once

Every action is logged against the record it touched, so when somebody asks why a case went the way it did, the answer is in the record instead of in a reconstruction. See how the history travels in insurance, construction, energy, and financial services.

Tell us about the process you want handled

Scoping SessionTalk to us