What the next session needs from the last one.

A useful handoff tells the next person what the team tried, what it decided and what’s still open. That’s what we want the Collab workflow to preserve.

The context model

From the Organization to the Session.

Every piece of context has a clear home, so it reaches the people who need it and nobody else.

LEVEL 01

Organization

The account that owns members, permissions and the knowledge the organisation has approved.

LEVEL 02

Products and Projects

Durable homes for engineering work. Context is scoped to the Product or Project it belongs to.

LEVEL 03

Rooms

Focused spaces where people and approved AI tools work through a problem, a review or a decision.

LEVEL 04

Sessions

Individual working periods inside a Room, each with its own participants, consent and record.

Three kinds of context

Evidence, working context and approved context stay distinct.

01

Evidence

Source material such as code, tickets, documents and session records, kept linked to where it came from.

02

Working context

What a team is exploring now, including open questions, options and draft conclusions.

03

Approved context

Knowledge a human Context Approver has reviewed and accepted as something the organisation can rely on.

How the context continues

Start with a problem. Keep what the team learns.

The workflow keeps the problem, evidence, decision and reviewed explanation connected from the first investigation to the next handoff.

Bring the context

Start with the technical problem and a Context Package limited to people who have permission. It contains the relevant code, prior decisions and evidence.

Work together

Use a persistent Room or instant Session to investigate assumptions, discuss the code and keep open questions visible.

Make the decision

Connect the chosen action to its source evidence, alternatives, trade-offs and responsible people.

Review what remains

Separate working evidence and proposals from conclusions the team has reviewed and approved.

Return with context

Let the next person, session or approved tool begin from what the team already knows.

What a useful handoff preserves

Leave enough context for the work to continue.

01

The decision

State what changed, what remains unresolved and who owns the next action.

02

The evidence

Keep the relevant code, tests, observations and alternatives connected to the decision they informed.

03

The boundaries

Record the access, approval and guardrails that still apply when another person or approved tool returns to the work.

A governed cRUD Collab handoff from a defined request and evidence through collaboration, human review and a trusted continuation state.
A handoff carries purpose, evidence, authority and the next action together, so work continues from a reviewed state.

Questions

Carrying work into the next session

How do a Room and a Session fit together?
A Room gives related work an ongoing place to live. A Session is a particular period of work within that Room, with its own activity and outcomes.
What should be available when someone takes over a piece of work?
They should be able to find the decision, the evidence behind it and the boundaries that still apply. Keep unresolved questions visible so the next person can see where their work starts.

See the complete product on the cRUD Collab website.

The cRUD Collab website explains how teams work with it, the principles behind it and the thinking that shaped it.