Customer health check

One Customer's checklist: what is missing, area by area, worst first, each with a link to where it is fixed.

For: System AdminLast checked: 2026-11-13

Opened from a Customer's row on the Health check, or from the Health check figure at the top of the Customer's record. Only System Admins open it. Back returns to the page you came from, such as the Customer's record or the register; if you opened this page from a bookmark, an email or a new tab, it goes to the Health check register's Customers tab. The ? beside the name opens this article.

The checks run when the page opens and again with Check again; nothing is stored. The description says when they ran. Open the Customer goes to the Customer's record. An archived Customer is not checked.

The figures

  • Health — the worst there is: N blockers, else N warnings, else All OK.
  • Blockers — a flow cannot complete, or someone cannot act. When there is one, the figure is a link that jumps to the first blocker.
  • Warnings — something is likely missing or incomplete. When there is one, the figure jumps to the first warning.
  • Passed — the checks that passed, with the number of notes (worth knowing; nothing is stuck) beneath.

The areas

The checks are grouped by area, always in this order, each showing its count when folded. On arrival the area holding the first blocker opens (or, with no blocker, the one holding the first warning) and the page scrolls to that check; with nothing failing, the first area is open. An area's count reads, for example, 1 blocker · 2 warnings or All 3 checks passed. In each area, failed checks come first, the most serious first. Each says what is wrong, lists every affected Country, Project or person with its own link, and has a Fix: button to the page where it is put right. Below them, the checks that passed (Passed), and those that do not apply (Not needed, with why, such as an add-on that is switched off).

AreaWhat is checked
AdministratorsThe Customer account is active (a note while it is suspended); at least one Customer Administrator has an enabled account (blocker); one has accepted the invitation and signed in.
Countries & projectsAt least one active Country (blocker); at least one active Project; every active Project has a Contractor.
FormsA Worker compliance form is applied on every live Project; every question is reviewed by a review stage that is switched on (blocker); every stage that is on has questions to review; a Contractor Country form is applied where registration is required; each of the Customer's Countries has an Obtempera Country Default for the Contractor Country form (without one, a Contractor's declaration there holds only the platform's own questions).
WorkflowSomeone can review every stage that is switched on (blocker); someone can review Contractor Country declarations, which needs an HR Administrator of the Country (blocker); nothing is waiting where nobody can act on it (blocker). System Admins never count as reviewers.
WorkersWorkers have been added to a Project; invited Workers have started within 14 days (a note).
ContractorsThe Customer's Contractors pass their own checks (a note), with a link to the Contractors' checks for this Customer.
Add-onsTraining: courses are available. Licensing: licence requirements are set. AI assistance: the Customer's own key is set, and someone may ask the Country agents that are on. Whistleblowing: someone handles reports (blocker), and a Disclosure Administrator is appointed (Obtempera appoints the first one; the Customer's setup checklist and O.B. say to ask Obtempera). An add-on that is off reads Not needed.
MailEmail can leave the platform for this Customer (blocker): until it does, invitations, password links and review notices are not sent.

A Customer's own Administrators see the same checks for their Customer as the Setup checklist on Customer Settings.