02Define the Job Before You Touch the Draft

Many weak documents are faithful responses to weak assignments. The request says, “Write a review,” “Turn this study into a paper,” “Prepare the protocol,” or “Make this patient friendly.” The writer begins immediately, only to discover that the target is unknown, the audience is contested, the data are incomplete, authors disagree about the message, or the template arrived after the draft was built.

Start by determining the nature of the document, desired outcome, applicable guidance, target audience, key messages, sources of information, and template.¹ These are not preliminary niceties. Together, they define the writing problem.

Name the document precisely

“Manuscript” is not precise enough. Is it an original research report, narrative review, systematic review, meta-analysis, case report, commentary, or protocol paper? “Summary” is not precise enough. Is it a clinical overview, lay summary, executive summary, study synopsis, advisory-board report, or summary of a body of evidence? “Presentation” is not precise enough. Is it a congress talk, internal decision deck, field-training deck, patient education presentation, or continuing-education activity?

Document identity matters because it changes the expected evidence, structure, governing material, and review path.¹ A narrative review can organize literature around a reasoned thematic argument; a systematic review treats the search and selection process as part of the research method. A protocol describes intended conduct; a study report explains actual conduct and results. A plain-language summary must preserve scientific meaning while changing the assumed vocabulary and explanatory burden.

If the output has no settled label, describe it operationally: who will receive it, what they will do with it, what information it must contain, what source package it draws from, and what format it must become. That description can route the work even before the final name is chosen.

Define the desired outcome

The desired outcome is not simply “a completed document.” It is the change in understanding, decision, or action the document should enable.¹ A journal paper should make a contribution clear enough for editors and readers to judge. A protocol should make intended conduct reproducible and reviewable. A study report should provide an accurate account of methods, deviations, results, and interpretation. A patient communication should help a non-specialist understand information relevant to participation, treatment, safety, or results.

Outcome definition sharpens inclusion. If a section does not help the reader reach the intended understanding or satisfy a governing requirement, it may not belong. Outcome definition also exposes conflict. A sponsor may want a persuasive message; a journal requires balanced reporting; an author wants methodological detail; a reader wants the clinical implication. The brief should record these pressures rather than allowing them to surface as late-stage edits.

Put yourself in the reader's place

Imagine the target reader's response before choosing the level of detail or the argument's order.¹ This is more demanding than naming an audience category. “Clinicians” may include generalists and specialists with different knowledge. “Patients” is not a single literacy level, language, culture, experience, or information need. “Regulators” read within a formal review task. “Authors” may focus on scientific reputation, while journal editors focus on fit, novelty, methods, and reader value.

Ask what the reader already knows, what they need explained, what decision they face, what might confuse them, what might make them distrust the document, and what evidence they will expect to inspect. Audience affects terminology, detail, sentence structure, visual design, ordering, and the amount of context required. It should not change the underlying facts.

For public-facing material, involve intended readers where possible. User testing is performance based: it shows how a document behaves in the hands of its audience and reveals weaknesses that expert review or a readability formula may miss.² Consent-document teams can combine plain language, validated glossaries, and literacy review.³ The reader is not an abstract persona when the work can include real reader input.

Treat key messages as hypotheses

Key messages help organize a document. They can also become a source of bias if accepted before the evidence is examined. The safest form is provisional: “The team expects the evidence to show X; confirm the scope, strength, and qualifications.” This wording lets the message guide investigation without ordering the writer to prove it.

Separate three categories in the brief:

• Required facts: Items that must be present because of the document's purpose or governing material.
• Proposed messages: Interpretations or emphases the team wants the evidence to support.
• Open questions: Issues the evidence, authors, statisticians, reviewers, or authorities still need to resolve.

Then connect each proposed message to its anticipated evidence. If the evidence is missing, weak, contradictory, or exploratory, record that state. A message without a plausible source path is not ready to become a drafting instruction.

Map the people around the document

Medical writing is collaborative, but collaboration without roles becomes comment accumulation. Identify the people who supply evidence, interpret science, decide scope, qualify for authorship, review language, check statistics, approve compliance, perform QC, and authorize release. The same person may hold several roles; the important point is that the roles are visible.

For publications, discuss authorship early and revisit it as contributions develop.⁴ For regulatory documents, distinguish document contributors from formal signatories or accountable functions.⁵ For patient material, include the people who can evaluate comprehension and relevance. For statistics-heavy work, identify the statistician who can answer analysis questions rather than relying on secondhand interpretation.

Name the decision owner for predictable conflicts: target journal, key message, analysis wording, author order, inclusion of a limitation, acceptance of a review comment, or release with an open item. If nobody owns the decision, the writer becomes the accidental adjudicator.

Define scope and boundaries

Scope is the agreement about what the project includes and excludes. It should cover the output, source package, therapeutic or scientific boundaries, time range for literature, number and type of visuals, reference volume, review rounds, expected rewrite depth, final format, and any associated files such as response letters or claim matrices.

Scope also protects quality. Fact-checking and source verification are not equivalent to copyediting. A “light edit” cannot safely include reconstruction of an incoherent analysis narrative unless the timeline and authority permit it. Plain-language adaptation is not merely shortening sentences. A systematic review cannot be produced from an undocumented convenience set of papers and still be represented as systematic.

Record what the writer is not being asked to decide. A writer may explain an analysis but not select it. A writer may flag a regulatory interpretation but not act as legal counsel. A writer may identify an authorship problem but not unilaterally resolve the author list. Boundaries make escalation professional rather than evasive.

Build the project timeline around decisions

A timeline made only of draft dates is too weak. Good milestones correspond to changes in project state: brief accepted, sources received, evidence gaps reviewed, target confirmed, Structure accepted, first section completed, data checks complete, author review reconciled, QC scope confirmed, final export validated.

A writing project moves through initiation, planning, execution, monitoring and control, and closure; risk identification and close-out documentation are core work, not ceremony.⁵ Clear workflows, roles, responsibilities, review stages, and collaboration rules reduce avoidable delay and ambiguity.⁶ The vocabulary matters less than the discipline: the project needs a plan, a way to detect drift, and a clear closing state.

Plan review time according to document risk and length. A long study report cannot receive a reliable data and consistency check in an implausibly short window. A multi-author paper needs time to reconcile comments rather than merely collect them. A patient document needs time for user input if that input is part of the method.

Capture the working brief

A useful one-page project frame contains:

The brief should remain editable while the project is being framed. Once accepted, changes should be visible. A shifting target is manageable when it is named; it is destructive when it silently rewrites the work.