Project Executive Summary Template and How to Write One
An executive summary is the one page the owner actually reads. The daily reports, the punch list, and the RFI log are the record. The executive summary is what the record means right now, written for someone who was not on site and has ten minutes: where the project stands, what is open, what could go wrong, and what they need to decide. Everything else is an attachment.
Most executive summaries fail one of two ways. Either they are a daily report with the heading changed — a list of activities the owner cannot act on — or they are a forecast dressed up as a status: "on track," with nothing behind it. This guide covers the six sections that work, how to write each one so the owner can act on it, and the rule that keeps the summary credible: keep what you observed apart from what you expect. The template at the end follows the same structure.
What an executive summary is for
Three jobs, and the first is the one that makes it an owner document rather than a report:
- The owner's decision document. Every summary should end with the decisions the owner owes the project, who owns each one, and when it is needed. If nothing needs deciding, the summary says so, and the owner can put it down.
- A record of what was known when. When a schedule slips and someone asks when the problem first surfaced, the summary from that week shows what was reported, to whom, and what was asked for.
- The bridge from the field to the office. It is written from the field record — the dailies, the punch list, the RFI log — not from memory and not from the contractor's schedule narrative. It does not introduce facts the record does not hold.
It is not a pay application narrative, not a place to argue a change order, and not a progress report for the project team. Those have their own documents. The executive summary points to them.
The six sections
The order below is deliberate. An owner with two minutes reads Status and Decisions Needed. An owner with ten reads it all.
1. Status
Three sentences. Where the project stands against the plan, in plain words, and the single most important thing the owner needs to know. If the project is behind, say by how much and why, in one sentence. The bad news goes here, first, not on page two.
Weak: "The project continues to make good progress with a few challenges being managed by the team."
Better: "Mechanical rough-in is complete and electrical is one week behind plan because the switchgear delivery slipped to 10/14. Substantial completion is still 11/20 if the switchgear lands on the new date. One decision is needed this week (see Decisions Needed)."
2. Progress
What got done since the last summary, as outcomes, not activities. "Chiller CH-2 set and piped" tells the owner something. "Mechanical contractor continued work on chiller installation" does not. Quantities where they exist, taken from the daily reports, not estimated for the summary.
3. Open Issues
What is not going to plan today: unforeseen conditions, delays and their cause, missing material, coordination conflicts, a submittal that has not come back. One line each, with who owns it and what happens next. Point to the RFI or change request by number instead of retelling it. An issue with no owner is a complaint, not an issue.
4. Risks
What could go wrong that has not gone wrong yet. A risk is not an issue: an issue exists, a risk might. For each one, the trigger — what would make it real — and what you would do about it. Three is plenty. A list of twelve risks is a list nobody reads, and it tells the owner you are not sure which ones matter.
5. Decisions Needed
The section that makes this an owner document. For each decision: what is being decided, the options if there are real ones, who owns it by name, the date it is needed, and what slips if the date passes. "Pending owner input" without a name and a date is how decisions stall for a month and become issues.
Weak: "Owner to advise on the roof drain approach."
Better: "Decision needed by 10/6 (J. Alvarez): replace the four existing roof drains at Grid D ($18,400, change request CR-07) or reuse and warranty-exclude them. Roofing is scheduled for that area on 10/13; a decision after 10/8 pushes roofing a week."
6. Next Steps
What happens between now and the next summary, with dates. Short. This is what the next summary's Status will be measured against, and it is how an owner tells a project that is being driven from one that is drifting.
If a section has nothing in it, write "None reported." The same rule as the daily report: a blank reads as "not checked," and "None reported" reads as "checked, nothing there."
Keep what you observed apart from what you expect
This is the rule that separates a summary the owner trusts from one they learn to discount.
"The switchgear arrived 10/14, three weeks late" is an observation. "Startup will slip one week" is a forecast. Both belong in the summary. They do not belong in the same sentence without a label, because the owner needs to know which statements are facts and which are your judgment about the facts.
In practice: observations go in Progress and Open Issues, stated as what happened and when. Forecasts go in Status, Risks, and Next Steps, and each one carries its basis — "per the contractor's 10/1 schedule update," "based on the remaining rough-in quantity in the 10/3 daily." A percent complete goes in only if you can say how it was measured. A number with no source is a number the owner will eventually catch, and after that they check everything.
Writing it so the owner can act
One page. If it runs to two, the second page is an attachment. The discipline of one page is what forces the summary to say what matters.
Bad news first. Owners forgive slips. They do not forgive learning about a slip from someone else, or finding it in paragraph four.
Write for the reader who was not there. No grid lines, no trade names, no equipment tags unless a decision hangs on them. "The north mechanical room" over "Grid C-4 to C-7."
Names and dates on every decision. A person, not a company. A date, not "ASAP."
Same structure, same cadence, every time. Weekly on active construction, monthly on a facility program, and any time a decision cannot wait for the next one. The owner learns where to look, and a summary that changes shape every week reads as if the project is changing shape too.
Build it from the record. The daily reports, the punch list, the RFI log. If something is not in the record, it does not go in the summary until it is. That is what keeps the summary defensible six months later.
Common mistakes
- A daily report with a new heading. Activities instead of outcomes; the owner cannot act on it.
- "On track" with nothing behind it. Every status statement needs a basis the owner could check.
- Burying the decision in the issues. If the owner has to find it, it will not get made.
- Risks that are already issues. If it has happened, it is an issue with an owner and a next step, not a risk.
- Forecasts stated as facts. A percent complete nobody measured, a finish date nobody re-scheduled.
- Decisions without names or dates. "Owner to advise" is a wish.
- A different structure each time. The owner should be able to find Decisions Needed without reading.
Download the template
The template follows the structure above: a project header with the period covered and who prepared it, then the six sections — Status, Progress, Open Issues, Risks, Decisions Needed, Next Steps — each with prompts and lines to write on. Portrait, prints in black and white, works in Word or as a PDF you fill by hand.
How FieldBinder AI produces an executive summary
When you generate an Executive Summary, the app reads every capture in the project — photos with their captions, notes, voice notes, measurements, punch items, RFIs, customer decisions, safety observations — and drafts the same six sections: Status, Progress, Open Issues, Risks, Decisions Needed, and Next Steps. It is told to use only the captures and the project details, and not to invent facts, quantities, names, dates, or measurements. A section with nothing behind it reads "None reported." Photos reach the draft as their captions, not as images.
The summary covers the whole project, not a date range, so the period covered on the printed template is yours to state. The draft is editable, and editing or regenerating it returns it to draft. When you mark it reviewed, the footer changes from "AI-generated draft" to "AI-assisted; reviewed by" with the reviewer's name, and the draft stamp comes off. Exporting from the app adds a Site Photos section with up to 30 of the project's photos; or copy the text into an email.
What the app does not do is decide what the owner needs to hear. Whether the project is on track, which risk matters, which decision is urgent — that is the judgment the person who was on site brings when they review the draft. Every generated report is marked as AI-assisted, and you review it before it goes out.
AI report generation is part of the Pro plan; capture and organization by project are included on every plan. See pricing · How it works for owner's representatives
Frequently asked questions
What is the difference between an executive summary and a progress report?
A progress report tells the project team and the pay application what was done. An executive summary tells the owner where the project stands and what they need to decide. The progress report is a source for the executive summary; it is not a substitute for it.
How long should a project executive summary be?
One page. Status and Decisions Needed should be readable in two minutes. Anything that needs more room belongs in an attachment the summary points to.
How often should an owner get an executive summary?
Weekly on active construction, monthly on a longer facility or maintenance program, and any time a decision cannot wait for the next scheduled one. The cadence matters less than keeping it.
Should the executive summary include cost and schedule forecasts?
Yes, when they carry their basis and are labeled as forecasts. A finish date "per the contractor's 10/1 schedule update" is useful. A finish date with no source is a promise the summary cannot keep. Cost figures should point to the change request or pay application they come from.
Who should write the executive summary?
The person responsible for the project on the owner's side — an owner's representative, a project manager, or the engineer running the work — working from the field record. It should not be written by someone who has not read the daily reports, and it should not be delegated to the contractor. Some contracts specify what an owner report must contain; check yours.
