The Worker record

One Worker: their details, Project assignments, licences, employment status, documents, training and requests.

For: Contractor Administrator · Customer Administrator · HR Administrator · EHS Administrator · Licence Reviewer · Report Viewer · System AdminLast checked: 2026-11-12

Who opens it

The Worker's own Contractor's administrators (and those of the Contractors above it), the Customer's Administrators, the HR and EHS Administrators and Licence Reviewers who review the Worker, Report Viewers and System Admin. A Licence Reviewer opens it from their queue: they have no Worker register.

Back (‹, beside the Worker's name) returns to the page you came from, or to Workers when there is none. The ? beside the page title opens this article.

Top of the record

The Worker's name and email (the email only for those who may see it, below), their Contractor and Worker Status. Edit login account opens the Worker's login account on the Users page; it shows once they have an account, and only to someone who may open it there. Below are counts of their Assignments, Projects, Countries and Project Access (Projects they are ready for), and whether their Portal Account is linked.

Worker Details

First name, Last name, Email, Status, Customer and Contractor. Change the name, email or status and press Save Worker. Anyone who may not change the record sees it read-only, with a note that changes are made by the Worker's own Contractor's administrators. The email is fixed once the Worker has an account or a Project assignment, because it identifies them; contact support to have it corrected.

Beside Save Worker, for the Worker's own Contractor Administrator, a Customer Administrator for the Customer's own workforce, and System Admin:

  • Assign to Project places the Worker on another Project of their own Contractor, alongside the ones they are on: choose the Project, then Create assignment. A Country where the Contractor's declaration is not approved yet is listed but locked, with the reason.
  • Transfer Worker moves an existing assignment: choose the Current Project and the Destination Project, then Confirm Transfer. The old assignment becomes history; approved documents that can be reused go with them and are reviewed under the new Project's reviews. A System Admin can also transfer to another Contractor or Country: moving a Worker between Contractors is a System Admin permission of its own (Transfer Contractor), named in the audit trail of every such move. It needs an assignment that is still active. Transferring to a site the Worker has left takes the ended placement up again (as adding them to that Project again does): it starts over as a new placement would.

There is no Delete button. To retire a record, set Status to Archived and save (see below).

Sections, in order

Most sections open and close; one with nothing to show, or for an add-on the Customer does not use, is left out.

  • Project Assignments — every Project they are on, with its Compliance status, Training and Project access (READY or NOT READY). The Training chip is red while a required course is still to do (Required, Enrolment pending, In progress, Action required, or Sync error when the training system could not confirm it), green once Training complete, and grey when nothing is outstanding or nothing can start yet (Not required, Skipped, or Waiting for compliance until every review has passed). Open a row for the Customer, the Contractor, Open Project, Open compliance record, the dates it was created, submitted and reviewed, how many requirements are approved, the latest invitation, and (for those who may) Suspend on this Project or Lift suspension, and End assignment.
  • Licences — the cards and certificates they hold, and Record a licence (where the Customer uses Licensing).
  • Status assessments — CIS, IR35 and RCT assessments, every one kept as the Worker's history (where the Customer uses Employment Status).
  • Risk signals — what the Reporting & Risk rules found about this Worker, Red or Amber, with Open for each. A signal never changes the compliance status.
  • About the person — what the Worker keeps under My Details, read-only, with their answers to any further questions Obtempera asks there.
  • More about the Worker — the answers to the questions Obtempera added to Add a Worker, where it has. Whoever may change the Worker record can Answer the questions (a Worker imported, or added before the questions were) or Change the answers; the form is the current one, checked in full. The Worker is not shown these answers on screen, but they and their files are in the Worker's copy of their data.
  • Requests — what the Worker has asked from their portal (see below).
  • Worker Portal Account — whether a login account is linked and active, how many Contractor records the person has, and the Privacy notice: signed (with the date, the notice version and the name they signed as), New wording awaiting signature, Not yet signed or No notice published. A Contractor Administrator is not shown the name it was signed with.
  • Completed Training — where the Customer uses Training.
  • Pulse Surveys — surveys sent to the Worker from an audit or from Communications, and whether they took part. An anonymous survey records that they took part, never their answers.

Basic data and read-only roles

EHS Administrators, Licence Reviewers and Report Viewers see basic Worker data only: the Worker's name, employer, Projects and Job Category. The email is left out at the top and under Worker Details, every other My Details answer is left out of About the person altogether, and no My Details file opens. Someone who is HR as well as EHS reads the record as HR does.

A Report Viewer reads the record and changes nothing: there is no Save Worker and no Open compliance record on an assignment, and the record's actions are not offered to them.

The compliance record

Open compliance record on an assignment opens the Worker's form for that Project; Open full page shows it on a page of its own (see Add a Worker). Its header shows the status and, where you may use them:

  • Reset Password and Reset two-step sign-in, once the Worker has accepted their invitation. Resetting two-step sign-in removes their authenticator set-up, backup codes and remembered browsers, after a confirmation. The reset is recorded in the audit log of each Customer the Worker is placed with.
  • Revoke Invitation, while an invitation is waiting to be accepted.

You can fill in the record and upload documents on the Worker's behalf: Save progress, Send remainder to Worker (saves, then emails them a portal invitation to finish it; a Worker who already has an account is sent nothing, and the page says they can sign in) and Submit worker to HR. Declarations and acknowledgements are the one exception: only the Worker can make them, in their own portal. You can submit the record once they have; until then the submission names each one still waiting for the Worker.

A System Admin opens a Worker's documents only in a break-glass window: give a reason, then Open break-glass access. The reason is recorded in the audit trail and the window closes after 30 minutes. While it is open, every page shows Break-glass open until with its end time and a Close now button that ends it early. The window covers evidence anywhere on the platform, not just this record.

Requests

What the Worker has asked from their portal: No longer on this Project, Leaving Obtempera, Removal of my data (GDPR) or A copy of my data (GDPR). Mark actioned records what you did, in a note the Worker sees and is emailed. Actioning No longer on this Project ends that assignment; actioning Leaving Obtempera ends every assignment of this record. A Worker can never action their own request, and those who may not action it are told who deals with it.

  • A copy of their data: Release the copy lets the Worker download, for 30 days, what they gave and the decisions they were shown; never other people's notes, audit working papers, risk signals or confidential reports.
  • Removal of their data: record what was removed and what is kept under which retention rule. Erase now deletes their answers, documents, My Details and Privacy Notice signatures at this employer at once and replaces their name and email with a fingerprint; type ERASE to confirm. Their licences and training records keep only an anonymous stub (which licence or course, held from and to), so your counts and audits still add up: card numbers, notes, card images, evidence and quiz answers go. It cannot be undone, and their assignments must have ended first. The audit trail is kept. Their login closes once their records are erased, unless they still have another Worker record or another role in Obtempera; they are told the outcome by email. Besides whoever actions the Worker's requests, the Customer's Administrators may Erase now an external Contractor's Worker: a Worker record holds only your Customer's placements, answers and documents, so what that Contractor holds for another Customer is untouched.

Both must be answered within one month under the GDPR: an open one shows Respond by the date, or Overdue since it. If it is still open after three weeks, the administrators it went to are reminded; if it is still open on the due date, the Contractor's and the Customer's Administrators and Obtempera are emailed.

Record a removal request is for a Worker who asked outside Obtempera, by phone, letter, email or in person. The Customer's Administrators (and Obtempera) record who asked, how, the day they asked and an optional note; a Contractor's administrators cannot. It is raised on each of the person's records at your Customer, never another Customer's, and then follows exactly the path above, with the month counted from the day they asked. Every open request is listed on GDPR requests.

View as

A System Admin can press View Obtempera as this user under Worker Portal Account to see the product as the Worker does, once they have an active account. It needs a written reason and a time window. It is read-only: nothing can be changed, sent or submitted as them, any attempt is refused and recorded against the administrator, and evidence files still need the administrator's own break-glass window.

Suspending a Worker on one Project

A Customer Administrator, or the Worker's own Contractor Administrator, can open an assignment and Suspend on this Project, giving a written reason. While suspended the Worker is red on that Project and still counted everywhere it is counted (the Project, the Compliance Matrix, the Customer and Contractor pages, the registers and the billing count), not cleared for site and cannot submit; their other Projects are not affected. Lift suspension puts the record back exactly where it was. Both are recorded in the audit trail.

Ending an assignment

From the assignment, End assignment (they are no longer on that site), with an optional reason. A Customer Administrator can end any Worker's assignment on the Customer's Projects; a Contractor Administrator their own Workers'. An ended assignment is off the site: the Worker is no longer cleared for it and its reminders stop. The record stays readable, and the Worker keeps their portal to see their own history. It cannot be undone; add them to the Project again if they return. To move them to another Project instead, use Transfer Worker.

Setting the Worker's status to Inactive, Left contractor or Archived ends every assignment they have in the same way; the Worker keeps their portal. Setting it to Suspended suspends each assignment instead, and setting it back to Active lifts exactly those. An archived Worker stays on the register (Filters › Status › Archived): set them back to Active to restore the record, or add them again on Add a Worker without a Project. Their ended assignments stay ended.

If the Worker's Contractor is Suspended, each of the Worker's assignments is suspended with the reason "Contractor suspended" (red, not cleared for site); they cannot submit and are sent no emails, and nobody at that Contractor can sign in. When the Contractor is Active again, exactly those suspensions are lifted; one an administrator set on its own stays. If the Contractor is Archived, the Worker's assignments end. Every change is in the audit trail. If the Project is Suspended, Completed or Archived, nothing on it can be submitted or reviewed and no new Workers join it.

Under chain review, an assignment waiting with a Contractor that has nobody left to review its stage shows Nobody can review, naming the Contractor and that its Contractor Administrator must give someone the reviewer role on the Users page.

When something lapses

A Compliant (or Training outstanding) Worker whose required document expires or can no longer be used (the malware scan blocked its file, or it has no expiry date its question needs), whose required licence is no longer met (expired, withdrawn, or only an unchecked or returned replacement: a checked licence that is corrected, given a new image or has its check undone waits for its check again), or whose required training expires, becomes Not compliant (red, not cleared for site) on that Project; the Worker sees Not compliant – renewal needed. Only the replacement is reviewed: the document renewal or new copy under Document Review, the licence check under Licensing review, or the course passed again (it is open to retake in the Worker's Training tab). Once nothing lapsed remains they return to where they were (Compliant, or Training outstanding), at once. The Worker Portal tells them why and where to put it right. A Compliant Worker with a course to do that has not lapsed (the Customer reset their progress, or the Project now requires a course they have not passed) is Training outstanding (red, not cleared for site) until it is passed, then Compliant again; the record shows who made the change. A required document, licence or course still valid but inside its warning window leaves them Compliant and amber, still cleared for site, flagged renewal due; an optional document never changes their status. A Privacy Notice they have not signed yet is a notice to sign flag; it does not change their colour.