digiQC — A construction quality-control platform for running inspections, raising and tracking issues, and maintaining registers. Available on web and mobile (Android & iOS).
Project — A construction site where quality control is carried out under common systems.
Web module / Web app — The browser-based part of digiQC: set up the Organisation and projects, view inspections, analyse data, and download reports.
Mobile app — The Android/iOS app for onsite inspection and raising issues. The Register module is web only.
Web Portal — A button in the mobile app that opens the digiQC web app in your browser.
Nomenclature — A standardised naming protocol where admins define master naming for mobile users, so inspections are named consistently for tracking and analytics.
Dashboard — A summarised, graphical view giving a macro-level update; presents data analytically.
Custom dashboard — A bespoke dashboard digiQC builds to a client's requirements; can be emailed automatically daily, weekly or monthly.
To Do tab — Items awaiting your action: inspections to approve (as Approver), issues to be responded, and registers to be approved.
Log tab — The activity log, with two sub-tabs: Inspect and Issue.
Report tab — Download project data (CSV/PDF).
Setup tab — Where you set up Users, Checklists and Teams.
Project tab — Lists all projects; the System Admin can add a new project.
Inspect — Run quality inspections using checklists; capture photo, remark, drawings and witness details through an approval workflow.
Issue — Capture observations and raise, assign and track issues to closure. Each issue has a Type and Tag.
Register (web only) — Maintain structured registers and logs where entries are recorded. Examples: Concrete Register, Material Register, Pour Log, Drawing Register, and others.
Organisation data — Company-wide data, templates and user details, created and maintained by the System Admin; can be imported into a project.
Project data — Data created or allocated within a project; accessible to the Project Admin & System Admin by default, others as per their rights.
User — A person with login credentials to access digiQC. A user can belong to multiple teams, in a project and in the organisation.
Paid user — A user who consumes a paid licence: Inspector, Project Admin, System Admin.
Complimentary user — A free user who does not consume a paid licence: Auditor, Associate.
System Admin — The main administrator who can edit at both Organisation and Project level; the only role that can access Organisation data; makes checklists live.
Project Admin — Administers a specific project: users, teams, access and data within it.
Inspector — Carries out inspections on site and records Pass/Fail.
Auditor — Reviews and audits project data; given View access only. (Complimentary)
Associate — A project role who can view their team's data and respond to issues raised to them or their team. (Complimentary)
Checklist Maker — An Organisation-level role who can create and edit checklists but cannot make them live — only the System Admin can make a checklist live.
Approver — Reviews and approves or redoes inspection stages, and accepts or rejects RFIs and responded issues.
Phone contact — A contact who raises issues via a phone number and is not part of the project.
Role — The user's designation (System Admin, Project Admin, Inspector, Auditor, Associate).
Permissions (Rights) — Per-user toggles: Location and Authentication.
Location — Geo-fencing for the user.
Authentication — Requires the phone lock to be unlocked before starting an inspection.
Access — What the user can reach: Web Access, Raise Instruction, assigned Checklists, and assigned RFI.
Web Access (Team | Project) — Data scope: Team (their team's data) or Project (all project data).
Raise Instruction — Permission allowing the user to raise issues.
Team — A group of users with a common scope; a user can be in multiple teams.
Main Team — The default team of the organisation that has purchased digiQC.
Checklist — Contains stages; each stage contains checkpoints.
Stage — A phase of a checklist (e.g. pre, during, post). Holds checkpoints, and carries its configuration and approval (0 up to 3 levels).
Checkpoint — A single question or check within a stage. Has a Title and a Type (Y/N, numeric, text, option), with options to make photo and remark mandatory.
EQC (Element of Quality Control) — The unit on which an inspection is carried out using its checklist. On start, a unique identifier (name/location) is created for searchability and analytics.
Inspection — Checking work against a checklist's stages and checkpoints and recording the results.
Witness details — Record of who witnessed the inspection.
Drawing — A construction drawing referenced or attached during inspection.
RFI (Request For Inspection) — Requires a request to start the inspection; raised before the inspection stage, with a single level of approval (Accept/Reject by the Approver).
Witness required — Requires a witness to be recorded, increasing accountability of the parties involved.
Drawing required — The Inspector must add a drawing photo to complete the inspection.
Skip stage — The Inspector can skip a stage with a single button, but photo and remark become mandatory.
Validate stage — The Inspector can pass or seek approval with a single button, with mandatory photo and remark.
Pass / Fail — The result on a checkpoint or stage — done by the Inspector during inspection.
Approve / Redo — The decision on a stage — done by the Approver.
Accept / Reject — The decision on an RFI (by the Approver) or a responded issue (by the raising team).
Approval level — A stage can have 0 up to 3 approval levels, in sequence. If a level has multiple approvers, any one can approve.
Issue — An observation or problem raised, assigned and tracked to closure. The earlier "Instruction" is now an Issue.
Raise — Opening an issue in digiQC.
Responded — When the issue has been responded to by the assignee or their team.
Accept / Reject (issue) — Done by the raising team on a responded issue.
Closed — When an issue is accepted, or directly closed by the raising team.
Issue Type — NCR, Observation, Safety, Material, Other.
Tag — Minor, Major, High, Critical, etc. A maximum of 2 tags can be added per issue.
NCR (Non-Conformance Report) — One of the Issue Types, for work that does not meet the required standard.
Instruction — Now handled as an Issue (legacy term; still appears in some report names).
Register template — A register's structure: a Detail part plus a Table part, built from fields.
Detail part — Appears once per log and is common to all entries of the table.
Table part — Has multiple rows; each row is an entry.
Field — A building block of a template. Types: text, option, checkbox, numeric, attachment (PDF/photo), calculation, and others.
Log — Created when entries are added. A register has multiple logs, each with its own detail page.
Entry — A single row within the table part of a log.
Log list — The section listing all logs of a register.
Entries list — The section listing all entries across a register's logs.
Register reports — Log list, entries list and individual logs can be exported as PDF and Excel.
Print & Digital — Report output formats — available in the Inspect module only; other modules use default formats.
Stage report — A report for that particular stage and its status.
Detailed report — Includes all stages of the inspection, with fails and redos.
Final report — Includes only the pass stages of the inspection.
EQC Log — All logs of an inspection (CSV).
EQC Latest Log — Only the latest state of an inspection (CSV).
EQC Count — Inspection count, checklist-wise (CSV).
EQC – QC Report (Link on Mail) — A PDF report of an inspection sent via an email link.
Instruction Detailed — A detailed log of issue activity.
Instruction Latest Log — The latest part of issue activity.
OTP (One-Time Password) — A one-time code sent to your registered mobile or email to verify identity.