The Workbench · The Shelf
The citation is the product; the template is the wrapper
This blog has already covered how a template goes stale once the source underneath it moves, and why every regulatory team keeps rebuilding the same documents instead of borrowing one that already exists. Both essays assume a premise worth making explicit on its own: what actually makes a template worth taking isn't its layout. It's whether every clause in it points back to something real, and whether that pointer still resolves.
A template is a claim, one clause at a time
Most working documents that circulate in this industry don't show their work. A CAPA form gets copied from a departing colleague's laptop, a document-control SOP gets inherited from a consultant's engagement three reorganizations ago, and by the time either one reaches a new team, nobody left in the building can say which field traces to which regulation and which one is just how the original author happened to lay out a table. That's not a formatting problem. Every field in a working document is implicitly a claim — this exists because a rule requires it — and a template that can't back that claim up with an actual citation is asking a team to trust it on reputation alone.
Source-mapped is a specific promise, not a slogan
What this shelf means by source-mapped is narrower than “well-researched”: every clause in a template is meant to carry the actual citation it traces to — the CFR section, the ISO clause, the named guidance — sitting next to the requirement itself, not buried in a methodology note nobody reads before using the document. That's a check a user can run without taking the shelf's word for anything. A field that can't be traced back to a citation doesn't belong on the template; if it earns its place for a genuine practical reason a rule doesn't state outright, it gets labeled as practice, not law, so a user never mistakes the shelf's own judgment for a regulator's.
A citation is a promise that has to be kept, not a credit banked once
This blog has already covered what happened to every US template built around the device master record: the Quality Management System Regulation retired that name, and the citation, on February 2, 2026, without changing the underlying obligation at all. A template that cited 21 CFR 820.181 was accurate the day it was written and wrong the moment the rule it pointed to stopped existing — and nothing about the template's own text would have told a user that had happened. Watching for that kind of drift is its own discipline: a citation isn't a fact a template gets to state once and rely on forever. It's a claim that has to be re-checked against a source that keeps moving, on a cadence someone actually keeps, not on the assumption that a rule cited correctly at launch stays cited correctly.
Why this is a maintenance discipline, not a launch feature
A single accurate template is a weekend project. A shelf of them that stays accurate is a standing commitment, and that's the harder half of the case for one shared shelf instead of a thousand private ones: a private SOP library never gets rechecked by anyone outside the team that wrote it, so a stale citation can sit undisturbed for years without a single person noticing, because nobody outside that one company was ever positioned to catch it. A shared, source-mapped shelf only earns the trust it's asking for if the citations get audited on a schedule and corrected in public when a rule moves — not just written correctly once and left to age quietly, the same failure this blog has already traced through the criteria behind what makes the launch catalog's own cut in the first place.
Where this meets the file
In practice that means every template on this shelf is built to carry two things next to each requirement, not one: the citation itself, and the date it was last checked against its source. A field with no citation gets labeled as house practice instead of quietly passing as law. A citation whose source has since moved gets flagged and fixed before the template ships again, not discovered by a user mid-audit. That structure is what “free” is actually in service of here — previewed in the launch catalog, and open to correction from anyone who's caught a citation this shelf got wrong, through a direct contribution.
The Regulatory Toolkit launches soon — a free shelf of source-mapped templates, checklists and browser-only tools for regulatory teams. Get one email when it opens, or contribute a template.