Training

The certification register: every worker's cards and certificates, their expiry dates, and who is not compliant for the role they hold or the site they are on. It lands on Compliance Gaps — who to chase — rather than the full matrix, and the strip above the tabs names what needs doing now. A certificate is recorded from the file itself, read by Saral and checked by a person; a course is booked outside and tracked inside. A new account starts with the standard construction catalogue (CSCS, first aid, and so on), which is yours to edit.

You enter

A certificate: drop the file (PDF or image) on Record certificate; Saral reads the worker, the course, the dates and the card number for you to check. Or link a SharePoint folder and let the sweep find them.
A certificate type: its validity in months, its category, which worker types and roles it is required for, and whether the law requires the employer to provide it.
A booking on the Training plan — the course, who goes, the date, the provider and who pays (the company, a grant, or the worker themselves) — and your verdict on each uploaded certificate in To check: verify, reject, or change its type.

Saral fills in

Each worker's verdict — compliant, expiring, expired or missing — from what each certificate type is required of their worker type, their role and the site they were last seen on, with the reason beside it.
The matrix, the expiry runway for the next twelve months, the renewals due within the chase horizon, and site coverage: who on each live site holds in-date supervision and first-aid cards.
A worker's own upload from their portal, and a dispute they raise on a certificate filed in their name, both queued in To check with the file beside the record.
Likely duplicates among the certificate types, suggested for a merge that a person decides.

It produces

Who to chase, by certificate or by worker, and the booking that fixes it; a competency pack per site for the principal contractor.
The training plan against the year's budget and grant funding; each worker's certificate profile with the file opened on a short-lived link.

What this page is for

A construction workforce is only as compliant as its weakest card, and the question somebody opens this register with is not what does everyone hold but who do I need to chase. The page is built around that: it lands on Compliance Gaps, the strip above the tabs says what needs doing now, and every verdict carries its reason — required for a Site Manager, required on this site, required of every CIS worker. A worker is compliant because an in-date certificate is on file, never because somebody ticked a box; a certificate counts once a person has checked it against the file. The matrix, renewals, site coverage and the plan are the same facts read for different jobs.

Recording a certificate from the file

Record certificate starts with the file. Drop the PDF or photo and Saral reads the worker's name, the course, the issue and expiry dates and the card number, fills the form, and flags anything it was unsure of; you check and save. A certificate that already exists is saved as a duplicate rather than refused. Link SharePoint folder points the sweep at a folder of certificates, and the leftovers it could not place land in To check. Workers upload from their own portal too, and can dispute a certificate filed in their name — not mine, wrong dates, wrong course — which puts it back in the queue in their words. A certificate's file is opened on a short-lived link and never a public one.

What is required, and of whom

Requirements come from three places and one resolver, and every one is set by a person: the certificate type says which worker types must hold it; a job role's list, set on Compliance Gaps → By role, says what its holders need; a project's own list says what is required on that site, and a site that states it requires a CSCS card requires one of everyone who attends it. Industry suggestions are offered beside the role list and never applied by themselves. The same resolver feeds the matrix's red rings, the Compliance Gaps verdicts and the worker's profile, so they can never disagree. The expiry runway reads the current certificates forward twelve months, and Site coverage asks a narrower question — on each live site, who holds in-date supervision and first-aid cards — and prints a competency pack for the principal contractor.

Book outside, track inside

Saral does not deliver training. A course is booked with a provider and delivered by them; the Training plan holds the booking — course, people, date, provider, cost — against the year's budget and any grant funding, and records who pays: the company, a grant, or the worker who booked and paid themselves. Book from a gap, from a renewal, from a runway month or from a worker's portal request; when the certificate comes back it is recorded against the booking and the gap closes. Training the law requires the employer to provide is flagged on the type, and who pays for it is a setting.

Where the settings live

HR → Settings → Training owns the training budget per company per financial year, the automatic training plan, and who pays for statutory training. The certificate types themselves — validity, category, who must hold them — are edited behind the gear on this page, because they are the register's own set-up. A job role's required certificates are set on this page under Compliance Gaps → By role; a site's own list is set on the project. Expiry reminders to the worker and the office are on HR → Settings → Compliance & Documents.

Next screen: /hr/safety

Not what you needed? Inside Saral, ask Kuku (Alt+K) — if it cannot answer, “Ask a human” sends the question to Saral support with the chat attached.