digiQC has several user roles, each with its own rights. Picking the right role for each person controls what they can see and do — from running the whole company's quality setup down to simply responding to an issue. This article explains each role, when to use it, and a real example. Roles are also either Paid (consume a licence) or Complimentary (free).
What they do: The organisation's top administrator — usually the Quality Control Head at Head Office. The only role that can add users, checklists and teams at Organisation level, edit at both Organisation and Project level, and make a checklist live.
When to use it: Give this to the one or two senior people who own quality across the whole company.
Example: The QC Head sets up the company in digiQC, builds the master checklists, makes them live, and creates the project teams.
What they do: Runs a specific project — usually the Project Manager / Construction Manager / site QC in-charge. Can add users, checklists and teams for their project, rename an EQC while its stages are still in progress, and use the mobile app to raise issues or give approvals. A project can have multiple Project Admins.
When to use it: For the person in charge at each site who manages that project day to day.
Example: A site Project Manager adds three inspectors, assigns their checklists, and approves inspections from the mobile app while walking the site.
What they do: Usually the site engineers. They raise RFIs (request for inspection) and carry out inspections. May be given permission to raise issues and assign them, and read-only access to the web app.
When to use it: For the engineers who do the actual quality checks on site.
Example: A site engineer raises an RFI for a column before concreting, then runs the reinforcement checklist on the mobile app, recording Pass/Fail with photos.
What they do: Helps the System Admin by creating and editing checklists at Organisation level, but cannot activate (make live) them — only the SA can. Web module only. Saves the senior QC manager's time by delegating checklist-building to a tech-savvy junior.
When to use it: When you want a junior engineer to build out checklists for the System Admin to review and make live.
Example: A junior engineer drafts 20 checklists over a week; the System Admin reviews them and makes them live.
What they do: Reviews the data generated in digiQC and comments on it. Comments are notified to the relevant users to improve their work methods. View access only.
When to use it: For an internal or third-party quality auditor who should review but not change data.
Example: An external quality consultant reviews completed inspections weekly and leaves comments where the method needs improving; the site team is notified.
What they do: A project user who can view their team's data and respond to issues raised to them or their team.
When to use it: For a contractor or sub-team member who needs to see their team's work and respond to issues, but not run inspections.
Example: A contractor's supervisor responds to an issue raised against their team's work, attaching a photo of the fix.
What they do: Any stage of a checklist can be set up for approval; the person who gives it is the Approver. An Approver can be internal or external, and (by configuration) remote or on-site.
Remote approver — need not be within the project's geo-fence; approves from the web app.
On-site approver — approves from the mobile app; any attached photo must be taken live from the camera.
When to use it: On stages where a senior must sign off before work proceeds.
Example: A structural consultant (remote) approves the reinforcement stage from the web app before concreting is allowed.
What they do: A Project Admin or Inspector made an approver — already a project user, hence "internal".
Example: The Project Manager is set as the Level-1 approver for the finishing checklist.
What they do: An expert set up as approver who is neither a Project Admin nor an Inspector on the project.
Example: An independent third-party structural engineer is added solely to approve critical stages.
Paid: System Admin, Project Admin, Inspector (and an Internal Approver, who is a Project Admin or Inspector). Complimentary: Auditor, Associate, Checklist Maker.
Yes — a project can have multiple Project Admins.
Only the System Admin. A Checklist Maker can create and edit checklists but cannot activate them.
An internal approver is a Project Admin or Inspector already on the project. An external approver is an outside expert added only to approve.
A remote approver approves from the web app and need not be inside the project geo-fence. An on-site approver approves from the mobile app, and any photo must be taken live from the camera.
Yes, if they are given read-only access.
