Skip to content
Skip to content
Build n Bloom
Menu
WorkflowsRolesDemosSystem BlueprintResourcesEvidenceExisting-client NDISInstallation
Request a Fit Call
← All ten role demos

Quality checker / EXAMPLE DESIGN

Catch the claim its source cannot support.

A citation alone does not make a claim correct. See how the Quality Checker compares the number, population and source version, with a reason for every item returned.

Working browser demonstration · Fictional sources · Local rules, no live agent

Quality checker: inputs, prepared output and human reviewOriginal evidence and Proposed draft supply the inputs. Prepared output: Omission, contradiction and citation report. Human review: Named reviewer accepts or returns the work. Source boundary: Read-only comparison; a discrepancy report is never professional sign-off. Example design with fictional records.Compare the proposed output with the original evidence and explain each discrepancy. The prepared output still needs human review.
WHAT GOES IN

A proposed claim and the original evidence it is supposed to describe.

WHAT COMES OUT

A discrepancy report showing what matches, what fails and why.

WHO DECIDES

The named reviewer decides whether to correct or issue the work. A clean check is not professional sign-off.

01 / TRY THE JOB

Prepare the output.
Inspect the evidence.

Compare a current claim with a stale 60% headline. Read the arithmetic and population checks separately. Set the input and select “Prepare this result”. Then read the output before recording a fictional review.

Choose the situation
120 respondents
80240

Changing an input starts a fresh example.

ALLOWED INPUTS

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

PREPARED OUTPUT

A discrepancy report showing what matches, what fails and why.

HUMAN REVIEW

The named reviewer decides whether to correct or issue the work. A clean check is not professional sign-off.

Ready to prepare

Compare a proposed headline with the original table. Inspect the number, sample and permission separately, with a reason for every discrepancy.

THE TASK

Check the claim against its source

Compare a proposed headline with the original table. Inspect the number, sample and permission separately, with a reason for every discrepancy.

Local fictional example · 0 recorded events · Revision 1

02 / THE ROLE’S SOURCE PACK

Check the source behind the answer.

These fictional originals belong to the selected case. Compare the output with the source, version and allowed use. Showing a source here does not clear missing evidence or grant wider access.

PUB-SAMPLEVersion 1

Original fictional survey table

Synthetic source. The adjustable N is completed responses, a whole number from 80 to 240 (default 120). Exactly 36 answered yes to repeated evidence requests in simulation week 1; N minus 36 answered no. These categories exhaust the sample. Rate = 100 × 36 / N; display one decimal place. This is invented data, not public research.

Use boundary: Fictional aggregate data may be quoted with the sample, period and synthetic label.

PUB-CLAIMVersion 1

Sample-bounded claim template

Synthetic source. Proposed text: In this fictional week-1 sample, 36 of N respondents (100 × 36 / N percent, rounded to one decimal) reported repeated evidence requests. Retain the denominator and invented-sample qualifier. One numerical claim requires editorial review.

Use boundary: Synthetic fixture; private review within this fictional case only.

PUB-CLAIM-OLDVersion 0

Superseded pilot headline — exception

Synthetic source. The old headline reads: 60% of advisory firms repeat evidence requests. Its 36 / 60 pilot denominator belongs to a different fictional sample. It is not the current N, and the phrase advisory firms overstates the population. Keep this source only to inspect the discrepancy.

Use boundary: Comparison only; this stale headline is not cleared for publication.

PUB-EDITORIALVersion 1

Editorial and distribution brief

Synthetic source. Use the survey statement, show the no-response category as N minus 36, and ask where repeated requests occur. Do not invent a client story. The proposed channel is an internal example newsletter. Publication, audience consent, delivery, responses and any enquiry attribution have no receipts in this demo; each remains pending its owner.

Use boundary: Synthetic fixture; private review within this fictional case only.

SELECT ROLES AFTER UNDERSTANDING THE WORK

Is this a recurring job in your firm?

Bring the task, its current owner and where it gets stuck to a no-fee Workflow Fit Call. If a paid System Blueprint is useful, it measures one service line and fully designs three connected workflows. Roles are chosen for those designs. Installation is separately scoped; pricing is quote-specific.