Foreman Report in Construction: What It Is, What to Include, and Why It Matters

If you're a commercial manager reading this, think of foreman reports as your primary evidence layer. Everything that feeds into your construction daily log, your delay analysis, your Defined Cost records, and your final account starts here. Get this wrong, and you're building a commercial position on sand.

Why Foreman Reports Matter More Than Most People Think

Here's the problem I see on almost every project. The site diary exists. The daily allocation sheet gets filled in. But when the commercial team needs to evidence a disruption claim nine months later? There's a gap.

The site diary says "concrete pour completed." It doesn't explain that the foreman had to redeploy six operatives from the drainage gang because the client's designer changed the reinforcement detail at 7am. That context lives in the foreman report. Or it should.

On a £35M highways package in the East Midlands, the Contractor submitted 23 compensation events over 18 months. Fourteen were assessed by the Project Manager with reduced time and cost because the contemporaneous evidence was thin. The site diaries were adequate. The foreman reports? Either missing or stuffed with "work continued as planned."

The commercial team estimated they lost around £420,000 in entitlement that should've been recoverable. That's not unusual. It's typical.

The Evidence Chain

Foreman reports sit at the bottom of a documentation hierarchy that ultimately supports every commercial claim on your project:

Each level should cross-reference the one below it. Say the site diary records "delay to piling operations due to unforeseen ground conditions." The foreman report should contain the specifics: what was encountered, at what depth, which piles were affected, how many operatives were standing, and for how long. Without that detail, the site diary entry is just a headline with no story behind it.

What a Foreman Report Should Contain

Most foreman report templates I've seen on UK sites are too basic. They capture what was done but ignore what went wrong, what changed, or why resources were deployed differently. Here's what a properly structured report actually needs.

Essential Fields

The Three Fields Most Foremen Miss

I've reviewed hundreds of foreman reports across rail, highways, and building projects. Three fields are consistently weak or absent.

1. Instructions received. Foremen receive verbal instructions daily. The Project Manager's rep says "move that stockpile," the designer says "change the rebar spacing," the client's environmental officer says "stop work in that area." These are potential compensation events under clause 60.1(4). If the foreman doesn't write them down with the time, the person who gave the instruction, and what was said, you've got nothing. The eight-week time bar starts ticking from when the Contractor became aware, and "aware" starts with the foreman on the ground.

2. Delays and their cause. "Delayed by weather" is useless. "Rainfall from 06:30 to 11:15 (approx 18mm), unable to excavate in area C due to waterlogged formation, 4 operatives and 1 excavator standing for 4.75 hours" is evidence. The difference between those two entries can be worth tens of thousands of pounds on a single compensation event.

3. Changed methods of working. When the foreman has to do something differently from the plan because of a client-caused issue, that's disruption. But foremen rarely record it because they see it as just part of the job. "Couldn't access area B because client's electrical contractor still in occupation, redeployed team to area D instead" is a disruption record. It proves the Contractor was willing and able to work but was prevented from following the planned sequence.

Worked Example: Foreman Report Supporting a Compensation Event

Foreman Report: 12 March 2026

• Shift: 07:00 to 17:30 (including 1 hour overtime approved by site manager)
• Weather: Dry, 6°C morning, 11°C afternoon, moderate wind from NW, ground firm and workable
• Labour: 8 operatives (2 steel fixers, 3 concretors, 2 labourers, 1 banksman). Joe Marsh off sick, replaced by agency operative from Randstad.
• Plant: 1x 20t excavator (operated 07:00-12:00, stood 12:00-15:30 awaiting revised design info, resumed 15:30-17:30). 1x concrete pump on standby from 08:00, not used until 15:45 due to design hold.
• Work completed: Completed rebar fix to base slab section 3A (26 tonnes fixed). Concrete pour to section 3A started at 15:45, completed at 17:15 (42m³ placed). Formwork stripped to section 2B.
• Instructions received: At 09:15, the client's structural engineer (Sarah Jenkins) verbally instructed a change to the reinforcement detail for base slab section 3B. Additional T25 bars at 150mm centres in the bottom mat, replacing T20 at 200mm centres. Instruction confirmed by email at 11:40 (ref: SJ/STR/2026/047). This is a change to the Works Information.
• Delays: Excavator stood from 12:00 to 15:30 (3.5 hours) while waiting for revised GA drawing for section 3B. Concrete pour to section 3A delayed from planned 10:00 start to 15:45 start because the pour sequence depends on rebar approval for adjacent section. Knock-on: overtime required to complete pour before temperatures dropped.
• Photographs: 4 photos taken: (1) rebar to section 3A before pour, (2) revised rebar detail sketch from Sarah Jenkins, (3) excavator standing at 13:00, (4) concrete pour at 16:30.

How the QS uses this:

That single foreman report gives the commercial team everything they need to notify a compensation event under clause 61.3. The instruction to change the reinforcement detail is a change to the Works Information under clause 60.1(1). The foreman's record captures:

• When the instruction was given (09:15 on 12 March)
• Who gave it (Sarah Jenkins, client's structural engineer)
• What changed (T25 at 150 replacing T20 at 200, bottom mat, section 3B)
• Impact already visible: 3.5 hours excavator standing, concrete pour delayed 5 hours 45 minutes, overtime incurred

The QS can now notify the compensation event within the 8-week window, with contemporaneous evidence already in place. When the Project Manager assesses the quotation under clause 63, the foreman report provides the basis for the Defined Cost calculation: labour standing time, plant standing time, additional materials (heavier rebar), and the knock-on delay to the programme.

Without this report? The QS reconstructs from memory weeks later, the site diary says "design change received, pour delayed," and the Project Manager assesses a lower figure because the evidence doesn't support the full claim.

Foreman Report vs Site Diary vs Daily Allocation Sheet

People confuse these three documents constantly. They're different tools with different purposes.

Here's the key point: these aren't interchangeable. A site diary without foreman reports backing it up is a summary without evidence. And a foreman report without a site diary? Raw data without interpretation. You need both.

For a deeper comparison of site records, see our guide to how to write a site diary and the site diary completion checklist.

How to Write a Good Foreman Report: Practical Guidance

Most foremen aren't commercially trained. They're experienced tradespeople promoted because they're good at managing a gang and getting work done. Writing detailed daily reports isn't what they signed up for, and most of them know it. So make it easy.

The 5-Minute Rule

A foreman report should take no more than 5 minutes to complete at the end of each shift. If it takes longer, your template is too complicated or you're asking for information that belongs somewhere else.

Template Structure That Works

I've seen dozens of templates. The ones that actually get filled in properly share three characteristics:

1. Pre-populated fields. The project name, contract number, section, and foreman's name should already be on the form. Don't make people write the same information every day.
2. Tick boxes for routine items. Weather conditions, safety observations, and shift times work better as selections than free text.
3. One open text box for "anything unusual." This is where the commercial gold lives. Train foremen to write anything that wasn't in the plan: instructions received, delays, changed sequences, unexpected conditions.

Training Foremen to Record What Matters

Here's what I tell foremen on every project I work on. You don't need to understand NEC4 clause numbers. You just need to answer four questions at the end of every shift:

1. What did we actually do today? (Not what was planned. What happened.)
2. Was anything different from the plan? (If yes, what, why, and who told you to change?)
3. Did anything stop us working or slow us down? (If yes, what, for how long, and how many people were affected?)
4. Did anyone give you an instruction? (If yes, who, when, and what did they say?)

If the foreman answers those four questions honestly and specifically every day, the commercial team has 80% of what they need. The QS fills in the clause references and commercial context afterwards.

Digital vs Paper

Paper foreman reports get lost. They get wet. They get left in the site cabin and nobody collects them for three weeks. They can't be searched, cross-referenced, or time-stamped.

Digital reporting solves all of these problems. Whether it's a dedicated app or a simple structured form on a tablet, the report gets submitted at the end of the shift. It's date-stamped automatically, photos are embedded, and the commercial team can access it straight away. No chasing. No three-week backlog.

This is exactly the kind of problem that AI-powered site diary tools solve. Instead of relying on foremen to identify which entries are commercially significant, the software reviews every report against the contract terms and flags potential compensation events automatically.

Common Mistakes

1. Recording only what was completed, not what went wrong. The most valuable entries in a foreman report describe disruption, delay, and changed methods. "Completed 40m of kerb laying" is progress data. "Planned to lay 60m of kerbing but client's drainage contractor still occupying chainage 450-520, redeployed team to footpath works in area F" is commercial evidence. The second entry is worth money.
2. Using vague language. "Some delay due to weather" means nothing in a compensation event assessment. Record specifics: duration, intensity, which activities were affected, how many operatives were standing, what the knock-on effect was.
3. Not recording verbal instructions. Verbal instructions are the most common source of unrecovered compensation events. If someone on the client's team tells a foreman to do something different, that needs to go in the report the same day. Not next week. Not when the QS asks about it.
4. Completing reports days later from memory. A foreman report completed on Friday for Monday, Tuesday, and Wednesday is a reconstruction, not a contemporaneous record. Adjudicators and Project Managers give significantly less weight to retrospective records. Five minutes at the end of each shift is non-negotiable.
5. Inconsistency between the foreman report and site diary. If the foreman report says 8 operatives and the site diary says 6, you've got a credibility problem. Cross-reference daily. The documents should tell the same story at different levels of detail.
6. Not photographing conditions. A photograph of an excavator standing idle next to a flooded excavation is worth more than 500 words of written description. Every foreman should have a phone camera and use it.

Reference Table: Foreman Report Checklist

Use this as a daily checklist. Print it and pin it in the site cabin, or use it as the basis for a digital form.