The weekly report is the most-produced and least-read document in government affairs. Most professionals write one, most executives skim the first paragraph and move on, and both sides quietly accept the ritual. That is a wasted asset, because the weekly report is the single most consistent tool you have for keeping the function visible and demonstrating judgment between the bigger moments. A report leadership actually reads is worth more than a dozen they file unread.
This guide covers why most government affairs reports fail, the three questions every executive is actually asking, the one-page format that works, how to write about regulatory proceedings for readers who are not experts, how the weekly report differs from the executive briefing and the board update, and how to automate the parts that should not take your Friday afternoon.
Why Most Government Affairs Reports Fail
Government affairs reports fail in four predictable ways, and they usually fail in all four at once.
They are too long. The professional, wanting to show the breadth of the work, produces three pages covering everything that happened. The executive, with fifteen minutes and nine other reports, reads the first third and stops. Length is not thoroughness. Length is a filter that removes your most important points by burying them.
They are too granular. The report recounts procedural detail that matters to the practitioner and means nothing to leadership: the docket number, the exact filing, the name of the ALJ. Granularity signals that the writer has not done the work of deciding what matters, and has offloaded that work onto the reader, who will not do it.
They have no clear so-what. The report lists what happened without saying why it matters or what it means for the company. An executive reading "the commission held a hearing on the rate case" has learned a fact and gained nothing. The value is in the interpretation, and a report that supplies facts without interpretation has done half the job and the less useful half.
They are written for the writer, not the reader. This is the root failure that produces the other three. The professional writes to document their own effort rather than to inform a specific reader who has specific questions. Flip that, and the report changes completely.
What Leadership Actually Wants to Know
Every executive reading a government affairs update is asking the same three questions, whether or not they say so. Write to these three questions and the report writes itself.
What do I need to worry about? Leadership wants to know about risk first: the issue that could hurt the company, the proceeding trending the wrong way, the legislation gaining momentum. What do I need to do? Leadership wants to know where they are needed: the meeting only they can take, the decision only they can make, the relationship only they can activate. If the report contains an ask, it should be unmissable, because a buried ask is an ask that does not get answered. Is this under control? Leadership wants reassurance that the function is on top of the landscape, that the things not requiring their attention are genuinely being handled.
Notice that none of the three questions is "how busy were you." Leadership does not read the weekly report to audit your activity. They read it to manage risk, know where they are needed, and confirm the landscape is covered. A report built around those three questions is a report they will read.
The One-Page Weekly Report Format That Works
One page. Four sections. Scannable in three minutes. Here is the structure.
Top Issues This Week
The three most important issues, maximum, each with its current status and the next action. Three is a discipline, not a suggestion. If everything is a top issue, nothing is, and forcing yourself to three is the act of judgment that makes the report valuable.
Key Interactions
Who you engaged this week and why it matters. Not a list of every meeting, but the interactions that changed something or that leadership should know about, each with a one-line so-what. "Met with the commissioner’s senior advisor; she signaled the commission is open to a settlement on the rate case, which improves our position." The interaction plus the meaning, not the interaction alone.
Coming Up
What the function is focused on in the next seven days. This tells leadership the work is planned and forward-looking, and it gives them the chance to redirect if priorities have shifted on their end. Keep it to the few things that matter.
Watch List
Issues being monitored that have not yet required action. This section does quiet but important work: it proves you are covering the landscape, it gives early visibility into things that might escalate, and it reassures leadership that the quiet issues are not unwatched issues.
If your weekly report does not fit on one page, you have not finished writing it. The second page is almost always detail that belongs in your own records, not in leadership’s inbox.
How to Write About Regulatory Proceedings for Non-Expert Readers
Most executives are not regulatory experts, and the weekly report is not the place to make them one. The skill is translating proceeding status into business meaning without either drowning the reader in process or dumbing the content down.
Lead with the stake, not the procedure. An executive does not need to know that the commission issued a procedural order setting a hearing date. They need to know that the rate case that will determine the company’s authorized return for the next several years is on track for a decision this fall, and that the current signals are favorable. State what is at stake for the business, then the status, then the outlook.
Translate the jargon or cut it. "Intervenor testimony was filed" becomes "the opposing parties made their case, and it was weaker than expected." "The ALJ issued a recommended decision" becomes "the judge overseeing the case recommended an outcome close to what we asked for, which the commissioners will now vote on." Keep the precise terms in your own tracking, and give leadership the meaning.
The test is simple. A smart executive with no regulatory background should be able to read your regulatory update and correctly answer three questions: is this good or bad for us, is it on track, and do I need to do anything. If your writing lets them answer those three, it is working, however much detail you left out.
Weekly Report, Executive Briefing, and Board Update
These three documents get confused, and using the wrong one for the wrong moment is a common mistake. They serve different readers and different purposes.
| Document | Cadence | Purpose | Length |
|---|---|---|---|
| Weekly report | Weekly | Keep leadership current on issues, interactions, and what is coming | One page |
| Executive briefing | Per meeting | Prepare an executive for a specific stakeholder meeting | One page, meeting-specific |
| Board update | Quarterly | Give the board the strategic issue and stakeholder landscape | A few pages, strategic |
The weekly report is the running pulse of the function, broad and current. The executive briefing is narrow and deep, everything an executive needs for one specific meeting: who the stakeholder is, the history, what they care about, the ask, the landmines. The board update is strategic and periodic, zooming out to the landscape, the major risks and opportunities, and the function’s results over the quarter. Match the document to the moment. Do not send the board a weekly report, and do not prep an executive for a commissioner meeting with a landscape overview. For the full picture of how these fit a new function’s operating rhythm, see how to build a government affairs function from scratch.
How to Automate the Reporting Process
The weekly report should not consume your Friday, and it will not if the underlying work is captured in a system rather than reconstructed from memory each week.
The report is, at its core, a synthesis of things you already recorded: the interactions you logged, the issues you tracked and their status changes, the outcomes that landed. If those live in a system, the raw material of the report assembles itself, and your job shrinks from reconstruction to judgment, deciding which three issues lead, what the so-what is, and where leadership is needed. That judgment is the part only you can do, and it is the part worth your time.
This is the practical case for logging discipline that is otherwise easy to skip. The professional who logs interactions as they happen and keeps issue status current can generate the skeleton of a weekly report in minutes and spend their effort on the framing. The professional who logs nothing spends Friday afternoon reconstructing the week from their inbox and their memory, produces a longer and worse report, and does it again every week. The discipline pays for itself first, and most visibly, in the reporting. If you are also building the metrics story behind these reports, the government affairs KPI framework picks up where this guide leaves off.
Michael-Christopher Warren has written hundreds of government affairs weekly reports, the good ones and the ones nobody read. He built StatecraftCRM to generate the skeleton of the report from logged data, so the only work left is judgment.
See how StatecraftCRM handles the work you actually do.
Set up your stakeholders, log a few real interactions, and see whether the system thinks about government affairs the way you do.