Skip to content
Skip to content
Build n Bloom
Menu
WorkflowsRolesSystem BlueprintResourcesEvidenceExisting-client NDISInstallation
Request a Fit Call
← All workflow paths

C2 · DEL.1 → DEL.2.W01 → DEL.3 → DEL.4 → DEL.6.W01 · Example design

Deliver a defensible decision pack

Connect permitted sources, an approved method, professional review and the client's acceptance record.

TRIGGER → ACCEPTED OUTPUTSigned work → reviewed decision pack

Typical sponsor: Practice lead and qualified reviewer. This is an illustrative route. It is not an installed workflow or a promise that this path is one of your three Blueprint designs.

01 / HANDOFF DESIGN

The object, the owner, the decision.

Select any stage to inspect what it receives and produces, which specialist role might assist, what it may access, and who makes the human decision.

C2 · DEL.1 → DEL.2.W01 → DEL.3 → DEL.4 → DEL.6.W01REFERENCE DESIGN · NOT AN INSTALLED SYSTEM

Scroll the diagram horizontally, or use the stage buttons below.

Signed work → reviewed decision packFive stages linked by named handoff objects. A rejected decision returns from stage 4 to stage 3. The full sequence and ownership are written below.Permitted source packAccepted evidence registerReviewed findings basisSource-linked issue versionReviewer rejects findings01 · DEL.1Signed scopeEngagement lead02 · DEL.2.W01Evidence registerEvidence owner03 · DEL.3Traceable analysisQualified practitioner04 · DEL.4Issue draftEngagement lead05 · DEL.6.W01Client acceptanceClient / authorised l…
SELECTED HANDOFF / 01

Signed scope

Engagement lead owns this step.

Receives
Signed brief and access decision
Produces
Mobilised case
Possible agent roles
Intake analyst · Case coordinator
Permission boundary
Signed case and source boundary
Human decision
Lead approves plan and access
Other stop and return routes
  • Missing evidence or permission at DEL.2 returns to the evidence owner or stops the case; it never becomes a silent complete pack.
  • Client correction or dispute at DEL.6 returns to the engagement lead at DEL.4 for a controlled revision or formal resolution.
Read the full handoff and exception sequence
  1. Signed scope (DEL.1) — Engagement lead receives signed brief and access decision and produces mobilised case. The handoff is permitted source pack. Lead approves plan and access.
  2. Evidence register (DEL.2.W01) — Evidence owner receives permitted pack and exact question and produces versioned facts, gaps and conflicts. The handoff is accepted evidence register. Evidence owner accepts version.
  3. Traceable analysis (DEL.3) — Qualified practitioner receives accepted register and approved method and produces findings and alternatives. The handoff is reviewed findings basis. Practitioner owns conclusion.
  4. Issue draft (DEL.4) — Engagement lead receives approved findings and source trail and produces review-ready deliverable. The handoff is source-linked issue version. Qualified reviewer signs issue.
  5. Client acceptance (DEL.6.W01) — Client / authorised lead receives professionally approved version and produces acceptance, correction or dispute record. This is the recorded outcome. Client or authorised lead accepts.

Return path: Reviewer rejects findings sends work from Issue draft to Traceable analysis.

Missing evidence or permission at DEL.2 returns to the evidence owner or stops the case; it never becomes a silent complete pack.

Client correction or dispute at DEL.6 returns to the engagement lead at DEL.4 for a controlled revision or formal resolution.

02 / WHY ASSESS IT

Value is a hypothesis until measured.

Net scarce-role time per accepted output may improve if source work and corrections fall without weakening quality.

MEASUREMENT BASIS

Records to inspect

Signed scope, permissioned case pack, versioned evidence register, approved method, review and client acceptance receipts.

STOP / RETURN

Where it can fail

Missing or conflicting evidence, wrong tenant or unsupported conclusion stops work; rejected evidence or draft returns to its owner.

DESIGN ACCEPTANCE

Cases to test

Test ordinary, missing/conflicting, permission, wrong period, injection, tool failure, revocation and reviewer-return cases.

03 / SPECIALIST ROLES

Possible assistance, bounded by authority.

These roles are candidate responsibilities in the reference architecture. They are not prebuilt products or active agents in your systems.

INTAKE

Intake analyst

Check one authorised case against its agreed intake list.

Boundary: Only the case workspace and signed scope; unexpected restricted material stops intake.

COORD

Case coordinator

Show the next owner, dependency or proposed follow-up.

Boundary: One current case state; routine effects require separate delegation and receipt.

LIBRARIAN

Evidence librarian

Find current permissioned internal sources for one case and question.

Boundary: Case-scoped internal search; no public-web egress or cross-client corpus.

CHECK

Quality checker

Compare a draft with the original permitted evidence and exact request.

Boundary: Read-only comparison; a discrepancy report is never professional sign-off.

ANALYSIS

Delivery analyst

Apply an approved calculation or comparison method.

Boundary: Validated inputs and authorised workpapers; no invented method or conclusion.

RESEARCH

Public researcher

Investigate one approved public question.

Boundary: Sanitised brief and public sources only; no confidential case context.

DRAFT

Deliverable writer

Prepare an article, proposal or client section from approved findings.

Boundary: Approved template, claims and versioned sources; draft remains private until review.

From reference to a firm-specific decision

A Blueprint starts with a service the firm already sells, examines permitted records and measures the constrained work. It selects three connected boundaries, designs each to the same depth and ranks the first installation. A reference path may change, narrow or be rejected when the evidence is different.

Inspect the System Blueprint ↗