Project meeting agenda checklist for UK builders

Streamline your site discussions and ensure CDM 2015 compliance with our comprehensive project meeting agenda checklist designed specifically for UK builders.

By BRCKS Team ·

Project meeting agenda checklist for UK builders

Construction manager checking meeting agenda on site

TL;DR:

  • Using a standardised agenda ensures focused and efficient construction site meetings that produce traceable records. Pairing WhatsApp with an automation tool like BRCKS captures real-time messages and converts them into auditable project documentation. This approach saves over two hours daily in manual admin and improves compliance, continuity, and dispute resolution.

Use this one-page project meeting agenda checklist to run a focused site meeting and produce auditable minutes your team can act on immediately. Copy the checklist below, paste it into your meeting invite or WhatsApp group, and you are ready. BRCKS automates the admin that follows, saving users over two hours of manual effort daily. Under CDM 2015 and HSE guidance, meeting records must be auditable and retrievable, so every item on this checklist is designed to produce a traceable output.

  • Copy the agenda below and share it before the meeting
  • Assign a chair and a minute-taker before anyone arrives on site
  • Upload minutes, photos and actions to your project records within 24 hours

Table of Contents

What goes on a project meeting agenda checklist?

A solid construction site agenda covers ten items, in this order:

  1. Attendance — names, roles, company (2 min)
  2. Safety briefing — site inductions, RAMS updates, near-misses, plant inspections (3 min)
  3. Progress update — work completed since last meeting vs. programme (5 min)
  4. Programme and timeline — upcoming milestones, float, critical path risks (3 min)
  5. RFIs — open requests for information, responses outstanding, new queries (3 min)
  6. Variations — instructed and potential changes, commercial impact (4 min)
  7. Materials and deliveries — lead times, outstanding orders, access requirements (2 min) are critical aspects covered by concrete and asphalt services providers to ensure smooth logistics on site.
  8. Site diary and photo log — confirm photos taken, weather noted, diary updated (1 min)
  9. Actions and owners — each action gets a name and a date (2 min)
  10. Next meeting — date, time, location, chair (1 min)

Post-meeting actions (within 24 hours):

  • Distribute minutes to all attendees and relevant stakeholders
  • Upload site photos to the central project record, tagged with location and date
  • Raise any new RFIs in your project management system
  • Flag any potential variations and convert to formal variation requests within 48 hours
  • Confirm the site diary entry is complete and linked to today’s meeting record

Site meetings are central to construction processes; minutes create continuity, accountability and a contractual reference point that can be called upon in any dispute.

How to run a focused 20–30 minute site meeting

A 20–30 minute meeting that produces auditable minutes is achievable with a strict agenda and clear role allocation. The table below maps each step to a time allocation and a named owner.

Site supervisor reviewing meeting checklist at desk

Step Time Owner
Welcome and attendance 2 min Chair
Safety briefing 3 min Site supervisor
Progress update 5 min Main contractor
Programme review 3 min Main contractor
RFIs 3 min Contract lead / PM
Variations 4 min Contract lead
Materials and deliveries 2 min Site manager
Site diary and photo log 1 min Site manager
Actions and owners 2 min Minute-taker
Next meeting confirmation 1 min Chair

Who should attend? For a standard progress meeting: main contractor, site manager, contract lead, and any subcontractor whose work is on the critical path that week. For a pre-start meeting, add the client, designer, and CDM coordinator. Snagging meetings can often be limited to the site manager, client representative, and the relevant trade. Keep the room tight — every extra attendee adds time and reduces focus.

The CIOB Code of Practice recommends clear information flows and written instructions for queries, which maps directly to the RFI and variation items above.

Pro Tip: When a topic threatens to run over, park it. Write it on the actions list as “to be raised as formal variation/RFI” and assign an owner and a 48-hour deadline. Convert any parked item into a numbered variation request within 48 hours to maintain commercial clarity and a clean audit trail.

Practical rules for using WhatsApp in site meetings

WhatsApp is useful for fast coordination but must be paired with an auditable system for minutes, RFIs and variation records. Used alone, it creates an untraceable paper trail that will not satisfy CDM 2015 or a contract administrator’s requirements.

Do:

  • Share the agenda via WhatsApp before the meeting
  • Send a photo of the whiteboard or action list immediately after
  • Use a WhatsApp group to confirm attendance and circulate the draft minutes link
  • Upload any photos shared in the group to your central project records, tagged with metadata (who, what, location, timestamp)

Don’t:

  • Issue formal variation instructions or RFI responses via WhatsApp only
  • Treat a WhatsApp message as a contractual instruction
  • Leave photos in a chat group as the only record
  • Share personal data (subcontractor contact details, accident reports) in an uncontrolled group

GDPR and data retention: The ICO advises keeping personal data handling minimal and obtaining consent where necessary. WhatsApp groups that include personal contact details or incident information must be managed carefully. Digital records are acceptable to inspectors but must be exportable to hard copy and retained for the legally required periods, which vary by record type under CDM 2015.

Post-meeting WhatsApp checklist:

  1. Save all photos from the group chat to your project folder
  2. Tag each photo with project code, date, location, and a brief description
  3. Upload to the central project record or site diary app
  4. Create any new RFIs or variations in your project management system
  5. Archive the WhatsApp thread reference in the meeting minutes

How BRCKS automates meeting admin and links WhatsApp to auditable records

BRCKS ingests WhatsApp messages, auto-generates site diary entries, tracks RFIs and variations, and produces a timestamped audit trail, all without manual re-entry. The workflow is straightforward: a message or photo sent via WhatsApp is captured by the BRCKS bot, structured into a project record, and assigned to the relevant action or RFI.

Core features relevant to site meetings:

  • WhatsApp ingestion — messages and photos captured automatically from site
  • Automated site diary — weather, progress notes and photos linked to project tasks
  • RFI tracking — open, responded and overdue RFIs visible in one place
  • Variation log — structured record of instructed and potential changes with commercial impact
  • Meeting transcription — audio or notes converted to structured minutes
  • Action assignment — each action gets an owner, a due date and a status
  • Client portal — clients see progress without calling the site manager
  • Audit trail — every record is timestamped and exportable

BRCKS saves users significant manual effort daily through automated site diaries, RFI tracking, and a structured variation log.

For setup guidance, the BRCKS WhatsApp project management page walks through ingestion configuration step by step.

Meeting minutes template and file-naming conventions

A consistent template makes records discoverable during inspections and reduces disputes over what was agreed. Structure every set of minutes in three parts.

Before the meeting:

  • Meeting reference (projectcode_YYYYMMDD_meetingtype)
  • Project name, location, date, time
  • Attendees confirmed and agenda distributed
  • Approved drawings and RAMS version numbers noted

During the meeting:

  • Weather and site conditions
  • Progress against programme (percentage complete per work package)
  • Issues raised, with RFI or variation reference numbers
  • Photos taken and linked to agenda items
  • Actions: owner, description, due date

After the meeting:

  • Minutes distributed within 24 hours
  • Photos uploaded and tagged
  • RFIs and variations raised in the project management system
  • Site diary entry confirmed complete

File-naming convention: Use projectcode_YYYYMMDD_meetingtype (for example, SMITH001_20260415_progress). This ensures chronological sorting and easy retrieval during inspections, as recommended in the BRCKS construction meetings checklist.

Pro Tip: Begin every meeting by stating the expected outcome and confirming how each item converts into a record. That single practice increases minute acceptance and reduces disputes when records are reviewed weeks later.

UK compliance and health & safety items every meeting must cover

Certain records are required by CDM 2015 and HSE guidance and must be kept; digital records are acceptable if secure and retrievable. The pre-start meeting checklist for UK sites confirms that essential documents including approved drawings, structural calculations and product specifications must be confirmed at the outset.

H&S and compliance checklist items:

  • Site inductions completed and recorded for all workers on site
  • RAMS reviewed, signed and version-controlled
  • Plant and equipment inspection records up to date (LOLER, PUWER)
  • Scaffolding inspection certificate current (weekly or after adverse weather)
  • COSHH assessments in place for any hazardous materials in use
  • Accident and near-miss book reviewed; any incidents reported to HSE (RIDDOR) where required
  • H&S file updated with any new drawings, specifications or method statements
  • Fire safety and emergency procedures confirmed with all new starters

For fire safety and higher-risk buildings, the golden thread approach requires that all design and construction information is captured digitally and remains retrievable throughout the building’s life. Every meeting that touches structural, fire or safety-critical work should produce a record that feeds into that thread.

Under CDM 2015, the principal contractor must maintain a construction phase plan and H&S file. Meeting minutes that reference RAMS, inspections and incidents form part of that evidential record.

For authoritative guidance, consult HSE’s CDM 2015 resources and the ICO for data retention obligations.

Key takeaways

A structured project meeting agenda checklist, paired with a strict 20–30 minute format and auditable digital records, is the most reliable way to keep UK construction projects on programme and dispute-free.

Point Details
Use a ten-item agenda Cover attendance, safety, progress, programme, RFIs, variations, materials, diary, actions, and next meeting.
Keep meetings to 20–30 minutes Assign a chair, allocate time per item, and park overruns as formal actions or variation requests.
WhatsApp needs a backup system Use WhatsApp for speed, but upload all photos and instructions to auditable project records within 24 hours.
File-naming matters Use projectcode_YYYYMMDD_meetingtype to keep archives searchable and inspection-ready.
BRCKS automates the admin BRCKS ingests WhatsApp, auto-generates site diaries, and tracks RFIs and variations, saving over two hours of manual effort daily.

Why WhatsApp-integrated workflows actually get used on site

The honest reason most meeting admin systems fail on UK construction sites is adoption, not capability. A site manager juggling six subcontractors and a client calling every afternoon is not going to log into a separate platform to type up notes. That is the reality.

What changes the behaviour is keeping the familiar tool — WhatsApp — and making the admin happen automatically in the background. When the team keeps messaging the way they already do, and the records appear in the project system without anyone having to re-enter them, the quality of documentation goes up because the friction of creating it goes down.

The meeting management guidance for UK contractors makes the same point: clear roles and prompt minute distribution reduce misunderstandings, but only if the process is light enough that people actually follow it. A three-week pilot on a single project, comparing time spent on admin before and after enabling WhatsApp ingestion, tends to make the case more convincingly than any feature list.

Two hours back every day: what BRCKS does for your meeting admin

Two hours of manual admin saved every day is the difference between leaving site on time and staying late to type up notes nobody will read until a dispute forces them to.

[IMAGE:cta_image]

BRCKS connects directly to your WhatsApp groups, captures photos and messages as they happen, and converts them into structured site diary entries, RFIs and variation logs with full audit trails. Your clients get a portal that shows them progress without a single phone call to you. Subcontractors and clients are invited free; you pay per seat for your core team, with no long-term contract required.

A 14-day free trial gives you enough time to run the WhatsApp project management setup, create your meeting templates, and see an auto-generated site diary after your first site meeting. For builders specifically, the BRCKS builders page covers the full feature set and pricing.

Useful sources and further reading

BRCKS guides:

  • Checklist for effective construction meetings
  • Meeting management tips for UK contractors
  • WhatsApp project management for construction
  • Site diary app for UK construction
  • Document control in construction

UK compliance and authoritative sources:

  • HSE CDM 2015 guidance — hse.gov.uk/construction/cdm
  • ICO data retention guidance — ico.org.uk
  • CIOB Code of Practice for Project Management (pre-start meeting specimen agenda)
  • RIBA pre-contract meeting agenda template

FAQ

What should a construction site meeting agenda include?

A construction site meeting agenda should cover attendance, a safety briefing, progress against programme, RFIs, variations, materials and deliveries, the site diary and photo log, actions with owners, and the next meeting date. Ten items, run in 20–30 minutes.

How do you capture meeting minutes on a construction site?

Assign a dedicated minute-taker before the meeting starts, record each action with an owner and due date, and distribute the minutes within 24 hours. Uploading photos and linking them to agenda items, as supported by a site diary app, keeps records auditable under CDM 2015.

Is WhatsApp acceptable for construction project records?

WhatsApp is useful for fast coordination but is not sufficient as a standalone record. Formal instructions, RFI responses and variation notices must be held in an auditable system. BRCKS ingests WhatsApp messages automatically and converts them into structured project records with timestamps and audit trails.

What file-naming convention should I use for meeting minutes?

Use projectcode_YYYYMMDD_meetingtype (for example, SMITH001_20260415_progress). This format ensures chronological sorting and makes records easy to retrieve during HSE inspections or contract disputes.

What CDM 2015 records must be covered in site meetings?

Meetings should confirm that site inductions, RAMS, plant inspection records, scaffolding certificates, COSHH assessments and accident reporting are all current. The principal contractor must maintain a construction phase plan and H&S file; meeting minutes referencing these items form part of that evidential record.

Recommended


How BRCKS Can Help

Adopting a structured approach to your project meetings ensures that every site visit and briefing drives your builds forward without wasting valuable time. BRCKS simplifies this process by centralising your project documentation and communication, making it easier to track action items and keep your team aligned with the agenda. By integrating these checklists into a digital workflow, you can reduce administrative friction and focus on delivering high-quality results. We invite you to see how BRCKS can transform your project management by exploring our platform today. Learn more at BRCKS and explore our full feature set.


Sources