Example design · fictional editorial desk
A persuasive headline still needs a sound source. Follow a fictional survey through research, claim checks and editorial review to see what an editor would need before publication.
Interactive browser demonstration · Fictional data · No live AI or client results
A survey table, a research question and permission to use the source.
A sourced article draft and a recorded editorial decision.
The named reviewer approves, returns or stops each step.
Change the sample size. Compare the headline with the original table, catch a stale percentage and follow the corrected claim back to its reviewer. Choose the situation, set the input and select “Run this case”. You make each fictional review decision; nothing is sent or applied outside the demo.
Changing the input or situation starts a fresh example.
Set the situation and input, then select “Run this case” to prepare the first output.
A fictional advisory practice is preparing a note about repeated evidence requests. In a made-up survey, 36 respondents reported the problem. Change the number of respondents and follow the claim through editorial review.
A sample can support a carefully bounded statement. It cannot support a claim about an entire market, a client result or a revenue uplift.
Source excerpts and the complete design remain readable below.
Use these fictional originals to check the number, period, version and permission behind each output. Missing or conflicting evidence remains visible. These are teaching records, not client results.
Synthetic source. Question: in this invented survey, how often did respondents report repeated evidence requests? The period is simulation week 1. Prepare one descriptive claim and one question for an editor; do not infer causation, sector prevalence or commercial results.
Use boundary: Invented public-research brief; no confidential client context or real web research.
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.
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.
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.
Synthetic source. Correction replaces the old 60% headline with 36 / N × 100, rounded to one decimal, and limits the statement to the fictional week-1 respondents. The numerator, current sample and permissions are unchanged. The editor must review this new claim version.
Use boundary: Replacement draft for the same fictional aggregate-data boundary; no wider story rights.
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.
Synthetic source. At Issue decision, the fictional source-preview connection stops. Preserve the current sample and claim versions and the pending editor decision. The technical investigator may compare the retained versions and propose a local retest. Diagnosis supplies no publication, restore or audience authority.
Use boundary: Synthetic fixture; private review within this fictional case only.
Practice lead receives approved question and public signal and prepares research brief.
Decision: Lead checks relevance. Permission: Public sources; sanitised question only.
Marketing lead receives public brief and approved offer and prepares claim set with rights.
Decision: Owner clears claims. Permission: Approved claims and story rights.
Editor receives cleared claims and brief and prepares marked article or asset.
Decision: Editor reviews evidence and tone. Permission: No confidential case content without rights.
Editor / rights owner receives source-linked asset and prepares approve, revise or decline.
Decision: Named editor approves release. Permission: Publication and audience authority.
Channel owner receives approved version and consent rule and prepares publication receipt and response review.
Decision: Owner validates distribution. Permission: Approved channel and recipients.
Return route: Claim or rights rejected. Unsupported claim or missing permission returns to source review; wrong audience or consent stops distribution.
See the workflow’s inputs and owners ↗Use the no-fee Workflow Fit Call to discuss where your cases get held up. If there is a fit, a paid System Blueprint measures one service line and fully designs three connected workflows, with a ranked installation roadmap. Installation is separately scoped; pricing is quote-specific.
