Three things worth seeing in a demo

Your processes, drawn the way your business actually works

Most process maps are drawn once for the auditor and never opened again, because changing one means redrawing it. Here you drag a shape and the map is updated — swimlanes, gates, hold points and witness points included, because in fabrication those mean genuinely different things.

Approve a version and it's locked and dated. Drill into a step to see the sub-process behind it. Link a step to the procedure, form or inspection it depends on, so the person following the map can open the document they need without going looking for it. Export it for the audit whenever you're asked.

And you don't start from a blank page. Enquiry to invoiced, estimating, design and drafting, fabrication, installation and project management all come drawn for a manufacturing business — edit them to match how you actually work rather than inventing them from scratch.

The document you're holding is the document that was approved

Drafts stay separate from published versions, so nobody works from a half-finished revision. Every change is logged automatically and can't be quietly overwritten. Read acknowledgements are captured by name and date, so when an auditor asks whether your people have seen the current procedure, you show them rather than argue.

The register of documents you're supposed to hold and the documents themselves are joined up, so the two can't drift apart. Nothing goes stale in the gap between the plan and the reality.

Management review that writes most of itself

The hardest part of a management review is assembling it: pulling non-conformance figures, audit results, KPI performance, supplier evaluations and customer feedback out of five places the week before the meeting.

Here it's already assembled. You turn up to discuss the business rather than to build a pack about it, record what was decided, capture the sign-off, and the whole thing freezes as a dated record. Next year's auditor sees exactly what was in front of the room on the day.

The parts that matter most

Nobody sees a colleague's file

Pay, performance, medicals, disciplinary history — the reason HR still lives in a locked cabinet in a lot of businesses is that nobody trusts software to keep it private. This is the most tightly held data in the platform, restricted to the people whose job it is, and locked down at the data layer rather than by hiding a menu item. When someone leaves, their access is gone the moment you deactivate them.

A new starter who's productive on day one

Before they walk in, they've signed the contract, read and acknowledged the policies, uploaded their tickets with expiry dates and rated their own skills. Their induction is booked and their file is already complete.

The signature isn't a tick box either — it captures exactly what they agreed to and exactly which version they signed, so the record holds up if it's ever questioned.

You find out before the ticket expires, not after

Every licence, medical and competency is watched. The person's file flags before the date lands and the chase goes to whoever needs to act on it, so nobody discovers a lapsed forklift ticket during an incident investigation.

That's the difference between owning a training matrix and knowing your people are actually competent to do the work in front of them.

Where it earns its keep

Get your first Tuesday of the month back

If you've ever spent a morning rebuilding the same board pack in PowerPoint, this is the part that pays for the subscription on its own. One click produces a branded report covering financial performance, your objectives and KPIs, quality and safety, and who owes what — with a plain-English paragraph under each section explaining what the numbers are telling you.

Same format every month, so your board can compare like with like instead of learning a new layout each time.

Enter it once

Load your profit and loss and the financial measures on your scorecard update themselves. No parallel spreadsheet, no reconciling two versions of the same number, no month where the scorecard quietly stops being true because nobody had time to update it.

Budgets are kept separate from targets, because they're different questions — what you planned to spend isn't what you're aiming to achieve, and blurring the two is how a scorecard loses the room.

Why this sits in an ISO platform at all

Because an owner who can see gross margin trend next to non-conformance rate makes better decisions than one who can only see either alone. Quality problems are expensive long before anyone calls them a quality problem, and this is where that shows up.

How it's put together

Start with ours, end up with yours

The problem with a generic training platform is that none of the content knows anything about manufacturing, so you either use material that doesn't fit or you build everything from scratch. Neither happens.

Here you start from a library written for manufacturing, take a pathway with one button, and change it to match how your business actually does the job — your terminology, your machines, your procedures. When we improve one of ours, you're told and you choose whether to take the change. Your version is never rewritten underneath you.

Training that can't go out of date

A lesson can point straight at the current approved procedure rather than a copy of it. Update the procedure and the training updates with it — no more inducting a new starter into last year's method because nobody remembered the course had a PDF stapled inside it.

This is the connection a standalone learning platform structurally cannot make, and it is the reason induction and awareness stop being an annual scramble.

Awareness you can actually show someone

Assign it, and the reminders chase without you. When the auditor asks how you know your people understand the quality policy, or when a customer asks what induction your crew received before they came on site, the answer is a report rather than a rummage through email.

Why one platform matters here

The Place button

This is the bit that only works because it's one platform. Press Place on a candidate and the system creates the employee record, sends the invitation, starts the onboarding checklist and the induction, marks the candidate placed and closes the role as filled. One click covers what is normally four systems and a fortnight of chasing.

Candidate data is treated like HR data

Because it is. Applications are visible only to the people doing the hiring — not to the rest of the business, and not to the candidate's future colleagues. And when someone applies and misses out, you can keep them on file for next time without quietly breaching privacy law: the system prompts you to review and clear the pool before you've held anyone's details too long.

Language matters on a job ad

Categories are grouped as trades, production and warehouse and professional, technical and office. Never "blue collar" and "white collar". The screening-question builder flags wording that carries anti-discrimination risk before you publish it.

The difference that makes it worth having

"Why wouldn't we just use Teams?"

Fair question, and worth answering plainly. Because a decision made in chat here becomes a tracked action with a name and a due date, chased like everything else. A board card isn't a copy of an action — it is the action.

Teams can't do that. A screenshot pasted into a channel is not a record, and "we discussed it in the group chat" has never once satisfied an auditor.

The bloke on the tools will never fill in your form

And you'll never change that by asking harder. So he doesn't have to. He describes what happened the way he'd describe it to you — typed or spoken, hands dirty, in the middle of a job — and the proper record gets raised behind him, read back for confirmation, and assigned to whoever needs to act.

Some things aren't left to a machine, deliberately. If someone got hurt, it's always an incident, never a hazard. Whether an event is notifiable is a legal judgement, so a person makes it. A change nobody has approved never quietly starts work.

The result is that you hear about the near miss on the day, from the person who saw it — which is the whole point of a reporting culture, and the part no amount of software has ever bought anyone before.

Private conversations stay private

Administrators cannot read direct messages. People stay attributed to what they said even after they leave, so the history stays true rather than being quietly rewritten. Your team can talk openly, which is the only condition under which any of this works.

The two AI actions

Fabricators lose tenders on compliance, not price

A missed insurance requirement. An unanswered clause about traceability. A deadline nobody diarised. The work was winnable and the price was right — the submission just wasn't complete.

The other half of the problem is quieter: reading a two-hundred-page pack properly takes a day nobody has, so half your opportunities never get assessed at all, and you find out too late which ones you should have chased.

Know what's being asked before you commit a week to it

Upload the pack and get back a plain read of what the client actually wants — not just the words, but the drawings, schedules and response forms, where the real requirements usually hide. What has to be submitted, what has to be evidenced, and by when.

"Can we already prove this?" answered in two minutes

This is the part nothing else can do, and it only works because it is one platform. Tender Hub compares what the tender is asking for against what you can already evidence — your certification, your welder qualifications, your safe work method statements, your supplier evaluations — and tells you what is genuinely missing.

So the bid decision stops being a gut call made under time pressure. You chase the work you can win, and stop burning weekends on the work you can't.