NR-555 Week 7 Policy Brief Construction: How to Write It

What NR-555 Week 7 asks for

The late stages of a policy course move from analysis to communication, and the shift catches people out. Students who have spent six stages learning to hedge properly are now asked to lead with a conclusion, and their first drafts read like abstracts: three paragraphs of background before anything is requested. A brief inverts that order permanently. Ask, then reason, then evidence, then what happens next.

Audience discipline does the rest. A legislative staffer needs to know whose constituents are affected, what it costs, who supports it and what the opposition will say. A regulatory audience wants statutory authority and administrative feasibility. A system board wants risk, reputation and margin. Write to one of them, name that reader in your first line or in a heading, and let the emphasis follow from the choice. A brief written to nobody in particular reads as a summary of your own paper, which is the most common shape of a low-scoring submission at this stage.

The equity content of your argument has to survive compression, and this is harder than it sounds. Distilled advocacy tends to collapse into an efficiency claim because efficiency compresses well. Keep one sentence in the brief that names who currently bears the burden and how unevenly, and place it where the reader cannot skip it, which is usually immediately after the ask rather than in a section near the end.

Deliverables at this stage often pair a brief with a reflective or explanatory piece: the brief itself, plus a short account of the choices you made in writing it. Treat the second piece as real work rather than as a formality, since it is where you demonstrate that the compression was deliberate. If a discussion accompanies the stage, one precise sentence about your ask beats a paragraph about advocacy in general.

The NR-555 Week 7 method, step by step

Six moves for building a brief that a busy reader can act on.

1. Name the reader before you write a word

   Write their title at the top of your draft file, then decide what they can actually do: introduce a bill, sign a rule, change a contract term, direct a department. Everything in the brief serves that specific capability.

2. Write the ask as one sentence with a verb and a subject

   Not raise awareness of care-transition failures, but require that a receiving facility be given a reconciled medication list before a resident leaves the sending unit. Test it by asking whether a reader could say yes or no to the sentence as written.

3. Put the burden sentence immediately underneath

   One sentence naming who is affected, how many, and how unevenly. This is the line that keeps the brief an equity document rather than an efficiency memo, and it belongs above the fold.

4. Give three reasons, in descending order of strength

   Each reason gets a short paragraph with one supporting fact and a citation. Three is enough; a fourth dilutes the first, and readers of briefs remember the opening reason far more reliably than the closing one.

5. Answer the strongest objection in the brief itself

   Name it fairly, then respond in two sentences. Briefs that ignore the obvious objection get handed to someone who will raise it, and a document that has already answered it survives that meeting.

6. Close with the next action and a route back to you

   What you want to happen next, by whom, and what you can provide: a site visit, a constituent voice, a technical detail. Advocacy that ends without a next step reads as commentary.

A layout and word budget for a policy brief

Our frame for a two-page brief, sized for roughly 800 to 1,100 words, with any accompanying reflective piece budgeted separately. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.

Evidence craft for advocacy writing

One number per point, chosen for its clarity. Briefs drown in statistics. Pick the single figure that makes each reason land, present it with its base and its period, and move on. The rest of your evidence belongs in the references or in an appendix if the format allows one.

Cite inside the brief, not only at the end. A staffer who wants to check a claim will not open a reference list. A short parenthetical attribution in the line where the claim appears is standard practice in this genre and it costs you six words.

Use one story, once, and keep it unidentifiable. A single care-transition scene of three sentences makes an abstract argument concrete. Two stories make the document sentimental, and any story with identifying detail is a boundary you must not cross regardless of how well it would read.

Do not overstate what the evidence supports. Advocacy that inflates gets discounted permanently by the reader who catches it. Where evidence is suggestive, the word is suggests, and a brief that qualifies one claim honestly earns more trust for the other two.

Write the opposition's case in their words, not yours. Facilities worried about a new requirement are worried about staffing hours at specific times of day. Naming their concern in operational terms shows the reader you have talked to somebody, which is the quality that separates a brief from an essay.

Five mistakes that cost points in this week's territory

• Background before the ask. Two paragraphs of context at the top of a brief means the ask arrives after the reader has stopped, and the genre row is lost immediately.
• An ask nobody can grant. Requesting increased awareness or better collaboration gives the reader nothing to sign, fund or vote on.
• Statistic stacking. Four numbers in one paragraph cancel each other, and none of them is remembered.
• Equity dropped in compression. A brief that becomes a cost-saving pitch has abandoned the argument the whole session was built to make.
• Academic register left in place. Long subordinate clauses, deferred conclusions and hedged verbs signal that the writer did not change genre when the task did.

Before you submit

• The reader is named and the ask is something that reader can actually do
• The ask appears in the first few lines as one sentence
• A burden sentence naming who is affected sits directly beneath it
• Each reason carries exactly one supporting fact with an in-line attribution
• The strongest objection is stated fairly and answered
• Any illustrative scene is unidentifiable and used once
• The document ends with a specific next action and a timeframe

Questions students ask about this stage

Keep going