ACTION in a site meeting report: what the project manager needs to know to avoid confusing an urgent request with routine tracking
You read “ACTION” in the Obs. column of a CR. It’s different from a PM — the action is expected before the next meeting, often within 48 hours. If you haven’t identified who’s responsible and by when, you’re already behind.
Type | Phase | Actors | Impact | Stakes | Where |
|---|---|---|---|---|---|
CR status | Execution | MOE (project manager), OPC (scheduling coordinator), Contractor, Inspection body (BC) | High | contractual | Obs. column of the CR tracking tables |
1. Operational definition + common mistake
In a site meeting report, the status ACTION designates a request requiring an immediate response or completion, before the next site meeting. Unlike PM (an ongoing point with a flexible deadline), ACTION is a point whose urgency the CR’s author explicitly flags: not acting on it is an anomaly from the very next day.
In this CR, ACTIONs cover a range of topics: “Cover the embankments with tarpaulin” (safety), “Supply follow-up of waste tracking forms (BSD) at the end of removals” (regulatory obligation), “Supply the setting-out survey report for the diaphragm wall” (technical validation), “Submit the declaration for your subcontractor TECHNISOL” (contractual obligation).
Many assume ACTION is just a stronger synonym for PM — in reality, an ACTION in a well-drafted CR means the MOE has judged that this point cannot wait for the next cycle. It’s an instruction to be handled within 24 to 48 hours, and failing to act on it can trigger a site blockage or a direct formal notice.
2. Where it appears
In a site meeting report — “Obs.” column, in each trade’s or actor’s section. ACTION is issued by the MOE (or OPC) on requests requiring immediate execution. It can concern a missing blocking document (VIC, BSD, survey report), a decision to be made before the next phase of works, or the immediate correction of a safety non-conformity. Examples from the analyzed CR:
“Supply the setting-out survey report for the diaphragm wall” — Obs.: ACTION
“Supply follow-up of waste tracking forms (BSD) at the end of removals” — Obs.: ACTION
“Submit the declaration for your subcontractor TECHNISOL” — Obs.: ACTION
“Supply a new site installation plan” — Obs.: ACTION
3. How to read this entry in the CR
If you’re the recipient of an ACTION → handle it before any other PM on your list. Confirm completion in writing, since a lack of confirmation can trigger escalation to REMINDER at the very next session.
If you’re the CR’s author → only use ACTION for genuinely urgent requests. Too many ACTIONs in a CR dilute its impact. If an ACTION isn’t handled by the next meeting, escalate it to REMINDER 1.
If an ACTION concerns safety (embankment tarpaulin, collective protections, a missing VIC) → also report it to the CSPS in writing. The CR alone isn’t enough for regulatory obligations with immediate effect.
4. Who does what
Actor | What ACTION means to them | Concrete action |
|---|---|---|
MOE / OPC | An urgent request issued, to be checked at the next CR | Identify the owner, set the deadline, verify completion before the next session |
Recipient contractor | A short-term duty to deliver a result | Handle it within 24–48h, confirm in writing, don’t wait for the next meeting |
Inspection body (BC) | If the ACTION concerns a technical document submitted to them | Report if the document is blocking their own opinion or sign-off |
CSPS | If the ACTION concerns a safety point | Confirm the obligation has been lifted in writing, independently of the CR |
5. What this changes in practice
A project manager who uses the ACTION status correctly can prioritize their follow-ups and demonstrate that urgent matters were flagged at the appropriate level. A project manager who reserves “ACTION” for routine PMs dilutes their authority and can no longer prove that certain requests were urgent rather than merely ongoing.
Failure scenario: the MOE places an ACTION on “Submit the subcontractor declaration for TECHNISOL.” The contractor doesn’t declare its subcontractor, who starts work without approval. In the event of an accident, the subcontractor’s lack of approval exposes the main contractor and the MOE who let the work start without verification.
6. Example of real wording
“Submit the declaration for your subcontractor TECHNISOL” — Obs.: ACTION
“Supply a new site installation plan” — Obs.: ACTION
7. Points of caution
An unhandled ACTION doesn’t stay ACTION at the next meeting: it escalates to REMINDER 1 — never let an ACTION age.
An ACTION on a regulatory point (VIC, BSD, subcontractor declaration) has immediate evidentiary value: it documents that the non-conformity was flagged urgently.
An ACTION with no named recipient is an anomaly: always specify the contractor or actor concerned.
Don’t confuse ACTION (urgent request, deadline < 1 week) with PM (ongoing point, deadline = 1 cycle).
A repeated, unhandled ACTION becomes REMINDER: continuity of numbering is essential for evidence.
8. Not to be confused with
Related term | Key difference |
|---|---|
PM | Ongoing point, one-cycle deadline — no explicit urgency |
REMINDER | Unhandled, overdue request — escalation from an earlier PM or ACTION |
IMPORTANT | Warning signal on a structural or contractual issue — not necessarily a request for immediate action |
PI | Informational point — no action expected in return |
9. Related terms
Same phase (execution): PM · Numbered REMINDER · PI · FAIT · RAS · VIC · BSD
Same actor (MOE/OPC): Site meeting report · Formal instruction (ordre de service) · Penalty tracking table
<-
BACK TO FULL GLOSSARY