Consulting Status Report Template
Four documents and three sheets that put float on every milestone, name the decision gating it, and calculate the color from both.
Free download · No account needed
Status Report · Ardenmoor Regional Transit Authority · fare collection replacement readiness review
Status: RED · Week 7 of 16 · 9 October 2026
Bottom line. The board recommendation now forecasts to 23 December, which misses the 15 December board. Two decisions, ten and five working days overdue, are the entire cause. Answering both by 16 October recovers the December date.
| Milestone | Baseline | Float | Gate | Forecast | Status |
|---|---|---|---|---|---|
| Current-state process map | 11 Sep | 10 Sep | Complete | ||
| Data quality assessment | 25 Sep | 24 Sep | Complete | ||
| Target operating model options | 16 Oct | 8 d | D-02 | 16 Oct | Amber |
| Vendor requirements pack | 6 Nov | 6 d | D-01, D-04 | 12 Nov | Red |
| Business case | 27 Nov | 2 d | D-01, D-03 | 9 Dec | Red |
| Board recommendation | 11 Dec | 0 d | Business case | 23 Dec | Red |
Every status in that column is calculated. Amber means the gating decision is overdue and the overdue days still fit inside the float. Red means they do not, and the forecast has moved by the difference. Target operating model options holds its date with three working days of float left, and turns red on 16 October if D-02 is still open.
Decisions we are waiting on. D-01, fare media scope, in writing since 11 September, needed 25 September, 10 working days overdue, 11 days blocked. D-02, depot maintenance in or out, 5 days overdue, 4 blocked. D-04, revenue files at transaction grain, 5 days overdue, 3 blocked and 5 worked around.
The two decisions closed on this engagement were answered in four and two working days.
Search this and the templates are current and close to unanimous. Project name and a red, amber or green status in the subject line. One bottom-line sentence. Accomplishments, next period, risks with a named owner and a date, and a decisions-needed section, which one of them rightly calls the most valuable part and the one most often left out. Follow every word of it and something is still wrong, and it is the part everybody reads first. The author picks the color.
Here the color is subtraction. Every milestone carries float in working days and names the decision gating it, and every open decision carries how many working days it is overdue. Wrenfield Advisory's week seven report on the Ardenmoor fare review has four open decisions and three of them late. The vendor requirements pack holds six days of float against a decision ten days overdue, so it moves four. The board recommendation had none, so it lands past the December board.
A decision nobody made is also a cost. FAR 52.242-17 makes a buyer's failure to act within a reasonable time a compensable delay, then bars any cost incurred more than 20 days before you gave written notice. So the report is the notice, and it is dated. Eighteen consultant days sit blocked and five went on a workaround, which is 10.5% of the days sold. The milestones it tracks come from the signed statement of work, and the plan behind them from the implementation roadmap pack.
What's in the pack
Milestone Tracker
Baseline, float in working days, the decision gating it, and a status calculated from the last two.
Decision Log
Every open question aged from the day it went in writing, with days blocked and days worked around kept apart.
Issue and Risk Register
One row per open item, each carrying an owner, a dated next action, and the days at stake behind it.
Status Report
One page: cause, consequence and remedy in the first three sentences, then the tracker with its arithmetic visible. Before anything larger goes out, the deliverable review pack re-performs every figure on it from its own source.
Decision Requests
A page per open decision with two or three costed options, a recommendation, and a date carrying its reason.
Issue Note
For anything needing more than three lines: what happened, what it costs in days, what was tried, and the options.
What a Status Report Owes the Sponsor
The standard behind the pack, including why a green run of six weeks is an arithmetic problem rather than an honesty problem.
Report Assembly
Runs on your reporting day, ages every open decision, recalculates each status, and refuses one the registers contradict.
How it works
- 1
Open in River
Edit with AI installs the pack as a private Space and starts filling it from what you send. Download gives you the Word documents and CSV sheets free, no account.
- 2
Float and gates
Send the workplan and where the work stands. Every open milestone gets its float in working days and the name of the decision holding it up.
- 3
Age the questions
Then everything you are waiting on an answer to, with the day it went in writing. Each one gets an overdue count and the consultant days behind it.
- 4
Send it on the day
The report comes out with every status calculated, the slip followed to the external date at the end of the chain, and a costed option list per decision.
Frequently asked questions
Is this consulting status report template free?
Yes. Download gives you the whole pack with no account and no email: four Word documents, one of them the standard the arithmetic rests on, and three CSV sheets. Edit with AI is the other route, which creates a free account, installs the same pack as a private Space, and fills it in from your workplan and your open questions.
What format are the downloaded files?
Documents come as .docx and sheets as .csv, so nothing needs converting. Word, Pages and Google Docs open the documents. Excel, Numbers and Sheets open the registers. Add ?format=pdf to the download URL for the documents as PDFs, useful when you are circulating a report rather than filling one in.
What stops me overriding a red status?
Nothing stops you, and that is the point of showing the arithmetic on the page. The report prints float, the gating decision and the overdue count in the same row as the status, so a status the numbers do not support is visible to every reader. Credibility comes from the columns, not from a locked cell.
Is naming a client's overdue decision going to damage the relationship?
Not the way this pack writes it. A date, a number, and the median answer time on closed decisions, no adjectives. The worked example closed in four and two working days, turning a ten day wait into a stated observation, not an accusation. Once a request stalls past what the escalation path allows at that tier, raising it again is procedure, not confrontation.
How do I set the date I need an answer by?
From the schedule, and you state the reason in the same sentence. Answer by the 16th, because the requirements pack goes to the panel on the 20th and takes six weeks. Asking for a dated decision is ordinary practice: federal rules give the buyer's side 60 days from a written request.
What happens when an overdue decision turns into extra work?
It stops being a status item and becomes a priced change. The log already holds the day it went in writing and the days spent working around it, which is most of what a change needs. From there the change order pack prices it on added work, work thrown away, and the extra weeks of carrying the engagement.
Does this track my fee and burn as well?
It reports days consumed against days planned and explains any variance, which is what a sponsor needs. Forecast to complete against a fixed fee is a different threshold with a different audience, and it lives in the consulting workplan template. Utilization, realization and the first unsold week belong to the practice, so they sit in the practice metrics template.
Stop choosing the color
Take the Word documents and CSV sheets blank, or send River the workplan and the questions you are waiting on and get the calculated report back.
Edit with AI