Your organisation
Seats and tokens across your Module Six products.
Set up
Everything your organisation needs before people start using it, in order. Each step ticks itself off as it is done. Nothing is sent to anybody until the last step.
Your people
Load everyone from one sheet, or add one person at a time. This puts people on your register and builds your structure: function, department and team. It sends nothing and spends nothing.
Add your people from a sheet
One sheet for all your products. Download the template, fill in one row per person and upload it. Where they sit runs function, then department, then team, with cost centre as a budget code; anything new is created for you. The product columns say what each person gets: a Calibrate seat, a Validate login, an IPP membership (which also opens Activate study), an Educate licence, and Exam funded, where your organisation pays their exam from your exam tokens (Y, or APME, FCPM, APE or FCP for a specific pool). You check every row before anything is written, and accounts, emails, seats and tokens only happen at Send invites.
Typing rows in directly? Start with this line of column names: email,name,cost_centre,function,department,team,manager_email,job_family,role_name,employee_ref,calibrate,validate,ipp,educate,activate, then one person per line in the same order, comma-separated. The five product columns each take Y or N. For example jane@co.com,Jane Smith,London,Operations,Infrastructure,Delivery,sam@co.com,Engineering,Site Engineer,EMP-1,Y,Y,N,N,N gives Jane a Calibrate seat and a Validate login, with no IPP membership, no Educate licence and no funded exam.
Or add one person
A single new starter, or yourself, to see how it works before loading a whole workforce. While invite emails are off, which is how they start, this adds the person to your register and sends nothing. Once you switch them on in Send invites, it also creates their account and sends their set-up email straight away.
Where they sit: the same columns as the sheet. Leave them blank and the person has no position until you give them one in People.
Your competencies
The tickets, licences and qualifications you track. Add them from our library for your industry, then add your own. This is the only place they are created: the sheets in the next two steps fill them in.
Competency catalogue
Every ticket, licence and competency the register can track, whether it expires and its validity period. A change here applies straight away to everyone who holds the item, so the console shows you who it affects before it saves.
What each role needs
Say what each role must hold. Pick one job family at a time, download the sheet, put M or D against each role, and upload it. Until a role requires something, nobody in it can be short of anything.
Roles & requirements
The roles your register recognises, grouped by job family, and what each one must hold. A job family can carry a default set of products, which applies to anyone onboarded into it. A sheet column or the who-gets-what grid still wins for an individual person, so the family default is a starting point and never a ceiling. Families and roles named in a sheet are created here automatically.
Where evidence is kept
Decide this before anybody records what people hold. Either certificates and cards are uploaded and held in Validate, or they stay in your own system and Validate records the outcome and where the document is. It applies to the whole organisation.
Evidence files
This is your decision as the organisation responsible for the records. You can change it later. Nothing already recorded is lost either way.
How Validate looks after evidence files
- Where. A private file store in Western Europe, run by our hosting provider. Encrypted at rest (AES-256) and in transit (TLS). Nothing sits on laptops, shared drives or in email.
- No public links. Every download checks who is signed in first. Files download rather than open in a tab, browsers are told not to keep a copy, and no file address contains a name or a ticket type.
- Who can open them. Your admins; line managers, for their own reporting line only; anyone you ask to approve a person, while that approval waits; and the worker, for their own record. Nobody else in your organisation, and no other organisation.
- Never held. Medicals, fitness checks, DBS, BPSS, CTC, SC and DV are refused on upload, whoever tries. Only the fact of the check, its reference and its expiry are recorded.
- Checked separately. An upload verifies nothing. Somebody with authority signs each item off, and the register records who, when and how.
- Backed up nightly, encrypted the same way. A deleted file's backup is kept 30 days, then removed.
- Yours. Your organisation is the data controller and Module Six the processor, under the Data Processing Agreement. Clients you send rosters to see status only, never documents.
Keep them in your own system instead, and Validate holds only the record: what is held, its dates, who signed it off and where they checked it.
Who holds what
Download the sheet with your people and your catalogue, fill in what each person holds and when it runs out, and upload it. A column that is not in your catalogue is skipped and reported.
Register from a sheet
Load what your people hold, and keep it up to date, from one spreadsheet. Download it and it comes pre-filled with everyone already in your register, so you are editing rather than retyping. Nothing is written until you have seen the preview, and nothing here removes anybody or gives anybody a login.
Send invites
Nothing has been sent until now. When you are ready, switch invite emails on and invite: accounts are created, and everyone you gave a product gets their set-up email.
Before anything is sent: invite emails
Nothing reaches a person while this is off, which is why it starts off. Staging, reviewing and correcting all work with it off. Invite below will refuse to run until you switch it on. Expiry reminders have their own switch on this card.
One reminder per person per day, climbing one step at a time so the person always hears first. Anything already expired always reaches compliance, whichever escalation you choose.
Invite and send set-up emails
Creates an account for each prepared person you have given at least one product, grants what you ticked, and sends their set-up email. People you gave nothing stay on the register with no account and no email. Only runs when invites are on above.
To invite a few people, choose who: the People list opens on everyone not yet invited, with a tick beside each. Tick them, or tick a whole team or reporting line at once, then Invite selected.
Resend an invite
Paste emails (one per line) to resend the same set-up email. Only for people who already have an account, and only when invites are on.
Deployments
PilotOptional. Deployments lets your people put workers on a project, build a roster for a shift, send it to the company you are working for, and take another company's people onto your own projects. It stays off until you switch it on, and then only the people you give a role to can use it.
Switch Deployments on Pilot
Deployments is in pilot. It works and it is supported, and we are still shaping it with the organisations using it, so tell us what gets in the way. Switching it off later stops anybody starting new work in it; rosters already sent keep working until their own end date, so nobody you are working for loses sight of who is on site.
Kit
Optional. Small plant and tools that need checking, such as cable locators, gas detectors, survey cameras and defibrillators, and who has them. Kit is joined to the register: nobody can accept kit they are not competent to use, and kit that is out of check cannot be handed to anybody. People pass kit to each other and return it to the store by scanning the QR on its label.
Stores and store managers
A store is where kit lives when nobody has it, such as a depot. Store managers add kit, record its checks, issue it, take returns in, and are the only people who can recall or reassign kit without the holder accepting. Each manager runs only the stores you give them.
Kinds of kit
Each kind says which ticket a holder needs and which checks it needs, and how often. Start from the standard list and change the intervals to your manufacturer's figures or your own policy.
Your kinds of kit
Add from the standard list
Add your own
Hired kit
Optional. Bring kit you hire in onto the same register as your own, held to the same tickets and checks. Each hire names its supplier, its project and one person accountable for getting it back, with its dates and costs. That person is reminded two working days before it is due off hire and on the day, and every working day it is over; their line manager is told from one working day over. Store managers see costs and overruns by project. Switching it off hides hired kit and stops the reminders; nothing is deleted.
Load kit from a sheet
One row per item: its asset number, kind, store, and up to four checks with the date each was last done. Stores and kinds must be set up above first; a row naming one that is not is refused rather than creating it. Checks loaded from a sheet count only once a store manager has confirmed them, so loaded kit reads out of check until then.
Authority audits
Optional. Each month people are drawn at random and a named auditor checks that the evidence on file supports the Authority to Work they hold. Each department and function has a head, who answers for it, and an auditor, who does the audits: the head, unless you name somebody to do them on the head's behalf. Departments are drawn first; a function's auditor then gets people from across the function who were not drawn for their department that month. Nobody audits their own record or anybody whose authority they approved. Auditors are emailed when they are given audits, halfway to the due date, on the due date and when overdue, and the head is copied on the last two. An audit records what was found and never changes the record.
Who audits each department and function
The head and auditor need a login. Leave the auditor as the head unless somebody audits on their behalf. A number of 0 draws nobody from that group.
The draw runs on the first of each month. To draw this month straight away, or to audit a whole department at once, open Audits in Validate.
Calibrate
Competency and CPD across your organisation. Open Calibrate for a person's full profile and evidence.
People
Everyone on a Calibrate seat: level, onboarding, CPD, and open validation gaps. Click a gap count to see what's outstanding. Nudge sends one reminder email.
Competency heatmap
Your organisation's average validated level in each competency area. Built from confirmed assessments only, so it reflects what reviewers have signed off, not self-ratings.
Engagement & adoption
Who is actually using what you bought: recent activity, dormant people, CPD pace and reviewer workload. Nudge sends a one-off re-engagement email.
Find people by capability
Who is validated at a level in an area — for staffing a project or finding a mentor. Confirmed levels only.
Position against role target
Every person against their role's target level, area by area, on confirmed levels: below, at and above, including areas the role does not require. Download as CSV for every area of every person.
Organisation report
A report to send to your directors: how each line manager and department is doing on reviews, development plans, CPD and work waiting for them, then competency, CPD and evidence across the organisation. The same figures as this console. Opens print-ready; save as PDF from the print dialog.
Organisation settings
Defaults that apply to everyone: the annual CPD target, how often competency reviews come round, and how long a validation can sit before a reminder goes out.
IPP membership
Company-issued membership tokens. Each is redeemed once by a person for their own 12-month access. Share a code to allocate it, and track who has redeemed it.
Your token pools
To issue membership: copy a code and send it to the person; they enter it at redeem.modulesix.io to claim their 12-month access. Copy link gives you a ready-to-send link that opens redemption with the code already filled in. Click a redeemed count to see who has claimed. Buy more to top a pool up.
Validate
Authority to Work oversight and provisioning. The full operational register lives in Validate.
Your catalogue, roles and requirements, and the register sheet are in Set up, with adding people and invites. This page is for running the register day to day.
Worklist
What's expired, expiring or missing across the register. Click a person to open them in the full register.
Annual review
How long an Authority to Work runs before the person is looked at again.
Each ticket keeps its own expiry, and the register already stops anyone whose ticket has lapsed. This is different: it is when their manager looks at the whole person again and re-approves them. It counts from each person's own approval, so reviews fall across the year. An approver can bring a date forward, with a reason, but never past this period.
A change applies to approvals from now on. Anyone already approved keeps the date they were given. Where expiry reminders are on, line managers are emailed 60 and 30 days before a review is due, and you are told if one lapses.
Document control
Who logs the reference once an Authority to Work is fully approved.
Nobody sends an approval to document control. When the last approver signs, it lands in the queue of whoever does this job, and they log the reference from your own document system against it. That reference is what appears on the person's authority record.
They need a login here, which costs no Validate licence. Leave it blank and completed approvals wait for an administrator to log the reference, which is right for a small organisation and a bottleneck in a large one.
Photographs
Whether your register holds an identification photograph of each person.
A record says a person is cleared. A photograph is what lets somebody at a gate check that the person in front of them is the one on the record, which is the half a borrowed card defeats. It is off until you switch it on, because holding photographs of your workforce is your decision and not ours.
Access sets
A named set of tickets that together allow one kind of access, such as Trackside or Offshore. A role carries a set beside its requirements, and each person's register row, card and wallet pass show whether they hold it, with the date it runs out. A set never changes whether someone is authorised to work, only whether they have that access.
Activate
Exam sittings you've bought to allocate, and who has redeemed them.
Exam tokens
To issue an exam: copy a code and send it to the person; they enter it at redeem.modulesix.io to claim their exam access. Copy link gives you a ready-to-send link that opens redemption with the code already filled in. Click a redeemed count to see who has claimed.
Educate
Course library licences and tokens. Give a person Educate from People (Edit) or from a sheet on Overview, drawn from your licences first and then your tokens, or give a licence when you approve a join request.
Licences and tokens
Licences are given to named people from People. A token is a place someone claims with a code.
People
Your roster: who is here, what they hold, where they sit in the structure, and requests to join. Tick people in the list to invite them or move them to another role or team. Loading everyone from a sheet lives in Set up.
People
Everyone in your organisation, once each, with what your sheet says about them: where they sit, their line manager, their role, what they have been given and where they are up to. Pick a group of columns to compare people across, filter to who is waiting on you, and tick people to invite them or to move them to another role, team or department together. Edit works for everybody, with or without a login.
Organisation structure
Your management line runs function, then department, then team. Use only the levels you need: a department with no function above it sits at the top and that is a position, not a gap. Cost centres are budget codes listed separately, because one can cut across several teams. A group can only be removed once nobody is in it, so move its people first or re-upload your sheet.
Requests to join
People asking to join your organisation. Approve opens a choice of what to give them: a Calibrate seat, the Validate register with a role, an Educate licence, an IPP Affiliate membership or an employer-funded exam sitting. Each draws on what your organisation holds, and you are told if there is none free.
Recent activity
Every change to your people in the last 30 days: who arrived or left, and who changed somebody's details, role or products. There is no undo, so this is the record of what was done and by whom.