Risk & Reports

The risk dashboard and register, reports on the compliance form answers, your rules and alerts, and the reference data.

For: Customer Administrator · Contractor Administrator · HR Administrator · EHS Administrator · Licence Reviewer · Report Viewer · System AdminLast checked: 2026-11-12Open this page in Obtempera ↗

Risk & Reports is in the top bar (under Oversight when you have Audits too), where Reporting & Risk is switched on for the Customer. The ? beside the page title opens this article. The tabs you see depend on your role:

  • Customer Administrator: Dashboard, Risk register, Scorecards, Insights, Reports, Rules & alerts and My alerts.
  • Contractor Administrator: Dashboard, Risk register, Scorecards, Insights, Reports and My alerts, over its own Workers and its subcontractors'.
  • HR, EHS and Licence Reviewers: Dashboard, Risk register and My alerts, over the Workers they review.
  • Report Viewer: Dashboard, Risk register, Scorecards, Insights, Reports and My alerts, over what the administrator it reads for sees (the whole Customer, or one Contractor and its subcontractors). It only reads: it never responds to, deals with, assigns or resolves a signal, sets no corrective action and has no Rules & alerts. It can run and export reports and the register, download a signal's evidence pack, and save its own reports and have them emailed. Wage figures are never shown to it.
  • System Admin: every tab, Reference data included; it reads and reports, but does not respond to, deal with or resolve a signal.

Someone who may read reports but not the register opens straight on Reports. A link to a tab your role does not have (from a colleague with another role, say) opens your first tab instead, with a line saying so.

Dashboard

Where to look first, over the signals you may see:

  • Headline figures: open Red and Amber, overdue, new in 30 days, median days to resolve, and the share resolved on time.
  • How long it has been open: the open signals in four bands (0–7, 8–30, 31–90 and over 90 days).
  • Where the open signals are: a table by Contractor, Project or Country and area. Choose a number to open the register filtered to it.
  • Signals opened and resolved, by week: the last 12 weeks.
  • Contractors to look at first: a score from 0 to 100, its 12-week trend, and how many of the Contractor's subcontractors also have signals.
  • Forced-labour indicators: the ILO indicators the open signals point to, as counts only.

Risk register

  • Filter: Red or Amber, Area, Status (Open and being dealt with to start with, each status, or Everything), Overdue only, Assigned to me, or Customer.
  • Search by Worker, Project or reference.
  • Sort: Red first, highest score, due soonest or newest.
  • Open shows a signal in a drawer: what raised it, its score (severity × how sure the evidence is), its due date and its history.
  • Add response (the Worker's Contractor, or the Customer): write what has been done and attach the evidence.
  • I'll deal with it, Resolve or Accept the risk (the Customer): resolving and accepting need a note.
    • Give it to a colleague and Assign hands the signal to one of the Customer's people who may deal with it. They are told in their notifications; it shows under Assigned to me in the register and in Assigned to you on their Today page. A signal already being dealt with can be handed on the same way; the history says who gave it to whom.
    • A resolved signal reopens if its answers still say the same.
    • An accepted one comes back for review after the period the Customer set.
    • A signal its answers no longer raise is Cleared.
  • Corrective actions (in the drawer): with Add an action the Customer sets what is to be done, the evidence that will show it done, the due date and who does it (the Worker's Contractor, or the Customer), then Set the action.
    • The owner writes what was done or attaches a file, and presses Submit evidence; the Customer presses Verify, or Return for more saying what is missing.
    • While a file sent with the evidence is still being checked for viruses, nobody can open it, so Verify waits: the drawer reads The evidence is still being checked. Return for more stays available.
    • The Customer can Withdraw an action that is no longer needed, saying why.
    • A signal is not resolved while one of its actions is open: verify or withdraw the action first, or accept the risk.
    • On a signal from what Workers said, the actions are always the Customer's own.
    • The Contractor is emailed when an action is set for it or returned, the Customer when the Contractor's evidence arrives. The emails give the signal's reference, area, Project and the due date, and never a Worker's name, an answer or the action's text.
  • Download the evidence pack (PDF) (in the drawer): one signal (what raised it, its actions, history and the documents on file with their fingerprints) for an auditor or an authority. The evidence pack and the due-diligence report carry the Customer's logo top-left (when it has one in Customer Settings, Branding) and Obtempera's mark top-right on every page.
  • Export icon (top right of the table): the register as it is filtered on screen.
  • The evidence pack and the export icon are there for those who may export reports: the Customer's and Contractor's Administrators, a Report Viewer and System Admin, not HR, EHS or Licence Reviewers.
  • Every download is written to the audit trail.

Scorecards

Where each Contractor stands among the Customer's own Contractors, 1st being the lowest risk: its score and 12-week trend, open and overdue signals, how quickly signals were resolved over the last 12 months, and its corrective actions. A Contractor sees its own scorecard and its subcontractors', never another Contractor's; the position still counts every Contractor of the Customer. Scores come from the compliance forms and the records; what Workers said is never counted here.

Insights

The workforce as its approved compliance form answers describe it, over the Workers you may report on. Each Worker counts once, however many Projects they are on. Filter by Customer, Project or Contractor.

  • Hourly wage by job category (Customer Administrators and System Admin only): lowest, middle half, median and highest agreed base hourly wage for each job category, plus the wage ranges chosen on the form. Nobody else sees a wage figure or a wage range here.
  • Passport issuing country: a world map, darker where more Workers hold that country's passport. Choose a country, on the map or in the table, for its right-to-work picture: EU/EEA or Swiss citizenship, work permits (valid, expiring within 30 days, expired), Schengen visas, posting, A1 certificates and open immigration signals.
  • The workforce: the mix of posting classification, pay group, average weekly hours, how the work is paid, wage range and age band.

A group of fewer than five Workers is never shown as a number: it reads fewer than 5, a job category with fewer than five wages shows no wage figures, and a passport country with fewer than five Workers shows nothing more than that. So small a group would name the people in it. Wages are in the currency of the Projects' country; where the Projects in view are in countries with different currencies, the chart says local currency.

Reports

Choose the report at the top of the tab: Form answers, Time to approve, People per role or Expiring. A Contractor Administrator sees each one over its own Workers and its subcontractors', never a sibling Contractor's or the one above it.

Saved, shared and emailed reports

Every report here, and the Compliance Matrix as filtered, can be saved. The Saved reports bar sits above each report.

  • Save as: keep the report's filters under a name; choose it later under Saved reports and Open it. Time to approve keeps the length of its period, ending on the day it is opened or sent (the last 30 days stays the last 30).
  • Share or email to others: only people whose own access allows that report and what it covers are offered. Someone at the Customer is offered everyone in the Customer; someone at a Contractor is offered their own chain plus the Customer: the Customer's own staff, and the people of their own company and of the Contractors below it, never a Contractor above or beside them. Share with lets them open it from their own Saved reports (Shared with you), each seeing only what they may see; they cannot change it, but Copy to my reports makes their own copy.
  • Save as and Save refuse a report that asks for more than your own access allows (another Customer, a Contractor beside or above yours, a Project you cannot see): This report asks for more than your own access allows.
  • Email it: daily, weekly (Mondays) or monthly (the 1st), to you and the people under Email it to. The email attaches the report: a CSV, or a PDF for the Compliance Matrix. Each person's copy is built with that person's own access, never yours. Someone who has since lost access is skipped, and the skip is recorded; they are emailed once to say the report was not sent to them, until the report is changed. A file over 5 MB is not attached: the email says so and links to the report. Every email and attachment is written to the audit trail, and each Worker it names sees it in their copy of their data.
  • Remove takes a saved report out of your list; Undo brings it straight back, or choose it later under Removed reports and Restore it, with a new name if its old one is now taken.
  • Start from a template: Obtempera's ready-made reports (for example Waiting for review over 7 days, Time to approve, last 30 days, by Contractor, People per role on a Project, Non-compliant Workers by Contractor, Expiring in the next 30 days). Use template copies it into your saved reports and opens it; the template itself does not change. System Admin keeps the templates, on Report templates in Platform Admin.

Time to approve

How long submissions took to be decided, and what is waiting for a reviewer now.

  • Decided from / To (the last 30 days to start with), Customer, Project and Contractor, then Run report.
  • Approved or returned is what the reviewers decided, not what happened since: a record approved whose document, licence or training later expired, or that was later paused, still counts as approved.
  • Decided: how many submissions were decided in the range (approved and returned), the median time from the Worker submitting to the final decision, and the 90th percentile (9 in 10 were decided within it). Then the same by HR, EHS and Licence stage, by Project and by Contractor.
  • Waiting for review now: every record waiting for a reviewer, whatever the dates, in four bands (under 1 day, 1 to 3, 3 to 7, over 7 days) and by stage, the longest waiting first.
  • Approximate figures: each Worker's record keeps only the dates of its latest submission, and a resubmission overwrites them, so a record sent back and resubmitted counts once, for its latest round. The page says so; a later review history will make the figures exact.
  • Export icons: the figures (no names), and the list of records waiting (by name). Each export is written to the audit trail, and the waiting list in each named Worker's copy of their data.

Expiring

Worker documents with an expiry date, licences (where Licensing is on) and the training the Projects require (where Training is on) that run out soon or already have, by Contractor and by Project.

  • Expiring in the next (30 days to start with) and and expired in the last (none to start with) set the period; What narrows it to documents, licences or training. The period is relative, so a saved or emailed report is always about the days ahead of the day it runs.
  • It reads the same records the expiry reminders read, and Expired is read where the Worker is placed, as the Worker's status reads it. A licence belongs to the Worker, so it counts under every Project they are on.
  • A Contractor Administrator sees its own Workers and its subcontractors', never a sibling Contractor's. The export icon downloads every item with the Worker's name; it is recorded in the audit trail and in each named Worker's copy of their data. Obtempera's template Expiring in the next 30 days starts you off.

People per role

How many Workers on active placements hold each Job Category at each Contractor, down the supply chain.

  • Project, Country (and Customer) narrow it. Contractors run across in chain order, each subcontractor indented under its parent, with its tier. Tiers are per Project: choose a Project for its exact chain.
  • A Worker's Job Category is the one set on the placement, otherwise their answer to the Job Category question. Answer not in the Job Category list and Not given are shown as rows of their own.
  • Choose a count to open the Workers register on exactly those Workers (Job Category, Contractor, Project and Country, active placements only).
  • The export icon downloads the table (counts only) and records it in the audit trail.

Form answers

Choose the questions (or none, for a plain list of the placements and their status), set the filters and Run report. The questions are Obtempera's and your Customer's own compliance form questions (marked "own question"): numbers, dates, yes/no and choices, never free text or documents. The export icon above the results downloads it and records the export in the audit trail.

  • Pay: a Worker's pay figures (wage, rate, wage range) are shown to the Customer Administrator and System Admin only. Others are not offered those questions; where a row's pay is not theirs to see, it reads Shown to the Customer's administrators only.
  • Sensitive answers: identity numbers, date of birth, nationality and health answers show only to those who may open that Worker's files; others read Shown to those who may open this Worker's files. Each export is also recorded against every Worker it names, and shows in that Worker's copy of their data.
  • Report settings (Customer Administrators and System Admin): Obtempera sets which questions can be reported on and which are sensitive. For the Customer's own Workers you may take a question out of reports (it then reads Not reported for this Customer) or mark it sensitive. You cannot loosen Obtempera's setting.
  • Annual due-diligence report (Customer Administrators and System Admin): choose the Year (this year or one of the two before) and Download PDF: the scope, the risks found by area, the forced-labour indicators, the action taken and how well it worked, mapped to the UK Modern Slavery Act, the Norwegian Transparency Act and the CSDDD. It names no Worker. The statement itself is yours to write and approve. Its list of the checks Obtempera ran leaves out the two hours checks until a legal hours limit is confirmed for one of your Countries.

Rules & alerts (Customer Administrators and System Admin)

Where Reporting & Risk is switched off for the Customer, this tab says so: Nobody can change these settings until it is switched on; what was saved is kept.

  • Risk appetite: how soon a Red and an Amber are dealt with, how long an accepted risk stands, and how long a resolved signal still counts in a Contractor's score.
  • Rules: switch each one on or off and set its limit. Rules that look for harm that cannot be undone stay on.
    • Work permit expiring or expired and ID document expiring or expired read the expiry date kept with the approved permit or ID document on the form (and the older expiry-date question, where a form still asks it).
    • Hours over the legal limit and The Worker says they work over the legal limit read Not active until Obtempera confirms a legal hours limit for one of your Countries: until then they cannot run.
  • Collective agreements: which agreement's minimum rates the pay rule reads in each Country, or on a Project that differs.
    • If Obtempera takes an agreement you chose out of use, your Customer Administrators are emailed, and this section names the Country or Project and the agreement, with is no longer in use: choose another. Wages there are not checked until you choose another; your choice is kept until you do.
  • Alerts: who hears about which signals, and how.
    • Each rule chooses Red, Amber or both; an area; Projects or Countries; who is told; and straight away, daily or weekly.
    • Nobody is ever told about a signal they may not open.
    • Keep at least one rule for Red. A Red is never silent: any Red that no rule catches (another area, Project or Country, or an audience nobody fills) goes to the Customer's Administrators straight away.

My alerts

How an Amber reaches you: as the Customer set it, in a daily or weekly digest, or only under the bell. A Red always comes as the Customer's rules say. Every signal you are told about also shows under the bell in the top bar. While Reporting & Risk is switched off for the Customer, its signals leave the bell; they come back if it is switched on again.

Reference data (System Admin)

The collective agreements' minimum rates by pay group and each Country's working-time limit, read from the country agents' documents with their page.

  • Add figures one at a time, or import a CSV laid out like the agents' wage tables.
  • Figures start as drafts; only confirmed figures are read by the rules.
  • A confirmed figure is ended, never changed, so each signal can still say which figure it was raised on.
  • A save, confirm or end answers at once. The rules then run again for every Customer with Reporting & Risk on, and the signals follow within about 15 minutes.