digiQC lets you configure the inspection workflow for each stage to match your organisation's quality process. A workflow decides who is involved and in what order — whether the Maker raises an RFI first, whether that RFI needs an internal check, what happens on a Redo (the Re-RFI setting), and how many sign-offs (up to 3) are needed. Every stage can use a different workflow. There are 20 combinations in all — this guide helps you pick the one that matches your project.
digiQC uses four workflow roles (the general term), which map to real parties on a construction project like this:
Workflow role (general) | On a construction project (specific) |
|---|---|
Maker | Contractor — does the work and raises the RFI |
Maker QC | Contractor's own QC team — clears the RFI internally before the Checker is called |
Checker | PMC (or the Client's QC engineer) — physically inspects the work against the checklist |
Approver (L1 / L2 / L3) | Senior sign-off — e.g. Site Engineer, PMC Manager, then Client (up to 3 levels) |
Throughout this guide the flows use the general role with the construction party in brackets — e.g. Maker (Contractor), Checker (PMC), Approver (Client).
Stage context — a workflow applies to one stage (e.g. Pre / During / Post). Each stage can have its own workflow. Completing a stage unlocks the next; the final stage completes the inspection.
RFI — a Request for Inspection the Maker (the Contractor, or whichever team/user is set to raise it) raises to signal work is ready. Some workflows have no RFI (the Checker inspects directly).
RFI Approval (Maker QC) — an optional internal check: the Maker QC (Contractor's QC) accepts the RFI before the Checker (PMC) is called.
Approval levels — after the inspection passes, up to 3 sequential sign-offs — Approver L1 → L2 → L3 (e.g. Site Engineer → PMC Manager → Client).
Re-RFI (Off / On) — decides what a Redo does once inspection has started: Off = back to the inspection stage (Checker re-inspects, no fresh RFI); On = the Maker must raise a fresh RFI first.
What a Redo or rejection restarts from depends on the stage and the Re-RFI setting:
- If Re-RFI is On, a Redo requires the Maker to raise a fresh RFI. - If Re-RFI is Off, a Redo goes back to the inspection stage (it has already started) — the Checker re-inspects, no fresh RFI. - If the RFI itself is rejected (before the inspection stage has started), you start again from the RFI — a fresh RFI — whatever the Re-RFI setting, because inspection never began.
An inspection fail re-inspects only the failed checkpoints — but you also have the option to change other checkpoints if needed.
The Maker-QC RFI check is optional — if it isn't set up, the RFI goes straight to the Checker.
Completing a stage unlocks the next (Pre → During → Post); the final stage ends the inspection.
Each stage can use a different workflow.
Answer four questions and you land on exactly one of the 20:
Does the Maker (the Contractor, or the team/user you set) need to formally request inspection? Yes → an RFI workflow (5–20). No → a No-RFI workflow (1–4).
Should the Maker QC (Contractor's QC) clear the RFI first? Yes → an "RFI Approval" workflow (9–12, 17–20).
How many sign-offs after the inspection passes? None, or L1 / L1-L2 / L1-L2-L3.
On a redo, must the Maker raise a fresh RFI? Yes → Re-RFI On (13–20). No → Re-RFI Off (5–12).
No RFI, no sign-off. The Checker (PMC) inspects the work against the checklist and passes it. Choose this when the checker is trusted and you need neither a request step nor a separate approval — e.g. a small project or a low-risk stage.
The Maker (Contractor) raises an RFI when work is ready; the Checker (PMC) inspects. No approval afterwards. Choose this when the maker should formally request the inspection, but a passed inspection is enough on its own.
The classic setup. The Maker (Contractor) raises the RFI, the Checker (PMC) inspects on site, and the Approver (Client) gives the final approval (L1). Choose this when the client wants to sign off every passed inspection.
The Maker (Contractor) raises the RFI, the Maker QC (Contractor's QC) clears it internally, then the Checker (PMC) inspects, and the Approver (Client) approves (L1). Choose this when the contractor must self-check before calling the PMC — it cuts down wasted PMC site visits.
Maker (Contractor) raises the RFI → Checker (PMC) inspects → Approver L1 (Site Engineer) → Approver L2 (PMC Manager) → Approver L3 (Client). Choose this for critical or high-value work needing several authorities. Use the Re-RFI On version (Workflow 16) when a redo should force the maker to raise a fresh RFI — maximum accountability.
Say an approver gives a Redo after inspection. With Re-RFI Off, the work goes back to the inspection stage — the Checker (PMC) re-inspects once the maker has fixed it, no fresh RFI. With Re-RFI On, the Maker (Contractor) must raise a fresh RFI first, formally re-requesting the inspection. (If instead the RFI was rejected before inspection ever started, you begin again from the RFI.) Off is lighter for a trusted contractor; On gives a formal paper-trail for high-accountability projects.
They fall into three groups: No RFI (1–4) — the Checker inspects directly; RFI, Re-RFI Off (5–12) — on Redo the work returns to the inspection stage; RFI, Re-RFI On (13–20) — on Redo the Maker raises a fresh RFI.
# | Workflow | RFI | RFI approval | Re-RFI | Approval levels |
|---|---|---|---|---|---|
1 | Inspection | No | No | — | None |
2 | Inspection → L1 | No | No | — | L1 |
3 | Inspection → L1 → L2 | No | No | — | L1 L2 |
4 | Inspection → L1 → L2 → L3 | No | No | — | L1 L2 L3 |
5 | RFI → Inspection | Yes | No | Off | None |
6 | RFI → Inspection → L1 | Yes | No | Off | L1 |
7 | RFI → Inspection → L1 → L2 | Yes | No | Off | L1 L2 |
8 | RFI → Inspection → L1 → L2 → L3 | Yes | No | Off | L1 L2 L3 |
9 | RFI → RFI Approval → Inspection | Yes | Yes | Off | None |
10 | RFI → RFI Approval → Inspection → L1 | Yes | Yes | Off | L1 |
11 | RFI → RFI Approval → Inspection → L1 → L2 | Yes | Yes | Off | L1 L2 |
12 | RFI → RFI Approval → Inspection → L1 → L2 → L3 | Yes | Yes | Off | L1 L2 L3 |
13 | RFI → Inspection (Re-RFI On) | Yes | No | On | None |
14 | RFI → Inspection → L1 (Re-RFI On) | Yes | No | On | L1 |
15 | RFI → Inspection → L1 → L2 (Re-RFI On) | Yes | No | On | L1 L2 |
16 | RFI → Inspection → L1 → L2 → L3 (Re-RFI On) | Yes | No | On | L1 L2 L3 |
17 | RFI → RFI Approval → Inspection (Re-RFI On) | Yes | Yes | On | None |
18 | RFI → RFI Approval → Inspection → L1 (Re-RFI On) | Yes | Yes | On | L1 |
19 | RFI → RFI Approval → Inspection → L1 → L2 (Re-RFI On) | Yes | Yes | On | L1 L2 |
20 | RFI → RFI Approval → Inspection → L1 → L2 → L3 (Re-RFI On) | Yes | Yes | On | L1 L2 L3 |
Scenario | Re-RFI Off | Re-RFI On |
|---|---|---|
Approver gives Redo (after inspection) | Back to the inspection stage — Checker (PMC) re-inspects, no fresh RFI | Maker (Contractor) must raise a fresh RFI |
RFI rejected before inspection starts | Start again from the RFI (fresh RFI) | Start again from the RFI (fresh RFI) |
Inspection fails | Re-inspect the failed checkpoints (option to change others) | Re-inspect the failed checkpoints (option to change others) |
Who controls re-inspection | Checker (PMC) | Maker (Contractor) formally re-requests |
Best for | Projects with a trusted contractor | High-accountability projects |
Workflow 6 — Maker (Contractor) raises the RFI, Checker (PMC) inspects, Approver (Client) signs off (L1). Add more levels (Workflow 7 or 8) if you need Site Engineer or PMC Manager sign-offs before the client.
Use an RFI Approval workflow (e.g. Workflow 10): the Maker QC (Contractor's QC) clears the RFI before the Checker (PMC) is called.
Yes — Workflows 1–4 have no RFI; the Checker (PMC) inspects directly, with 0 to 3 sign-offs afterwards.
On a Redo after inspection: Off sends the work back to the inspection stage (the Checker re-inspects directly); On makes the Maker raise a fresh RFI first. On is more formal and accountable.
The work goes back for re-inspection. With Re-RFI Off it returns to the inspection stage (Checker re-inspects, no fresh RFI); with Re-RFI On the Maker raises a fresh RFI first. After it passes again, the approval cycle restarts from L1.
If the RFI is rejected before inspection starts, you start again from the RFI (raise a fresh RFI) — whatever the Re-RFI setting — because the inspection stage never began.
Only the failed checkpoints are re-inspected — though you also have the option to change other checkpoints if needed.
Up to three (L1 → L2 → L3), applied in sequence — e.g. Site Engineer, PMC Manager, Client.
Yes — every stage (Pre / During / Post) can have its own workflow.
Decide the steps and levels you need, then contact the digiQC team to configure it.
Workflows are configured per stage — each can differ, and completing one unlocks the next.
Approvals are sequential, and a Redo restarts the approval cycle from L1.
A Redo restarts from the inspection stage (Re-RFI Off) or a fresh RFI (Re-RFI On); a rejected RFI restarts from the RFI because inspection never began.
An inspection fail re-inspects only the failed checkpoints, with the option to change others.
There are 20 combinations across three groups — No RFI, RFI (Re-RFI Off), RFI (Re-RFI On). Contact the digiQC team to configure yours.
2.2.7 RFI process and inspection
2.2.8 RFI process without Approver
2.2.9 RFI process with Approver
2.2.6 How to "PASS" the Approved EQC to complete the stage?
