Part II · Build the Evidence System

05Know What Governs the Document

Chapter 5 of 146 min read7 sources
The gist30-second version
  • “Guideline” can mean law, regulatory guidance, technical standard, reporting checklist, ethical policy, target instruction, organizational procedure, or clinical-practice evidence.
  • Applicability depends on document type, study design, jurisdiction, audience, target, lifecycle stage, and source version.
  • Build a governing stack and extract requirements into an operational constraint register.
  • Templates help with structure but do not replace understanding or authority.
  • When sources conflict, expose the conflict, identify the decision owner, and preserve the rationale.

Medical documents may be shaped by ICH families for drug development, reporting recommendations for study designs, good publication practice, journal instructions, regulatory requirements, templates, style guides, plain-language principles, statistical guidance, device frameworks, and organizational procedures.1,2,3 These sources do not all have the same authority, purpose, or scope.

The writer's first guideline skill is therefore classification.

Several different things are called guidance

Use a practical taxonomy:

  • Law and regulation: Binding within a defined jurisdiction and scope.
  • Regulatory guidance: An authority's expectations or recommended approach, with a stated status.
  • Technical or consensus standard: A harmonized framework such as the ICH material used across drug-development documents.1,3
  • Reporting guideline: A checklist or explanation for complete and transparent reporting of a study design or evidence method.2,4
  • Ethical and publication-practice policy: Authorship, disclosure, trial registration, data transparency, editorial conduct, and professional-writing support.
  • Target instructions: Requirements from a journal, congress, authority, payer, platform, or other destination.
  • SOP or house rule: Sponsor, client, institution, agency, or team procedure.
  • Template: A reusable structural artifact, form, or content shell.
  • Clinical-practice or society guideline: Domain evidence about care, usually cited as content rather than used as the reporting structure.

The distinctions prevent category errors. A clinical-practice guideline can support a statement about current management but does not tell the writer how to report a randomized trial. A reporting checklist can improve completeness but may not determine the file format or word limit. A sponsor template can dictate headings without overriding the underlying regulatory requirement.

Determine applicability before extracting rules

For every candidate governing source, ask:

  1. What document or process does it govern?
  2. Which study design, product, population, or lifecycle stage is in scope?
  3. Which jurisdiction or destination applies?
  4. What is its status: final, draft, superseded, optional, mandatory within an organization, or informative?
  5. Which version and effective date apply to this project?
  6. Does a target-specific instruction narrow or extend it?
  7. Does an extension apply because of the study or audience?

Do not rely on memory for high-stakes requirements. Standards, policies, questions-and-answers documents, and implementation practice evolve; good publication practice alone has been revised repeatedly since 2003, including the GPP 2022 update.5 Check the authoritative text, version, status, scope, and effective date instead of assuming that a remembered summary remains current.3

Build the governing stack

The governing stack is the set of applicable sources arranged by role and authority. It might contain a regulatory requirement, technical guideline, sponsor SOP, controlled template, statistical reporting guidance, target-journal instructions, authorship policy, and house style. Each contributes something different.

Represent the stack as a register:

SourceTypeScopeVersion/statusOperational effectOwner/query
Governing standardTechnical or regulatoryDocument or programChecked versionRequired content and organizationRegulatory lead
Reporting guidelineStudy designManuscriptChecked versionCompleteness and transparency itemsLead author
Target instructionsDestinationSubmissionCurrent target pageWord limits, headings, files, disclosuresCorresponding author
Sponsor procedureOrganizationWorkflowControlled versionReview, terminology, approvalsDocument owner
TemplateStructural artifactDeliverableApproved versionHeadings and placeholdersWriter

The register turns a reading task into a production tool. Instead of remembering that a source “applies,” the writer records what it changes.

Extract requirements into the Structure

Guidance becomes useful when translated into operations:

  • Required sections and sequence
  • Mandatory content items
  • Definitions and controlled terminology
  • Data presentation and statistical reporting expectations
  • Safety and balance requirements
  • Authorship, acknowledgment, disclosure, registration, and transparency statements
  • Word, table, figure, reference, and supplement limits
  • Required appendices, forms, checklists, or schemas
  • File types, naming, submission components, and destination behavior
  • Review, approval, and recordkeeping requirements

Map each requirement to a section, document-level check, or workflow gate. If it has no destination, it is likely to be forgotten.

Templates are scaffolds, not substitutes for thought

Templates can save time, improve consistency, and encode required structure. They can also encourage mechanical completion. A heading may remain after its purpose has changed. Boilerplate may survive into an incompatible study. A prior document may carry obsolete language, a superseded requirement, or an assumption that does not fit the new evidence.

Before drafting into a template, inspect every section. Ask what requirement it serves, what source belongs there, whether it applies, and whether the current project needs additional structure. Keep required sections even when content is unavailable, but mark the gap clearly rather than filling space with generic prose.

Reusable components can reduce repeated work, but template-based authoring remains labor-intensive and component reuse pays off only when it is managed deliberately.6 Common formats, controlled text, checklists, and collaborative authoring can improve consistency and shorten development when ownership and review are explicit.1,7 Reuse is safest when content identity, approved context, source support, and update responsibility are controlled. Copy-and-paste reuse without provenance is not a system; it is version drift.

Resolve conflicts explicitly

Conflicts may arise between a target instruction and a house template, between two versions of guidance, between a sponsor preference and a reporting requirement, or between a word limit and the content needed for complete interpretation.

Use a disciplined response:

  1. Confirm that both sources actually apply.
  2. Check version, status, and scope.
  3. Identify whether the conflict is real or whether one source is more specific.
  4. Define the consequence for the document.
  5. Route the decision to the accountable owner.
  6. Record the rationale and affected sections.
  7. Recheck the final document against the resolved rule.

Do not hide conflicts inside stylistic editing. A choice that affects compliance, scientific interpretation, or disclosure deserves a visible decision.

Guidelines improve completeness, not judgment by themselves

Reporting guidelines help writers remember essential items, but they are aids rather than substitutes for judgment and often require application to the specific manuscript.2,4 They do not decide whether the study was well designed, whether a claim is fair, whether a limitation is material, or whether the reader will understand the document. Checklist completion can coexist with poor reasoning.

Use a checklist twice: once while building the Structure, so required content has a home, and again during final review, so the completed text can be tested. Record “not applicable” deliberately. A blank checkbox is ambiguity; a reasoned exclusion is a decision.

Open the full guideline and standards shelf ↗

The section in one breathRecap
  • Classify governing sources before treating them as equivalent.
  • Check applicability by document, design, jurisdiction, audience, target, lifecycle, version, and status.
  • Build a stack that assigns each source an operational role.
  • Translate requirements into sections, checks, or gates.
  • Use templates as controlled scaffolds.
  • Surface conflicts and route them to the right owner.
  • Apply reporting checklists during Structure design and final verification.
  • Consult the current controlling source for live work.
Go deeperCorpus shelf
  • Strategic Scientific and Medical Writing — planning with guidelines and templates, ICH families, IBs, CTD documents, protocols, reports, and papers.
  • Writing High-Quality Medical Publications — ethical and reporting standards, manuscript QC, authorship, and disclosure.
  • EMWA: Regulatory Writing Basics — regulatory document context and writer responsibilities.
  • EMWA: Authors and Authorship — GPP, transparency, and authorship.
  • EMWA: Clinical Trials — trial documents and reporting practice.
  • AMWA Journal: Technology, Plain Language, and Submission Workflows — plain-language consent, program lexicons, submission leadership, and AI implementation.

References

Sources cited on this page, numbered in order of first appearance.

  1. Joubert PH, Rogers SM. Strategic Scientific and Medical Writing: The Road to Success. Springer; 2015.
  2. Leventhal PS. Guidelines for manuscript writing: here to help. Med Writ. 2012;21(2):164-168.
  3. Morley G. Regulatory writing basics. Med Writ. 2014;23(2):81-82. doi:10.1179/2047480614Z.000000000191.
  4. Rogstad TL. Judging the quality of medical literature. AMWA J. 2009;24(4):176-181.
  5. Zhou Q. An overview of the 2022 update of Good Publication Practice (GPP) guidelines: a medical writer's perspective. AMWA J. 2023;38(2):5-9.
  6. Kiran A. Standardizing, simplifying, and scaling medical writing in life sciences: intelligent content creation and reuse. AMWA J. 2019;34(4):147-150.
  7. Panek R, Fernandes S, Meloni M, Morehouse G, Grunspan R. Using innovative tools and lean writing workflow processes to accelerate regulatory document writing. AMWA J. 2024;39(1):46-52.