Document Development Reflex Area
2026-09-29
Table of Contents
- Determining Whether a Document Is the Right Response
- Defining the Document's Purpose and Intended Outcome
- Understanding the Intended Readers and Users
- Identifying the Primary Reader or User
- Distinguishing the Reader From the Requester, Sponsor, Reviewer, and Approver
- Understanding the Conditions in Which the Document Will Be Used
- Handling Several Audiences With Competing Needs
- Developing a Document When the Actual Audience Is Not Yet Clear
- Testing What the Reader Can Reasonably Be Expected to Know Already
- Anticipating the Reader's Main Questions, Concerns, and Objections
- Understanding Whether the Document Will Be Read, Referenced, Acted On, Approved, or Audited
- Accounting for Accessibility, Language, and Other Reader Needs
- Deciding When Different Audiences Need Different Versions
- Clarifying Requirements, Constraints, Roles, and Approval
- Surfacing Requirements That Have Been Assumed but Not Stated
- Distinguishing Binding Requirements From Preferences and Conventions
- Reconciling Conflicting Requirements From Different Sources
- Clarifying Scope, Length, Deadline, Format, Tone, and Evidence Expectations
- Working Within Confidentiality, Security, Privacy, or Tool Constraints
- Clarifying Who Owns, Contributes to, Reviews, and Approves the Document
- Establishing the Review and Approval Path Before Major Work Begins
- Working With an Infeasible Combination of Scope, Time, Evidence, and Format Constraints
- Responding to Requirements That Change During Development
- Choosing the Document Type and Governing Conventions
- Developing the Central Idea, Question, or Proposition
- Defining Scope and Content Boundaries
- Planning Research and Evidence Needs
- Finding and Gathering Sources and Material
- Evaluating Sources and Evidence
- Organizing Research, Notes, and Evidence Traceability
- Synthesizing Information and Evidence
- Developing Claims, Explanations, and Arguments
- Testing Assumptions, Alternatives, and Uncertainty
- Developing Conclusions, Judgments, and Recommendations
- Designing the Document Architecture
- Drafting the Document
- Developing Sections, Paragraphs, and Continuity
- Calibrating Detail, Explanation, Examples, and Qualification
- Designing Tables, Figures, Lists, and Other Supporting Elements
- Managing Citations, References, and Attribution
- Revising Substance, Scope, and Reasoning
- Revising Structure, Coherence, and Consistency
- Editing for Clarity, Concision, Style, and Language
- Collaborating and Integrating Multiple Contributors
- Reviewing, Incorporating Feedback, and Managing Approval
- Controlling Versions, Decisions, and Document Status
- Final Verification and Proofreading
- Verifying Material Factual Claims Before Finalization
- Checking That Citations Actually Support the Claims They Accompany
- Performing a Whole-Document Consistency Check
- Confirming That All Required Content Is Present
- Verifying Names, Numbers, Dates, Quotations, and Other High-Risk Details
- Testing Links, Cross-References, Contents Entries, and Internal Navigation
- Checking Final Numbering, Formatting, Tables, Figures, and Captions
- Performing a Final Accessibility Check
- Reviewing the Actual Exported or Rendered Artifact for Production Errors
- Proofreading After the Last Substantive Change
- Preparing the Document for Release and Use
- Adapting and Reusing Documents for New Purposes and Contexts
- Maintaining, Updating, Replacing, and Retiring Documents
Determining Whether a Document Is the Right Response
Responding to a Document Request When the Underlying Need Is Unclear
- What prompted the request for a document in the first place?
- What problem, decision, action, or information need is supposed to improve because the document exists?
- Who is experiencing the underlying need, and what are they currently unable to do?
- Why has a document been proposed as the response rather than another form of action?
- What important facts about the underlying need are still unclear?
- What would happen if the requested document were produced exactly as specified but the underlying need remained unresolved?
- How can the underlying need be stated clearly enough to test whether a document is actually the right response?
Checking Whether an Existing Document Already Meets the Need
- What existing documents already address some or all of the need?
- What was each existing document originally intended to accomplish?
- How well does the most relevant existing document support the current use?
- Which parts are still accurate, authoritative, and usable?
- What material gaps, outdated content, or usability problems remain?
- Would correcting those weaknesses be simpler and clearer than creating another document?
- What evidence would justify creating a new document despite the existing one?
Deciding Between Creating a New Document and Updating an Existing One
- How closely does the new need relate to the purpose of the existing document?
- Would the required changes preserve the existing document's basic identity or fundamentally change it?
- How much of the existing content remains valid and useful?
- Would creating a separate document produce duplication, conflicting sources of truth, or unnecessary navigation?
- Would updating the existing document create confusion for readers who rely on its current scope or status?
- What version, approval, or maintenance consequences follow from each option?
- Which choice creates the clearest and most maintainable authoritative document landscape?
Recognizing When the Problem Is Not Actually a Documentation Problem
- What observable problem is the document expected to solve?
- Is the problem caused by missing information, or by behavior, incentives, authority, process, capability, resources, or another factor?
- What evidence shows that inadequate documentation is materially contributing to the problem?
- What non-document interventions could address the underlying cause more directly?
- What would a document realistically be able to change, and what would remain outside its influence?
- Could a document still play a useful supporting role alongside another intervention?
- What should be addressed before investing in substantial document development?
Determining Whether a Decision Must Be Made Before a Document Can Be Developed
- Which parts of the proposed document depend on a choice that has not yet been made?
- What materially different versions of the document would result from different decisions?
- Who has authority to make the unresolved choice?
- Which content can be developed responsibly before that decision is made?
- What assumptions would have to be introduced if drafting continued without a decision?
- What risk would arise if those assumptions were later mistaken for an approved position?
- What decision or confirmation is needed before the document can proceed on a reliable basis?
Testing Whether a Document Can Realistically Produce the Intended Outcome
- What specific outcome is the document expected to cause or support?
- What would readers have to understand, decide, or do for that outcome to occur?
- Do the intended readers actually control the actions or decisions needed?
- What external dependencies must also be satisfied for the document to have the intended effect?
- What evidence supports the assumption that a document can materially influence the outcome?
- Where could a strong document still fail because the real constraint lies elsewhere?
- What more realistic role should the document play if it cannot produce the full intended outcome by itself?
- What capability does the underlying need actually require?
- Would people benefit most from persistent reference material, direct interaction, training, a decision, a process change, a tool, or another intervention?
- How important is it for the information or reasoning to remain available after the immediate interaction?
- Does the situation require explanation and reference, or real-time clarification and adaptation?
- How consequential would misunderstanding or inconsistent execution be?
- Would a combination of a document and another intervention work better than either alone?
- Which response best addresses the actual need with the least unnecessary complexity?
Working With a Document That Is Required Even When Another Approach Might Work Better
- What rule, authority, process, or stakeholder requirement makes the document mandatory?
- What minimum content and form must the required document contain?
- What underlying need exists beyond satisfying the formal requirement?
- Where is the required document genuinely useful, and where are its limitations?
- What complementary action could address needs the document cannot meet?
- How can the document remain proportionate rather than expanding to compensate for unrelated problems?
- How should the required artifact and any additional intervention relate to each other?
- Which documents currently contain substantially overlapping information?
- What distinct purpose or audience, if any, justifies each document's existence?
- Where have duplicated facts, instructions, definitions, or decisions begun to diverge?
- Which document is supposed to be authoritative when the versions disagree?
- Would consolidation make the information easier to maintain and use?
- Where should separate documents remain but refer back to a common authoritative source?
- What transition would reduce duplication without breaking legitimate existing uses?
Recognizing When a Requested Document Is Premature
- What prerequisite decision, evidence, agreement, or definition is still missing?
- Which parts of the document would have to be invented or heavily assumed if development started now?
- How likely are the unresolved matters to change the document's purpose, scope, reasoning, or structure?
- What rework or confusion could result from developing the document too early?
- Is there useful preparatory work that can proceed without pretending the document is ready to be developed?
- What conditions would indicate that the request has become mature enough to proceed?
- How should the current state be communicated so delay is understood as dependency management rather than inaction?
Defining the Document's Purpose and Intended Outcome
Clarifying Why the Document Needs to Exist
- What event, problem, opportunity, requirement, or decision created the need for the document?
- Who needs the document, and why do they need it now?
- What is currently difficult, uncertain, inconsistent, or impossible without it?
- What would happen if no document were created?
- What contribution should the document make that existing material does not already make?
- Which broader organizational or personal objective does the document support without becoming responsible for that entire objective?
- How can the document's purpose be stated in one clear sentence?
Defining What the Reader Should Understand, Decide, Do, or Be Able to Use
- What should be different for the reader after engaging with the document?
- What must the reader understand correctly?
- What decision, if any, should the document enable?
- What action, task, or process should the reader be able to carry out?
- What information should remain available for later reference or verification?
- Which misunderstandings or missing capabilities would make the document unsuccessful?
- What concrete reader outcome should guide decisions about content and structure?
Separating the Requested Deliverable From the Outcome It Is Supposed to Produce
- What deliverable has been explicitly requested?
- What outcome is the requester ultimately trying to achieve through that deliverable?
- What assumptions connect the requested format to the desired outcome?
- Would the same outcome still matter if the requested document type were unavailable?
- Could a different artifact or intervention support the outcome more effectively?
- Which parts of the requested deliverable are genuine constraints and which are merely the initial proposed solution?
- How should the deliverable be defined once the underlying outcome is made explicit?
Reconciling Several Purposes Within the Same Document
- What distinct purposes is the document expected to serve?
- Which purposes reinforce each other and can naturally coexist?
- Which purposes require different evidence, structures, tones, or levels of detail?
- Where could one purpose make another harder to achieve?
- Which purpose should govern when tradeoffs become unavoidable?
- Could layering, appendices, or clearly separated sections allow compatible secondary purposes to remain?
- At what point would the purposes be better served by separate documents?
Identifying the Primary Purpose When Different Stakeholders Want Different Outcomes
- What does each stakeholder expect the document to accomplish?
- Which stakeholder needs relate directly to the document's intended use?
- Who has legitimate authority to define the document's primary purpose?
- Which stakeholder expectations are compatible with a shared primary purpose?
- Which expectations would pull the document in materially different directions?
- Which secondary outcomes can be supported without weakening the primary one?
- What primary purpose should govern scope, evidence, architecture, and revision decisions?
Connecting the Document to the Decision, Action, or Process It Supports
- Where does the document enter the larger decision, action, or workflow?
- What information or reasoning must it provide at that point?
- Who receives the document, and what are they expected to do with it next?
- What upstream inputs must be available before the document can perform its role?
- What downstream work depends on the document being correct and usable?
- What happens if the document arrives late, is ignored, or is misunderstood?
- How should its content and structure change once its exact role in the larger process is clear?
Defining What Successful Use of the Document Would Look Like
- What observable behavior or outcome would indicate that the document is working?
- What should readers be able to find, understand, evaluate, decide, or do?
- What kinds of errors or confusion should the document prevent?
- How would successful use differ from simply having delivered the artifact?
- What feedback or downstream evidence could reveal whether the document is actually useful?
- What level of performance is necessary for the document to be considered good enough?
- Which success criteria should guide review and finalization?
Understanding the Consequences of the Document Being Misunderstood or Ignored
- What could happen if readers misunderstand the document's central message?
- Which parts of the document carry the greatest consequence if interpreted incorrectly?
- What happens if intended users never consult the document at all?
- Which misunderstandings are most plausible given the audience and context?
- Where would additional clarity, emphasis, redundancy, or confirmation be justified by the risk?
- What consequences require stronger review, evidence, accessibility, or approval?
- How should the potential cost of misunderstanding change the development standard?
Revisiting the Purpose After Research or Drafting Changes the Original Understanding
- What has been learned that materially changes the original understanding of the need?
- Does the original purpose still describe the most useful job for the document?
- Has the intended reader, decision, scope, or outcome changed?
- Which existing sections were developed under assumptions that no longer hold?
- What parts of the document remain valid despite the change in purpose?
- What downstream changes to research, architecture, drafting, or review now follow?
- How should the revised purpose be stated before development continues?
Recognizing When the Stated Purpose and Actual Use Do Not Match
- What purpose is officially stated for the document?
- How is the document actually expected to be used in practice?
- What evidence suggests that the real use differs from the stated one?
- Would the current content be adequate and appropriate for that actual use?
- What risks arise if a document developed to inform is later used to approve, justify, direct, audit, or record?
- Can the stated purpose and actual use be reconciled without distorting the document?
- Should the purpose, content, governance, or intended use be changed to remove the mismatch?
Understanding the Intended Readers and Users
Identifying the Primary Reader or User
- Who most directly needs to understand, evaluate, decide, act, or refer to the document?
- What specific task or responsibility makes that person or group the primary user?
- How does the primary user's need differ from the interests of everyone else who may read the document?
- What level of subject knowledge and authority does the primary user have?
- What would make the document unusable for this reader even if other stakeholders liked it?
- Which secondary audiences also need to be accommodated?
- Whose needs should govern when audience preferences conflict?
- Who requested the document?
- Who is sponsoring or accountable for the work?
- Who will actually read or use the document?
- Who will review its substance or quality?
- Who has authority to approve or release it?
- Where do these roles have different expectations or incentives?
- Which role should govern each decision about purpose, usability, evidence, and approval?
Understanding the Conditions in Which the Document Will Be Used
- In what environment will readers encounter the document?
- Will they read it continuously, skim it, search it, consult it during work, or return to it intermittently?
- How much time and attention will readers realistically have?
- What devices, formats, or access conditions will shape how the document is used?
- Will readers need to use the document under pressure or while performing another task?
- What information must be especially easy to locate because of those conditions?
- How should architecture, navigation, length, and presentation adapt to the actual use environment?
Handling Several Audiences With Competing Needs
- Which distinct audiences need to use the document?
- What does each audience need to understand or accomplish?
- Which information is common and useful to all of them?
- Where do their required depth, terminology, evidence, or emphasis conflict?
- Could layered structure allow different audiences to navigate to the level they need?
- Would separate versions reduce complexity or create unacceptable inconsistency?
- Which audience should control the main reading path when all needs cannot be optimized equally?
Developing a Document When the Actual Audience Is Not Yet Clear
- What plausible audiences could ultimately receive or use the document?
- What evidence exists about who the likely primary audience will be?
- Which audience assumptions would materially change the document's development?
- What design choices can remain flexible until the audience is confirmed?
- Which choices would create expensive rework if made on the wrong assumption now?
- What information should be obtained before audience-specific drafting proceeds?
- What provisional audience assumption is safe enough to use if work cannot wait?
Testing What the Reader Can Reasonably Be Expected to Know Already
- What background knowledge does the document currently assume?
- Which terms, concepts, events, systems, or prior decisions are essential to understanding it?
- What evidence supports the assumption that readers already know those things?
- Which assumed knowledge is likely to vary significantly across the audience?
- What misunderstanding would arise if an assumption about prior knowledge were wrong?
- Which concepts need explanation, definition, linking, or reference?
- How can the document provide enough context without repeating material the intended reader genuinely knows?
Anticipating the Reader's Main Questions, Concerns, and Objections
- What will the reader most want to know when approaching the document?
- Which claims or recommendations are likely to attract the greatest scrutiny?
- What evidence will the reader expect before accepting the main conclusion?
- What practical concerns could prevent the reader from acting on the document?
- Which credible objections or alternative interpretations are likely to arise?
- Which reader questions should be answered directly in the main document rather than left implicit?
- How should anticipated concerns influence the order and emphasis of the material?
Understanding Whether the Document Will Be Read, Referenced, Acted On, Approved, or Audited
- What is the document's primary mode of use?
- Will readers consume it from beginning to end or enter at particular sections?
- Does the document need to support immediate action or mainly later reference?
- Will a reviewer or approver need to trace claims and decisions back to evidence?
- Could the document later be examined as a record of what was known or decided?
- What navigation, traceability, detail, and control does the intended mode of use require?
- Which secondary modes of use also need to be supported without weakening the primary one?
Accounting for Accessibility, Language, and Other Reader Needs
- What accessibility needs should be expected among intended users?
- Will any readers rely on screen readers, keyboard navigation, magnification, captions, or other assistive technologies?
- Do language proficiency or literacy levels affect how the document should be written?
- Are there mandatory accessibility or inclusive-content requirements?
- Which tables, figures, headings, links, or formatting choices could create avoidable barriers?
- Would an alternative representation or version materially improve access for some users?
- How will accessibility be tested rather than merely assumed?
Deciding When Different Audiences Need Different Versions
- How materially do the audiences differ in purpose, knowledge, authority, or required detail?
- What information should remain identical across every version?
- Which content genuinely needs to change for a particular audience?
- Would one combined document become unnecessarily long or confusing?
- What risk of contradiction or semantic drift would separate versions create?
- Which version should remain the authoritative source for shared facts and reasoning?
- What criteria justify creating separate versions rather than using one layered document?
Clarifying Requirements, Constraints, Roles, and Approval
- What does the request explicitly require the document to contain?
- What limits are stated for scope, length, format, timing, evidence, or audience?
- Which deliverables, attachments, or supporting elements are mandatory?
- What review, approval, or submission requirements are explicitly specified?
- Which requirements come from a formal source rather than informal preference?
- Where is the wording ambiguous enough to require clarification?
- How can the explicit requirements be captured so they remain visible throughout development?
Surfacing Requirements That Have Been Assumed but Not Stated
- What expectations are people acting on even though they were never explicitly documented?
- Which prior versions, templates, accepted examples, standards, or workflows suggest additional requirements?
- Who appears to expect these requirements to be followed?
- Which inferred requirements are strongly supported and which are only plausible assumptions?
- What consequence would follow if an assumed requirement were ignored?
- Which inferred requirements need confirmation before substantial work depends on them?
- How should confirmed requirements, inferred requirements, preferences, assumptions, and unresolved questions be distinguished?
Distinguishing Binding Requirements From Preferences and Conventions
- What is the source of each apparent requirement?
- Who has authority to impose or change it?
- What happens if the requirement is not followed?
- Is it mandatory, negotiable, conventional, preferred, or merely inherited from prior practice?
- Which conventions are useful even though they are not binding?
- Where might treating a preference as mandatory unnecessarily constrain the document?
- How should each constraint be classified before development proceeds?
Reconciling Conflicting Requirements From Different Sources
- Which requirements are in conflict?
- Where does each requirement come from, and what authority does its source have?
- Are the requirements truly incompatible or merely expressed differently?
- What underlying purpose is each requirement intended to protect?
- Is there a hierarchy, governing rule, or responsible authority that resolves the conflict?
- What tradeoff or exception would be necessary if both cannot be satisfied?
- How should the resolution be recorded so the conflict does not reappear later?
- What scope is expected, and which boundaries remain unclear?
- Is the requested length a hard limit, target, convention, or preference?
- Which deadline applies to drafting, review, approval, submission, or actual use?
- What format is required, and what practical reason lies behind it?
- What tone or level of formality follows from the document's role and audience?
- What level and type of evidence will be considered sufficient?
- Which of these expectations still need negotiation or confirmation before they shape the work?
- What information in the document or its source material is sensitive, restricted, personal, or confidential?
- Who is permitted to access that information?
- Which tools, systems, AI services, or collaboration environments are approved for handling it?
- What material must be withheld, anonymized, redacted, or transformed before being shared?
- Do source restrictions affect what can be quoted, cited, reproduced, or externally verified?
- What risks arise from copying material into uncontrolled drafts, messages, or tools?
- What working process will protect the information without making responsible development impossible?
Clarifying Who Owns, Contributes to, Reviews, and Approves the Document
- Who is accountable for the document as a whole?
- Who is responsible for contributing particular knowledge or sections?
- Who has subject-matter authority over technical content?
- Who can edit wording or structure without changing substantive decisions?
- Who is expected to review the document, and for what?
- Who has authority to approve the final artifact or underlying decision?
- Where do unclear or overlapping roles need to be resolved before work continues?
Establishing the Review and Approval Path Before Major Work Begins
- What stages of review will the document require?
- Which reviewers are needed at each stage?
- What should each reviewer be evaluating rather than commenting on generally?
- In what order should specialist, substantive, editorial, risk, and approval reviews occur?
- What dates or dependencies constrain the review sequence?
- Who resolves disagreements or decides when review is complete?
- What approval must be obtained before the document can move into its intended use?
- Which combination of constraints makes the current request infeasible?
- What work would actually be required to satisfy the stated scope and quality standard?
- Which constraints are genuinely fixed and which can be negotiated?
- What would have to be reduced, delayed, simplified, or left uncertain to meet the deadline?
- What minimum viable document could still serve the essential purpose responsibly?
- What risks would be created by pretending the original requirements can all be met?
- What explicit tradeoff or revised commitment needs to be agreed before development proceeds?
Responding to Requirements That Change During Development
- What requirement has changed, and who authorized the change?
- Why did the requirement change?
- Which completed or planned work is affected?
- Does the change alter the purpose, audience, scope, evidence burden, architecture, or approval path?
- What existing decisions remain valid despite the change?
- What new work, rework, or schedule consequences follow?
- How should the revised requirements be baselined so older expectations do not continue shaping the document?
Choosing the Document Type and Governing Conventions
Choosing a Document Type Based on What the Reader Needs to Do
- What does the reader need to understand, decide, perform, approve, reference, or verify?
- Which document forms naturally support that kind of use?
- Does the reader need continuous reasoning, structured reference, step-by-step instruction, comparison, or formal record?
- What evidence, navigation, and level of detail does each plausible form support well?
- Which document type would impose unnecessary structure or convention on the material?
- What organizational or professional expectations constrain the available choices?
- Which form best supports the actual reader task rather than merely matching a familiar label?
Questioning Whether the Requested Document Type Is the Right One
- Why was this particular document type requested?
- What underlying outcome is the requester trying to achieve?
- Which features of the requested form support that outcome?
- Where does the requested form work against the reader's actual needs?
- What alternative document types would better fit the intended use?
- Is the requested form mandatory or can it be renegotiated?
- If the form cannot change, how can its weaknesses be mitigated without ignoring its requirements?
- Which elements are necessary for the document type to perform its professional or practical function?
- Which elements exist mainly because of inherited visual or stylistic convention?
- What standard, process, or reader need makes a particular section or element substantive?
- What would happen if a conventional feature were changed or omitted?
- Which formatting conventions improve familiarity or usability even though they are not mandatory?
- Where could following convention mechanically distort the document's reasoning or content?
- How should genuine genre requirements and optional presentation conventions be documented separately?
Working Within a Mandatory Template
- Which fields, sections, or formats in the template are genuinely mandatory?
- What purpose is each required element intended to serve?
- Which parts of the template fit the actual document well?
- Which required sections appear irrelevant, duplicative, or poorly matched to the reasoning?
- What important content does the document need that the template does not explicitly provide for?
- How much flexibility exists to combine, extend, cross-reference, or adapt template sections?
- How can the template be satisfied without allowing its boxes to substitute for substantive thinking?
Working With a Conventional Structure That Does Not Fit the Document's Actual Use
- What conventional structure would normally be expected for this document type?
- Which parts of that structure do not support how the document will actually be used?
- What reader tasks or reasoning dependencies require a different arrangement?
- Which conventional elements still need to be preserved for recognition, compliance, or review?
- Where can sections be reordered, combined, renamed, or layered without violating substantive requirements?
- What risks arise from departing from the familiar structure?
- How can the adapted structure be tested against both reader use and governing conventions?
- What distinct functions does the document need to perform?
- Which established document forms partially fit those functions?
- Where does each established form fail to represent the actual need?
- What is the simplest structure that can support all essential functions?
- Are there useful precedents without treating them as mandatory templates?
- What confusion could arise if the resulting artifact is given a misleading familiar label?
- How should the new or hybrid form be explained so readers know how to use it?
Identifying Professional, Organizational, or Regulatory Conventions That Apply
- Which professions, organizations, standards, or regulatory regimes govern the document?
- What authoritative sources define the applicable conventions?
- Are those conventions current and applicable to this exact document and context?
- Which requirements affect substance, evidence, terminology, structure, or presentation?
- Which conventions are recommendations rather than mandatory rules?
- Where do multiple governing conventions conflict or require interpretation?
- What specialist review is needed before relying on an uncertain convention?
Determining Whether the Document Type Changes the Required Evidence or Approval
- What evidentiary burden normally accompanies this kind of document?
- Does the document make claims, recommendations, commitments, or instructions that increase the required support?
- What traceability must be available to readers, reviewers, or auditors?
- Which specialist reviews are expected because of the document type?
- What authority is required to approve or issue the document?
- Would a different document type materially reduce or increase those requirements?
- What evidence and approval standard should govern once the form is chosen?
Working in an Unfamiliar Document Genre Without Copying an Example Mechanically
- What job is this unfamiliar document type expected to perform?
- Which structural features appear consistently across authoritative examples or guidance?
- Which features are functional requirements and which are incidental choices made by individual examples?
- What terminology or conventions require subject-matter clarification?
- Which parts of a precedent are inappropriate for the current audience, purpose, or context?
- How can the document be designed from its actual requirements rather than by imitating one example?
- What expert or user review would confirm that the result functions credibly within the unfamiliar genre?
Deciding When One Hybrid Document Should Become Several Separate Artifacts
- What distinct functions is the hybrid document currently trying to perform?
- Do those functions serve the same audience at the same point of use?
- Are different sections requiring incompatible structures, levels of detail, tones, or approval?
- Has combining the functions made the document harder to navigate or maintain?
- Which information must remain common and authoritative if the document is split?
- How could separate artifacts reference each other without creating duplication or contradiction?
- What threshold would justify maintaining several coordinated documents instead of one increasingly complex hybrid?
Developing the Central Idea, Question, or Proposition
Turning a Broad Topic Into a Developable Document Idea
- What broad subject has the document been asked to address?
- Which specific problem, tension, decision, relationship, or unexplained pattern within that subject appears most consequential?
- What part of the topic can the document realistically illuminate rather than merely describe?
- Which potential directions are too broad, peripheral, or weakly connected to the intended use?
- What existing knowledge or evidence already suggests a promising focus?
- What would make the chosen idea distinctive enough to justify developing the document?
- How can the broad topic be restated as a focused idea that can guide research and reasoning?
Converting an Initial Request Into a Governing Question
- What is the request ultimately asking the document to establish, explain, assess, or decide?
- Which uncertainty sits underneath the requested deliverable?
- What question would need a credible answer for the document to fulfill its purpose?
- Is the current question descriptive, explanatory, comparative, evaluative, predictive, or decision-oriented?
- Does the question quietly assume an answer, cause, solution, or preferred option that has not been established?
- What material questions should remain subordinate rather than compete with the governing question?
- How can the governing question be stated so it is focused enough to guide development but open enough to permit an unexpected answer?
Choosing Among Several Plausible Directions
- What materially different directions could the document take from the current starting point?
- What question or contribution would define each direction?
- Which direction best matches the document's purpose and intended use?
- What evidence appears available for developing each option responsibly?
- Which direction depends most heavily on assumptions that have not been tested?
- What would be lost or excluded by choosing one direction over another?
- What basis is strong enough to choose a working direction without pretending the alternatives have been disproved?
Discovering the Main Contribution Hidden in Existing Material
- What recurring finding, tension, distinction, or implication appears across the existing material?
- Which parts of the material seem important but have not yet been connected into a larger point?
- What does the material collectively make possible to understand that individual pieces do not?
- Which apparent themes are merely frequent and which materially affect the document's purpose?
- What conclusion or insight would be missing if the strongest material were simply summarized source by source?
- Is the emerging contribution genuinely supported or being imposed retrospectively on unrelated material?
- How can the document's likely contribution be stated provisionally before the full reasoning is complete?
Developing a Working Proposition Before the Final Conclusion Is Known
- What answer currently appears most plausible to the governing question?
- Which evidence or reasoning gives that proposition its initial credibility?
- What important parts of the proposition remain uncertain or weakly supported?
- What assumptions must hold for the proposition to remain viable?
- What evidence would strengthen, narrow, qualify, or overturn it?
- How can the proposition guide research and architecture without becoming a conclusion that the work is forced to defend?
- What wording keeps the proposition useful while making its provisional status clear?
Testing Alternative Framings Before Committing to One
- What different ways could the same issue reasonably be framed?
- What does each framing treat as the central problem, cause, unit of analysis, or decision?
- Which relevant evidence becomes more or less visible under each framing?
- What assumptions does each framing introduce before the analysis begins?
- Which stakeholders or perspectives are privileged or obscured by each framing?
- Would materially different conclusions become plausible if another framing were adopted?
- Which framing best supports responsible inquiry while remaining open to revision?
Recognizing When the Initial Framing Is Only a Symptom of the Underlying Issue
- What visible problem does the initial framing focus on?
- What conditions or mechanisms could be producing that visible problem?
- What evidence suggests the stated issue may be a consequence rather than the underlying cause?
- Would solving the framed problem leave the deeper issue substantially unchanged?
- What alternative framing becomes possible if attention shifts from symptom to cause?
- How would that change the research questions, evidence needs, or scope?
- What should become the new working problem if the original framing is too superficial?
- What course of action currently appears most promising?
- What problem or objective is the provisional recommendation intended to address?
- What evidence presently supports it?
- Which assumptions about feasibility, effects, costs, risks, or stakeholder behavior remain untested?
- What credible alternatives need to be compared before the recommendation can be defended?
- What evidence or analysis could materially reverse the preferred direction?
- How should the recommendation be described so it guides further development without being mistaken for a settled conclusion?
Clarifying an Idea That Feels Important but Cannot Yet Be Stated Precisely
- What observation or concern makes the idea feel important?
- Which parts of the idea are concrete and which remain vague?
- What terms are carrying several possible meanings?
- What examples or counterexamples help reveal what the idea actually includes?
- What relationship, mechanism, distinction, or consequence might sit at the center of the idea?
- What would need to be known before the idea could become a defensible proposition?
- What provisional formulation is precise enough to work with while remaining open to refinement?
Determining When the Central Idea Is Mature Enough to Guide the Document
- Can the document's governing question or working proposition now be stated clearly?
- Is its significance connected to the document's purpose and intended reader?
- Are the main boundaries of the idea sufficiently understood?
- Are the largest assumptions and uncertainties visible rather than hidden?
- Is there enough plausible evidence to justify developing the idea further?
- Would another round of open-ended ideation materially change the direction, or mainly produce variations on the same idea?
- What should remain provisional as the central idea begins to guide research, architecture, and drafting?
Defining Scope and Content Boundaries
Narrowing a Document That Has Become Too Broad
- What different subjects, questions, or purposes have accumulated inside the current scope?
- Which of them are essential to answering the governing question?
- Which material is merely related rather than necessary?
- Where is breadth preventing adequate depth or evidence?
- What can be excluded without making the main conclusion misleading or incomplete?
- Which excluded topics need only a brief boundary statement or referral elsewhere?
- What narrower scope still allows the document to fulfill its intended purpose responsibly?
Expanding a Scope That Is Too Narrow to Support a Responsible Conclusion
- What conclusion is the current scope expected to support?
- Which relevant factors fall outside the present boundary?
- Could any excluded factor materially change the interpretation or recommendation?
- What necessary context is missing for the reader to understand the issue correctly?
- Does the current scope omit affected populations, time periods, alternatives, dependencies, or consequences?
- How far must the boundary expand before the conclusion becomes responsibly supportable?
- What additional territory should remain excluded even after the necessary expansion?
Separating Core Content, Necessary Context, and Excluded Territory
- What content is indispensable to answering the document's governing question?
- What surrounding context is necessary for readers to interpret that core correctly?
- Which related material may be useful but does not materially affect the document's purpose?
- What topics should be explicitly excluded to prevent later scope drift?
- Where is background material currently being mistaken for core analysis?
- Which excluded areas require acknowledgement because readers may reasonably expect them?
- How can the boundary between core, context, and exclusion be made explicit enough to guide development?
Defining Relevant Time, Geography, Population, Organization, or System Boundaries
- What time period is genuinely relevant to the question being examined?
- Which geographic or jurisdictional boundaries affect the evidence or conclusions?
- What population, organization, system, product, or process is actually in scope?
- Are any current boundaries inherited from convenience rather than substantive relevance?
- What important variation exists just outside the proposed boundary?
- How would expanding or narrowing any dimension change the claims the document could responsibly make?
- Which boundaries should be stated explicitly so readers do not generalize beyond them?
Deciding How Much Adjacent Material the Document Actually Needs
- What adjacent subject appears relevant to the document?
- What specific dependency, interaction, or boundary makes it relevant?
- How much of that subject must the reader understand for the main document to work?
- Where would further treatment stop supporting the document and become a separate subject in its own right?
- Could the adjacent material be summarized, referenced, or moved to supporting material?
- What risk arises from omitting it entirely?
- What is the smallest treatment that preserves the integrity of the main document?
Revising Scope When Research Changes the Understanding of the Problem
- What new evidence has changed the original understanding of the issue?
- Which current scope assumptions no longer hold?
- Has the relevant problem become broader, narrower, or differently bounded?
- Which existing research or draft material now falls outside the revised scope?
- What new evidence or questions become necessary because of the change?
- Does the revised scope still serve the original purpose, or does the purpose also need reconsideration?
- How should the new boundary be recorded before further development proceeds?
Balancing Breadth Against the Depth Needed for the Intended Use
- How broad must the document be to support its intended use?
- Which areas require deep treatment because the reader will rely on them heavily?
- Which areas can be handled at a higher level without creating material misunderstanding?
- Where is added breadth reducing the quality of analysis within the most important territory?
- Where would excessive depth make the document unusable for its actual reader?
- What tradeoff between coverage and depth is justified by the consequence of the document?
- How should research and space be allocated once that tradeoff is explicit?
Stopping Individual Sections From Expanding Beyond the Document's Purpose
- What job is the expanding section supposed to perform?
- Which material directly contributes to that job?
- What content has accumulated because it is interesting rather than necessary?
- Has the section started answering a different question from the document's governing question?
- Does any of the excess material belong elsewhere in the document or in supporting material?
- What would the reader lose if the section were substantially reduced?
- What boundary should govern further additions to the section?
Reconciling Different Stakeholder Expectations About What the Document Should Cover
- What does each stakeholder expect to be included?
- Why does each stakeholder consider that material necessary?
- Which expectations directly support the agreed purpose?
- Which requests would materially expand or redirect the scope?
- Are any expectations driven by accountability, risk, or authority that cannot simply be ignored?
- What content can be accommodated through concise treatment, appendices, or separate artifacts?
- Who should resolve the remaining scope tradeoffs when stakeholder expectations cannot all be satisfied?
Making Important Exclusions and Scope Limitations Explicit
- Which excluded topics could a reasonable reader otherwise assume were considered?
- Why is each material exclusion outside the document's scope?
- Does the exclusion limit how broadly the findings or recommendations can be applied?
- Which unavailable data, inaccessible populations, time limits, or methodological constraints narrow the coverage?
- What wording distinguishes a deliberate boundary from an accidental omission?
- Where should the limitation appear so readers encounter it before overgeneralizing the conclusions?
- What claims need to be narrowed because of the stated exclusions?
Planning Research and Evidence Needs
Turning Document Requirements Into Research Questions
- What must the document establish to satisfy its purpose and requirements?
- Which of those needs can be answered from existing knowledge and which require research?
- What factual, descriptive, causal, comparative, evaluative, or feasibility questions are implied?
- Which questions relate directly to the document's central conclusion or recommendation?
- What questions are necessary only because of a formal requirement or reader need?
- Which research questions can be combined, narrowed, or removed because they would not change the document?
- What research question set gives sufficient coverage without turning research into general exploration of the topic?
Identifying Which Emerging Claims Will Need Evidence
- What claims is the developing document likely to make?
- Which claims are factual rather than interpretive or explicitly judgment-based?
- Which claims are central enough that weak support would undermine the document?
- Which claims are contestable, surprising, quantitative, causal, or consequential enough to require stronger evidence?
- What claims rely on assumptions that should be researched rather than merely stated?
- Which background statements are sufficiently established that extensive sourcing would add little value?
- What evidence burden should be assigned to each material claim before drafting proceeds?
Deciding How Much Research the Consequence of the Document Justifies
- What decisions or actions may depend on the document?
- How costly or difficult to reverse would an error be?
- How much scrutiny is the document likely to receive?
- Which claims carry the greatest practical, legal, financial, safety, or reputational consequence?
- What level of uncertainty is acceptable for the intended use?
- Where would additional research materially reduce consequential uncertainty?
- What research effort is proportionate to the stakes without pursuing impossible certainty?
Choosing the Types of Evidence Needed for Different Questions
- What kind of question is being answered?
- Does the question require authoritative rules, empirical data, direct observation, expert interpretation, lived experience, examples, or another form of evidence?
- What source type is closest to the underlying fact or event?
- Where is synthesis across multiple studies or sources more useful than one primary source?
- What evidence would reveal magnitude, mechanism, variation, feasibility, or experience?
- Which evidence types would be insufficient if used alone?
- What combination of evidence best matches the claims the document may need to make?
- Which claims depend on the present state of a law, policy, market, technology, organization, or other changing condition?
- Which older evidence remains relevant because the underlying mechanism or historical event has not changed?
- How quickly does the subject matter become outdated?
- What date range is appropriate for different parts of the inquiry?
- Could older sources remain useful for background while newer evidence governs current claims?
- What consequences would follow from relying on information that has been superseded?
- What recency standard should be applied to each material research question?
Identifying Authoritative Sources Before Broad Searching Begins
- Which institutions, records, databases, standards, or original documents are likely to have direct authority over the subject?
- What counts as an authoritative source for each major research question?
- Which claims should be checked against primary rather than derivative reporting?
- Are there official repositories or established systematic sources that should be searched first?
- What limitations or incentives might still affect an authoritative source?
- Which secondary sources would add interpretation or context without replacing the authoritative source?
- What initial source map will prevent broad searching from being driven mainly by visibility or search ranking?
Planning How to Look for Counterevidence and Alternative Explanations
- What emerging conclusion or expectation could create confirmation bias?
- What evidence would contradict, narrow, or complicate that conclusion?
- Which alternative explanations deserve deliberate investigation?
- What search terms, source communities, or datasets might surface evidence the initial search would miss?
- Which stakeholders or disciplines are most likely to interpret the issue differently?
- What result would genuinely cause the document's direction to change?
- How will counterevidence be captured so it remains visible during synthesis rather than being discarded as an inconvenience?
Prioritizing Research When Time or Access Is Limited
- Which unanswered questions could most change the document's conclusion or recommendation?
- Which claims carry the greatest consequence if wrong?
- What research can realistically be completed with the available time and access?
- Which sources offer the greatest increase in confidence for the least effort?
- What lower-priority questions can remain uncertain without making the document irresponsible?
- Where should uncertainty be disclosed instead of hidden by weak substitute research?
- What order of research gives the best chance of resolving the most material unknowns first?
Defining When the Research Will Be Sufficient to Move Forward
- Which critical questions must have credible answers before drafting or concluding can proceed?
- What level of evidence is appropriate to the consequence of each claim?
- Have the major relevant source types been examined?
- Has material counterevidence been actively sought?
- Are new sources still changing the understanding or mainly repeating what is already known?
- What important uncertainty will remain even after reasonable further research?
- At what point is additional research unlikely to change the document enough to justify delaying development?
Revising the Research Plan When the Document's Direction Changes
- What changed in the document's purpose, scope, proposition, or emerging conclusion?
- Which existing research questions are no longer material?
- What new questions have become necessary?
- Which sources already gathered remain relevant under the new direction?
- What evidence gaps have been created by the change?
- Does the revised direction require different source types, time periods, populations, or expertise?
- How should the research plan be rebased so effort follows the current document rather than the superseded direction?
Finding and Gathering Sources and Material
Locating the Original or Primary Source Behind a Claim
- Where did the claim first appear in the material currently available?
- Does that source cite or link to an earlier original source?
- What document, dataset, record, study, statement, or event actually generated the underlying information?
- Can the original source be inspected directly?
- Does the original support the claim in the form now being repeated?
- What qualifications or context were lost as the claim passed through secondary sources?
- Which source should the document ultimately rely on and cite?
Finding the Most Current Authoritative Source
- What aspect of the information is capable of changing over time?
- Which authority is responsible for maintaining the relevant information?
- What is the latest applicable version, publication, dataset, or official statement?
- Has a newer source superseded an older one without necessarily being easier to find?
- Does the newest source apply to the same jurisdiction, population, or context?
- What material changed between the older and current versions?
- How should the current source and its effective date be recorded for later verification?
Searching Across Different Terms for the Same Concept
- What terminology is currently being used for the concept?
- What synonyms, older terms, specialist terms, abbreviations, or local labels might other sources use?
- Do different disciplines describe the same underlying phenomenon differently?
- Could the initial terminology be biased toward one interpretation of the issue?
- What adjacent terms would surface relevant evidence without broadening the search uncontrollably?
- Which search terms are producing genuinely different source sets?
- What terminology map is sufficient to reduce the risk of missing material because of wording alone?
Gathering Relevant Internal and External Material
- What internal documents, records, data, decisions, or experience are relevant to the question?
- What external research, standards, benchmarks, or public evidence are needed?
- Which claims require local evidence rather than general external knowledge?
- Where could internal material be incomplete, self-serving, outdated, or undocumented?
- Where could external material fail to transfer to the local context?
- What confidentiality or access restrictions affect how the materials can be used?
- What combination of internal and external evidence provides the most useful basis for the document?
Looking Deliberately for Evidence That Challenges the Emerging View
- What conclusion is currently becoming dominant?
- What evidence would make that conclusion less convincing?
- Which credible sources or perspectives are likely to disagree?
- Are there failed cases, null results, contrary datasets, or alternative interpretations that should be sought?
- What search strategy would avoid simply reproducing the assumptions behind the current view?
- Does the challenging evidence reveal a genuine weakness, different context, or inferior source quality?
- How should contrary material be preserved for later synthesis and reasoning?
Finding Data, Examples, Cases, and Other Material Needed by the Document
- What function should the missing material perform in the document?
- Does the document need magnitude, trend, mechanism, illustration, precedent, feasibility, or another kind of support?
- What would make a dataset, example, or case genuinely comparable to the present context?
- Is the material being sought to test a claim or merely make the document more vivid?
- What limitations prevent an example or case from establishing prevalence or causation?
- How many examples or cases are sufficient for the role they are meant to play?
- What material should be gathered so each element contributes something the existing evidence does not?
Working Around Missing, Inaccessible, or Incomplete Sources
- What information is missing or inaccessible?
- How material is that information to the document's likely conclusions?
- Why can the preferred source not be obtained?
- What alternative evidence could address the same question without pretending to be equivalent?
- Can the claim be narrowed to match what the available evidence actually supports?
- What uncertainty or limitation should remain explicit because the gap cannot responsibly be filled?
- At what point should the document state that no reliable conclusion can be reached from the accessible evidence?
Building Sufficient Coverage Without Collecting Repetitive Sources
- What distinct perspectives, populations, methods, time periods, or contexts need representation?
- Which sources add genuinely new evidence rather than restating familiar material?
- Are many sources ultimately relying on the same original study, dataset, or announcement?
- What important part of the evidence landscape remains underrepresented?
- When does another similar source increase confidence, and when does it merely increase volume?
- What source diversity is needed for the particular question being answered?
- When is the evidence base broad enough that continued collection should give way to synthesis?
Recovering the Source Behind a Statistic, Quotation, or Claim Already in the Draft
- What exact statement in the draft needs its source recovered?
- Where did the wording or number first enter the working material?
- Can notes, earlier drafts, links, citations, or source files reconstruct its provenance?
- Does the recovered source contain the exact statistic, quotation, or claim?
- Has the draft changed the meaning, units, population, date, or qualification?
- What should happen if the original source cannot be located or verified?
- How should the recovered source be recorded so the provenance is not lost again?
Recognizing When Continued Searching Is Not Producing Better Evidence
- What new information have the most recent searches actually added?
- Are new sources materially changing the understanding or repeating established findings?
- Have the important source types and opposing perspectives already been covered?
- Is the search continuing because of a real evidence gap or discomfort with remaining uncertainty?
- What unresolved question could additional searching realistically answer?
- Would further effort be better spent evaluating, synthesizing, or testing the evidence already collected?
- What stopping point preserves responsible coverage without turning research into an indefinite activity?
Evaluating Sources and Evidence
Assessing Whether a Source Has Authority for the Claim Being Made
- What exact claim is the source being asked to support?
- What relationship does the source have to the underlying fact, rule, event, or evidence?
- Does the source have formal authority, relevant expertise, direct observation, or another credible basis for speaking to that claim?
- Is the source authoritative for this particular question rather than merely reputable in general?
- What incentives, limitations, or conflicts could affect what the source says?
- Is a more direct or authoritative source reasonably available?
- What weight should this source receive once its actual authority is understood?
Determining Whether a Source Is Current Enough for the Question
- What information in the source may have changed since publication?
- How quickly does the relevant subject normally change?
- Has a newer law, standard, dataset, version, study, or event superseded the source?
- Is the source being used for a timeless mechanism, historical fact, or current-state claim?
- Does an older source remain valuable for comparison or background even if it cannot establish the present state?
- What would be the consequence of relying on outdated information here?
- What recency threshold is appropriate for the claim the document needs to make?
Testing How Directly the Evidence Applies to the Document's Actual Context
- What population, organization, jurisdiction, setting, technology, or conditions produced the evidence?
- How closely do those conditions match the context addressed by the document?
- Which contextual differences could materially affect transferability?
- Does the evidence support the exact outcome or only a related proxy?
- Are important groups or circumstances absent from the underlying evidence?
- What qualification is necessary if the evidence is informative but indirect?
- How narrowly should the document state the claim given the evidence's actual applicability?
Assessing the Methodological Quality of Empirical Evidence
- What research design or data-generation process produced the evidence?
- Is that method suitable for the question the source claims to answer?
- How were the sample, variables, measurements, and comparisons defined?
- What important sources of bias, confounding, missingness, or measurement error remain?
- Are the analysis and reported conclusions proportionate to the design?
- Have the findings been replicated, independently examined, or situated within a broader evidence base?
- How much confidence should the document place in the evidence after those limitations are considered?
Checking Whether Apparently Independent Sources Rely on the Same Underlying Evidence
- What original data, study, report, announcement, or testimony does each source rely on?
- Are several sources independently generating evidence or merely repeating the same underlying material?
- Have later sources added verification, analysis, or only republication?
- Does apparent agreement disappear once common provenance is recognized?
- Is one interpretation being amplified through citation chains rather than independently supported?
- How many genuinely independent lines of evidence remain?
- How should the document characterize the strength of support once source dependence is accounted for?
Choosing Between Primary Evidence and Secondary Interpretation
- What question is the document trying to answer?
- Is direct access to the underlying event, data, rule, or study important for this claim?
- What can the primary source establish that a secondary source cannot?
- What synthesis, context, methodological critique, or interpretation does the secondary source add?
- Could the secondary source misrepresent or oversimplify the primary material?
- Would relying only on the primary source miss the broader evidence landscape?
- What combination of primary and secondary material best supports both factual accuracy and informed interpretation?
Assessing Whether Evidence From Another Context Can Be Transferred Reliably
- What important characteristics differ between the source context and the document's context?
- Which mechanism or relationship is expected to remain stable across those differences?
- What evidence supports that assumption of transferability?
- Are there local factors that could reverse, weaken, or strengthen the observed effect?
- What comparable evidence exists from contexts more similar to the one being addressed?
- Should the external evidence be treated as proof, indication, hypothesis, or illustrative precedent?
- What qualification should accompany any conclusion derived from transferred evidence?
Determining Whether the Evidence Supports a Causal, Comparative, or Descriptive Claim
- What type of claim is the document attempting to make?
- What does the evidence directly observe or measure?
- Does the evidence establish association, sequence, mechanism, comparison, or actual causal effect?
- What alternative explanations could produce the observed relationship?
- Are comparison groups, baselines, or counterfactuals adequate for the intended inference?
- Is the proposed wording stronger than the design permits?
- What is the strongest claim that can be made without exceeding the evidence?
Weighing Conflicting Sources of Unequal Quality
- What exactly do the sources disagree about?
- Do they examine the same population, period, definitions, outcomes, and conditions?
- How do their methods, authority, directness, independence, and recency differ?
- Could the apparent conflict result from context or measurement rather than one source simply being wrong?
- Which source is better suited to the specific claim the document needs to make?
- What uncertainty remains even after differences in source quality are considered?
- Should the document prefer one interpretation, describe context-dependent findings, or leave the conflict unresolved?
Concluding That the Available Evidence Is Not Strong Enough
- What conclusion is being considered?
- What evidence currently supports it?
- What critical weakness prevents that evidence from carrying the required burden?
- Is the problem insufficient quantity, poor quality, indirectness, inconsistency, missing context, or unresolved alternatives?
- Could the conclusion be narrowed or reframed into something the evidence does support?
- What additional evidence would materially improve confidence, if it is realistically obtainable?
- How should the document represent the uncertainty if no stronger evidence becomes available?
Organizing Research, Notes, and Evidence Traceability
Capturing Source Provenance While Research Is Still Fresh
- What information about each source needs to be captured before its origin becomes difficult to reconstruct?
- Which author, organization, title, date, version, location, and access details matter for later verification?
- What exact part of the source produced the note, quotation, statistic, or interpretation being recorded?
- How should direct source material be distinguished from observations made while reading it?
- Which sources are likely to change and therefore require version or retrieval information?
- What minimum provenance record is sufficient without making research capture unnecessarily burdensome?
- How should provenance be stored so it remains attached to the material as research moves into drafting?
Connecting Important Claims to Their Supporting Evidence
- What material claims is the document currently expected to make?
- Which evidence directly supports each claim?
- Where does a claim depend on several sources rather than one decisive source?
- Which evidence supports only part of a claim or requires qualification?
- What claims currently have no adequate supporting evidence?
- Can the relationship be traced in both directions from claim to source and from source to its use in the document?
- What claim-evidence structure will remain usable as the argument and document architecture change?
Separating Direct Quotations, Paraphrases, Interpretations, and Personal Notes
- Which notes reproduce source language exactly?
- Which notes paraphrase what a source states?
- Which notes record the researcher's own interpretation or synthesis?
- Which comments are reminders, questions, judgments, or ideas rather than source-derived information?
- Where could unclear labeling cause an interpretation to be mistaken for a source statement?
- What notation or structure will keep these categories distinguishable during drafting?
- How should ambiguous legacy notes be handled when their status can no longer be established confidently?
Organizing Research Around Questions Rather Than Around Individual Sources
- What research questions is the document actually trying to answer?
- Which findings from different sources contribute to each question?
- What happens to understanding when notes are reorganized by issue rather than by publication?
- Where do several sources converge, conflict, or address different parts of the same question?
- Which questions have accumulated substantial material without producing a clear answer?
- Which sources contribute to several different questions and need to remain traceable across them?
- What research organization will make later synthesis easier without losing source provenance?
Tracking Which Version of a Changing Source Was Used
- Which sources are updated, amended, replaced, or republished over time?
- What exact version was consulted when the relevant claim or note was created?
- What date, edition, revision number, or effective period distinguishes that version?
- Has the source changed since it was first used?
- Do later changes alter any claim, quotation, figure, or interpretation in the developing document?
- When should the document rely on the historical version rather than the latest one?
- How should version information be preserved so future reviewers can reconstruct what evidence was available at the time?
Keeping Material Assumptions Separate From Established Evidence
- What statements in the research base are known from evidence and what statements are being assumed?
- Which assumptions are necessary to connect incomplete evidence to the working argument?
- What source, if any, could verify each important assumption?
- Which assumptions are temporary working devices and which are likely to remain in the final reasoning?
- What would change if a material assumption proved false?
- How can assumptions remain visible without cluttering ordinary research notes?
- When should an assumption be promoted to a research question rather than allowed to persist untested?
Recording Contradictory Evidence Without Losing It During Drafting
- What evidence challenges the emerging interpretation or preferred conclusion?
- Which contradiction reflects genuine disagreement rather than different populations, definitions, periods, or methods?
- How strong is the contradictory evidence relative to the evidence supporting the current view?
- Where should contrary findings be recorded so they cannot disappear when notes are condensed?
- What part of the developing argument could the contradiction alter?
- Does the contradiction require qualification, a competing explanation, or a different conclusion?
- How can contradictory evidence remain attached to the reasoning process through drafting and revision?
Preventing Facts and Statistics From Becoming Detached From Their Sources
- Which facts or numbers are likely to be copied repeatedly during development?
- Can each one still be traced to the source and exact location from which it came?
- What definitions, units, populations, dates, or qualifications belong with the value?
- Has any statistic already lost contextual information as it moved between notes and drafts?
- How should derived calculations be distinguished from values reported directly by a source?
- What should happen when the provenance of a fact can no longer be reconstructed?
- What working practice will keep source context attached to high-risk facts throughout development?
- What categories of research material need to be managed across the project?
- How should source files, excerpts, notes, datasets, and working analyses be named and organized?
- What metadata is necessary to find, understand, and verify material later?
- Where should one authoritative copy of each important source or note set reside?
- How can duplicated, superseded, or incomplete research material be distinguished from current material?
- What organization is simple enough to maintain consistently across a long project?
- How will another contributor or future maintainer reconstruct the evidence base without relying on the original researcher's memory?
Preserving Traceability as Sections and Claims Change During Revision
- Which claim-to-source relationships could be broken when material is moved, merged, shortened, or rewritten?
- How can evidence links follow claims as they change position in the document?
- What happens when several claims are consolidated into one broader proposition?
- Which citations or notes become obsolete when a claim is narrowed or removed?
- How can a reviewer tell whether revised language is still supported by the original evidence?
- What traceability checks should occur after major substantive or structural revision?
- What record is sufficient to preserve evidentiary continuity without freezing the document against necessary change?
Moving Beyond Source-by-Source Summaries
- What question is the collected material supposed to answer collectively?
- What does each source contribute beyond its individual summary?
- Which findings can be grouped because they address the same underlying issue?
- What relationships become visible only when the sources are considered together?
- Where are source summaries substituting for an actual integrated understanding?
- What claims or conclusions become possible once individual findings are connected?
- How can the synthesis be organized around implications rather than around the order in which sources were read?
Identifying Where Different Sources Converge
- Which findings or interpretations are supported across multiple sources?
- Are the sources genuinely independent or drawing on the same underlying evidence?
- Do they converge on the same result for the same reasons?
- How consistent are the populations, definitions, methods, and contexts behind the apparent agreement?
- Does convergence strengthen confidence in a broad claim or only in a narrower proposition?
- What relevant evidence does not fit the convergent pattern?
- What conclusion is proportionate to both the agreement and the remaining differences?
Understanding Why Credible Sources Appear to Conflict
- What exact proposition do the sources appear to disagree about?
- Are they using the same definitions, measures, populations, periods, and outcomes?
- Do methodological differences explain some or all of the disagreement?
- Could both findings be valid under different conditions?
- Has one source been superseded by later evidence or a changed context?
- Which differences are consequential enough to alter the document's reasoning?
- Should the synthesis resolve the conflict, explain its conditions, or leave it explicitly unresolved?
Grouping Evidence Around Themes, Mechanisms, or Questions
- What organizing logic best reveals how the evidence relates?
- Which findings belong together because they answer the same question?
- Which findings point to the same mechanism even when they come from different contexts?
- Are any apparent themes merely broad labels that hide important differences?
- What evidence belongs in more than one group because it has several relevant implications?
- Which groups are central to the document and which are secondary?
- What grouping will best support later reasoning without predetermining the conclusion?
Distinguishing Findings That Apply in Different Contexts
- Under what conditions was each important finding produced?
- Which populations, systems, environments, jurisdictions, or time periods differ materially?
- What pattern appears stable across contexts?
- Which findings reverse, weaken, or strengthen when conditions change?
- What mechanism could explain the contextual variation?
- Which context most closely matches the document's intended application?
- How should the synthesis preserve contextual differences rather than averaging them into a misleading generalization?
Giving Greater Weight to Stronger Evidence Without Ignoring Relevant Outliers
- Which evidence is strongest on authority, directness, method, relevance, and independence?
- What findings are supported mainly by weaker or more indirect evidence?
- Is an outlier weak because of poor evidence quality or important because it reveals genuine variation?
- What would be lost by simply following the majority of sources?
- Does stronger evidence justify discounting conflicting findings completely or only reducing their weight?
- How should unusual but credible findings affect the boundaries of the emerging conclusion?
- What synthesis represents the relative weight of evidence without pretending that every source contributes equally?
Identifying What the Combined Evidence Still Does Not Establish
- What conclusions might a reader be tempted to draw from the accumulated evidence?
- Which of those conclusions are not actually supported?
- What causal, comparative, predictive, or generalizing steps remain unproven?
- What important variables or populations are missing from the evidence base?
- Which uncertainties survive even though several sources point in the same direction?
- What additional evidence would be required to close the most important remaining gap?
- How should the synthesis state what is known while keeping unsupported conclusions out?
Integrating Quantitative and Qualitative Evidence
- What does the quantitative evidence establish about magnitude, frequency, pattern, or change?
- What does the qualitative evidence reveal about mechanism, experience, meaning, or context?
- Where do the two forms of evidence reinforce each other?
- Where do they appear to conflict or describe different parts of the same phenomenon?
- Are differences caused by what each method is capable of observing?
- What conclusion becomes stronger or more nuanced when both forms are considered together?
- How should the document integrate them without treating one form as inherently superior to the other?
Reducing a Large Evidence Base to What the Document Actually Needs
- Which findings are necessary to establish the document's central propositions?
- Which evidence adds confidence without adding a new idea?
- Which material is useful background but not necessary to the reader's task?
- What contradictory or qualifying evidence must remain even if space is limited?
- Where can several similar findings be synthesized rather than reported individually?
- What supporting detail should remain available outside the main narrative?
- What is the smallest evidence set that preserves the accuracy and defensibility of the document's reasoning?
Determining When the Synthesis Is Sufficient to Support Further Reasoning
- Have the major research questions produced coherent findings?
- Are important areas of convergence and disagreement understood?
- Has contradictory evidence been incorporated rather than postponed?
- Are the main contextual limitations visible?
- What material uncertainty remains unresolved?
- Would further synthesis materially change the emerging reasoning or mainly refine its wording?
- Is the evidence base now organized well enough to begin developing defensible claims without pretending the synthesis is final?
Developing Claims, Explanations, and Arguments
Turning Evidence Into a Defensible Claim
- What does the evidence directly establish?
- What claim is being proposed on the basis of that evidence?
- What reasoning connects the evidence to the claim?
- Does the wording extend beyond the population, context, period, or conditions actually supported?
- What credible evidence challenges or qualifies the claim?
- How would the claim change if the weakest supporting evidence were removed?
- What is the strongest formulation that remains defensible without overstating what is known?
Calibrating the Strength and Breadth of a Claim to the Evidence
- How strong is the available evidence for the proposed claim?
- How broad is the population, context, or condition over which the evidence applies?
- Does the current wording imply greater certainty than the evidence warrants?
- Does it generalize beyond the settings actually examined?
- Would narrowing the claim preserve its usefulness while making it more defensible?
- What qualifying language genuinely reflects uncertainty rather than merely sounding cautious?
- What formulation best matches the actual strength, scope, and specificity of the evidence?
Making the Reasoning Between Evidence and Claim Explicit
- What evidence is being used to support the claim?
- What unstated reasoning must be true for that evidence to justify the claim?
- Is the connection obvious to the intended reader or does it need explanation?
- What assumptions are embedded in the inferential step?
- Could the same evidence support a materially different interpretation?
- What additional evidence or reasoning would strengthen the connection?
- How can the document make the warrant clear without overexplaining straightforward logic?
Building a Chain of Claims That Supports the Document's Central Proposition
- What central proposition must the document ultimately establish?
- What subordinate claims must be true for that proposition to hold?
- Which claims depend on earlier claims and which stand independently?
- Does every major link in the chain have adequate evidence or reasoning?
- Where does the argument jump from one proposition to another without establishing the connection?
- Are any claims redundant or unnecessary to the final proposition?
- What claim sequence gives the reader the clearest path from evidence to the central conclusion?
Developing a Causal Explanation Without Claiming More Than the Evidence Supports
- What cause-and-effect relationship is being proposed?
- What evidence establishes sequence, association, mechanism, or intervention effect?
- What alternative causes could explain the same observed outcome?
- Are the supposed cause and effect measured directly or through proxies?
- Under what conditions does the proposed mechanism appear to operate?
- What parts of the causal account are supported and what parts remain inferential?
- How should the explanation be worded if the evidence supports contribution or association but not definitive causation?
Distinguishing Description From Analysis
- Which statements simply report what happened, exists, or was observed?
- Which statements interpret why those facts matter?
- Where does the document move from describing a pattern to explaining it?
- Are analytical claims being presented as though they were direct observations?
- What reasoning or evidence supports each interpretive step?
- Where is description necessary before analysis can be understood?
- How can the document signal the transition from observed information to interpretation without making the prose artificial?
Combining Several Pieces of Evidence to Support a Larger Claim
- What larger claim requires support from more than one piece of evidence?
- What distinct role does each piece of evidence play?
- Are the sources independent, complementary, or merely repetitive?
- Does one piece establish magnitude while another explains mechanism, context, or feasibility?
- Are weak pieces of evidence being combined in a way that creates only an illusion of strong support?
- What important part of the claim remains unsupported even after the evidence is combined?
- How should the document show cumulative support without turning the argument into an evidence dump?
Distinguishing Observation, Interpretation, and Inference
- What was directly observed, measured, recorded, or stated?
- What meaning is being assigned to that observation?
- What further conclusion is being inferred from the interpretation?
- Which step relies on assumptions not contained in the original evidence?
- Could another reasonable interpretation lead to a different inference?
- Where has the draft collapsed these levels into one apparently factual statement?
- How should the reasoning be expressed so readers can distinguish evidence from the conclusions drawn from it?
Organizing Main Claims and Supporting Claims Into a Coherent Argument
- Which claims carry the main argumentative burden of the document?
- What supporting claims are needed to establish each main claim?
- Are any supporting claims actually separate main propositions?
- What order allows each claim to rely only on reasoning already established?
- Where are claims repeated because their structural relationship is unclear?
- Does every major claim contribute to the governing proposition or conclusion?
- What argument structure makes the hierarchy of claims understandable without forcing the reader to reconstruct it?
Revising a Claim When New Evidence Changes What Can Be Defended
- What new evidence challenges or extends the current claim?
- Which part of the claim is no longer supportable?
- Does the evidence require narrowing, qualifying, broadening, or reversing the proposition?
- What existing reasoning depends on the original formulation?
- Which sections, conclusions, or recommendations must be reconsidered if the claim changes?
- What evidence still supports the revised claim?
- How should the change propagate through the document so the superseded formulation does not survive elsewhere?
Testing Assumptions, Alternatives, and Uncertainty
Surfacing Assumptions That the Reasoning Depends On
- What must be true for the current argument or conclusion to hold?
- Which of those conditions are established by evidence and which are merely assumed?
- Why was each assumption introduced?
- How material is each assumption to the final conclusion?
- What evidence could confirm or challenge the most important assumptions?
- What happens to the argument if a key assumption is false?
- Which assumptions need to be tested, disclosed, or removed before the reasoning is considered sound?
Testing Competing Explanations for the Same Evidence
- What leading explanation currently accounts for the observed evidence?
- What other credible explanation could produce the same pattern?
- What evidence would each explanation predict if it were correct?
- Which available findings discriminate among the alternatives?
- Are some explanations compatible rather than mutually exclusive?
- What evidence would be needed to distinguish the remaining plausible explanations?
- Which explanation is best supported, and what uncertainty should remain if the evidence does not decisively discriminate?
Developing and Answering a Serious Counterargument
- What is the strongest credible challenge to the document's emerging position?
- What evidence or reasoning gives the counterargument real force?
- Does it expose a false assumption, missing evidence, alternative value judgment, or different interpretation?
- Which parts of the main argument survive the challenge?
- What response is supported by evidence rather than merely defensive?
- Does the counterargument require qualification or revision of the original position?
- How should the document address it so readers can evaluate the disagreement rather than seeing a caricature of the opposing view?
Checking Whether a Conclusion Changes Under Different Assumptions
- Which assumptions have the greatest influence on the emerging conclusion?
- What reasonable alternative values or conditions could replace them?
- How does the conclusion change under those alternatives?
- Which assumptions affect only magnitude and which can reverse the direction of the conclusion?
- Are any assumptions being treated as fixed merely because they are convenient?
- What range of assumptions leaves the conclusion substantially unchanged?
- How should sensitivity to assumptions affect confidence, wording, or recommended action?
Distinguishing Different Types of Uncertainty
- What exactly is uncertain in the current analysis?
- Does the uncertainty arise from missing evidence, measurement, model choice, interpretation, future events, scope, or another source?
- Which uncertainty could be reduced through additional research?
- Which uncertainty is inherent and unlikely to disappear with more information?
- How does each type of uncertainty affect the strength of the conclusion?
- Would combining different uncertainties into one vague caveat conceal important distinctions?
- What representation best communicates each material uncertainty to the intended reader?
Working With Evidence That Supports More Than One Interpretation
- What different interpretations are consistent with the available evidence?
- What assumptions lead from the same evidence to each interpretation?
- Are the interpretations genuinely incompatible or focused on different aspects of the issue?
- What additional evidence would help distinguish among them?
- Does one interpretation have stronger support even though alternatives remain plausible?
- What decisions or conclusions can still be made without resolving the ambiguity completely?
- How should the document preserve multiple plausible interpretations without creating false equivalence?
Identifying the Boundary Conditions of an Emerging Conclusion
- Under what conditions does the conclusion appear to hold?
- What populations, contexts, time periods, or systems have actually been examined?
- Where does the supporting evidence become weaker or inconsistent?
- What mechanism suggests the conclusion may fail outside particular conditions?
- Which exceptions are material enough to state explicitly?
- How would the conclusion need to change if applied beyond the supported boundary?
- What boundary statement prevents readers from generalizing the conclusion too broadly?
Searching for Evidence That Could Disprove or Qualify the Preferred View
- What finding would seriously weaken the preferred interpretation?
- Where would such evidence most likely be found?
- Have sources with opposing incentives, methods, or perspectives been examined?
- What negative, null, failed, or contrary cases are available?
- Is contrary evidence being dismissed because it is weak or because it is inconvenient?
- What qualification follows if credible contrary evidence remains?
- Has the preferred view survived a serious attempt to find evidence against it?
Deciding How Uncertainty Should Change the Language of the Document
- What uncertainty materially affects the claim being expressed?
- Does the wording currently imply more certainty than the evidence supports?
- Would a probability, range, scenario, conditional statement, or qualitative qualifier represent the uncertainty better?
- Is cautious wording genuinely informative or merely vague?
- Where could excessive hedging obscure a conclusion that is actually well supported?
- What uncertainty must remain visible because it could change the reader's decision or interpretation?
- What language communicates the appropriate level of confidence without laundering uncertainty into certainty or weakening justified conclusions?
- What current uncertainty has the greatest potential to alter the conclusion?
- What specific evidence would resolve or reduce that uncertainty?
- Could the new information strengthen, narrow, reverse, or leave the conclusion unchanged?
- Is the information realistically obtainable within the decision timeframe?
- Would obtaining it justify delaying the document or decision?
- If the information cannot be obtained, what conclusion remains defensible?
- What future finding should trigger reconsideration after the document is complete?
Developing Conclusions, Judgments, and Recommendations
Moving From Findings to a Supported Conclusion
- What findings are most material to the governing question?
- What do those findings collectively establish?
- What reasoning is required to move from the findings to the proposed conclusion?
- Does the conclusion depend on assumptions that remain uncertain?
- What contrary evidence or limitations constrain it?
- Is the conclusion broader or more certain than the evidence allows?
- What formulation captures the strongest conclusion the completed reasoning can responsibly support?
Distinguishing an Evidence-Based Conclusion From a Professional Judgment
- What part of the proposed conclusion follows directly from evidence and analysis?
- Where does professional interpretation or judgment enter?
- What criteria, experience, values, or contextual knowledge inform that judgment?
- Could another qualified person reasonably reach a different judgment from the same evidence?
- What parts of the statement should therefore be attributed to judgment rather than presented as fact?
- Does the person making the judgment have the relevant expertise and authority?
- How should the document distinguish evidence-supported findings from the judgment made on their basis?
Determining Whether the Evidence Supports a Firm Conclusion
- What conclusion is currently being considered?
- How strong, direct, consistent, and relevant is the supporting evidence?
- What important alternatives have been tested?
- What uncertainty remains material to the conclusion?
- Would additional evidence plausibly change the answer?
- Does the consequence of the conclusion require a higher evidentiary threshold?
- Should the document state a firm conclusion, a qualified conclusion, several possibilities, or no reliable conclusion?
Comparing Alternatives Against Explicit Criteria
- What alternatives are genuinely available?
- What objective or decision is the comparison meant to support?
- Which criteria matter to that objective?
- Who has authority to determine the relative importance of those criteria?
- What evidence supports the assessment of each alternative against each criterion?
- What tradeoffs or sensitivities could change the comparative result?
- How should the comparison be presented if no alternative dominates across all material criteria?
Deciding Whether the Analysis Justifies a Recommendation
- What problem or decision is the recommendation intended to address?
- What does the analysis establish about the available courses of action?
- Is the recommended option supported by the criteria and evidence actually used?
- What assumptions about implementation, cost, timing, behavior, or future conditions does the recommendation depend on?
- What credible alternatives remain?
- What material uncertainty or unresolved tradeoff could change the preferred course?
- Is the analysis strong enough to recommend action, or should the document stop at findings and options?
Making a Recommendation While Material Uncertainty Remains
- What uncertainty remains despite the completed analysis?
- How could that uncertainty affect the consequences of the recommended action?
- Is the decision reversible, adaptable, or robust across plausible scenarios?
- What risks arise from acting now compared with waiting for more information?
- What conditions, safeguards, pilots, or review points could make action more responsible?
- What uncertainty needs to be disclosed to the decision-maker?
- What recommendation is justified once both the evidence and unavoidable uncertainty are considered?
Making Tradeoffs Visible in a Recommended Course of Action
- What benefits does the recommended course prioritize?
- What costs, risks, limitations, or forgone benefits accompany it?
- Which competing objectives cannot all be maximized?
- Who bears the negative consequences and who receives the benefits?
- What criteria or values justify accepting the tradeoff?
- Could an alternative design reduce the most important downside without sacrificing the core benefit?
- How should the recommendation state the tradeoff so the decision-maker understands what is being accepted?
Avoiding a Recommendation That Does Not Follow From the Diagnosed Problem
- What problem did the analysis actually establish?
- What causes or constraints appear to be driving that problem?
- How does the proposed recommendation address those causes or constraints?
- Is the recommendation responding to the diagnosed problem or to a solution that was preferred beforehand?
- What evidence suggests the proposed action could produce the intended effect?
- What parts of the problem would remain untouched even if the recommendation were implemented?
- What recommendation, if any, follows most directly from the actual diagnosis?
Leaving a Choice Open Because the Decision Depends on Values or Authority Outside the Document
- What choice remains after the factual and analytical work is complete?
- Which parts of that choice depend on values, priorities, risk tolerance, or legitimate authority rather than unresolved evidence?
- Who has the authority to make that choice?
- What information does the decision-maker need to exercise that authority responsibly?
- Would making a recommendation improperly substitute the author's preferences for the decision-maker's judgment?
- Can the document clarify consequences and tradeoffs without selecting the outcome?
- How should the open choice be framed so the analysis informs rather than silently makes the decision?
Concluding That No Responsible Recommendation Can Yet Be Made
- What recommendation is being sought?
- What critical evidence, criterion, decision, or authority is still missing?
- Why would choosing now exceed what the analysis can support?
- Can any options be ruled out even if no positive recommendation is justified?
- What can the document conclude reliably despite the inability to recommend?
- What additional work or decision would make a recommendation possible?
- How should the document communicate the absence of a recommendation without disguising uncertainty or inventing false decisiveness?
Designing the Document Architecture
Choosing the Main Organizing Principle for the Document
- What does the reader primarily need to understand, decide, compare, perform, or retrieve?
- Which organizing principle best supports that task: argument, chronology, problem and solution, decision structure, task sequence, comparison, reference structure, or another logic?
- What relationships among the material would each plausible structure make easier or harder to see?
- Does the proposed structure follow the document's reasoning or merely imitate a familiar template?
- Where would a different organizing principle materially improve comprehension or use?
- Does the document need one dominant organizing principle or several deliberately combined ones?
- What organizing logic gives the document the clearest overall path without forcing the material into an artificial sequence?
Turning Document Functions Into Major Sections
- What distinct jobs must the document perform for its purpose to be fulfilled?
- What question should each major section answer for the reader?
- Which functions require their own section rather than a paragraph within another section?
- Are any proposed sections based mainly on available material rather than a genuine reader or reasoning need?
- What output should each section produce for the section that follows?
- Are any necessary document functions missing from the current architecture?
- What section set represents the document's essential functions without unnecessary fragmentation?
Sequencing Sections According to Their Dependencies
- What must the reader understand before each major section can make sense?
- Which conclusions depend on definitions, evidence, analysis, or decisions established earlier?
- Are any sections currently asking the reader to accept something that has not yet been established?
- Which sections can stand independently and which have strong dependencies?
- Would changing the sequence reduce repetition or the need for forward explanation?
- Where should context stop and substantive reasoning begin?
- What sequence allows each section to build naturally on what the reader already has?
Distinguishing the Order of Development From the Order of Presentation
- In what order is it easiest to develop the document's reasoning and evidence?
- In what order does the intended reader need to encounter the final material?
- Which conclusions may need to be developed late but presented early?
- Which background material may need to be researched first but presented only when relevant?
- Would drafting in presentation order create unnecessary dependence on unresolved earlier sections?
- What information can be developed independently before its final placement is known?
- How should the working architecture distinguish development sequence from final reading sequence?
Deciding What Belongs in the Main Document Versus Appendices or Annexes
- What information must readers encounter to understand or evaluate the document's main conclusions correctly?
- What material is useful mainly for verification, reproduction, technical depth, or secondary reference?
- Would moving the material out of the main narrative improve flow without hiding an important limitation or assumption?
- Which readers are likely to need the supporting detail?
- Could a reader reach a materially different conclusion if they never opened the appendix or annex?
- How should the main text summarize and cross-reference supporting material?
- What division between main document and supporting material preserves both usability and transparency?
Designing Layers for Summary, Main Analysis, and Supporting Detail
- What does a reader need from the document at the quickest level of engagement?
- What reasoning and evidence must appear in the main analytical layer?
- What supporting detail should remain available for readers who need deeper verification?
- Are conclusions consistent across the summary, main body, and supporting material?
- What information is being repeated unnecessarily across layers?
- Which qualifications must remain visible even in the shortest layer?
- How can the layers support different depths of use without becoming separate inconsistent documents?
Structuring a Document for Reference Rather Than Continuous Reading
- What information will readers most often need to locate directly?
- What entry points should allow readers to reach that information without reading preceding sections?
- Which categories, headings, indexes, navigation aids, or cross-references would support retrieval?
- How much context must each section carry because readers may enter it independently?
- Where is deliberate repetition justified because the document will be used nonlinearly?
- What dependencies between sections could make direct lookup unsafe or confusing?
- How should the architecture change when retrieval matters more than narrative progression?
Choosing the Right Level of Section and Subsection Granularity
- What distinct piece of reader or reasoning work does each proposed section perform?
- Is any section broad enough to contain several independent functions?
- Is any subsection so narrow that it does not justify a separate structural unit?
- Are headings helping readers navigate meaningful distinctions or merely breaking text into small pieces?
- Where does excessive nesting make the document harder to understand?
- Where would an additional structural level materially improve navigation or reasoning?
- What granularity gives each section a coherent purpose while keeping the hierarchy manageable?
Designing an Architecture When No Standard Structure Fits
- What functions must the document perform that standard structures fail to accommodate?
- Which parts of existing document models remain useful?
- What reasoning dependencies should determine the structure instead of convention?
- What reader expectations could be disrupted by an unfamiliar architecture?
- Which headings or navigation devices would help readers understand the new structure quickly?
- How can the architecture remain simple enough to use despite being nonstandard?
- What test would show that the custom structure works better than forcing the document into an established template?
Designing a Hybrid Architecture When More Than One Organizing Principle Is Needed
- What different kinds of material require different organizing logics?
- Which organizing principle should govern the document at the highest level?
- Where should another principle take over within a section or subsection?
- Are the different structural logics complementary or likely to confuse the reader?
- What transitions are needed when the document changes from one organizing principle to another?
- Could a simpler architecture achieve the same result without combining structures?
- How can the hybrid structure remain visibly coherent as one document rather than several structures stitched together?
Drafting the Document
Starting a Draft When the Blank Page Is Blocking Progress
- What part of the document is already clear enough to put into words?
- Is the difficulty caused by missing thinking, missing evidence, uncertainty about structure, or reluctance to write imperfectly?
- What provisional statement, section, example, or explanation could externalize the current thinking?
- Would starting somewhere other than the introduction reduce the blockage?
- What questions can be left visibly unresolved rather than solved before drafting begins?
- What minimum amount of prose would create enough material to react to and improve?
- How can the first drafting step remain explicitly provisional so it does not create premature commitment?
Turning a Stable Outline Into Provisional Prose
- What function is each outlined section expected to perform?
- What central point should the first draft of each section establish?
- Which evidence, examples, or reasoning already belong under each heading?
- Where does the outline contain labels without enough thinking to support actual prose?
- Which transitions become necessary once the outline is expressed in sentences and paragraphs?
- What parts should remain rough rather than being polished during the first prose pass?
- How can the draft test whether the outline actually works rather than merely filling its headings?
Drafting From Notes, Sources, and Fragments
- What coherent point is hidden across the available notes and fragments?
- Which material represents source evidence, personal interpretation, tentative language, or abandoned thinking?
- What should be synthesized rather than copied into the draft piece by piece?
- Which fragments belong together because they serve the same section function?
- What important reasoning is missing between the collected pieces?
- Which material should remain outside the draft because it is interesting but nonessential?
- How can fragmented inputs be converted into original coherent prose without losing source traceability?
Drafting While Evidence or Decisions Remain Open
- What parts of the document are sufficiently settled to draft responsibly?
- Which statements depend on evidence or decisions that are still unresolved?
- What placeholders can make those dependencies explicit without inventing an answer?
- Which provisional claims can be drafted safely if their status is clearly marked?
- What downstream sections should wait because they depend too heavily on unresolved matters?
- How will open items be tracked so provisional text cannot accidentally survive into the final document?
- What drafting progress is useful now without creating false certainty or excessive later rework?
Drafting Sections Out of Reading Order
- Which section is currently most ready to be drafted?
- What sections can be developed independently of material that comes earlier in the final document?
- Would drafting the core analysis first clarify what the introduction and summary eventually need to say?
- What dependencies must still be respected even when sections are drafted nonsequentially?
- How will terminology, assumptions, and cross-references remain consistent across separately drafted sections?
- What provisional transitions should be avoided until the final order is stable?
- How should independently drafted sections later be integrated into one continuous reading experience?
Writing the Introduction or Conclusion While the Main Substance Is Still Moving
- What is sufficiently stable to say about the document's purpose, question, or emerging conclusion?
- Which parts of the introduction or conclusion remain dependent on unfinished analysis?
- Would drafting either section now help clarify the document's direction?
- What language should remain provisional because the underlying substance may still change?
- Is the introduction promising coverage or conclusions that the body does not yet support?
- Is the conclusion merely repeating an early expectation rather than reflecting the developing analysis?
- When should these sections be revisited so they accurately represent the final document rather than an earlier version of it?
Using Placeholders Without Losing Track of Unresolved Work
- What unresolved item does each placeholder represent?
- Is the missing content evidence, a decision, a source, a calculation, wording, or another dependency?
- What information is needed before the placeholder can be resolved?
- Who owns the unresolved item, if anyone other than the writer?
- How consequential would it be if the placeholder were accidentally left unresolved?
- What consistent marker or tracking system will make every placeholder easy to find?
- When should all placeholders be reviewed before the document moves into final revision?
Drafting When the Reasoning Is Still Emerging Through Writing
- What part of the reasoning becomes clearer only when it is expressed in prose?
- Where is the draft revealing a gap between evidence and the intended conclusion?
- Which sentences are exploratory thinking rather than reader-ready claims?
- Has writing exposed an assumption, contradiction, or alternative that was not visible in the outline?
- Does the new reasoning require changes to research, claims, or architecture?
- What exploratory material should be retained for further development and what should eventually be removed?
- When has the reasoning become stable enough to stop using drafting as exploration and start revising for the reader?
Recognizing When Sentence-Level Polishing Is Premature
- What larger parts of the document are still unstable?
- Could the section, paragraph, or argument containing the sentence still move or disappear?
- Is the wording problem actually a symptom of unclear reasoning or structure?
- How much polished language would likely be discarded if substantive revision occurs?
- What minimum level of clarity is sufficient at the current stage?
- Which local problems genuinely need correction now because they obstruct further thinking?
- At what point will sentence-level optimization become a productive use of effort?
Determining When the Draft Is Complete Enough for Full Revision
- Does every required major section now contain enough material to evaluate its function?
- Are the central claims, evidence, and reasoning visible even if they are not yet polished?
- Are unresolved gaps clearly marked rather than concealed?
- Is there enough of the document to judge overall architecture and coherence?
- Would further drafting mainly add detail rather than reveal the document's fundamental shape?
- What major missing element would make full-document revision premature?
- Is the draft now complete enough that the next improvement is more likely to come from revision than continued generation?
Developing Sections, Paragraphs, and Continuity
Clarifying What a Section Is Supposed to Accomplish
- What distinct job does the section perform within the document?
- What question should the reader be able to answer after reading it?
- What information or reasoning must enter the section from earlier material?
- What conclusion, understanding, or transition should the section produce?
- Does every major part of the section contribute to that function?
- Is the section trying to perform several unrelated jobs at once?
- How should its purpose be stated internally to guide drafting and revision?
Turning a Section Purpose Into a Coherent Sequence of Paragraphs
- What major steps are required for the section to accomplish its purpose?
- What should each paragraph contribute to that progression?
- Which ideas need to come before others because they establish necessary context or reasoning?
- Where should evidence, explanation, qualification, and implication appear?
- Are any paragraphs present only because material was available rather than because the sequence needs them?
- What paragraph order minimizes backtracking and repetition?
- Does the final sequence lead the reader from the section's opening question to its intended result?
Giving Each Paragraph One Recognizable Function
- What is the paragraph principally trying to establish, explain, illustrate, qualify, or connect?
- Can that function be stated in one sentence?
- Are multiple independent ideas competing within the paragraph?
- Does every sentence contribute to the paragraph's main function?
- Should any material move to another paragraph because it serves a different purpose?
- Is the paragraph too thin to justify standing alone?
- What revision would make the paragraph's contribution immediately recognizable without oversimplifying its content?
Using Opening Sentences to Establish What a Paragraph Is Doing
- What should the reader understand about the paragraph from its opening?
- Does the current opening state or clearly orient toward the paragraph's main point?
- Is important context needed before the point can be stated?
- Does the opening connect appropriately to the preceding paragraph?
- Is the opening so general that it could introduce several unrelated paragraphs?
- Does the remainder of the paragraph actually fulfill what the opening leads the reader to expect?
- What opening best frames the paragraph without mechanically announcing its structure?
Creating Logical Transitions Between Paragraphs
- What relationship connects the two paragraphs?
- Is the relationship additive, causal, contrastive, sequential, conditional, or something else?
- Does the reader need an explicit transition or is the conceptual progression already clear?
- Is a transition phrase being used to hide a missing logical connection?
- Would changing the paragraph order solve the problem better than adding connective wording?
- What concept should carry forward from the first paragraph into the next?
- How can the transition make the reasoning easier to follow without becoming formulaic?
Connecting Section Openings and Endings to the Larger Document
- What prior material does the section opening need to connect with?
- Why does this section belong at this point in the document?
- Does the opening orient the reader to the section's role rather than merely repeat its heading?
- What has the section established by its end?
- What subsequent section or conclusion depends on that result?
- Does the ending need to summarize, interpret, transition, or simply stop once the section's job is done?
- How can the section feel integrated into the larger argument rather than self-contained and detachable?
Preventing Sections From Becoming Independent Mini-Documents
- What material is being repeated because the section is trying to stand entirely on its own?
- Which context has already been established elsewhere in the document?
- Is the section reintroducing definitions, evidence, or conclusions unnecessarily?
- What cross-references could replace repeated explanation?
- Are local introductions and conclusions becoming disproportionate to the section's actual role?
- Which information genuinely must be repeated because readers may enter the section independently?
- How can the section retain enough local coherence while still depending appropriately on the document around it?
Integrating Evidence Into a Paragraph Without Losing the Main Point
- What claim or point is the paragraph making?
- What evidence is necessary to support it?
- Is the evidence introduced in a way that makes its relevance clear?
- Has source detail begun to dominate the paragraph's own reasoning?
- What interpretation is needed after the evidence is presented?
- Are several pieces of evidence being listed when synthesis would be clearer?
- How can the paragraph keep the reader focused on the proposition while preserving adequate support and attribution?
Breaking a Dense Paragraph Into Distinct Units of Thought
- How many independent ideas or reasoning moves does the paragraph currently contain?
- Where does the paragraph shift from one function to another?
- Which sentences belong together because they develop the same point?
- Would splitting the paragraph expose a missing transition or logical connection?
- Are any ideas too closely dependent to separate without creating fragmentation?
- What order should the resulting paragraphs follow?
- Does the revised structure make the reasoning easier to follow without turning every sentence into its own paragraph?
Recovering Continuity in a Draft That Reads Like Disconnected Notes
- What makes the draft feel fragmented to the reader?
- Do the individual paragraphs have clear functions even though their relationships are weak?
- Is there a missing argument, sequence, or section purpose connecting the pieces?
- Which repeated or contradictory fragments came from separate drafting sessions or sources?
- What concepts, terminology, or reasoning threads should continue across the passage?
- Does the problem require transitions, reordering, consolidation, or deeper structural revision?
- What continuous line of thought should the reader be able to follow once the fragments are integrated?
Calibrating Detail, Explanation, Examples, and Qualification
Explaining an Important Concept the Reader May Not Know
- What does the reader need to understand about the concept for the document's purpose?
- Which parts of the concept are likely to be unfamiliar?
- What prior knowledge can reasonably be assumed?
- Does the concept need a definition, explanation, example, distinction, or combination of these?
- What technical detail is essential to understanding its role in the document?
- What could be omitted without creating a misleading simplification?
- How can the explanation become sufficient for use without turning into a general lesson on the subject?
Choosing the Right Level of Technical Depth
- What technical understanding does the reader need to use or evaluate the document correctly?
- How much specialist knowledge can reasonably be assumed?
- Which technical details materially affect the conclusion, decision, or action?
- What detail is necessary for credibility or reproducibility?
- Where would additional technical depth obscure rather than clarify the main point?
- Could deeper material be layered, referenced, or moved to supporting sections?
- What level of depth gives the intended reader enough information without forcing them through unnecessary complexity?
Deciding How Much Background the Reader Actually Needs
- What background is necessary to understand the current issue?
- What does the intended reader probably already know?
- Which historical or contextual facts materially affect the interpretation?
- Is background being included because it is relevant or merely because it was researched?
- How quickly does the reader need to reach the document's main substance?
- Could some background be linked, summarized, or placed in supporting material?
- What is the minimum context that prevents misunderstanding without delaying the document unnecessarily?
Using an Example to Make an Abstract Point Recognizable
- What abstract concept or claim is difficult to understand without an example?
- What characteristics must the example share with the underlying point?
- Is the example representative, illustrative, exceptional, or hypothetical?
- Could readers mistakenly treat the example as evidence of prevalence or universal applicability?
- What detail makes the example concrete without distracting from the concept?
- Would a contrasting example clarify the boundary of the idea?
- How should the example connect back to the general point so the reader understands what it demonstrates?
Simplifying Complex Material Without Distorting It
- What complexity is inherent in the subject and what complexity comes only from the current explanation?
- Which distinctions must survive any simplification?
- What details can be removed without changing the meaning?
- Would an analogy, example, diagram, hierarchy, or staged explanation make the material easier to understand?
- What exception or condition would make an apparently simple formulation misleading?
- Has the simplification changed uncertainty, causality, responsibility, or scope?
- What is the simplest explanation that remains substantively accurate?
Qualifying a Claim Without Making It Unnecessarily Weak
- What limitation or condition genuinely applies to the claim?
- How material is that qualification to the reader's interpretation?
- Does the current claim overstate certainty, scope, causality, or generalizability?
- What wording would make the limitation precise rather than vaguely cautious?
- Is the qualification repeated more often than necessary?
- Could the main claim remain direct while the relevant condition is stated separately?
- What formulation preserves both warranted confidence and necessary precision?
Balancing Necessary Qualification Against Reading Flow
- Which qualifications materially change how the reader should interpret the main point?
- Which caveats are important but secondary?
- Are qualifications interrupting every sentence and making the argument difficult to follow?
- Could related qualifications be consolidated rather than repeated?
- Which conditions need to appear immediately beside the claim and which can be explained afterward?
- Would moving a caveat make the prose smoother but create a risk that readers miss it?
- How can the document remain readable without presenting a cleaner or more certain picture than the evidence supports?
Deciding When Repetition Is Necessary for Understanding
- What information is being repeated and why?
- Will readers encounter the repeated material in separate contexts or entry points?
- Does repetition reinforce a critical warning, instruction, definition, or conclusion?
- Is the reader likely to remember or have access to the earlier occurrence?
- Could a cross-reference serve the purpose better than repeating the full content?
- Has necessary reinforcement turned into redundant explanation that slows the document?
- What amount of repetition supports understanding without creating inconsistency or unnecessary length?
Defining Necessary Specialist Terms Without Overloading the Document
- Which specialist terms are genuinely necessary for precision?
- Which terms could be replaced with ordinary language without loss?
- What definition does the intended reader need?
- Does the term have competing meanings across disciplines or contexts?
- Should the definition appear at first use, in a glossary, or through another reference mechanism?
- Are too many new terms being introduced for the reader to retain comfortably?
- How can terminology remain precise while minimizing the cognitive burden of specialist language?
Recognizing When Added Detail Is Obscuring the Main Point
- What main point is the reader supposed to retain from the passage or section?
- Which details materially support that point?
- What added material is technically relevant but not important to the reader's immediate task?
- Is the volume of examples, caveats, background, or evidence hiding the conclusion?
- Could some detail be summarized, removed, or moved to supporting material?
- What essential nuance would be lost if the passage were substantially reduced?
- What amount of detail preserves defensibility while allowing the main point to remain visible?
- What does the reader need to do with the information?
- Is the main task understanding reasoning or comparing repeated attributes across items?
- How many items and dimensions need to be compared?
- Would prose force the reader to reconstruct relationships mentally?
- Would a table add unnecessary structure to information that can be understood in a sentence or short list?
- Does the information require exact values that readers may need to locate later?
- Which representation makes the important relationship easiest to understand without duplicating the same content elsewhere?
Designing a Table for Accurate and Efficient Comparison
- What comparison or lookup task is the table supposed to support?
- What should each row and column represent?
- Which dimensions are necessary for the reader's decision or understanding?
- Are labels, units, definitions, and time periods unambiguous?
- Does the ordering of rows or columns help reveal the most important comparison?
- Has the table become too wide, dense, or structurally complex to scan reliably?
- What can be removed, split, grouped, or moved elsewhere while preserving the information readers actually need?
Choosing Between a Table and a Chart
- Does the reader need exact values or primarily the visual pattern among values?
- Is the important insight a trend, distribution, ranking, difference, or relationship?
- How many categories or data series must be represented?
- Would a chart make the pattern more obvious than a table?
- Would a table allow more accurate lookup than the chart?
- Is the data too sparse or too detailed for one representation to work well?
- Which format best supports the reader's actual task, and is there a genuine reason to include both?
- What pattern or relationship should the reader notice?
- What type of visual encoding best represents that relationship?
- Which variables need to be compared, ordered, grouped, or shown over time?
- Does the proposed visual make the important pattern perceptually obvious without exaggerating it?
- Are scale, baseline, axes, categories, and units represented honestly?
- What visual complexity can be removed without losing necessary information?
- Would a reader understand the intended pattern correctly without relying on the surrounding prose to repair the visual?
Using a Diagram to Explain a Process, System, Hierarchy, or Dependency
- What relationship is difficult to understand in prose alone?
- Is the diagram showing sequence, flow, hierarchy, dependency, architecture, causality, or another structure?
- What entities or steps genuinely need to appear?
- What do lines, arrows, positions, containers, or other relationships mean?
- Are any relationships implied visually that the evidence or process does not actually support?
- Can the diagram be simplified without removing important dependencies or exceptions?
- What accompanying text or accessible alternative is needed so readers can interpret the diagram correctly?
Choosing Between Bullets and Numbered Steps
- Are the items parallel alternatives or parts of an ordered sequence?
- Does changing the order change the meaning or outcome?
- Must every item be completed or are the items independent?
- Is numbering likely to imply rank or sequence where none exists?
- Would bullets obscure a procedural dependency that readers need to follow?
- Are any items too complex to remain in one list?
- Which list form communicates the relationship among the items without introducing false structure?
Creating Captions, Labels, and Cross-References That Remain Useful After Revision
- What stable identity does each table, figure, or other element need?
- Does the caption explain what the element contains or shows?
- Can the element be understood without relying entirely on nearby prose?
- Are cross-references based on stable labels rather than temporary spatial phrases such as "below" or "on the left"?
- Can numbering and references be generated automatically in the authoring system?
- What happens to references when elements are moved, added, or deleted?
- How should final verification confirm that every label and cross-reference still points to the correct element?
- Why does the table or figure appear at this point in the document?
- What should the reader notice in it?
- Does the surrounding prose introduce its purpose before the reader encounters it?
- Is the prose interpreting the element rather than merely repeating every value or feature?
- What conclusion or reasoning step depends on the information shown?
- Are important qualifications visible either in the element or immediately around it?
- Could the element be removed without weakening the reasoning, and if so, does it actually earn its place?
- What is the visual supposed to communicate?
- Which elements directly support that message?
- What labels, series, dimensions, decoration, or annotations are creating unnecessary complexity?
- Has one visual been asked to communicate several different messages at once?
- Could the information be split into several simpler visuals or represented as a table?
- What detail is necessary for accuracy even if it adds some complexity?
- What redesign makes the intended relationship immediately clearer without hiding material information?
- What essential information or relationship does the visual communicate?
- Can that meaning be expressed adequately in concise alternative text?
- Does a complex chart or diagram require a longer textual explanation or accompanying data table?
- Is any distinction communicated only through color, position, shape, or visual styling?
- Would simplifying the visual make it more accessible to all readers rather than merely adding metadata?
- Does the surrounding prose already communicate part of the visual's meaning without unnecessary duplication?
- What alternative representation ensures that readers who cannot perceive the visual still receive the material information needed to understand or use the document?
Managing Citations, References, and Attribution
Deciding Which Claims Need Explicit Citation
- Which statements depend on facts, findings, data, ideas, or wording that came from an external source?
- Which claims are contestable, quantitative, surprising, technical, historical, or consequential enough to require traceable support?
- What material reflects common knowledge within the intended context and does not need unnecessary citation?
- Which analytical conclusions are the document author's own synthesis but still depend on cited evidence?
- Could a reader reasonably mistake an uncited sourced claim for the author's original knowledge or judgment?
- Would adding a citation clarify the evidentiary basis or merely clutter a claim that is already adequately established?
- What consistent standard should determine when explicit citation is required throughout the document?
Citing the Original Source Rather Than an Unnecessary Secondary Reference
- What original study, dataset, rule, record, statement, or document generated the information being used?
- Is the original source reasonably accessible and understandable?
- Does the secondary source add interpretation that the document actually needs?
- Has the secondary source preserved the original meaning, limitations, and context accurately?
- Would citing only the secondary source make verification harder or obscure the true evidentiary basis?
- When is a secondary source more appropriate because it provides necessary synthesis or because the original cannot be obtained?
- Which source or combination of sources gives the reader the clearest and most defensible evidence trail?
Placing Citations So Their Relationship to Claims Is Clear
- What exact statement or set of statements does each citation support?
- Is the citation close enough to the supported claim that the relationship is unambiguous?
- Could a citation placed at the end of a long paragraph appear to support claims it does not actually substantiate?
- When do several consecutive claims require separate citations rather than one grouped reference?
- How should citations be placed when one sentence combines sourced fact, interpretation, and judgment?
- Can several sources be grouped without obscuring the distinct role each one plays?
- What placement preserves traceability while keeping the prose readable?
Working Within a Required Citation or Reference System
- What citation system, style guide, publication standard, or organizational convention governs the document?
- Which parts of that system affect in-text citations, notes, bibliography entries, ordering, punctuation, or source metadata?
- Are there source types that require special treatment under the chosen system?
- What mandatory details are often omitted or entered inconsistently?
- Can citation-management tools automate formatting without being trusted blindly for metadata accuracy?
- How should unusual or incomplete sources be handled when the style guide does not provide an obvious example?
- What final normalization pass will ensure the entire document follows one consistent system?
Distinguishing Direct Quotation From Paraphrase and Synthesis
- Which wording has been reproduced exactly from a source?
- Which passages restate one source's meaning in the document author's own words?
- Which passages synthesize ideas from several sources into a new formulation?
- Are quotation marks, block quotation, or other conventions making direct borrowing unmistakable?
- Has a paraphrase remained too close to the source's language or sentence structure?
- Does the synthesis accurately preserve the contributing sources without implying that any one source stated the combined conclusion?
- What attribution is needed so readers can distinguish source language, source ideas, and the document author's own synthesis?
- Was the element reproduced directly, modified, redrawn, translated, or created from underlying source data?
- What source produced the original material?
- Does the document need permission, a license notice, or another form of rights acknowledgement?
- How should the attribution distinguish "reproduced from" from "adapted from" or "based on"?
- Have substantive changes been made that could alter the original interpretation?
- Does the caption or note make both authorship and evidentiary provenance clear?
- What attribution allows readers to locate the original while accurately describing what the current document has changed?
- What bibliographic or identifying information is currently missing?
- Can the missing details be recovered from the original source, publisher, repository, DOI record, or authoritative catalogue?
- Are different versions of the source reporting conflicting metadata?
- Which version was actually consulted and should therefore be referenced?
- What information can legitimately remain absent under the governing citation system?
- What should be done when a source cannot be identified reliably enough to support a formal reference?
- How can incomplete references be flagged and resolved before finalization rather than silently guessed?
Using Pinpoint References for Long or Complex Sources
- What exact page, section, paragraph, table, clause, timestamp, or other location contains the material being relied on?
- Would a general citation force the reader to search an unnecessarily large source?
- Does the governing citation system support the type of pinpoint reference needed?
- Is the source paginated or structured consistently across formats and editions?
- What locator remains stable enough for another reader to reproduce the lookup?
- When does a broad reference remain sufficient because the document relies on the source as a whole?
- Which claims benefit enough from pinpointing to justify the added citation detail?
Balancing Evidence Traceability Against Reading Flow
- How frequently do citations interrupt the current prose?
- Which citations are essential for verification and which are adding little evidentiary value?
- Can several closely related claims be structured so their shared evidentiary basis is clearer?
- Would notes or another citation form reduce disruption without weakening traceability?
- Are readers likely to need immediate source visibility or primarily a clean reading experience?
- Is any attempt to make the prose smoother creating ambiguity about where important claims came from?
- What citation density preserves both credible sourcing and readable prose for this document's purpose?
Checking That the Final Reference List Matches the Sources Actually Used
- Does every source cited in the document appear in the final reference list where the citation system requires it?
- Does every reference-list entry correspond to a source actually cited or intentionally included?
- Are author names, titles, dates, editions, identifiers, and links accurate?
- Do in-text citations and reference entries use consistent names and dates?
- Have sources removed during revision also been removed from the reference list?
- Are duplicated entries or different records for the same source still present?
- What final cross-check will confirm that the citation system is complete and internally consistent?
Revising Substance, Scope, and Reasoning
Revising a Draft After Its Central Purpose Has Shifted
- What has changed about the document's central purpose?
- Which existing sections were developed for the previous purpose rather than the current one?
- What material remains useful despite the shift?
- What new content or reasoning does the revised purpose require?
- Which conclusions, examples, or evidence now receive too much or too little emphasis?
- Does the architecture still support the new purpose or is structural revision also necessary?
- What should be removed or rewritten so the draft no longer carries traces of the superseded purpose?
Repairing a Claim That the Available Evidence Does Not Support
- What exact claim currently exceeds the available evidence?
- Which part of the claim is unsupported: certainty, scope, causality, magnitude, generalization, or something else?
- What evidence does remain credible and relevant?
- Can the claim be narrowed, qualified, or reframed into something defensible?
- Would additional research realistically close the evidence gap?
- What downstream reasoning or conclusions depend on the stronger unsupported version?
- How should the revised claim propagate through the document so the original overstatement does not survive elsewhere?
Removing Scope That Accumulated During Research and Drafting
- What material entered the draft beyond the agreed scope?
- Why was each added topic included?
- Does it materially contribute to the governing question or merely reflect interesting research?
- Has the expanded material created new obligations for evidence, explanation, or conclusion?
- What can be removed without making the remaining reasoning incomplete?
- Should any excluded material move to an appendix, separate document, or future work?
- What revised boundary should guide the rest of the substantive revision?
Returning to Research When Revision Reveals Missing Evidence
- What claim, conclusion, or section cannot currently be revised responsibly because evidence is missing?
- Why was the gap not visible during the original research?
- How material is the missing evidence to the document's overall conclusion?
- What specific research question now needs to be answered?
- What source type would best address that question?
- Can the document proceed with a narrower claim if the evidence cannot be obtained?
- When has enough additional research been completed to resume revision without reopening the entire research phase?
Resolving Substantive Contradictions Across the Draft
- Which statements, findings, assumptions, or conclusions contradict each other?
- Are the contradictions genuine or caused by different contexts, definitions, time periods, or levels of analysis?
- Which version is better supported by evidence?
- Has the document changed position over time without updating earlier sections?
- Could both statements remain valid if their conditions are made explicit?
- What downstream arguments depend on each conflicting proposition?
- How should the contradiction be resolved so the document presents one coherent substantive position where the evidence permits one?
Revising a Recommendation That No Longer Follows From the Analysis
- What recommendation does the draft currently make?
- What analysis was originally supposed to justify it?
- What new or revised reasoning has weakened that connection?
- Is the recommendation still defensible under different criteria or evidence?
- Should it be narrowed, conditioned, replaced, or removed entirely?
- What alternative actions are now better aligned with the analysis?
- Which surrounding sections must change so the document does not continue steering the reader toward the superseded recommendation?
Retesting Important Assumptions After the Full Argument Is Visible
- What assumptions does the completed draft now reveal as central to the argument?
- Which assumptions received little scrutiny earlier because their importance was not yet apparent?
- What claims or conclusions would change if those assumptions failed?
- What evidence currently supports or challenges them?
- Are any assumptions actually judgments, constraints, or unresolved decisions that should be labeled differently?
- What sensitivity or alternative-case analysis is needed?
- Which assumptions must be revised, disclosed, or researched before the substantive argument is stable?
Removing Interesting Material That No Longer Contributes to the Document
- What passage or material is being considered for removal?
- What function does it currently perform?
- Does it support a necessary claim, reader need, or document requirement?
- Is it being preserved mainly because substantial effort went into producing it?
- Would removing it create any substantive gap elsewhere?
- Is there another location or artifact where it would be genuinely useful?
- What does the document gain in focus, clarity, or proportion if the material is removed?
Revising Conclusions After New Evidence Changes the Understanding
- What new evidence materially changes the previous interpretation?
- Which existing conclusions are directly affected?
- Does the evidence weaken, qualify, broaden, or reverse those conclusions?
- What earlier reasoning steps must also be revised?
- Are any recommendations no longer justified?
- What remaining evidence still supports the revised position?
- How should the document communicate the new conclusion without leaving contradictory traces of the earlier one?
Deciding Whether the Draft Needs Local Repair or Substantial Reconstruction
- What problems are currently visible in the draft?
- Are they isolated to particular claims, sections, or passages?
- Do several local defects share the same deeper cause?
- Has the purpose, reasoning, scope, or central conclusion changed enough to invalidate large parts of the draft?
- Would repeated local edits preserve a fundamentally weak structure or argument?
- What material can confidently be retained if the draft is reconstructed?
- Which level of intervention will fix the originating problem rather than merely its symptoms?
Revising Structure, Coherence, and Consistency
Diagnosing a Draft Whose Actual Structure Is Hard to See
- What does each existing section and paragraph actually do?
- Does the current sequence reveal a recognizable organizing logic?
- Where do headings describe topics without showing the role those topics play?
- Which sections contain several unrelated functions?
- What important reasoning occurs outside the place where the structure suggests it should occur?
- Does the draft follow the intended architecture or has a different structure emerged during writing?
- What structural map best represents the document as it currently exists before any reorganization begins?
Reordering Sections That Appear in the Wrong Sequence
- What dependency or reader need suggests the current section order is wrong?
- What does the reader need to know before each affected section?
- Are conclusions, evidence, context, or definitions appearing before their prerequisites?
- Would moving one section reduce repetition or awkward forward references?
- What transitions or cross-references would become unnecessary after reordering?
- Could the proposed new order create different dependency problems elsewhere?
- What sequence gives the reader the most coherent progression through the document's reasoning or use path?
- Which sections currently appear to perform substantially the same job?
- What repeated claims, evidence, explanations, or background appear across them?
- Is any meaningful distinction being obscured by treating them as duplicates?
- Would a merged section improve coherence or become too broad?
- What common section purpose could govern the combined material?
- What repetition can be removed once the material is brought together?
- How should the merged section be organized so distinct subtopics remain understandable without recreating the original fragmentation?
Splitting a Section That Contains Several Distinct Jobs
- What different functions is the current section performing?
- Can each function generate a distinct reader question or reasoning step?
- Where does the section visibly shift purpose, evidence type, or argument?
- Are readers likely to need one part without the others?
- What structure would separate the functions without creating unnecessary micro-sections?
- What common context should remain outside the split to avoid repetition?
- How should the resulting sections be ordered so their relationship remains clear?
Adding a Missing Section or Reasoning Step
- What does the reader currently need that the architecture does not provide?
- Where does the document jump from one conclusion or topic to another without sufficient development?
- Is the missing material substantive content, explanation, evidence, comparison, or transition?
- Does the gap justify a full section or only a smaller addition?
- Where should the new material sit according to the document's dependency structure?
- What existing sections need adjustment once the gap is filled?
- Does the addition solve a real structural need or merely make the outline look more symmetrical?
Repairing Transitions That Reveal a Break in the Underlying Logic
- What feels discontinuous at the transition point?
- Are the two passages genuinely related in the current order?
- What reasoning step is missing between them?
- Is the problem caused by wording or by a deeper structural gap?
- Would moving, merging, splitting, or adding material solve the issue better than a transitional phrase?
- What relationship should the reader understand between the two sections?
- What revision makes that relationship real rather than merely verbally asserted?
Reconciling an Executive Summary With the Main Document
- What conclusions, recommendations, and qualifications appear in the main document?
- Does the executive summary represent them accurately?
- Has the main body changed since the summary was drafted?
- Does the summary introduce claims or certainty that the analysis does not support?
- Are material limitations omitted in a way that could mislead a reader who reads only the summary?
- Does the summary emphasize the same priorities the full document ultimately establishes?
- What changes are needed so the summary functions as a faithful compressed representation rather than a competing version of the document?
Reconciling Conceptual Distinctions That Have Drifted Across Sections
- Which concepts are defined or used differently across the document?
- Are the differences intentional or the result of separate drafting histories?
- Does the document collapse distinctions that were important earlier?
- Has one term gradually changed meaning as the argument developed?
- What substantive consequences follow from the inconsistent conceptual treatment?
- Which formulation best reflects the final reasoning?
- How should the distinction be corrected throughout the document without reducing it to mere word replacement?
Rebalancing Sections That Have Developed at Unequal Depth
- Which sections are disproportionately long or detailed?
- Does the imbalance reflect genuine importance or simply where more material happened to be available?
- Which sections are too thin to perform their intended function?
- Has one topic accumulated evidence and examples beyond what the reader needs?
- Does another section need deeper reasoning or evidence rather than simply more words?
- What redistribution, compression, or expansion would better reflect the document's priorities?
- How can the sections become proportionate without forcing artificial equality of length?
Reconstructing a Document That Is Locally Strong but Globally Incoherent
- Which individual sections or passages are substantively strong?
- What prevents them from forming one coherent document?
- Is the global problem primarily purpose, argument, sequence, scope, terminology, or architecture?
- What central through-line should connect the strongest existing material?
- Which sections can be retained substantially intact and which need relocation or rewriting?
- What material must be removed because it cannot be integrated into the reconstructed logic?
- What new architecture best preserves valuable local work while solving the document-level coherence problem?
Editing for Clarity, Concision, Style, and Language
Rewriting Sentences That Are Difficult to Understand
- What is the sentence actually trying to say?
- Which part creates difficulty: syntax, abstraction, ambiguity, length, terminology, or too many ideas?
- Can the main actor and action be identified clearly?
- Are necessary conditions or qualifications buried inside the sentence?
- Should the sentence be divided into more than one unit?
- What precision would be lost by simplifying it?
- What revised wording makes the meaning easier to grasp without changing the substance?
Shortening Wordy Prose Without Removing Necessary Meaning
- What essential point must the passage preserve?
- Which words or phrases repeat information already implied?
- Are abstract phrases replacing simpler direct verbs or nouns?
- Does the passage restate the same idea in several forms?
- Which examples, qualifiers, or background details are genuinely necessary?
- Would compression remove a meaningful distinction or condition?
- What is the shortest formulation that preserves the intended meaning, tone, and evidentiary precision?
Making Actors and Actions More Explicit
- Who is actually performing the action described?
- Is the actor currently hidden behind passive construction, abstraction, or nominalization?
- Does the document know the actor, or is the actor genuinely unknown or irrelevant?
- Would naming the actor improve accountability or comprehension?
- What concrete action is hidden inside an abstract noun phrase?
- Are responsibility and authority being blurred by vague wording such as "it was decided" or "action will be taken"?
- How can the sentence make agency clear without falsely assigning responsibility the evidence does not establish?
Replacing Unnecessary Jargon Without Losing Technical Precision
- Which terms are likely to be unfamiliar to the intended reader?
- Is the specialist term necessary because it carries a precise meaning?
- Can ordinary language express the same concept accurately?
- Would replacing the term erase a distinction important to the field?
- Could the technical term be retained but defined briefly at first use?
- Are fashionable or organizational expressions being used where simpler language would be clearer?
- What wording gives the reader maximum clarity while preserving necessary technical accuracy?
Adjusting Tone to the Document's Purpose and Audience
- What relationship should the document establish with its reader?
- Does the current tone fit the document's function and level of consequence?
- Is the language too informal, distant, promotional, defensive, tentative, or authoritative?
- Where does tone vary unintentionally across sections?
- Are confidence and caution aligned with the evidence rather than with stylistic preference?
- What organizational or professional conventions legitimately constrain tone?
- What adjustments make the language appropriate without creating an artificial voice?
Correcting Inconsistent Voice, Tense, and Point of View
- What voice, tense, and point of view should govern the document?
- Where does the draft shift among them without a substantive reason?
- Are tense changes justified by differences between past events, current conditions, and future actions?
- Does the document alternate between "we," "the organization," impersonal wording, and other perspectives inconsistently?
- Are active and passive constructions being used deliberately or randomly?
- What exceptions are substantively necessary?
- How can the document be normalized without mechanically forcing every sentence into the same grammatical form?
- Which words, sentence openings, transitions, or structures recur conspicuously?
- Is the repetition serving clarity or merely reflecting a drafting habit?
- Are several paragraphs using the same rhetorical pattern regardless of content?
- Does formulaic wording make important distinctions sound artificially identical?
- What repeated terms must remain stable because they are technical or defined concepts?
- Where can syntax or phrasing vary without changing meaning or tone?
- How can the prose become more natural while retaining structural consistency where consistency actually helps the reader?
Normalizing Terminology Across the Document
- Which concepts are referred to by more than one term?
- Are those terms genuine synonyms or do they carry distinct meanings?
- What preferred term should represent each stable concept?
- Where could replacing terminology accidentally erase a substantive distinction?
- Are abbreviations introduced and used consistently?
- Do tables, figures, appendices, and headings use the same terminology as the prose?
- What controlled terminology should be applied across the document once the conceptual distinctions are settled?
Copyediting Grammar, Punctuation, Spelling, and Usage
- What grammar or usage errors remain in the draft?
- Is punctuation supporting the intended meaning clearly?
- Are spelling conventions consistent with the required language variety or house style?
- Do capitalization, numerals, dates, units, and abbreviations follow one standard?
- Are recurring errors systematic enough to require a document-wide search?
- Could any apparent correction alter a deliberate technical term, quotation, or source wording?
- What final copyediting pass will correct surface errors without reopening settled substantive language unnecessarily?
Recognizing When Further Stylistic Polishing Is No Longer Improving the Document
- What reader problem would the proposed edit actually solve?
- Does the change improve clarity, precision, concision, consistency, or audience fit?
- Are successive edits merely exchanging one acceptable formulation for another?
- Is stylistic preference beginning to destabilize settled terminology or meaning?
- What higher-priority work remains unfinished elsewhere in the document?
- Has the prose reached the required standard for its intended use?
- What stopping rule will prevent low-value polishing from consuming effort without materially improving the artifact?
Collaborating and Integrating Multiple Contributors
Dividing Work Among Contributors Without Fragmenting the Document
- What major parts of the document can be developed independently?
- Which sections depend heavily on shared reasoning or evidence and should not be divided too early?
- What expertise makes particular contributors appropriate for particular parts?
- What common purpose, architecture, terminology, and source base must everyone share?
- Where could separate ownership create duplication or gaps between sections?
- Who remains responsible for the coherence of the document as a whole?
- What division of work captures the benefits of specialization without turning the artifact into a collection of disconnected contributions?
Establishing One Person to Integrate the Document as a Whole
- Who is best positioned to understand the document's complete purpose, reasoning, and audience?
- What authority does the integrator have to reconcile overlaps, restructure material, and normalize terminology?
- Which substantive decisions must remain with subject owners or another authority?
- What inputs does the integrator need from every contributor?
- When should integration occur rather than being postponed until all drafting is finished?
- How will disagreements between local section owners and whole-document needs be resolved?
- What responsibilities must remain clearly assigned to the integrator through finalization?
Aligning Contributors on the Architecture Before They Draft Independently
- What document architecture has been agreed before sections are distributed?
- What function does each contributor-owned section need to perform?
- What inputs and outputs connect neighboring sections?
- Which shared definitions, claims, assumptions, and evidence must remain consistent?
- What decisions are settled and should not be independently reinterpreted?
- Where is flexibility deliberately left to individual contributors?
- What alignment artifact or discussion will give contributors enough common context to draft compatible material?
Integrating Sections Written in Different Voices
- What differences in tone, syntax, terminology, detail, or perspective are visible across sections?
- Which differences reflect legitimate subject-specific needs rather than inconsistency?
- What common voice is appropriate for the final document?
- Are contributors making different assumptions about the reader's knowledge?
- Which passages require substantive reconciliation before stylistic normalization can work?
- How much local character can remain without making the document feel fragmented?
- What integration pass will create continuity while preserving technically necessary differences?
Preventing Gaps and Duplication Between Contributor-Owned Sections
- What exact territory is assigned to each contributor?
- Where do neighboring sections share concepts, evidence, or responsibilities?
- Which material is currently being drafted by more than one person?
- What important topic is each contributor assuming somebody else will cover?
- Which definitions or background should appear once rather than be repeated across sections?
- How should cross-section dependencies be tracked while drafting continues?
- What whole-document review will identify remaining gaps or duplicate treatment before final integration?
Coordinating Sections That Depend on Work Being Produced Elsewhere
- What information or decision does this section need from another contributor?
- Is that dependency already settled, provisional, or still unknown?
- What can be drafted safely before the upstream work is complete?
- What assumptions would create rework or contradiction if used prematurely?
- How should changing upstream material be communicated to dependent contributors?
- Who is responsible for confirming that the dependency has been resolved?
- How can the team sequence work so dependencies are managed without unnecessarily blocking independent progress?
Resolving Substantive Disagreement Between Contributors
- What exact proposition, interpretation, or recommendation do contributors disagree about?
- Is the disagreement about evidence, reasoning, requirements, audience, values, or professional judgment?
- What evidence supports each position?
- Are the positions genuinely incompatible or based on different assumptions or scopes?
- Who has authority or subject responsibility to resolve the issue?
- Should the document acknowledge legitimate unresolved disagreement rather than forcing false consensus?
- What decision must be recorded so the disagreement does not repeatedly reopen during drafting?
Keeping Contributors Aligned on Sources, Terminology, and Settled Decisions
- What shared sources or evidence should all contributors treat as authoritative?
- Which terminology has been defined and should remain stable?
- What substantive decisions have already been settled?
- Where are contributors currently using outdated sources, labels, or assumptions?
- How will changes to shared decisions or terminology be communicated?
- What lightweight shared record can prevent everyone from maintaining separate versions of the same context?
- How often does alignment need to be checked without creating unnecessary coordination overhead?
Incorporating Late Contributions Without Destabilizing the Whole Document
- What new material has arrived and why is it late?
- Does it introduce genuinely new evidence, reasoning, requirements, or merely another formulation?
- Which existing sections would need to change if the contribution is accepted?
- Does the new material conflict with settled decisions or approved content?
- What benefit justifies the disruption of incorporating it now?
- Can the contribution be deferred, narrowed, or placed in supporting material without weakening the current document?
- What controlled integration process will prevent one late addition from causing unnoticed inconsistencies elsewhere?
Handing Work Between Contributors Without Losing Context or Responsibility
- What exactly is being handed from one contributor to another?
- What purpose, decisions, assumptions, sources, and unresolved issues does the recipient need to understand?
- Which parts of the work are settled and which remain provisional?
- What responsibilities transfer and what responsibilities remain with the original contributor?
- Are there source files, comments, or working notes that need to accompany the handoff?
- What misunderstanding is most likely if the recipient sees only the current text?
- What handoff record or conversation gives the next contributor enough context to continue without reconstructing the work from scratch?
Reviewing, Incorporating Feedback, and Managing Approval
Determining What Kind of Review the Document Needs Next
- What stage of development has the document actually reached?
- What kinds of defects or uncertainties are still most likely to matter?
- Does the next review need to test purpose, reasoning, evidence, usability, compliance, language, or final accuracy?
- What would be premature for reviewers to focus on at this stage?
- Which unresolved issues should be settled before a narrower review begins?
- What review would produce information that materially changes the next development step?
- What should reviewers be explicitly asked to examine in this round?
Choosing Reviewers With the Right Expertise or Authority
- What knowledge, experience, user perspective, or authority does the document need from a reviewer?
- Which parts require subject-matter expertise rather than general editorial judgment?
- Who can evaluate whether the document will work for its intended users?
- What risk, compliance, legal, security, or other specialist review is necessary?
- Which reviewer has decision or approval authority rather than merely advisory expertise?
- Where would adding more reviewers create redundancy or conflicting preferences without improving quality?
- What combination of reviewers covers the material risks without turning review into an uncontrolled open consultation?
Asking Reviewers for Targeted Feedback
- What is the document's current maturity when it is sent for review?
- Which questions or uncertainties would be most valuable for the reviewer to examine?
- What parts are already settled and should not be reopened without a material reason?
- What kinds of comments would be premature or outside the reviewer's role?
- What context does the reviewer need to understand the document's purpose and intended use?
- What deadline and feedback method will make the review usable for the development process?
- How should the review request be framed so the reviewer evaluates the document rather than simply offering general impressions?
- Which comments identify errors, unsupported reasoning, missing requirements, or material reader problems?
- Which comments concern important improvements rather than personal preference?
- Are several comments different symptoms of the same underlying weakness?
- Which changes would affect the largest amount of downstream material?
- What comments conflict with already settled requirements or decisions?
- Which low-impact comments can be deferred or declined without weakening the document?
- What order of resolution will address the most consequential feedback before local polishing begins?
Resolving Conflicting Reviewer Feedback
- What exactly does each reviewer want changed?
- Is the disagreement about evidence, purpose, audience, requirement, risk, judgment, or style?
- What expertise or authority does each reviewer bring to the disputed issue?
- Which position is better supported by the document's purpose, evidence, and governing requirements?
- Can both concerns be addressed without creating an incoherent compromise?
- Who has authority to decide when the disagreement cannot be resolved by evidence alone?
- How should the final decision be recorded so the same conflict does not repeatedly return?
Distinguishing a Real Document Weakness From a Reviewer's Stylistic Preference
- What concrete reader or document problem does the comment identify?
- Would the suggested change improve accuracy, logic, clarity, usability, consistency, compliance, or risk control?
- Is the reviewer reacting mainly to a personal wording or formatting preference?
- Could a different change solve the underlying problem better than the reviewer's proposed wording?
- Do other readers or reviewers show evidence of the same difficulty?
- Would accepting the comment destabilize settled terminology or introduce a new weakness?
- What response addresses material problems while avoiding unnecessary churn between equally acceptable formulations?
Handling a Late Reviewer Who Wants to Reopen a Settled Decision
- What settled decision does the reviewer want reconsidered?
- What new evidence, requirement, risk, or reasoning is being offered?
- Is the objection materially different from issues already considered?
- What parts of the document would need to change if the decision were reopened?
- What consequence would follow from declining to reopen it?
- Does the new information meet the threshold for revisiting a settled decision?
- How should the decision to reopen or preserve the existing position be documented?
- Which review comments are material enough to require an explicit disposition?
- What change, decision, or explanation resulted from each comment?
- Who decided whether the comment would be accepted, modified, deferred, or rejected?
- Which comments remain unresolved and could still block approval?
- Can the current document be traced to the decisions made during review?
- What level of tracking is proportionate to the consequence and formality of the document?
- What record should remain after review so future contributors understand why material choices were made?
Clarifying What Has Actually Been Approved, Including Conditions and Exceptions
- What exactly did the approver accept: the document, its analysis, a recommendation, publication, or an underlying decision?
- Did the approver have authority over everything that others are treating as approved?
- What conditions, limitations, exceptions, or required follow-up accompanied the approval?
- Which statements in the document remain analysis, assumptions, or recommendations rather than approved commitments?
- Does the approval apply to this exact version of the document?
- What remains unresolved despite the approval?
- How should the approved status be recorded so users do not infer more authority than was actually granted?
Determining When the Document Has Received Enough Review to Move Forward
- What review objectives were established for the document?
- Have the required substantive, technical, user, risk, editorial, and approval reviews been completed where applicable?
- What material issues remain unresolved?
- Are new review rounds still identifying important defects or mainly generating preferences?
- What consequence would justify seeking another independent review?
- Has the document reached the quality and assurance level appropriate to its intended use?
- What evidence supports moving forward rather than extending review indefinitely?
Controlling Versions, Decisions, and Document Status
Establishing One Authoritative Working Version
- Where should the current working document live?
- Who is allowed to edit or integrate changes into that version?
- What other copies currently compete with it as apparent sources of truth?
- How will contributors know they are working from the latest authoritative content?
- What collaboration or access method minimizes the creation of parallel versions?
- How should temporary exports or personal copies be distinguished from the authoritative working version?
- What simple rule will make it possible to answer "Which version should we edit?" unambiguously?
Recovering From Several Parallel Copies of the Same Document
- How many active copies exist and who has been editing each one?
- Which copy contains the most current substantive decisions?
- What unique changes appear in each version?
- Are any changes contradictory or based on superseded assumptions?
- Who should decide which changes are integrated into the recovered authoritative version?
- How can the copies be reconciled without blindly accepting the newest timestamp?
- What control should be introduced afterward to prevent the same fragmentation from recurring?
Distinguishing the Current Working Draft From the Current Approved Version
- What is the latest version currently being edited?
- What is the latest version that has actually received formal approval?
- Which changes in the working draft have not yet been approved?
- Where should each version be stored and labeled?
- Who needs access to the working draft and who should rely only on the approved version?
- What risk arises if the newest file is assumed automatically to be the authoritative one?
- How can users identify both states without relying on ambiguous filenames such as "final" or "latest"?
Making Document Version and Status Unambiguous
- What version identifier should distinguish this document from earlier and later states?
- What status does the document currently have: draft, under review, approved, released, superseded, or another defined state?
- Where should version and status information appear?
- What event or decision changes the status from one state to another?
- Who has authority to assign or change that status?
- Are distributed copies carrying enough information to reveal when they are no longer current?
- What convention will keep version identity understandable without creating unnecessarily complex control?
Preserving a Useful History of Material Changes
- What changes are important enough to preserve in a version history?
- Does the record need to capture what changed, why, when, and by whom?
- Which minor editorial changes do not justify separate historical entries?
- What decisions or requirement changes should remain visible even after the text itself changes?
- How much historical detail will future reviewers or maintainers realistically need?
- Where should change history live so it remains connected to the authoritative document?
- What record preserves meaningful development history without becoming an exhaustive log of every edit?
Recording Important Decisions That Future Reviewers May Otherwise Reopen
- What material document-development decisions have been settled?
- Why was each decision made?
- What alternatives were considered?
- What evidence, requirement, or authority supported the chosen direction?
- Under what new circumstances would reopening the decision be justified?
- Where should the rationale be recorded so future contributors can find it?
- How can the record prevent accidental re-litigation without making legitimate reconsideration impossible?
Preventing Superseded Content From Reappearing in a New Revision
- What content, decision, source, or wording has already been superseded?
- Where does the obsolete material still exist in older drafts, notes, or contributor copies?
- Why was it replaced or rejected?
- Could copying from an older document silently reintroduce it?
- How can contributors identify which historical material is unsafe to reuse?
- What review should specifically look for regressions after large merges or AI-assisted revisions?
- What control will keep superseded content available for history without allowing it to become current again?
Keeping Comments, Proposed Changes, and Current Text From Becoming Confused
- Which material represents current accepted text?
- Which material is only a suggestion, unresolved comment, tracked change, or alternative formulation?
- Are contributors editing the same document under different assumptions about what has been accepted?
- Who has authority to resolve proposed changes?
- What should happen to comments once their underlying issue has been decided?
- How can unresolved issues remain visible without being mistaken for approved content?
- What document state should exist before the next review or approval round begins?
Managing Exported, Downloaded, or Circulated Copies That Can Become Stale
- What copies of the document exist outside the authoritative working location?
- Who may continue relying on those copies after the source document changes?
- Can exported files display a version, date, status, or link back to the authoritative source?
- Which distributed copies must remain fixed as records rather than update with the working document?
- What process should replace or withdraw obsolete operational copies?
- How can recipients tell whether a local copy is still current?
- What distribution practice balances convenient access with the risk of stale information remaining in use?
Determining When a Changed Document Requires Renewed Approval
- What has changed since the document was last approved?
- Does the change affect substance, obligations, recommendations, risk, authority, or intended use?
- What approval rule or threshold governs modifications?
- Are the changes purely editorial or could they alter how the document is interpreted or applied?
- Which previous approvals depended on content that has now changed?
- Does the full document need reapproval or only the materially changed portion?
- What approval status should the revised document carry until the necessary review is complete?
Final Verification and Proofreading
Verifying Material Factual Claims Before Finalization
- Which factual claims would create the greatest problem if they were wrong?
- What authoritative source supports each high-risk claim?
- Is the source current and applicable to the exact context?
- Has the claim changed during drafting in a way that exceeds what the source supports?
- Are any apparently factual statements actually inference, judgment, or assumption?
- What claims originated through AI or secondary summaries and therefore require independent verification?
- What final evidence check is necessary before the document can be treated as factually reliable?
Checking That Citations Actually Support the Claims They Accompany
- What exact claim is each citation intended to support?
- Does the cited source actually contain evidence for that claim?
- Has the draft made the claim broader, stronger, or more certain than the source permits?
- Are page, section, clause, or other pinpoint references correct?
- Do grouped citations all support the same proposition or only different parts of it?
- Are any citations fabricated, malformed, inaccessible, or carried forward from superseded text?
- What should be changed when the evidence and cited claim do not match?
- Do repeated facts, numbers, dates, definitions, and names agree everywhere they appear?
- Are conclusions stated consistently in the summary, body, tables, and supporting material?
- Does the document use important terminology consistently?
- Are assumptions treated the same way across different sections?
- Do figures and tables agree with the prose that interprets them?
- Have revisions created contradictions between earlier and later passages?
- What document-wide searches or comparisons can reveal inconsistencies that local proofreading would miss?
Confirming That All Required Content Is Present
- What explicit requirements must the finished document satisfy?
- Are all mandatory sections, fields, declarations, attachments, and supporting materials present?
- Have any required elements disappeared during restructuring or shortening?
- Does each required section contain substantive content rather than merely a heading?
- Are all previously identified material gaps resolved or explicitly accepted?
- What requirements checklist or source should be used for the final comparison?
- What missing element would prevent the document from being complete for its intended use?
Verifying Names, Numbers, Dates, Quotations, and Other High-Risk Details
- Which details are especially vulnerable to transcription or revision errors?
- Do names, titles, organizations, and technical terms match authoritative sources?
- Are dates and time periods accurate and internally consistent?
- Are numbers, units, percentages, totals, and calculations correct?
- Do direct quotations reproduce the original wording accurately and completely enough for their use?
- Have any copied values lost qualifiers, denominators, currencies, or measurement definitions?
- What independent check can confirm these details rather than relying on familiarity with the draft?
Testing Links, Cross-References, Contents Entries, and Internal Navigation
- Does every external link still open the intended destination?
- Do internal cross-references point to the correct section, table, figure, appendix, or note?
- Does the table of contents match the final heading structure and pagination where applicable?
- Are bookmarks, anchors, indexes, or navigation links functioning correctly?
- Have moved or deleted sections left stale references behind?
- Is link text understandable without relying solely on surrounding context where accessibility requires it?
- What should be tested again after the final export or publication step?
- Are headings, sections, lists, notes, tables, figures, and appendices numbered correctly?
- Is formatting consistent with the required template or style?
- Do tables and figures fit, render, and remain readable in the final format?
- Are captions accurate and attached to the correct elements?
- Are labels, legends, units, and source notes complete?
- Have page breaks, column widths, or layout changes separated elements from essential context?
- What final visual inspection is needed beyond automated formatting checks?
- Does the final document use a meaningful semantic heading hierarchy?
- Are tables structured so row and column relationships remain accessible?
- Do informative images and complex visuals have appropriate text alternatives?
- Is meaning communicated through more than color or spatial position alone?
- Are link text, reading order, lists, and navigation understandable with assistive technologies?
- Did the final export preserve accessibility features from the source document?
- What accessibility problems remain serious enough to block release or require an alternative format?
Reviewing the Actual Exported or Rendered Artifact for Production Errors
- What exact file or format will the recipient actually receive?
- Did conversion change fonts, spacing, pagination, links, tables, figures, or special characters?
- Are any lines, images, footnotes, or table cells clipped or displaced?
- Did the export preserve comments, metadata, hidden content, or tracked changes that should not be released?
- Are accessibility and navigation features still functioning after conversion?
- Does the rendered artifact match the approved source in all material respects?
- What defects appear only in the final output and therefore require correction before release?
Proofreading After the Last Substantive Change
- What changed since the previous proofreading pass?
- Could those changes have introduced spelling, punctuation, numbering, formatting, or cross-reference errors?
- Are there unresolved placeholders, comments, tracked changes, or drafting notes?
- Has any text been accidentally omitted, duplicated, or moved during final revision?
- Are final line breaks, headings, lists, footnotes, and page transitions clean?
- Is the proofreading being done against the exact release candidate rather than an earlier draft?
- What final correction threshold will prevent substantive rewriting from restarting during the proof stage?
Preparing the Document for Release and Use
- What submission rules govern the document?
- Are format, length, filename, required fields, declarations, attachments, and supporting materials compliant?
- What submission portal, address, or process must be used?
- Who is authorized to submit the document?
- Does the submitted version exactly match the final approved version?
- What receipt, confirmation, or evidence of submission should be preserved?
- What last check should occur immediately before the document leaves the author's control?
Preparing a Document for Public or External Publication
- What additional scrutiny follows from making the document externally available?
- Are facts, citations, permissions, confidentiality, accessibility, and legal or policy requirements satisfied?
- What contextual information must be self-contained because external readers lack internal knowledge?
- Are links, metadata, titles, summaries, and publication details ready for the public environment?
- Has sensitive or internal-only material been removed appropriately?
- Who has authority to approve external publication of this exact version?
- What published artifact should be checked immediately after release to confirm it appears and functions as intended?
Preparing an Approved Document to Become the Authoritative Version
- What approval has been granted and to which exact version?
- What identifier and effective date should the authoritative version carry?
- Where will the approved document reside as the source of truth?
- What working drafts or superseded versions need to be relabeled, restricted, or removed from active use?
- Who needs to know that the authoritative version has changed?
- What dependent documents, systems, or processes should reference the new version?
- What evidence should be preserved showing when and by whom the document became authoritative?
Preparing a Document to Support a Presentation or Decision Meeting
- What role will the document play before, during, and after the meeting?
- What information must decision-makers absorb before the discussion begins?
- Which conclusions, options, tradeoffs, or unresolved issues need to be easy to locate quickly?
- What material belongs in the document rather than in spoken presentation?
- What questions or challenges are likely to arise during the meeting?
- How should any presentation materials remain consistent with the document's evidence and conclusions?
- What decision or follow-up record should connect the meeting outcome back to the document?
Preparing an Operational Document for Use in Real Work
- What task, process, decision, or behavior will depend on the document?
- Can users identify exactly when and how they are expected to use it?
- Are responsibilities, prerequisites, steps, exceptions, and escalation paths sufficiently clear?
- Is the authoritative version available at the actual point of use?
- What error could result from ambiguous or outdated instructions?
- Have representative users tested whether the document works under real operating conditions?
- What ownership and change control are needed once the document becomes operational?
Handing the Finished Document to the People Who Will Use or Maintain It
- Who needs to receive the finished artifact?
- What do recipients need to know about its purpose, status, limitations, and intended use?
- Who becomes responsible for maintaining or updating it after handoff?
- What source materials, editable files, decision records, or data should accompany the document?
- Which unresolved issues or known limitations must not disappear during handoff?
- What access or permissions do future users and maintainers require?
- How will responsibility be confirmed so the document does not become effectively ownerless?
- What filename clearly identifies the document without relying on informal labels such as "final"?
- What version, date, status, author, owner, or classification metadata is necessary?
- Which files need to be distributed together?
- Are supporting files named and organized so recipients can understand their relationship?
- What distribution method is appropriate to sensitivity, file size, access control, and intended use?
- Could packaging accidentally expose hidden, temporary, or confidential material?
- What release package gives recipients everything they need without creating unnecessary duplicate copies?
- What information is present in the working document that cannot be released to the intended audience?
- Why is the information restricted?
- Can it be removed without making the released document misleading or unusable?
- Does redaction conceal the information securely rather than merely covering it visually?
- Are comments, revision history, metadata, embedded files, or hidden layers carrying restricted information?
- Does removal require explanatory wording so readers understand an apparent gap?
- What verification confirms that protected material cannot be recovered from the released artifact?
Preserving the Correct Record or Archival Copy
- What exact version needs to be preserved as the official record?
- What evidence of approval, publication, submission, or effective date should accompany it?
- In what format should it be retained to preserve integrity and future readability?
- What source files or supporting evidence must also be retained?
- Who controls access, retention, and eventual disposition where formal rules apply?
- How will the archived record remain distinguishable from editable working copies?
- What information will future users need to understand the document's historical status and context?
Making the Final Go-or-No-Go Decision Before Release
- Have all material substantive issues been resolved or explicitly accepted?
- Has the exact release candidate passed the required verification and review?
- Are necessary approvals complete for this version and use?
- What known defects, uncertainties, or limitations remain?
- Could any remaining issue materially harm the intended use if release proceeds now?
- What consequence would follow from delaying release compared with releasing with the known limitation?
- Who has authority to make the final release decision, and what decision should be recorded?
Adapting and Reusing Documents for New Purposes and Contexts
Changing a Document's Length Without Breaking the Original Reasoning
- What new length or level of detail is required?
- Which conclusions, reasoning steps, evidence, and qualifications must remain regardless of length?
- What material can be compressed, summarized, expanded, or omitted without changing the meaning?
- Would shortening remove evidence needed to evaluate the conclusion?
- Would expanding the document introduce new claims or implications not present in the source?
- How should layers such as summary, main analysis, and supporting detail change with the new length?
- What comparison with the source will confirm that the revised length has not altered the original logic?
Adapting a Document for a Different Audience
- How does the new audience differ in knowledge, role, authority, needs, or concerns?
- What parts of the original document remain equally relevant?
- What terminology, context, examples, or explanation need to change?
- Which evidence or qualifications must remain unchanged even if they are less convenient for the new audience?
- Does the new audience need a different order or emphasis?
- Would adaptation alter the intended decision or action in a way that requires more than audience tailoring?
- What check will confirm that accessibility and relevance improved without changing the underlying substance improperly?
Reusing Existing Material for a Different Purpose
- What was the original material designed to accomplish?
- What new purpose is it expected to serve?
- Which parts remain valid under the new purpose?
- What assumptions or framing from the original use no longer apply?
- What new evidence, reasoning, context, or approval does the changed purpose require?
- Could reuse make outdated or purpose-specific material appear universally valid?
- What should be rewritten rather than copied so the new artifact is genuinely developed for its intended use?
- What new format is required and how will people use it?
- Which information relationships must survive the transformation?
- What prose should become tables, slides, fields, modules, or another structure?
- What information could be lost because the new format has less room or a different navigation model?
- Which citations, qualifications, and evidence links must remain traceable?
- Does the target format introduce accessibility or technical requirements absent from the source?
- How will the transformed artifact be checked against the original for semantic completeness and accuracy?
Adapting a Document to a Different Jurisdiction or Regulatory Context
- What laws, regulations, standards, institutions, or official terminology differ in the new jurisdiction?
- Which original claims depend on jurisdiction-specific assumptions?
- What definitions, obligations, thresholds, dates, units, or procedures need independent verification?
- Which parts of the source document remain transferable without change?
- Where would direct substitution of local terms create a false equivalence?
- What local professional or legal expertise is required before the adaptation can be relied on?
- How will the adapted version distinguish verified local requirements from content retained from the original context?
Translating or Localizing a Document Without Changing Its Meaning
- What language and locale will the adapted document serve?
- Which terminology requires consistent domain-specific translation?
- What dates, units, currencies, examples, conventions, or cultural references require localization rather than literal translation?
- Which legally or technically significant wording must be handled with particular care?
- Could a fluent translation alter certainty, obligation, responsibility, or scope?
- What source language should remain available for comparison when meaning is disputed?
- What bilingual or subject-matter review is needed to confirm semantic equivalence?
Reusing Individual Sections or Components in a New Document
- What function did the reusable section serve in its original document?
- Does the new document need the same function?
- What dependencies on earlier definitions, evidence, or assumptions are embedded in the section?
- Is the material still current and properly sourced?
- What terminology or cross-references depend on the original context?
- Would direct reuse introduce duplication or inconsistent reasoning into the new document?
- What adaptation is required before the component can function independently in its new setting?
Using an Older Document as the Starting Point for New Work
- Why is the older document a useful starting point?
- Which parts remain substantively current?
- What requirements, evidence, context, terminology, or decisions have changed since it was created?
- Are outdated conclusions being inherited merely because they already have polished wording?
- What should be independently reconsidered rather than carried forward?
- Which reusable structures or components genuinely save work without constraining new thinking?
- How can the new document preserve useful continuity without becoming an edited copy of assumptions that no longer hold?
Preserving Important Qualifications and Dependencies During Adaptation
- What qualifications materially limit the original document's claims or conclusions?
- What dependencies must remain true for the original reasoning to hold?
- Which of these are easy to lose when content is shortened, reformatted, translated, or retargeted?
- Has adaptation moved a conclusion away from the evidence or conditions that originally supported it?
- What wording or structure keeps essential limitations visible in the new version?
- Which qualifications no longer apply because the context has genuinely changed?
- How should every removed or altered qualification be justified before the adaptation is accepted?
Comparing an Adapted Version With the Source to Detect Semantic Drift
- What propositions, decisions, obligations, and conclusions should remain invariant between the versions?
- Has any wording change altered certainty, causality, scope, responsibility, or recommendation?
- Were important exceptions or conditions omitted?
- Has new material been introduced that the original evidence does not support?
- Do numbers, definitions, references, and factual details still match where they should?
- Are intentional differences traceable to the new audience, purpose, format, or jurisdiction?
- What discrepancies need correction before the adapted version can be treated as faithful to the source?
Maintaining, Updating, Replacing, and Retiring Documents
Assigning Ownership and a Review Cycle to a Living Document
- Who is accountable for keeping the document accurate and usable after release?
- What knowledge, authority, and access does the owner need to maintain it responsibly?
- Which events or changes should trigger review before the normal review date?
- How frequently should the document be reviewed if no specific trigger occurs?
- Who should contribute specialist input when parts of the document fall outside the owner's expertise?
- How will overdue reviews or unclear ownership become visible rather than allowing the document to age silently?
- What maintenance arrangement is proportionate to the document's consequence, rate of change, and operational importance?
Reviewing a Document When an Important Source Changes
- What source has changed, and which parts of the document depend on it?
- Does the change supersede, contradict, qualify, or merely update the information previously used?
- Which claims, figures, instructions, conclusions, or recommendations could now be affected?
- Does the new source apply immediately or only from a particular effective date or context?
- What other dependent evidence or reasoning needs to be rechecked because of the change?
- Can the document remain in use while the implications are assessed, or is an interim warning or withdrawal necessary?
- What revisions and renewed verification are required before the document can again be treated as current?
Correcting a Document After an Error or Operational Failure Is Discovered
- What exactly is wrong in the current document?
- How did the error contribute to, or become visible through, the operational failure?
- Which users, decisions, processes, or other documents may have been affected?
- Is the problem isolated to one statement or does it reveal a deeper weakness in reasoning, evidence, structure, or maintenance?
- What immediate correction or warning is necessary to prevent continued reliance on the error?
- What review is needed to ensure the proposed correction does not introduce a new problem?
- What should be recorded about the error, correction, and underlying cause so the same failure is less likely to recur?
Using Reader or User Feedback to Identify Needed Updates
- What recurring difficulty, misunderstanding, omission, or outdated information are users reporting?
- Is the feedback about the document itself or about a separate process, system, or capability problem?
- How representative is the feedback of the wider user population?
- What evidence from actual use supports or challenges the reported problem?
- Would the issue be best addressed through revised content, structure, navigation, examples, or another change?
- Could responding to one group's feedback make the document worse for other important users?
- What feedback threshold or pattern should trigger a formal update rather than an isolated editorial adjustment?
Responding to Changes in Laws, Standards, Processes, Systems, or Responsibilities
- What external or internal change has occurred?
- Which provisions, instructions, definitions, roles, or assumptions in the document depend on the previous state?
- When does the change take effect, and is there a transition period?
- What authoritative source establishes the new requirement or operating condition?
- Which related sections must be reconsidered rather than updated through simple term replacement?
- What approvals, specialist reviews, training, or downstream changes are required because the document is changing?
- How will the updated document make the new state clear while preventing continued reliance on superseded requirements?
Updating a Document Without Losing Control of Its Approved Status
- What change needs to be made to the approved document?
- Is the change editorial, administrative, corrective, or substantively significant?
- What rules determine whether the existing approval remains valid?
- Which portions can be updated without reopening settled content elsewhere?
- How should proposed changes be developed while the current approved version remains authoritative?
- What version and status should the revised document carry until any required reapproval is complete?
- How will users know exactly when the updated version replaces the previously approved one?
Deciding Whether a Change Requires a Minor Update or Major Redevelopment
- What has changed since the document was last developed or substantially reviewed?
- How much of the document's purpose, scope, evidence, reasoning, structure, or intended use is affected?
- Can the necessary changes be made locally without creating inconsistencies elsewhere?
- Are the original assumptions and central conclusions still valid?
- Would incremental editing preserve an architecture that no longer fits the current need?
- How much of the existing document can still be relied on without independent revalidation?
- What threshold indicates that redevelopment from the governing purpose and evidence is safer than continued patching?
Replacing a Document That Can No Longer Be Maintained Effectively
- What makes the current document increasingly difficult or unsafe to maintain?
- Has repeated revision created structural complexity, duplication, contradiction, or accumulated legacy content?
- Does the document still match the purpose, audience, process, and environment for which it is being used?
- Would another round of updates solve the underlying problem or merely postpone replacement?
- What useful content, evidence, decisions, or history should be preserved in a successor document?
- How should the replacement be developed without automatically inheriting weaknesses from the old document?
- What transition plan will establish the new document as authoritative while preventing parallel use of the obsolete one?
Retiring or Archiving a Document That Is No Longer Needed
- Why is the document no longer needed for active use?
- Does any legal, operational, historical, audit, or knowledge need require it to be retained?
- Should the document be archived, withdrawn, deleted, or retained under another defined status?
- What metadata is necessary to explain why and when it ceased to be current?
- Which active documents, systems, links, or processes still point to it?
- Who needs to be informed that the document should no longer guide current work?
- What disposition preserves necessary records while making it unmistakable that the document is no longer authoritative?
Preventing Obsolete Versions From Remaining in Active Use
- Where could superseded versions still be stored, linked, downloaded, printed, or locally retained?
- How can users identify the current authoritative version without relying on memory or filename conventions?
- Which old copies need to be removed, restricted, relabeled, redirected, or marked as superseded?
- What downstream documents, systems, bookmarks, or workflows still reference obsolete material?
- How should offline or distributed copies be handled when they cannot be centrally replaced?
- What controls can reduce the chance that search results or shared repositories surface obsolete versions as current?
- How will future checks confirm that superseded versions have stopped influencing active work?