On the mobile app, inspection data is now team-scoped — you only see *EQCs (inspections) your team is actually working on and that are assigned to you. The first team to act on a stage type locks it to their team, and other teams stop seeing it. This keeps each team's data private and their list clean.*
The doer team is the team whose user first performs a stage.
There are two independent locks:
- RFI doer team — the first team to act on any RFI stage owns all RFI stages of that EQC. - Checklist (inspection) doer team — the first team to act on any inspection stage owns all inspection stages.
Once set at the first action, the doer team is locked and cannot change.
A multi-team user can keep one lock and lose the other — the two are independent.
An EQC appears on mobile only to:
Users who are both (a) in the doer team for the currently active stage type and (b) assigned to that work (checklist or RFI assignment), and
The approver of the current active stage + level.
Everyone else no longer sees it.
If you belong to more than one team, the first time you start an RFI or an inspection stage, you're asked "Which team are you doing this for?" Your choice locks the doer team. You're asked once — never again.
After every stage you submit (RFI and inspection), you pick the Maker team — the team that did the physical work. This is for web reporting and analysis only and never changes who sees the EQC on mobile. You can pick more than one.
Approvers see an EQC only while it sits at their exact approval stage and level — not before, not after. (RFI approval is its own single-level approval.)
Available — action cards for your stage type, plus view-only cards for the other stage type (tapping one explains why).
Paused — a personal tab: inspections and RFIs you paused midway (only you see them).
Approval — items you submitted for approval, plus items an approver sent back as Redo (now actionable).
To-Do → To-be Approved — an EQC only while you're the approver of its current active stage + level.
To-Do → Draft — a personal sub-tab: approval reviews you saved as Draft.
A Fail or Redo notifies everyone who has acted on the EQC so far (doers and approvers), so nobody who worked on it is left unaware.
Visibility is driven by the doer team, not the Maker team.
The two locks (RFI and inspection) are independent.
This scoping applies on mobile.
2.2.5 EQC list explanation — Available, Paused & Approval
Who is the Maker and the Checker?
What is the Maker team in digiQC?
2.5.20 Project user roles, permissions & access explained
