Why every regulatory team rebuilds the same documents

Somewhere today, a regulatory affairs specialist is building a CAPA log in a blank spreadsheet, from memory, for the third company in a row. The log will be fine. It will also be the third time that person has paid for the same lesson — and their team will pay it again when they leave.

Regulatory work runs on documents. Not prose — working documents: the submission checklist, the technical-file index, the audit plan, the complaint log, the document-control SOP. They are the load-bearing structure of a quality system, and nearly every one of them has been built thousands of times before, by thousands of teams, to satisfy the same regulation read from the same page.

Yet almost none of that structure is shared. Consulting firms keep template libraries as house assets, because billable hours are the product. Enterprise QMS platforms bundle templates behind seat licenses, because lock-in is the product. Experienced practitioners carry private stashes from job to job — quietly, because the stash technically belonged to the last employer. The commons that should exist, doesn't.

How the wheel gets reinvented

It isn't that teams enjoy rebuilding. The rebuild happens because documents live and die inside company walls. A quality system is audited as a private artifact; nobody's job description says publish the good parts. When a company folds or a team turns over, its accumulated document craft — the checklist that caught the labeling gap, the tracker whose aging column actually got CAPAs closed — evaporates. The next team starts from a blank sheet or, worse, from whatever the QMS vendor shipped as a default.

The cost isn't typing time. A competent specialist can lay out a submission checklist in an afternoon. The cost is structural: the afternoon version encodes only what its author remembered that day. The item they forgot is invisible until an intake reviewer finds it, and a submission that bounces on completeness grounds doesn't lose an afternoon — it loses weeks, sometimes a full review cycle, at whatever a delayed clearance costs the business per month.

What a template actually is

A template is not a formatting convenience. A good one is an argument about how the work should go: what has to exist before what, what the reviewer on the other side will look for first, which fields future-you will wish present-you had captured. The revision-history block in a document-control SOP is not decoration — it is the encoded memory of every audit where its absence became a finding.

That's why "just write it fresh" undersells the problem. Fresh documents encode one person's recall under deadline. Shared, criticised, revised documents encode the field's. The difference between the two is exactly the difference a checklist is supposed to make.

Building the shelf in public

The Regulatory Toolkit is our attempt at the missing commons: a shelf of submission-ready templates, checklists and trackers that any team can take, free at launch, each one mapped to the primary source it serves — the RTA policy, the ISO clause, the guidance section — so you can check our work instead of trusting it.

The launch catalog is small on purpose; the next essay in this series explains what makes the cut. If you've built a document your peers would use, the shelf takes contributions — edited, credited, published.