company logo

Rate us on Google Play StoreRate us on App Store
All collections2 Knowledge2.5 Web Setup, Monitoring, Tracking and Analysis2.5.28 All Inspection workflows with RFI

2.5.28 All Inspection workflows with RFI

The RFI and Re-RFI workflows with diagrams: with/without approver, with/without inspection-stage approval, and Re-RFI On/Off. Maker raises RFI → (approver review) → Checker inspects → Pass/Approve moves on; Fail/Redo triggers a fresh RFI (Re-RFI On) or restarts from Inspection (Re-RFI Off).

Overview

When RFI is enabled, an inspection can follow one of a few RFI workflows, depending on (1) whether an RFI approver is involved, (2) whether there is approval at the inspection stage, and (3) whether Re-RFI is On. This article explains those flows, with a diagram for each.

🧭 How the RFI workflow works

Roles: Maker/Contractor (raises the RFI, does the work), Checker/Inspector (inspects), Approver (optional — accepts/rejects the RFI at Review, and/or approves after inspection).

  1. Raise RFI — the Maker requests inspection when work is ready.

  2. Review RFI (only if an RFI approver is set) — the approver Accepts or Rejects. Reject → the Maker rectifies and raises a fresh RFI.

  3. Inspection — the Checker inspects → Pass or Fail.

  4. Approval at inspection stage (if configured — up to 3 levels) — after a Pass, an approver Approves or gives Redo.

  5. Fail or Redo — what happens next depends on Re-RFI (below).

Re-RFI — On vs Off

  • Re-RFI On (default) — on a Fail or Redo, the Maker must raise a fresh RFI (Re-RFI) after corrections to restart.

  • Re-RFI Off — on a Fail or Redo, the process restarts from the Inspection stage — no fresh RFI.

The RFI workflows

1. RFI → Inspection (Re-RFI On) — no approver, no inspection approval. On a Fail, the Maker raises a fresh RFI.

2. RFI → Inspection (Re-RFI Off) — same, but on a Fail the inspection restarts from the Inspection stage (no fresh RFI).

3. RFI → Inspection → Approval (Re-RFI On) — the inspection stage has approval. A Fail or a Redo sends the Maker back to raise a fresh RFI.

4. RFI → Inspection → Approval (Re-RFI Off) — with inspection approval, but a Fail or Redo restarts from the Inspection stage.

5. RFI (with Approver) → Inspection (Re-RFI On) — an approver Accepts/Rejects the RFI first. Reject → Rectify RFI; Fail → fresh RFI.

6. RFI (with Approver) → Inspection → Approval (Re-RFI On) — the full chain, with both approval points (RFI Review and inspection Approval).

❓ FAQ

1. What's the difference between RFI with and without an approver?

With an approver, the RFI is accepted or rejected at Review before inspection. Without, the RFI goes straight to inspection.

What is "approval at the inspection stage"?

After the inspection Passes, an approver signs it off (up to 3 levels: L1 → L2 → L3) before the stage completes. This is separate from the RFI approver.

On a Fail or Redo, what does Re-RFI On vs Off do?

On — the Maker raises a fresh RFI. Off — the process restarts from the Inspection stage (no fresh RFI).

What happens if the approver rejects the RFI?

The Maker rectifies and raises a fresh RFI.

Where's the complete list of inspection workflows?

See 2.2.13 digiQC Inspection Workflows — the full 20-workflow catalogue (RFI and non-RFI).

💡 Good to know

  • RFI workflow depends on: RFI approver (no/yes) × inspection-stage approval (none / L1–L3) × Re-RFI (On/Off).

  • Re-RFI On (default) = fresh RFI after a Fail/Redo; Off = restart from the Inspection stage.

  • Re-RFI must be enabled in the project RFI settings (2.6.9).

  • The full workflow catalogue is in 2.2.13.

🔗 Related articles

  • 2.6.9 RFI Introduction and setup for the Project

  • 2.6.10 Setup RFI stage for Project Checklist

  • 2.2.13 digiQC Inspection Workflows

  • 2.2.9 RFI process with Approver

Did this answer your question?
😞
😐
😁