Long Reports and Proposals

A long report is not a short report that got away from you. It is a different instrument, built for a different job: carrying a decision through an organization where the person who acts on it will never sit in the room with you. Somebody will skim your summary in a hallway, forward page 14 to finance, and quote your recommendation in a meeting six weeks later. That is the real test. Proposals raise the stakes further, because a proposal is a document that competes — against other bidders, against doing nothing, against a reviewer with forty submissions and a scoring sheet. This chapter treats both as engineering problems with rules you can learn: scope the work before you draft, build the document in modules a reader can enter anywhere, keep an unbroken chain from evidence to recommendation, and answer the ask exactly as it was asked. Every principle here comes attached to a sample you can copy.

Section 1Before you write: scoping the long document

What makes a report “long” — and what that costs the reader

Length is the least interesting thing about a long report. What actually changes at scale is the reader’s relationship to the document. A two-page memo is read; a forty-page report is used. Nobody reads it front to back. The chief nursing officer reads the summary. The unit manager reads the recommendations and the schedule. Finance reads the cost appendix and nothing else. Legal reads the limitations. Six months later a new director reads the background section to figure out why the policy exists.

That pattern has a design consequence: each part of a long report has to work when it is torn out of the whole. If your recommendations only make sense to someone who has read the methods section, they will be misread. If your appendix table has no caption, it will be forwarded without one. Writing long means writing modular.

The second cost is that mistakes become expensive. In a memo, a fuzzy sentence costs one email of clarification. In a report that becomes the basis for a $200,000 decision, a fuzzy sentence costs a meeting, a delay and some of your credibility. This is why long documents get a planning stage that short ones do not.

The scope statement: five questions, answered in writing

A scope statement is a short written agreement — often half a page, often inside an email — that answers five questions before you start collecting anything. What problem are we addressing? What will this document be used to decide? What is explicitly outside the boundary? What evidence will count? What exactly will be delivered, to whom, by when?

Notice that the fifth question is a contract, not a courtesy. “A twenty-page recommendation report with a two-page executive summary, delivered to the Quality Committee by 14 March” is a deliverable. “Something on falls” is an invitation to rework. When you send the scope statement back to whoever assigned the work and they reply “yes, that’s it,” you have converted a vague request into a documented agreement that protects you later.

The out-of-scope line does the most work per word. Most rework in professional writing comes from the moment a reader opens a document and looks for something you were never asked to produce. Naming the exclusions in advance — and naming them again in the report’s introduction — heads that off.

Worked example: turning a vague charge into a scoped one

Here is a request as it actually arrived, and the scope statement that came back the next morning. The running example for this chapter is a fictional 32-bed medical–surgical unit, 4 East at Ridgeview Regional, where patient falls have increased.

The right-hand column took about twenty minutes to write. It will save two weeks. Note also what it makes possible: with the questions named, you already know your findings section will have three subsections, and you already know which table you need for each.

Plan the evidence before you gather it

Working writers build a small evidence plan — one line per question — that names the source, who can get it, and how long it takes. “Question 2: screening completion. Source: report from informatics. Owner: me. Lead time: five business days.” The lead time column is the one people skip and the one that sinks schedules, because data requests, interview scheduling and privacy review all run on other people’s calendars.

Then draft the skeleton before the evidence arrives. Write your headings, write the sentence you expect each section to support, and mark it clearly as a placeholder. This is not prejudging the answer; it is exposing the argument early enough to notice that Question 3 has no achievable data source, while there is still time to renegotiate.

Section 2Architecture: front matter, body, back matter

The standard parts and what each one is for

Formal reports have a conventional anatomy. Organizations vary the labels, and some house styles drop parts entirely, but the underlying logic is stable: front matter orients and summarizes, the body argues, and back matter documents. If your organization has a template, use it — deviating from a familiar shape makes readers work harder for no benefit.

Two conventions worth knowing. First, front matter is traditionally paginated in lowercase roman numerals and the body restarts at arabic 1, so that a late-arriving executive summary does not renumber the whole document. Second, appendices are lettered and each one is called out by name in the body — “the full staffing grid appears in Appendix C” — because an appendix that is never referenced is an appendix that is never opened.

Direct order or indirect order: a real choice

In direct order the recommendation comes first and the evidence follows. In indirect order the reasoning comes first and the recommendation lands at the end. Most workplace guidance now defaults to direct order, for two reasons: readers are busy, and a buried recommendation is often simply not found.

But the choice is genuinely contested, and it should be. When the audience is skeptical, when the recommendation is unwelcome, or when the credibility of the method is the actual point of contention, leading with the conclusion invites a reader to reject it before seeing why. Experienced report writers often split the difference: direct order in the executive summary, indirect order in the body. The decision-maker gets the answer immediately; the specialist who will attack the method gets walked through it.

Say which one you are doing, in the introduction, in one sentence. “This report presents recommendations first, in Section 2, followed by the evidence supporting each.” That single sentence prevents a reader from thinking you have skipped the analysis.

Talking headings: make the table of contents do the work

A generic heading names a container. A talking heading delivers the content. Compare the two tables of contents below — the second one is a summary in itself, and a reader who never opens the report still learns something true.

One caution. Some organizations require standardized headings — regulatory submissions, government reports and many grant applications specify exact section titles, and inventing better ones will cost you points. In that case, keep the required heading and add an informative first sentence immediately under it. The heading satisfies the reviewer; the sentence serves the reader.

Navigation, cross-references and accessibility

Long documents need wayfinding: a generated table of contents rather than a typed one, running headers that name the current section, page numbers on every page, and figure and table numbers that never change meaning between drafts. Cross-reference by name and number, not by position — “see Table 4” survives editing, “see the table above” does not.

Structure is also an accessibility requirement, not a nicety. Use real heading styles rather than bold text sized up, because screen readers navigate by heading level and a visually-bold paragraph is invisible to them. Give tables true header rows. Give every figure alt text that states what the figure shows rather than what it is called. Chapter 4 covers the mechanics; the point here is that in a forty-page document, structural markup is the only navigation some of your readers have.

Section 3The executive summary and the analysis chain

Summary, abstract, introduction: three different jobs

These get confused constantly. An abstract is a compressed account written for readers deciding whether to read further; a descriptive abstract says what topics the document covers, an informative abstract states the actual results. An executive summary is written for someone who will not read further and must still act correctly — so it always includes findings, recommendations and cost. An introduction orients a reader who is about to read the whole thing, and therefore includes scope, exclusions and a roadmap that the summary omits.

Length conventions vary and you will see confident, contradictory rules. Roughly ten percent of the report is a common guideline; so is “never more than two pages”; so is “one page per twenty.” These conflict for a forty-page report, and there is no settled answer. The defensible position is to ask what decision the summary must support, then write the shortest version that supports it, and check whether your organization or the funder has published a hard limit that overrides all of this.

Worked example: a summary that stands alone

Weak version. “This report was prepared at the request of the Chief Nursing Officer. It examines the issue of patient falls on the 4 East unit. Several data sources were reviewed and staff members were interviewed. A number of themes emerged from this analysis. Recommendations are presented in the final section of the report. The authors wish to thank the unit staff for their cooperation during this project.”

That paragraph contains no information. It describes the existence of findings without stating any. A reader who reads only this knows nothing except that a report exists.

Revised version. “Falls on 4 East rose from 2.9 to 4.6 per 1,000 patient-days between January and June; four of the 14 falls caused injury, two requiring imaging. Three conditions coincide with the increase and are its most plausible contributors; the data are observational and cannot establish cause. Risk screens are completed on admission but repeated after a change in condition only 31 percent of the time. Bed alarms were deactivated in 9 of 14 post-fall reviews, which suggests alarm status is being lost during handoff rather than clinically discontinued. And the evening aide position eliminated in October has not been backfilled, leaving the 1900–2300 window — when 64 percent of falls occurred — short one staff member. We recommend rescreening at every handoff, adding an alarm-verification step to the handoff script, restoring the evening aide position, and reporting call-light response times to the unit monthly. Estimated annual cost is $84,000, against an estimated $129,136 a year in costs attributable to injurious falls (basis in Appendix D). Recommendations and cost detail begin on page 14.”

The revision is longer, and every added word does work. Each sentence carries a fact instead of announcing that facts exist, and the last line tells a reader where to go for detail. Write the summary last, from the finished report, and then test it: hand it to a colleague who has not read the report and ask them what they would do on Monday. If they cannot answer, the summary has failed regardless of how well it reads.

Findings, conclusions, recommendations: keeping the chain unbroken

A finding is what the evidence shows. A conclusion is what you judge it to mean. A recommendation is what someone should do about it. Collapsing these is the single most common failure in analytical reports, and it takes two forms: stating a conclusion as though it were data, and producing a recommendation that no finding supports.

Read the table down each column and the logic holds. Now read across row 3 and notice the hedge: “plausibly a contributing factor, though the data cannot establish cause.” That is not weakness. Incident data of this kind is observational, the vacancy coincided with other changes, and a reviewer who knows that will trust the rest of your report more because you said so first.

Recommendations someone can actually execute

A recommendation that names no owner, no date and no cost is a wish. Compare: “Staff should be more vigilant about fall risk” against “Add a required fall-risk rescreen to the shift handoff checklist; unit educator implements by 1 May; no added cost; compliance audited monthly by the charge nurse.” The first is unfalsifiable and unassignable. The second can be scheduled, funded and checked.

Rank recommendations rather than listing them flat, and say what ranking you used — impact, cost, speed of implementation. Where a recommendation depends on another, say so explicitly (“Recommendation 3 assumes Recommendation 1 has been implemented”), because leaders routinely approve some items and defer others, and a dependency that lives only in your head will be broken.

Finally, include the option you rejected and why. “We considered purchasing floor-mat alarm systems for all 32 beds ($14,000) but the post-fall reviews did not identify unwitnessed bed exits as the dominant pattern.” Reviewers frequently arrive with a favorite solution. Showing that you evaluated it, with a reason, is faster than defending its absence in a meeting.

Section 4Evidence, sources and honest analysis

Primary and secondary sources, and where each belongs

A primary source is evidence you or your organization generated or that reports original data: your incident logs, your staffing grid, your interviews, a published study reporting its own results. A secondary source summarizes or interprets primary material: a review article, a professional association’s practice brief, a trade-press summary, a vendor’s white paper.

Both belong in a long report, but in different places and with different weight. Local primary data belongs in findings, because it is the specific evidence about your specific problem. Secondary sources belong in background and discussion, where they establish that the problem is recognized elsewhere and that your proposed intervention has support beyond your own hunch. Trouble starts when a secondary source is used to carry a factual claim about your organization — a national average is not a statement about your unit.

Vendor material deserves its own caution. A vendor white paper may contain perfectly good information and still be a sales document. Cite it by name, describe what it is (“the manufacturer reports”), and never let it be the only support for a purchase you are recommending. Reviewers notice.

Match your claim language to your evidence

Most credibility damage in professional reports comes not from bad data but from language that outruns it. The fix is mechanical: pick the verb that matches what you actually have.

The right column is not more forceful; it is more fragile. One reader who knows the reporting system is voluntary will discount your entire findings section over that last row. Precision is persuasive.

Limitations are an argument for you, not against you

Every serious report has a limitations passage: what your evidence cannot tell you and why. Small sample. Single site. Self-reported data. A six-month window that includes a holiday period. A data extract that could not distinguish assisted from unassisted falls.

Writers new to long reports treat this as a confession and try to bury it. Reviewers read it as competence. The reason is simple: the limitations of your evidence exist whether or not you name them, and the reviewer will find them. Naming them first demonstrates that you understand your own data and lets you frame the implication yourself — “because the sample is small, we recommend a six-month trial with re-measurement rather than a permanent change” is a stronger recommendation than a confident one that gets challenged in committee.

Where limitations belong is a real disagreement. Academic convention often places them near the end of the discussion; many workplace and government report templates put a “scope and limitations” subsection in the introduction so nobody reads the findings with the wrong expectations. Either is defensible. What is not defensible is scattering them in footnotes.

Citing, attributing and the boilerplate trap

Which citation style you use is a house decision, not a moral one. Healthcare organizations commonly use AMA or Vancouver numeric styles; education and social science lean APA; engineering and government have their own. Pick the one your reader expects, apply it consistently, and make sure every claim a reader might challenge is traceable to a named source with a date.

Internal sources need attribution too, and this is routinely skipped. “Staffing data provided by Nursing Administration, extracted 3 February” tells a future reader which version of the numbers you had, which matters enormously when someone re-runs the report in April and gets different figures.

Then there is boilerplate — reusable blocks of organizational description, methodology text and qualifications that get pasted from document to document. Boilerplate is legitimate and saves enormous time. It also produces the most embarrassing errors in professional writing: the wrong client name in paragraph two, a statistic that was current three years ago, a reference to a program that no longer exists. Treat every reused block as a draft. Search the finished document for the previous client’s name before it leaves the building.

Section 5Proposals: answering the ask

Solicited and unsolicited; RFI, RFQ, RFP and NOFO

A solicited proposal answers a request someone published. An unsolicited proposal arrives uninvited — an internal pitch for a new program, a consultant proposing work nobody asked for. The two need different openings. A solicited proposal can assume the reader agrees a problem exists, because they wrote the solicitation. An unsolicited proposal must first establish that there is a problem worth spending on, in the reader’s own terms, before proposing anything.

The solicitation vocabulary varies by sector, and mixing it up signals inexperience. In broad terms: an RFI (request for information) gathers market intelligence and awards nothing; an RFQ (request for quotation) asks for price against a specification the buyer has already written; an RFP (request for proposal) asks you to propose a solution and a price, evaluated against stated criteria. Government grant work uses NOFO (notice of funding opportunity), which largely replaced the older FOA (funding opportunity announcement); the National Institutes of Health still issues RFAs (requests for applications) as well. Terms overlap and organizations use them loosely — read the document itself rather than trusting the acronym on the cover.

One judgment call worth naming: unsolicited proposals have a low hit rate, and some practitioners consider them a poor use of effort compared with cultivating a relationship first. Others build entire practices on them. What is not disputed is that an unsolicited proposal sent to a stranger with no prior contact is very unlikely to be read.

Compliance first: the elimination round is administrative

Here is the part that surprises people. In most formal procurements and grant competitions, the first pass is not about the quality of your idea. Someone checks whether you submitted the required forms, stayed under the page limit, used the required font size, addressed each required section, and hit the deadline. Proposals that fail this check are set aside without being read on the merits.

The defense is a compliance matrix: a table built directly from the solicitation, one row per requirement, tracking where you answer it and who owns it. Build it on day one, before writing. It becomes your outline, your assignment sheet and your final checklist. Cite the solicitation’s own section numbers, and get them right: in a federal solicitation using the uniform contract format, Section C is the work itself — the specifications and statement of work — while the instructions telling you what to describe, provide or include live in Section L, and the scoring factors live in Section M.

Notice the last two rows. The page limit is tracked as a requirement with a live status, because “we will cut it at the end” is how good content gets deleted at 11 p.m. And the evaluation criteria in row M.1 are treated as structural: if past performance is worth 30 points, past performance gets its own prominent section, not a paragraph tucked into the introduction. Answer in the order and the proportion the scorer is scoring.

Use the solicitation’s own language in your headings. If they ask for a “staffing plan,” head your section “Staffing Plan” — not “Our Team.” A scorer with forty proposals and a checklist should never have to hunt.

The persuasive core: problem, plan, qualifications, budget, schedule

Underneath every proposal format is the same five-part argument. Problem: here is the situation, described in your reader’s terms and numbers, not ours. Plan: here is specifically what we will do, in what order. Qualifications: here is why we are the ones who can do it. Budget: here is what it costs and what each dollar buys. Schedule: here is when each piece lands and how you will know it worked.

The qualifications section is where most proposals go flat, because writers describe themselves instead of differentiating themselves. Compare:

Weak. “Our organization has many years of experience in quality improvement. We are committed to excellence and to partnering with our clients. Our staff are highly qualified professionals dedicated to patient safety.”

Revised. “We have implemented fall-prevention programs on eleven acute-care units since 2021. On the three most comparable units — 28 to 36 beds, medical–surgical, community hospitals — the fall rate fell by a median of 34 percent within nine months and held at twelve months. The project lead, J. Okonkwo, ran two of those three implementations and will be assigned at 40 percent effort. References for all three are in Appendix A.”

Every sentence in the revision is checkable. That is the difference between a claim and a discriminator — something true of you that is not equally true of every competitor. “Committed to excellence” is true of everyone and therefore worth nothing. A named person with a percent effort and three verifiable references is worth points.

A win theme is the two or three claims you want the scorer to remember, repeated deliberately at the top of each major section and supported with evidence each time. Themes should come from the solicitation’s own stated priorities. If the RFP says three times that sustainability after the grant period is a concern, sustainability is a win theme, and it should appear in your plan, your staffing and your budget — not just in a paragraph promising it.

Budget, schedule and the credibility of numbers

A budget is a rhetorical document. Reviewers read it to check whether you actually understand the work, and a budget that does not match the narrative is the fastest way to lose trust. If your plan promises weekly on-site coaching for six months and your budget contains twelve hours of travel, one of the two is false.

Build it in categories the funder asked for — commonly personnel (with percent effort and fringe), equipment, supplies, travel, subcontracts, and indirect costs (overhead, sometimes negotiated at a fixed rate). Then write a budget narrative that justifies each line in a sentence: “Project lead, 0.40 FTE for 12 months. Conducts unit assessments, trains charge nurses, and chairs the monthly review; based on 16 hours per week across two units.” The narrative is where you demonstrate that the number came from a calculation rather than a wish.

Schedules follow the same rule. A milestone table with real dates, named owners and a measurable completion test beats a decorative timeline graphic every time. “Month 3: baseline audit complete, defined as 100 percent of eligible charts reviewed and the report delivered to the committee” can be verified; “Month 3: assessment phase” cannot.

Review and submit: red team, version control, the final hour

Serious proposal teams run a red team review: colleagues who did not write the draft score it against the actual evaluation criteria, as harshly as a real reviewer would, with enough time left to fix what they find. The instruction matters — “tell me what you think” produces compliments, “score this against Section M and tell me where we lose points” produces useful damage.

Long documents with multiple authors need version control or they will lose work. Use a shared authoritative copy rather than emailed attachments; if you must use files, name them so sorting is chronological and the owner is visible, such as FallsProposal_v04_2026-03-08_JO.docx. Never let two people hold different “final” files.

Then a final pass that is purely mechanical, done by someone who has not been staring at the prose: every compliance-matrix row marked complete, page and font limits verified in the exported file, all cross-references resolving, no leftover highlighting or tracked changes, the correct client name everywhere, required forms signed, file format and naming as specified, and the submission confirmation saved.

Words worth knowing