Hobfolk
Department 05 · Assurance

The paperwork,
and the proof.

Two jobs that look unrelated and are the same job: producing the documents that let work proceed, and establishing that work which reported success actually happened.

Start a conversationSee the whole crew
You go home. It doesn't.Every promise gets a row and a due dateAnswered the same day, not the next working dayA drawing before the quoteUnverifiable is never a passNine desks, one address eachNothing is sent that a human cannot read backThe folder exists before you price itYou go home. It doesn't.Every promise gets a row and a due dateAnswered the same day, not the next working dayA drawing before the quoteUnverifiable is never a passNine desks, one address eachNothing is sent that a human cannot read backThe folder exists before you price it
The case for it

Compliance, documents & H&S

Unverifiable is never a pass.

Every failure this system has ever had reported success while failing. A message that returned an id and never arrived. A deploy that exited zero over an unchanged page. A watcher that ran flawlessly for six weeks and could not see the thing it was watching.

So one desk here exists purely to disbelieve the others. It checks at the far end — the actual inbox, the actual live page, the actual carrier record — and never accepts the actor's own log as evidence. It returns pass, fail, or unverifiable, and a fail reopens the job automatically.

The one who knows which link to hit
The one who knows which link to hit
What the desk does

Six things, every day, without being asked

Take the whole desk or one line of it. Everything below is included in the department retainer — there is no menu underneath the menu.
01

Risk assessments and method statements

Task-specific RAMS for the work you actually do, not a template with your logo on it. Re-issued when the method changes, and kept where the site team can reach them.
02

O&M manuals and handover packs

As-builts, product data, warranties, care instructions, spares. Assembled through the job rather than reconstructed in a panic the week after practical completion.
03

Confidentiality before drawings

A one-page mutual agreement out to any new supplier, tracked to signature, and drawings held until it comes back. Words are free; pictures are not. A request for a price is never blocked by it.
04

Compliance calendar

Insurance renewals, certifications, filings and registrations, with the reminder arriving early enough to be useful rather than the week it expires.
05

Independent verification

Every unattended send, deploy or dispatch produces a claim with a runnable check. Somebody other than the doer runs it. A fail reopens the job; it does not file a note.
06

Incident record

When something does go wrong, what it cost is written down and turned into a numbered test, so the same failure has to be new to happen twice.
Depth

What this desk actually knows

Two bodies of knowledge: the documents that let work proceed, and the discipline of proving that work actually happened.

Safety documentation

  • Task-specific risk assessments and method statements written to the job, not a template with a logo dropped on it.
  • COSHH assessments for the resins, solvents, adhesives and coatings a fabrication floor actually uses.
  • CDM 2015 duty-holder awareness — who is the client, who is the principal designer, who is the principal contractor, and what each of them owes at what point.
  • Pre-construction information in, health-and-safety file out.

Handover

  • O&M manuals assembled through the job — as-builts, product data, warranties, care and cleaning, spares and lead times.
  • Assembled as the work happens rather than reconstructed in a panic in the week after practical completion, which is when handover packs are normally written and why they are normally wrong.

Quality management

  • Run to the shape of ISO 9001 — document control and revision status, nonconformance raised and closed, corrective action with a root cause rather than a shrug, internal audit on a cycle, management review that produces decisions.
  • 🔴 We are not ISO registered and we do not claim to be. We build the discipline; certification is yours to pursue if you want the badge, and we will prepare you for it.

Verification

  • Every unattended action produces a claim with a runnable check.
  • The check is run by a desk with no stake in the answer, at the far end — the recipient's inbox, the live page, the carrier's own record.
  • Verdicts are pass, fail, or unverifiable. Unverifiable reopens the job. It is never quietly rounded up.

The second column is the one that is unusual. Most automation reports its own success and is believed. Ours is disbelieved on principle, by something that did not do it.

The run of it

How a job moves through

  1. The work is claimed

    Whatever ran states plainly what it says it did.

  2. A check is written

    Runnable by someone else, against the far end, not the log.

  3. It is run

    By a desk with no stake in the answer.

  4. A verdict is returned

    Pass, fail, or unverifiable.

  5. A fail reopens it

    Automatically. Not a note in a report nobody opens.

  6. It becomes a test

    So it has to be a new failure next time, not the same one.

Where we stand

What we are liable for, said plainly

Most suppliers bury this. We would rather you read it now than find it in a schedule after something has gone wrong.

Our financial liability is limited to the implementation fees paid for the work in question. We do not underwrite your commercial outcomes, and we do not carry the consequential loss of a system we operate on your behalf. Any supplier who tells you otherwise at this price is either not reading their own contract or not intending to honour it.

That is only half a position, though, and the other half is the part that matters. A cap on liability is worthless to you if you cannot tell whether the thing is working. So the trade we offer is this: we limit what we owe, and in exchange we make the system provable by you.

Professional indemnity and public liability cover appropriate to the engagement is put in place and confirmed in writing before work starts, and the certificates go into your tender pack. The cap above is contractual and sits in the engagement agreement, in clear English, in the same size type as everything else.

What “provable by you” means concretely

  • Every automated action produces a check you can run yourself. Not a report we write about ourselves — a check, against the far end, that you or your auditor can execute without us in the room.
  • Your directors and stakeholders get their own access to the verification layer and the incident record. Not a filtered dashboard: the same view we use.
  • The incident record is not curated. Failures that affected your work are reported to you with what happened and what it cost.
  • Nothing is a black box. Every rule the system follows is written down in language a person can read, and the rules are yours.
  • You can test it adversarially, at any time, without telling us. We would encourage it. A system that only passes when it knows it is being watched is not a system.
The limits

What this desk will not do

Every department has a written boundary. A service that claims no limits has simply not found its own yet, and you will find it for them.

Where this desk stops

  • Verification does not fix the work. Deliberately. A desk that both does the job and marks it is not checking anything.
  • It is not a substitute for a qualified safety adviser where your sector requires one, or for a competent person's sign-off on regulated work.
  • It does not sign documents. A signature from something that is not a person is not a signature, and the defect surfaces years later.
Questions

Asked before, answered here

Are the RAMS legally sufficient?
They are task-specific and competently written, and where your sector requires a qualified adviser to review or sign, that review is arranged rather than skipped.
Who verifies the verifier?
The checks are runnable by you. Anything the assurance desk claims, you can re-run yourself, which is the only definition of verification worth having.
Can we see the failures?
Yes. The incident record is yours and it is not curated.
What about GDPR?
Data is processed under a written agreement, scoped per department, and the privacy notice sets out recipient categories and transfers. See the privacy notice for the detail.
Next department

Logistics & dispatch

Then getting the thing to where it is going.

Open Logistics

Which of the seven is costing you the most this month?

That is the one to start with. Tell us and we will tell you plainly whether we are the right shape for it.

Start a conversation Read the method