Staff and contractor onboarding, step by step.

Each person you onboard gets their own link. They open it, work through what you have asked for, and can come back later to pick up where they left off. No account to create, no password, and it works on a phone.

• One private link per person, sent by email or shared however you like
• No accounts, no passwords, nothing to install
• Part-finished portals save, so nobody starts over
• Built for a phone, because that is where it gets filled in

Build the list yourself: file uploads, short and long text, dropdowns, multi-select questions, dates, PDFs to sign, section headings and sign-offs, ordered the way you want people to work through them. Any request can carry a document or link to read first.

• File uploads for insurance certificates, licenses, tickets and IDs
• Text, single-select and multi-select questions
• Date questions from the phone’s date picker, which can be limited to today or earlier (a date of birth) or today or later (a start date)
• PDFs to sign: upload a contract, policy or NDA and each person signs it on their phone, with a signed copy for you both
• Section headings to break a long portal into readable blocks
• Attach the policy, the map or the PPE photo to the request itself, from an upload or your files library
• Mark anything required, so nothing arrives half finished
• Mark tax file numbers, bank details and ID as sensitive: stored encrypted, masked for your team, visible only to admins, with every view logged
• Save the set as a request pack and reuse it across everyone in a role

Build the list once as a request pack, then add it to a portal in one click. A pack per kind of person you bring on: contractor, new starter, driver, stallholder. Or start from a ready-made staff or contractor pack for your country.

• Ready-made staff and contractor packs for Australia, New Zealand, the UK and the US, with the official tax forms linked
• Certificates and business numbers in a starter pack save to the person’s record, so they count on every portal
• Pick a pack on a portal and untick the asks that portal does not need before they go on
• Up to 100 packs, with up to 100 asks in each
• Every kind of ask, fully configured, including its reference document
• Drag to set the order people work through them in
• A pack is a starting position, so editing it later leaves finished portals alone
• Task asks keep reading their steps from the workflow, so one correction still fixes every portal

Not everything you need back is a file. A Task request is a checklist the person ticks off as they go: complete the induction, watch the safety video, walk the site. Build it from one of your saved workflows and the written procedure comes with it.

• Tasks with their own steps underneath, ticked off one at a time
• Add from a saved workflow, or type a one-off
• Step wording is read live from the workflow, so one correction fixes every portal using it
• What a step said is snapshotted the moment it is ticked
• Still one line on your dashboard, however many steps sit inside it

Gate a whole section behind an earlier answer. The portal asks a driver for their license and vehicle details, and never shows those questions to anyone else. One portal, a different path per person.

• Show or hide a group of requests based on an earlier answer
• Target a section at named people as well as by answer
• One portal covers several roles, instead of one portal per role
• Shorter portals get finished

Policies, agreements, waivers and site inductions go out to read and sign online. Every version of the wording is kept, and each acceptance is pinned to the version that person actually saw.

• Read and sign in the portal, with no printing or scanning
• Versioned terms library, so you know which wording was accepted
• Ask for a typed name, a drawn signature, or neither
• Upload a contract or policy PDF for each person to sign, and download their signed copy
• Download any version as a PDF, and report on every acceptance by date
• Dated record kept against the person, not in an inbox

Share one self-registration link, or put it on a QR code at the gate or in an induction pack, and people add themselves. Each one gets their own portal and starts working through it without you sending an invite.

• A single link or QR code that anyone can start from
• Everyone who registers becomes a contact on that portal, with their own private link back
• Automatic welcome email the moment somebody registers
• Useful for site inductions, gate signage and open calls

WorkZerk opens on Requests, the one screen that looks across every portal at once: who has not finished, what is waiting on your approval, what is about to expire, and what you have sent back.

• Four live counts across the whole account, each one scrolling to its list
• A completion ring per portal, split into finished, in progress and not started
• By person for the chase list, by item for what is holding everybody up
• Approve or reject from the queue without opening a portal per file
• Expiring documents in one list, with a one-click prompt for a fresh copy

Review what comes in, approve it, or reject it with a reason and WorkZerk emails that person to ask for a better copy. Anything waiting on you sits in its own Awaiting approval list rather than being quietly accepted.

• Approve or reject each submission, with a reason
• Automatic re-submit email when you reject something
• Awaiting approval list spanning every portal
• An Admin History on every request, showing each change to it, who made it and when
• A re-answered question keeps what it used to say, dated, underneath the current answer
• Delete one person’s answer to one question when it should never have been collected, files included, leaving everyone else’s alone
• A blurry photo of a certificate stops being your problem

When someone uploads a document with an expiry date, AI reads the date on the document and compares it with the date they entered. If the two differ, WorkZerk flags the upload and holds the approval until you have looked. You still approve every document. You just stop reading the fine print on all of them.

• AI reads the expiry date on PDFs and photos, within about 10 minutes of the upload
• A date that matches the document is marked, so you can go straight to the ones that do not
• A different date is shown beside the upload, and Approve waits until you tick that you have checked the document
• A notification when a date differs, so it is not left for you to find in the queue
• The review window opens a PDF on the page the date was read from
• When AI cannot read a clear date it says so and leaves the check to you
• Turn the check off for any request, and those files are never sent to AI
• Runs on Microsoft Azure OpenAI

Put an expiry date on anything you collect and WorkZerk marks it current, expiring soon or expired, and shows you who to go back to. The one that lapsed six weeks ago stops looking the same as the one that did not.

• Automatic status on every document: current, expiring soon, expired
• Filter your whole list by what is outstanding
• Ask any person for a fresh copy without rebuilding the request
• Hide anyone you already nudged, so a second pass is only the people who have not heard from you
• No renewal dates to keep in a diary

One screen answers whether everyone has a current, approved copy of every document you need. Your people down the side, your document types across the top, and a compliant or not compliant verdict for each person, with the ones who are not listed first.

• Every cell says where that document stands: current, expiring, awaiting review, expired, rejected or missing
• A certificate sent on one portal counts on every other portal that asks for it
• Only approved documents count, so nobody is cleared on a file you have not looked at
• Optional documents show but never make someone not compliant
• A compliant or not compliant badge on each person in a portal, and a documents line on their contact record
• Filter by portal, tag and expiry window, and export the lot to CSV

Turn check-in on for a portal and everyone gets a Check in button on the link they already hold. They tap once when they arrive and once when they leave, and you get a live count and a named roster of who is on site right now. It is the list you would want in your hand if the building had to be cleared.

• One tap in, one tap out, from the link they already have. No app, no account
• A live count on the portal, and a roster split into on site now and not checked in
• Works with no signal: a tap on a dead spot is held on the phone and sent when the connection comes back
• Check anyone in or out yourself, and the log records whether they did it or you did
• Every change is appended, never overwritten, with the name as it stood that day
• A roll call for an evacuation: mark each person safe at the assembly point, and call anyone missing
• The assembly point shows on every link, under the check-in button
• A full history of every check-in and check-out, with a CSV download
• Off by default and set per portal, so a paperwork-only portal stays as it is

Chasing people is the part of onboarding nobody has time for, so hand it over. Twelve triggers cover the whole loop, from somebody being added through to a document quietly going stale, and each one sends on the day counts you choose. Two are on from the start: the reminder to finish outstanding requests, sent at 7 days and again at 14, and the alert when an invite is never opened. The rest wait until you turn them on, and once they are on you stop being the reminder.

• Twelve triggers: somebody added, self-registration, their requests finished, everybody finished, a document approved, one expiring, one expired, a rejected upload not replaced, an unfinished portal, an invite never opened, a file left unreviewed, and time to ask again
• The document chases run per document, so replacing a file re-arms them
• Time to ask again re-asks for the documents that carry no expiry date at all: police checks, site inductions, policy sign-offs, WHS refreshers
• Two of them chase you rather than them: a link that was never opened is a dead address, not a slow contractor, and a file sitting unreviewed is your queue, not theirs
• Actions that act, not just email: send their invite the moment you add them, give them a named section so one role gets one pack, or set their status
• Email the person, yourself, or any address you type, so a compliance inbox or a site manager with no login here gets the alert directly
• Timed waits, so a sequence drips instead of arriving all at once
• Nobody on a closed portal is chased, because their link no longer opens
• Spin up a workflow of internal tasks automatically
• Every email WorkZerk sends is an editable template

Onboarding is not only what you ask people for. Build the jobs your own team does as reusable workflows, write the actual procedure into each step, and print the library as a manual you can hand to whoever picks it up next.

• Reusable workflows for the internal jobs, applied in a click
• Write the how, not just the what, against every step
• Written once and read by every task made from it, so a correction corrects everything
• Sort workflows into your own categories, in your own order
• Print the lot as a branded procedures manual, PDF or CSV
• Reads live off your workflows, so there is no stale copy to regenerate

Every portal builds a real contact record rather than a one-off response. Months later you can find that person, see everything they have ever sent you, and ask for one more thing without rebuilding anything.

• A reusable record per person, not a one-off response
• Search, filter and tag your whole list in one place
• Import your existing contacts in bulk from a spreadsheet
• Or import a spreadsheet straight onto a portal, and everyone in it gets their own link
• Custom fields for whatever you track that we did not think of

Link a question to a contact field and the answer writes straight through. Ask for a phone number in the portal and the contact record has the new number, with no re-keying and no separate job to remember.

• Link any question to a field on the contact record
• Portal answers update the record automatically
• No re-keying from a submission into a database
• Send someone a short portal purely to refresh their details

Report across portals, people, contacts, request answers, document compliance, expiring documents, procedures, terms history and who viewed sensitive information, plus two that measure the onboarding itself rather than listing it. Read it on screen, print it, or export it to CSV for whoever is asking.

• Eleven reports: the lists you would expect, and two that measure how onboarding is actually going
• Outstanding requests is the account-wide chase list: everyone who still owes you something, across every portal at once, with the requests holding the most people up
• Switch it to the link engagement view to separate the people who never saw their link, who need a resend, from the ones who opened it and stopped, who need a nudge
• Response speed times the three legs, link issued to first opened, opened to finished, and start to finish, as medians per portal with the completion rate beside them
• Expiring documents across every portal at once, and a full terms history
• A log of every time someone viewed a sensitive answer or opened a sensitive file
• CSV export on every report
• Print-friendly views for the ones that get handed over
• Your data leaves as easily as it arrives