The Governing Stack

Page 1 of 164 min read

Medical writers use the word guideline for sources with very different force. A law is not a journal checklist. An agency guidance is not a sponsor procedure. A treatment recommendation may be evidence for the document without governing its structure. A template may reveal an expected sequence without explaining the rule that created it. Good work begins by classifying every source.

1. Law and regulation

Law and regulation create binding duties in a defined jurisdiction and situation. They may govern authorization, clinical-trial conduct, informed consent, transparency, privacy, safety reporting, devices, labeling, accessibility, or submission. The writer records the jurisdiction, scope, status, and effective date and obtains legal or regulatory interpretation where needed.

The writing consequence is often larger than a sentence-level requirement. A rule may determine which document must exist, who must approve it, when it must be submitted, what information must be included, how personal data are handled, and which public disclosures are required.

2. Regulatory guidance

Regulatory guidance describes an authority's expectations and recommended approaches. It can shape study documents, evidence summaries, dossier modules, safety reports, public information, and submission interactions. Status matters: final and draft materials do not play the same role, and regional guidance may add to or interpret harmonized guidance.

A writer should not reduce guidance to a contents list. Extract expectations about purpose, evidence, analysis, presentation, cross-references, appendices, lifecycle maintenance, and quality control. Record questions for the regulatory lead instead of converting ambiguous language into private certainty.

3. Consensus and technical standards

Consensus standards give industries and disciplines a common technical language. The corpus repeatedly discusses ICH guidance in drug development and ISO-related standards in areas such as devices, quality, terminology, and plain-language practice. A standard can govern content, data, process, terminology, or performance.

Access and copyright constraints may mean the project cannot reproduce a standard. The writer needs the controlled source or an authorized organizational interpretation, a clear applicability decision, and a checklist containing only what the team is entitled to operationalize.

4. Reporting guidelines

Reporting guidelines help authors report a particular study design or evidence-synthesis method completely and transparently. Examples discussed throughout the corpus include CONSORT for randomized trials, PRISMA for systematic reviews and meta-analyses, STROBE for observational research, CARE for case reports, and statistical reporting recommendations such as SAMPL. Extensions address particular interventions, data sources, outcomes, populations, designs, or formats.

These sources answer what a reader needs to see to understand and appraise the work. They do not repair poor methods, replace a protocol, turn a narrative search into a systematic review, or guarantee journal acceptance.

5. Publication ethics and good practice

Publication practice includes authorship, contributor roles, professional medical-writing support, acknowledgments, conflicts of interest, funding, data integrity, originality, duplicate publication, trial registration, results disclosure, corrections, and interactions with journals. The corpus treats ICMJE recommendations, Good Publication Practice, COPE materials, journal policies, and author or sponsor procedures as an interlocking practice layer.

This layer controls not only the manuscript's declarations but also the process used to create it. Authorship discussions, contribution records, writing support, approvals, and disclosure information must be managed before the submission screen asks for them.

6. Target instructions

Journal, congress, authority, payer, registry, and portal instructions govern the destination. They specify article or submission type, section order, length, format, displays, references, supplementary files, declarations, forms, metadata, deadlines, and technical validation.

Target instructions are project evidence. Preserve the version or capture used to plan the work. A remembered word limit or a template from another target is not sufficient.

SOPs, work instructions, controlled terminology, data-handling rules, review systems, approval matrices, quality standards, and house style determine how the team works. These private requirements are not universal medical-writing rules. They are nevertheless controlling inside the project when valid and applicable.

Record the owner, version, effective date, role implications, required records, and escalation route. Keep sensitive material inside approved systems.

8. Templates and schemas

Templates, forms, data schemas, authoring tools, and submission structures express requirements in usable form. A template is a starting architecture, not permission to paste irrelevant boilerplate. The writer must know which fields are mandatory, which sections are conditional, which prompts are instructions rather than document text, and which content is inherited or generated elsewhere.

9. Clinical and professional guidance as evidence

Treatment guidelines, consensus statements, position papers, and professional recommendations often support background, clinical context, comparator choice, or implications. They belong in the evidence dossier unless a target or process specifically makes them a governing requirement.

This distinction prevents a common category error: a recommendation about clinical care does not automatically determine how a study must be reported.