The Proposal Questions Nobody Revisits

An R&D proposal can read beautifully and still fail to explain what the team will actually deliver, which assumptions could change the plan, or what makes the approach meaningfully new. These are not minor drafting problems. They affect whether the proposed work is intelligible and credible.

A useful internal review can isolate three kinds of question: actions and dependencies, clarifying assumptions, and intellectual property or novelty. Some teams maintain these as separate sections of their working documents. That is an editorial tool, not a federal proposal format.

There is no universal federal R&D requirement for “Section 8: Action Items,” “Section 9: Clarifying Questions,” and “Section 10: IP & Novelty.” The solicitation, agency instructions, and application forms govern what goes into a submitted proposal. Inventing a standard ten-section format confuses an internal drafting method with the rules reviewers actually use.

The argument behind the review

The Heilmeier Catechism remains a useful set of questions for technical program design: what are you trying to accomplish, what is different from current practice, why does it matter, what could go wrong, what resources are required, and how will progress be measured?

Those questions are a diagnostic lens. They are not a substitute for agency-specific merit review, eligibility, page limits, or the instructions in a funding opportunity.

A technically competent team might present convincing methods while leaving dependencies implicit. It might use the word “innovative” without identifying the closest prior art. Or it might put technical risks into a generic table that says “schedule delays” instead of describing what experiment would disprove its core hypothesis.

The remedy is not a new mandated chapter. It is a stronger internal review of the argument.

Actions: where the approach meets the schedule

A project plan should make its dependencies visible. A milestone such as “demonstrate prototype performance” is less useful than a statement of which test, data set, acceptance criterion, and responsible role will produce evidence of progress.

Consider an illustrative milestone: “By month three, the technical lead and the program contact agree on test-case selection criteria.” Whether a government contact is permitted or required to approve such criteria depends on the solicitation and eventual award. The point is the link between the technical approach and a checkable decision.

An internal actions register can identify owners, dependencies, evidence artifacts, and unresolved approvals without pretending those fields belong in a specific numbered section of the submission.

Assumptions: uncertainty that should not be hidden

A draft often contains decisions that make sense only if an assumption holds: a data interface will be available, a partner can supply material on schedule, an assay will meet a threshold, or a regulator will permit a proposed pathway.

A clarifying-questions register is a useful private tool for the team. Some questions may be appropriate for the agency’s formal question-and-answer process; others should be resolved through the solicitation itself, partner commitments, or a contingency plan. Placing an unanswered question into the final proposal is not always appropriate.

A strong internal review distinguishes questions the team can answer from genuine external dependencies. It also documents what the team will do if an assumption proves false.

Novelty: compare against something real

A novelty claim becomes meaningful when it names the closest available alternative and identifies a specific, testable difference. That does not require exaggerated patent language.

For example, “Our approach applies algorithm Y to dataset Z” is a description. “The proposed method differs from method A in mechanism B, which we expect to reduce complexity under test C” is a hypothesis that reviewers can evaluate. A claimed factor-of-two improvement would need benchmark evidence or clearly labeled prospective success criteria.

Not every funding opportunity asks for formal IP analysis in the technical narrative. Intellectual-property strategy and commercialization questions should be addressed wherever the particular program requires them, and any legal IP claim needs appropriate professional review.

Review the weak assumptions before polishing the prose

Before line-editing a proposal, I would ask three questions. Can someone trace each major promise to a milestone and owner? Can the team name the assumptions that could invalidate its approach? And can it distinguish what is genuinely new from what prior work already demonstrated?

This does not predict award success. Federal selection depends on program priorities, eligibility, competition, budget, reviewer judgment, and agency-specific criteria. It does expose weaknesses that polished language can hide.

The most useful review is grounded in the actual solicitation, not a generic template masquerading as a regulation. McIntosh Consulting’s federal funding readiness work can help identify those gaps and support a proceed, revise, redirect, or stop decision. Explore the scope.

Dr. Vernon McIntosh

Dr. Vernon McIntosh

Independent practice in biotech, data, and AI/ML

Vernon McIntosh writes about hard biology, data systems, and the practical edge of AI in scientific work. If a post raised a question you want to talk through, book a call or reply by email.

Keep in touch

New essays by email

New essays arrive as they publish. Every so often there is a shorter note when something in the work is worth passing along. If you would rather not do email, the same posts go out on the RSS feed.

Your email is used only for these essays. See the privacy notice.

Send Vernon a message

For consulting inquiries or employment opportunities. A valid return email is required. All other fields are optional.

Messages are processed by Web3Forms and emailed to Vernon. Please do not include confidential information. See the privacy notice.

Prefer email? consulting@vernonmcintosh.com