The record was already there: Assignar and the six diseases

The ticket expired the week the client audited the crew.

Nobody hid it. The expiry date had been in the field app since the day the ticket was entered. It was in the same system the supervisor opened every morning to check who was on site. It simply was not the job of anything in that system to count down to it and put the renewal in front of someone with time to act.

That is the pattern behind every one of the six diseases we wrote about on Monday. The record exists. It is in the wrong shape, in the wrong place, or read too late.

This is the first Partner Showcase. Every Wednesday we take one system contractors already run, show what comes across when you connect it, and say which of the six diseases it helps stop. We start with Assignar, because for a self-perform civil contractor it is where the day actually gets written down.

---

What comes across

Assignar connects with OAuth client credentials. Demiton reads by default. It writes only inside a scheduling or workforce workflow you switch on, and only to allocations and worker records - each of those writes supports a dry run first.

Two kinds of data come across.

Records Assignar models itself. Projects, workers, plant, suppliers, allocations, expanded timesheets, pay codes, leave, and each worker's competencies with their expiry dates.

Your forms. This is the part most integrations skip, and it is where the diseases live. Every contractor builds their own forms in Assignar: a daily site diary, a plant prestart, a day works docket, an NCR, a toolbox talk. No two companies name them the same way. Demiton reads your form titles and matches each one by title to the register it belongs on, so your "Daily Diary - Civil" and another company's "Site Diary v3" land in the same register format.

When a form matches no disease register, its submissions still reach the compliance document register - every form result is kept as evidence - but it will not shape a disease until someone maps it. We would rather show you an unmatched form during onboarding than let a register look full when it is not.

Here is what those records fill, and which disease each one is a feeder for:

Assignar also keeps the project list, allocations and expanded timesheets current. Those are what the cost side reads, and none of them is a feeder register for a disease yet.

Every register format is published in full in the register catalogue, and the Assignar connector page lists every resource we read.

The six diseases, and where Assignar stops

Disputes

It went to a lawyer, and the record for that week is empty.

This is the disease Assignar is best placed to stop, because the evidence in a dispute is mostly the site diary, and the diary is an Assignar form.

A diary that says what happened is evidence. A diary that was never filled in is a gap the other side will find before you do. Demiton has an alert written for the second kind: no diary on an active project by the end of the day, raised while the people who can still write it are on site.

It is waiting on one piece of machinery, and it is specific. The alert is about the absence of a record, and no rule over a record that never arrived can express that; the silence watch - the thing that notices the missing diary - is the piece still to land. So the alert is written and visible in the product today, marked with exactly what it is waiting on, rather than armed and quietly doing nothing. We would rather show you the alert we have built and not yet switched on than describe one that does not exist.

Where Assignar stops: transmittals, subcontracts and retention positions live in your document system and your ERP.

Rework

The inspection failed, and the next stage was already built on top of it.

A failed inspection, a flagged item on a prestart, an issue raised at a toolbox talk: each is an early sign that work is about to be done twice. Assignar records all of them on the day.

One of those three Demiton can already match on exactly, and it is worth being precise about which. The register carrying a pass-or-fail flag is the test-result register, and that one is filled by reading test certificates, not by your Assignar forms; the Assignar inspection forms carry a defect count instead. The flag makes a non-compliant result a condition the alert fires on rather than a threshold someone has to tune, and that alert is written and waiting on the rework verdict that decides what the failure means for the programme. The prestart alert is written the same way and waits on the same verdict.

Where Assignar stops: test results from the lab, and many NCRs, are kept as documents rather than forms. If yours are, the NCR register fills from your document library, not from Assignar.

Lapsed compliance

The insurance lapsed the week the client checked.

Assignar holds each worker's competencies and inductions with their expiry dates. Connecting it fills the worker qualification and training registers on day one.

Lapsed compliance is the first cure rolling out, and its countdown is running. Every certificate and insurance expiry in the register counts down at 90, 30 and 7 days, and the alert names the obligation, the party and the date, and cites the register it came from, so the person who receives it does not have to go looking.

Worker competencies from Assignar are the register that joins the countdown next. The feeder was wired on 15 September; the Assignar facts do not yet carry the subject anchor the verdict keys on, so those expiries are not counting down today while that lands. We would rather tell you the countdown is running on company certificates and insurance than imply it is already running on every ticket in the field app.

The third channel is where the honest limit sits. The app registers a phone when you sign in, but no device has registered against the demo stack yet, so mobile push reports no registered devices and has not carried a disease alert to anyone. A competency expiry that reaches a supervisor's inbox is better than one that reaches nobody, and it is not yet the same as a buzz in their pocket.

We have watched the countdown fire end to end in a demo tenant: a real verdict, a real expiry, the notification in the app and an accepted email. We have not yet watched it prevent a lapse on a live job. When that happens, you will read about it here.

Where Assignar stops: company insurance certificates and prequalification sit outside the field app.

Missed claims

The extra work was real, and the notice went in three days late.

A claim is two things: proof the work happened, and a notice inside the contract's window. Assignar holds the first. The day works docket records the delay days and the extra work. The diary records the hours the crew was interrupted.

Demiton's claim-window watch is built to pair that evidence with the notice window from your contract, so the notice is drafted before the window closes rather than found after it. It waits on the claim verdict, like the rest of them.

Where Assignar stops: the notice windows come from the contract itself, and variations and progress claims from your ERP.

Weather

It rained for four days, and nobody claimed it.

Assignar does not know it rained. Demiton does: rainfall by weather station and region is one of our own public registers. What Assignar knows is that the crew stood down, and that the diary says why.

Put the rain gauge and the diary side by side against the programme and the contract's extension of time grounds, and a wet day becomes a decision while the ground is still wet: resequence, or claim.

Where Assignar stops: the programme and the contract's grounds for an extension.

Cost drift

Nobody saw the job drift until the final account.

Assignar holds the labour side of the cost: who was allocated, and the hours they actually booked against each project. Read against the plan, that is the earliest signal of a crew too large for the work in front of it.

Where Assignar stops: budget against actuals lives in your ERP. Cost drift is the one disease where Assignar is clearly half the picture, and Business Central is the other half.

One worker, not two

The registers are only useful if the worker in the Assignar timesheet is the same person as the employee in payroll, and the Assignar project is the same job as the cost centre in the ERP.

So every connection ends with identity. Workers, projects and plant from Assignar are resolved against the same records in your other systems, and every match carries the evidence for it. On Friday's long read we explain why we built that part ourselves.

How to try it

Connecting Assignar is the first step of onboarding for most of the contractors we work with, because it answers the question onboarding asks first: which of your projects are live, and what is on them. No cure is held back for a higher tier: Public is free and protects up to AU$1M of projects a calendar year, and connecting a system starts on Insights.

If you run Assignar, book a 30-minute call and we will connect it and show you your own registers. Next Wednesday: Business Central, and the other half of cost drift.