| S.No. | Checkpoint | IS Requirement | Status |
|---|---|---|---|
| A. REGISTER COLUMN DEFINITIONS | |||
| A1 | Column 1: OBS NO — unique sequential number (OBS-YYYY-###) Acceptance: Unique; chronological; no gaps; format consistent across project | Cl. 7.5.3 — Documented information | OK NC NA HOLD |
| A2 | Column 2: DATE — date of observation Acceptance: DD-MM-YYYY format; entered same-day; traceable to walk or event | Cl. 9.1.1 — Monitoring | OK NC NA HOLD |
| A3 | Column 3: OBSERVED BY — name and role Acceptance: Consultant/QA/auditor/owner rep; authority to observe documented | Cl. 5.3 — Organizational roles | OK NC NA HOLD |
| A4 | Column 4: AREA / LOCATION — where observation made Acceptance: Grid, floor, element; unambiguous; photo tagged to location | Cl. 8.5.2 — Traceability | OK NC NA HOLD |
| A5 | Column 5: OBSERVATION — specific, factual description Acceptance: Factual (not judgmental); measurable; photo ref; includes what spec/practice expected | Cl. 9.1.1 — Factual recording | OK NC NA HOLD |
| A6 | Column 6: CATEGORY — Safety / Quality / Housekeeping / Environment / Process / Good Practice Acceptance: One primary category; enables trend analysis; Good Practice highlighted positively | Cl. 9.1.3 — Categorization | OK NC NA HOLD |
| A7 | Column 7: RECOMMENDED ACTION — suggested improvement Acceptance: Specific, actionable; assigned to responsible trade; no vague suggestions | Cl. 10.3 — Continual improvement | OK NC NA HOLD |
| A8 | Column 8: RESPONSIBLE / DUE DATE — who will action and by when Acceptance: Named person; due date realistic (typically 7-14 days) | Cl. 10.2 — Action ownership | OK NC NA HOLD |
| A9 | Column 9: STATUS — OPEN / ACTIONED / CLOSED / ESCALATED TO NCR Acceptance: Status updated weekly; escalation documented if observation recurs/serious | Cl. 10.2.2 — Status tracking | OK NC NA HOLD |
| A10 | Column 10: CLOSURE NOTES / VERIFIED BY — evidence and sign-off Acceptance: Action evidence captured; verifier name and date; follow-up photo attached | Cl. 10.2.1 — Effectiveness verification | OK NC NA HOLD |
| B. OBSERVATION SCOPE AND DIFFERENTIATION | |||
| B1 | Observations cover all project dimensions: safety, quality, housekeeping, stacking, environment Acceptance: Not limited to one trade/discipline; site walk covers full project footprint | Cl. 9.1.1 — Comprehensive monitoring | OK NC NA HOLD |
| B2 | Material stacking and storage issues flagged per IS 4082 recommendations Acceptance: Bagged material off-ground on wooden planks; steel under cover; max stack heights observed | Cl. 4 — Stacking | OK NC NA HOLD |
| B3 | Observations distinguished from NCRs: observation = advisory, NCR = binding defect Acceptance: If requirement is violated = NCR raised; if improvement needed = observation logged | Cl. 10.2.1 — Scope demarcation | OK NC NA HOLD |
| B4 | Good-practice observations included to reinforce positive behavior and share across teams Acceptance: At least 10-15% of entries are Good Practice; shared in toolbox talks and newsletters | Cl. 10.3 — Improvement culture | OK NC NA HOLD |
| C. ACTIONING AND ESCALATION | |||
| C1 | Open observations reviewed weekly in QA/site coordination meeting Acceptance: MoM shows obs review; actions followed up; aging list kept short | Cl. 9.3 — Management review | OK NC NA HOLD |
| C2 | Recurrent observations (same issue repeated ≥3 times) escalated to NCR Acceptance: Recurrence counted; NCR raised automatically on 3rd occurrence of same issue | Cl. 10.2.1 — Escalation | OK NC NA HOLD |
| C3 | Overdue observations (open >21 days) escalated to project manager Acceptance: Aging report weekly; >21 days triggers PM alert; action plan revised | Cl. 10.2 — Timeliness | OK NC NA HOLD |