03Build the Project Dossier

Medical writers often receive a pile: protocol, amendments, statistical analysis plan, tables, figures, listings, study report, slide deck, selected papers, author notes, a journal link, a prior manuscript, and an email containing the actual instruction. The pile may be rich in information and poor in control.^1,2

The dossier is the organized body of material from which the document will be built and defended. Its purpose is not aesthetic file management. It is to let the writer answer, quickly and accurately, “What source should govern this decision?” Version status, finality, and completeness determine whether an apparently relevant file can safely support the draft.¹

Classify by role, not extension

A PDF tells you how a file is stored, not what it means. The same format may contain a protocol, article, guidance document, template, prior deliverable, or scanned comments. Classify sources by their role in the project:

• Evidence: Material that supports scientific, medical, statistical, operational, or factual claims.
• Directive: Material that instructs the work, such as a brief, authority guidance, journal instructions, SOP, approved terminology, or review decision.
• Template or exemplar: Material that shapes form, house style, sequence, or expected level of detail.
• Working record: Decisions, queries, correspondence, review comments, search logs, and version notes.
• Deliverable: The document being produced and its controlled derivatives.
• Excluded material: Content intentionally kept outside the evidence path because it is superseded, irrelevant, unverified, or prohibited.

Add domain-specific roles beneath those broad functions. A clinical-study project may contain a protocol, amendments, SAP, CSR, TFLs, patient narratives, case-report forms, registry information, and results slides. A narrative review may depend on a curated literature set, clinical-practice guidance, seminal papers, and expert input. A device evidence project may draw on evaluation plans, prior reports, state-of-the-art literature, post-market data, risk files, and device descriptions. The deep-dive pages expand these patterns.

One source can have several jobs

A clinical study report can supply methods, results, safety context, deviations, and appendices. It is a pivotal resource for industry-supported manuscripts and may change as analyses and reporting mature, so updates must be tracked.³ It may also reflect amendments and analysis decisions that require comparison with the final protocol and SAP. A published paper can provide background evidence, a model for journal structure, and a source of references, but those roles should not be confused. An old deliverable can be a style exemplar without becoming evidence for a new claim.

Allowing several roles prevents false simplification. It also creates a duty to state which role is active at the point of use. “Use the prior manuscript” might mean copy its tone, inherit its references, preserve its terminology, or update its conclusions. Those are very different instructions.

Record identity and provenance

For each material source, capture enough identity to distinguish it from similar or superseded versions:

• Title or descriptive name
• Source type and project role
• Author, owner, or originating function
• Version, date, and status
• Relationship to other versions or amendments
• Access level and confidentiality
• Whether full text or only metadata/abstract is available
• Whether it can be cited publicly, used only as project context, or used only as an exemplar
• Any known quality, conversion, OCR, or completeness problem

This can be lightweight for a small project. The point is not to create a database for its own sake. The point is to prevent “final,” “final 2,” and “final approved” from silently governing different sections. Shared repositories, explicit naming conventions, and one controlled master reduce the risk of comments being lost or applied to the wrong version.^2,4

Establish the source-of-truth hierarchy

Different sources may disagree because they describe different project states. The protocol may define a planned endpoint; an amendment may change it; the SAP may operationalize it; the CSR may describe what happened; a table may present the analyzed result; a slide may simplify it for discussion. The writer needs to know which source governs which question. CSR quality depends on coordinated review of the statistical analysis plan, final data, and validated outputs, with data issues resolved before results enter the narrative.⁵

Create a hierarchy by question, not one universal ranking. For intended study conduct, the final protocol and applicable amendments may govern. For prespecified analysis, the final SAP matters. For numerical reporting, validated outputs may govern. For interpretation, the document may require integration of results, study design, literature, and expert review. For wording and format, a current target instruction or controlled template may govern.

When two authoritative sources conflict, do not resolve the difference by choosing the more convenient one. Log the conflict, identify the owner, and keep the affected drafting area open until the decision is made.

Separate public citation from project traceability

Published literature normally enters a public reference list. Client materials, protocols, tables, analysis plans, prior drafts, and internal decisions often support the work without belonging in that reference list. Both kinds of sources matter.

The dossier should therefore distinguish:

• Citable literature: Sources intended to appear in formal references when used.
• Context evidence: Project materials that support claims, numbers, methods, and decisions but may be represented through internal traceability rather than public citation.
• Directive sources: Items that explain how to write but do not support a scientific claim.
• Exemplars: Items that influence form or style without serving as evidence.

This separation prevents a common mistake: treating anything not destined for the bibliography as if it does not need traceability.

Make gaps first-class project information

A missing file is not only an inconvenience. It changes what can be written. Record gaps with a useful status:

• Missing: Expected and not supplied.
• Partial: Some of the role is covered, but material pieces are absent.
• Inaccessible: Known to exist but not available to the writer.
• Conflicting: Available sources disagree.
• Unverified: Present but not yet authenticated or quality checked.
• Deferred: Intentionally postponed to a later gate.
• Not applicable: Considered and deliberately excluded.

State the consequence. “Final SAP missing” is less useful than “prespecification status of subgroup analyses cannot be confirmed until the final SAP is available.” A gap becomes manageable when it names the blocked decision.

Thin dossiers do not always stop work. The writer can build a Structure, draft stable background, or mark exact placeholders. But the document should not conceal the gap by converting an assumption into a fact. If a source is missing, under revision, or not final, raise the gap early enough to avoid a late trail of “unable to verify” comments.¹

Inspect conversion and readability

Medical-writing sources arrive in Word documents, spreadsheets, slide decks, PDFs, reference exports, images, scanned pages, and systems. Conversion can introduce errors: broken symbols, merged columns, lost footnotes, missing superscripts, malformed tables, or OCR mistakes. A source can look present while being unusable for precise verification.

Spot-check extracted content against the original where stakes are high. Pay particular attention to minus signs, inequality symbols, decimal points, superscripts, Greek letters, units, table alignment, footnotes, and patient-level identifiers. If a source cannot be reliably searched, note the limitation and plan a manual inspection path. Source verification requires access to everything used to create the claim, not only the most convenient summary.^1,6

Produce the dossier readback

Before building the document Structure, summarize the dossier in plain language:

“The project contains the final protocol and two amendments, the final SAP, validated efficacy and safety tables, a draft CSR, 46 citable references of which 39 have full text, the target journal's author instructions, and a prior manuscript used only for style. The CSR and one results slide disagree on the analysis population for a secondary endpoint. Patient narratives are not yet available. The subgroup analysis is present in a table but its prespecification status still needs confirmation.”

This readback does three things. It demonstrates understanding, invites correction before drafting, and exposes the decisions the Structure must carry. Clear roles, source access, and planned decision points make collaborative work faster to review and easier to recover when the project changes.²