Features
Part of Government records and public documents verification guide
Fictional case: correcting a complaint reported as a ruling
Court record correction case showing how a newsroom mistakes complaint allegations for a ruling, reconstructs the docket, rewrites the story, and fixes each surface.
What to take away
- A civil complaint records a plaintiff's claims and requested relief, not a court finding that the conduct occurred.
- Docket position, filing party, document type, and later entries must appear in the verification notes.
- A correction must remove the false ruling language from the headline, body, alerts, and graphics.
- Do not replace one unsupported conclusion with another about the merits of the case.
- Build court-record controls around entry numbers and posture, not filenames alone.
This case is fictional. The court, parties, lawsuit, docket, company, and publication are invented. It demonstrates how to correct a story that transformed allegations in a newly filed complaint into a judicial ruling.
The original alert
The fictional West Basin Wire receives a PDF named court-rules-vendor-overbilled.pdf from a source. The first page carries a federal-style case caption and a court filing stamp. The newsroom publishes a mobile alert:
Court rules Northstar Civic Systems overbilled county by $8.4 million
The story says a federal judge found that the vendor inflated invoices and ordered repayment. It quotes paragraphs describing duplicate charges and an $8.4 million damages demand.
No editor opens the full docket. The PDF is the county's complaint, filed that morning. It contains no judge's signature, order, or judgment.
Step 1: freeze the record
The standards editor preserves:
- the supplied PDF and its file metadata;
- the published headline, alert, body, image, and metadata;
- homepage, newsletter, and social versions;
- reporter and editor notes; and
- publication and discovery times.
The team computes a hash for the supplied file and stores an untouched copy. This makes it possible to compare the source attachment with the official filing.
Step 2: reconstruct the docket
The editor searches the official fictional court system by party name and finds the case. The docket shows:
| Entry | Time | Document | Filed by |
|---|---|---|---|
| 1 | 9:04 a.m. | Civil complaint and exhibits | County |
| 2 | 9:07 a.m. | Civil cover sheet | County |
| 3 | 9:10 a.m. | Summons issued | Clerk |
There is no answer, motion, hearing, order, opinion, or judgment. The source PDF matches docket entry 1, apart from its misleading local filename.
Cornell Law School's Legal Information Institute defines a civil complaint as the pleading that starts a case, states the plaintiff's claims, and requests judicial relief. That role supports writing "the county alleged" and "the lawsuit seeks," not "the court found" or "the judge ordered."
Step 3: map every false statement
The newsroom creates a claim log:
| Published statement | What the record shows | Status |
|---|---|---|
| Court ruled against Northstar | County filed complaint | False |
| Judge found invoices inflated | County alleged inflation | False |
| Court ordered $8.4 million repayment | County requested damages | False |
| Lawsuit filed Tuesday | Filing stamp and docket confirm | Supported |
| Contract concerns billing system | Complaint and exhibit identify contract | Supported as case context |
This prevents a partial correction that changes only "ruled" to "said" while leaving an invented repayment order.
Step 4: contact the parties and court
The reporter calls the clerk to confirm that no order or judgment has been entered. The clerk does not comment on the merits. The county confirms it filed the case. Northstar says it disputes the allegations and will respond in court.
The story attributes those positions. It does not call the company's denial proof that the complaint is false.
Step 5: understand the missing document
A judgment would be a different record produced by a different actor after judicial consideration. Cornell's definition of a judgment describes it as a court or tribunal's decision after considering relevant evidence and the parties' rights and obligations. The docket contains no such decision.
The editor also checks whether a proposed order was attached to the complaint. Even if one existed, a party's proposed language would not become the court's order unless the judge entered it.
Step 6: replace the story
Because the error reverses who spoke and what happened, the Wire replaces the article rather than burying a wording change. The new headline reads:
County lawsuit alleges Northstar overbilled $8.4 million
The lead states that the county filed a civil complaint, that the allegations have not been adjudicated, that the county seeks damages, and that Northstar disputes the claims.
The corrected story describes the cited invoice examples as allegations tied to complaint pages and exhibits. It avoids repeating every accusation merely to explain the mistake.
Step 7: publish a complete correction
The notice appears above the new article:
Correction, August 8, 2027: An earlier version incorrectly reported that a court ruled Northstar Civic Systems overbilled the county and ordered $8.4 million in repayment. The document was the county's civil complaint, which contains allegations and a request for damages. The court docket showed no order, judgment, or finding on those claims at publication. We changed the headline and article, withdrew the original alert and graphic, and added Northstar's response.
The notice does not say the story "mischaracterized a document." It names the false claims and the correct posture.
Step 8: repair every surface
The production editor follows an inventory:
- withdraw the push alert and send a correction alert;
- replace the homepage and app cards;
- change title, description, and structured metadata;
- delete or correct social posts and attached images;
- annotate the newsletter archive;
- update syndication partners; and
- remove the false claim from a running contract timeline.
The original URL remains live with the corrected story and notice. Internal records retain the prior version.
Step 9: diagnose the workflow failure
The review identifies four failures:
- A source-created filename was treated as document metadata.
- The official docket was not checked.
- The filing party and entry number were absent from notes.
- The headline review asked whether the amount appeared, not who asserted it.
The newsroom adds a court-record card requiring court, case number, entry number, filing party, document type, filing date, operative language, later status, and second-person review.
Step 10: establish language controls
| Record | Default attribution |
|---|---|
| Complaint | Plaintiff alleges; lawsuit seeks |
| Answer | Defendant admits or denies |
| Motion | Party asks the court |
| Declaration | Declarant states |
| Order | Court orders or holds |
| Judgment | Court enters judgment |
The table is a starting control, not a replacement for reading the document. Orders can be procedural, and complaints can be amended or dismissed.
Common questions
Can the story quote allegations from the complaint?
Yes, when newsworthy and fairly attributed. Give the response, procedural status, relevant context, and only the detail needed for the report.
Does a court filing stamp make allegations true?
No. It confirms filing in the case system. It does not turn a party's claims into judicial findings.
Should the outlet say the company was cleared because no ruling exists?
No. The merits remain unresolved. The correction should restore uncertainty, not declare the opposite outcome.
What if a judgment appears after publication?
Cover it as a new procedural event, read its scope and later status, and do not retroactively excuse the original error.
