16 of 25: what Demiton checks today

Sixteen of 25. A job loses its margin to five diseases, each disease has five causes, and Demiton has a check running on 16 of those causes today. The owner signing for protection needs to hear about the other nine before the contract, not after a loss they assumed was covered. Four are causes where the records come in and nothing reads them on a schedule yet. Five have no check at all. A check you were told about and do not have is worse than no check, because you stop looking.

A running check is in production, reads your registers on a schedule, and sends what it finds to whoever signs off that kind of thing on the job. It needs your records, and each section below says which. It does not mean the check has caught money on a real job, because none has yet. The figures below come from Bridgeworks, Demiton's demo company.

The last column counts the obligation library. Of its 699 duties, 432 cannot produce a verdict today whatever you connect. Most read an event no connected system records. Others have no number to count: "notify a latent condition as soon as it is found" has no deadline for a clock to run to. In the app, each disease opens into its causes, and each cause page leads with what is stopping it on your jobs.

Rework: two of five

The check that has run longest is on your purchase lines: the same job and cost code ordering the same item again inside a set window, leaving out consumables such as fuel, fasteners and PPE, and items bought routinely across jobs. Its total is the rework figure on your Baseline.

New: that figure now opens. Planning, procurement and sequencing lists every repeat purchase counted, with its purchase order lines, and someone on the job marks each one: rework and who pays (principal, supplier or your own business), or not rework and why. A pattern marked not rework leaves the figure and stops alerting until a new order for the same item on the job reopens it. A number somebody can check line by line is one they can believe.

New: design and documentation has a check. Revision C arrives by email, while the lot on site is being built to revision B, and the person who can stop it is not on the email. In the Outlook panel you record the issue and the panel names who was asked: the quality hold goes to whoever holds that sign-off on the job, with their Offsider. A test lot built to a revision already superseded on its first test date is then flagged, comparing revision dates and never labels. The limit is real: the test result has to name the drawing revision, that field is new, and no connected system fills it yet.

Not covered. Failed tests, non-conformance reports and punch lists are captured, but no check reads them for workmanship, so Demiton does not yet tell you that a failed test has been built over. Scope and change, and setting-out, ground and external conditions, have no check. Six of the library's 19 rework duties can be checked: a non-conformance report within one working day under TMR's MRTS50 can, and a hold point release under the same standard cannot.

It needs: purchase lines from your finance system.

Cost drift: two of five

Across every cost code, a daily run compares committed plus actual cost with the cost budget and flags a code over it. Two causes now sit on top of that.

New: input price rises has its own page, and it takes two paths. Where the contract has a rise-and-fall clause, each certified claim produces the adjustment. AU$18,063.24 is what September was worth on Bridgeworks' Coomera package, on a clause we wrote for the demo and indices that are real and published. The contract administrator would otherwise have to notice the claim was certified, find four indices for the right quarter and give notice inside 40 business days, with October's claim already on their desk. A clause nobody works out is a price rise the contractor pays for.

The claim opens the notice window and raises a request to whoever signs variations and claims on that job. A claim whose index quarter is not out yet waits. A clause naming an index Demiton does not hold is blocked and names the index; Demiton never substitutes a series or re-weights the others.

The second path is for the work you price yourself. A rate card takes the last price you paid, ages it by the item's index when a newer quarter is out, and proposes the sell rate that holds your target margin. On Bridgeworks, 375mm RCP sits on the books at AU$312.50 and sells at AU$390.00, a 19.87% margin against a 20% target. Replacing it costs AU$322.50, so the margin is really 17.31%, and the card proposes AU$403.13. It never proposes a price cut. A job with no clause shows the rise it is absorbing, from the purchases it has made.

New: tender pricing runs at 07:00 Brisbane time on Mondays. For every job with a linked price, it compares forecast cost with priced cost on each priced activity, and on labour lines it compares hours and rates and names which of the two cost more. If the median rate paid across three jobs falls outside 90% to 110% of the priced rate, your estimator gets one proposed lesson to accept or decline. An accepted lesson is proven only when three closed jobs priced after it show less variance than the three newest before it. A job that cannot be measured names the step it is missing: price, link to the job, budget, confirmed map, progress or cost.

Not covered. Quantity growth has no check, because no customer holds quantities built. Labour hours are captured, and no scheduled check compares them with time elapsed. Plant hours and fuel are captured and nothing compares them with what was priced. The tender pricing page does not yet show its input register or the before-and-after comparison.

It needs: a job budget, plus cost lines or purchase lines. Tender pricing also needs your priced activities linked to the job.

Missed claims: three of five

The whole disease runs on one clock, and the contract sets its length. A delay in the site diary, or a delay raised from an email, starts the extension-of-time notice period, which is how penalty days get caught. A variation, a day-works docket or extra work raised from an email starts the variation notice period. A certified progress claim starts the price adjustment notice, which is the part of payment and retention that runs today.

You lodge the notice from Demiton and the window is marked lodged. Miss it and a high-severity alert goes out. With no contract on the job, or a contract silent on notice, there is no clock and Demiton says so; it never invents a default period.

Not covered. Nothing starts a clock on a latent condition, because no register records one on its own; the diary and RFIs hold it as text. Delay costs are captured as plant hours and site days, and nothing compares them with a granted extension. Reference dates, retention and securities are not timed yet. Of the library's 107 duties here, 55 can be checked.

It needs: contract terms, plus site diaries, day-works dockets or variations.

Disputes: five of five

Disputes is the only disease with a check on every cause, and it is the same check each time. For each job and each standard that applies to its place and contract, it asks whether the record a dispute would call for exists: met, at risk, missed or unmeasurable, with the reason and the amount exposed. Watched duties are measured at 05:00, 12:00 and 14:30 site time.

Not covered. This check says whether the record exists. It does not judge whether your case is good. The library holds 203 duties here, and 107 can be checked.

It needs: contract terms, plus progress claims, retention, payment schedules, a programme, dockets or diaries.

Lapsed compliance: four of five

Every expiry counts down at 90, 30 and 7 days: tickets on people, registration on plant, certificates on insurance, and certificates on the company. Plant has a second check, comparing GPS starts with prestart records, so a machine running with no prestart shows up.

New: the page now reads the way a site manager asks. It used to name the stage a compliance gate failed at. It now asks whose ticket is out: people, plant, insurance, company or site.

Not covered. The countdown knows a ticket's date, not whether it covers the task in hand. Inductions, a policy's territory and limit against the contract, and a prequalification's conditions are not checked. Site has no check: permits to work, traffic management plans, environmental conditions and the asbestos register are all unread. This is where the library's gap is widest: 97 of 366 duties can be checked, largely because most read an event no connected system records.

It needs: one of your certification register, insurance certificates or worker qualifications.

Getting the records in

Every check above reads a register, so this is where protection starts.

• You sign what Demiton reads. Each connected system can carry a written authority: a versioned record of the credential, the scope, the security roles and the registers Demiton may read, frozen at signing, with a PDF. Only an admin or director can sign it. Once signed it is the allow-list, and an unapproved register is skipped before any call reaches your system. A connector with no signed version keeps reading as configured.
• Connecting a system ends on What to read. It shows the diseases that system feeds and the part each register plays, with everything else off until you tick it. Assignar offers 33 registers, of which seven feed a disease and two more are read by the checks.
• Aconex is built. On the Baseline plan it harvests nine registers on a schedule, among them drawings, transmittals, RFIs, notices, change events and retention, feeding rework, cost drift, missed claims and disputes. It is proved in tests and has not yet run against a customer's live project. A Procore mapping is written and nothing runs it yet.

Also this week

• French, France and Washington State. A person can pick English or French (marked beta) on their account; stored facts, findings and alerts stay in English for now. France and Washington State are places you can put a job. France is not on sale until its tax line is confirmed, and neither has a holiday calendar yet, so the four Washington duties that count working days read as unmeasurable.
• The free trial is gone. A web signup starts on Free. Demiton sets the plan for a Pilot or Baseline organisation, whose people see a screen saying what is being done for them while their registers fill.
• Margin Watch and Benchmarks are retired from Explore. The weekly tender pricing run is where an estimate now meets the job.
• The job page states its units: business days, calendar days, a percent or an amount, and it says so when the contract stated no unit and business days were assumed. A job with no protection now says that in one line, where it used to show "Needs attention: 0".
• Deadlines end at midnight on site, not midnight UTC.
• The project board works on a phone, with "Not protected" visible on a 390-pixel screen.
• A refused sign-in link says why: another browser, already used, or expired after 15 minutes.
• Six broken calls and the report library work again. The SharePoint and document location pickers, among others, were failing on a doubled API path, and Reports was returning an error.
• demiton.io changed. How it works opens on the money, Ask Demiton asks one question per disease and shows real cited answers, Outlook and mobile have their own pages, and a demo is 30 minutes on a booking page. docs.demiton.io has a Diseases section, and its public roadmap now redirects to the changelog.
• Analytics on demiton.io count by default in Australia, New Zealand, the US, South Africa and Canada outside Quebec, with a way to turn them off. Everywhere else stays off until you accept. The privacy policy says so from 1 November.

Fixes and security

• A password reset revokes your API keys and OAuth tokens. Before, a key made from a stolen session outlived the reset.
• Another tool's output cannot write to your memory unasked. If a Studio turn has used an external tool, anything it then tells Demiton becomes a proposal in your approvals queue.
• Studio's approval card. When a tool call needs approval, web and mobile show Approve or Decline with a two-minute countdown. Before, nothing drew the request, so it timed out and was declined.
• Permissions tightened. Connector discovery and data-exception routes require permission to manage connectors, memory reads respect the data scope of each register, and adapters refuse a URL that reaches a private address or moves the host they were configured for.
• The API stays up through more. A slow database call inside a request could stall every other request for seconds. Those calls now run off the main loop, and a Postgres restart no longer adds about four minutes of crash and backoff.

For integrators

• Removed: the Margin Watch and Benchmarks routes, and the four tender-baseline endpoints.
• API keys take a lifetime: 24 hours, 7 days, 30 days, 6 months, 1 year or never.
• Fixed: PUT /users/me, which returned a 500 on every call, and tell_demiton, which could crash.

What's next

Microsoft's certification of Demiton for Outlook, still waiting on review. The Microsoft 365 Copilot package, rebuilt to answer five must-fix items in Microsoft's 29 October report. The iPhone and iPad app on the App Store, which it is not yet. A register for safe work method statements. Holiday calendars for France and Washington.

And still the one this series is waiting to report: a protection that fires on a live job, catches something real, and is signed off with cash recovered. Sixteen causes have a check running, and none of those checks has done that yet. The first one that does goes at the top of this page.