GPTBots
Material Compliance Audit
Problem Solution How it works Try it FAQ
Try the live system
Electrical & mechanical works · Live with a HK government department

Approve contractor material submissions in minutes. Reject the rest with evidence.

On public electrical and mechanical works, every batch of material a contractor installs — luminaires, cables, switchgear, distribution boards — must first be proven compliant through hundreds of pages of datasheets, test reports and certificates. GPTBots turns the governing specifications into executable rules, audits that evidence against them, and links every verdict to the page it came from.

For the reviewing authority

Confirm a drafted conclusion that already carries its evidence, instead of searching four documents to build one.

For the contractor

Find out exactly which requirement is unevidenced and which document closes it — before another submission cycle is lost.

Open the live system Run an audit yourself
Sign in with a GPTBots Workspace account — no separate registration.
64 executable rules from one LED luminaire specification
107 pages of evidence audited in a single pass
100% of verdicts carry a page number and the original wording
GENERAL SPEC
PROJECT SPEC
MERGED RULE 01 High risk
Supply Voltage & Frequency
Luminaires, driver and LED module shall operate at 220 V ±6%, 50 Hz ±2%, single phase AC.
Accept via compliance list, CoC or test report
P18 of 107 pages
“…rated 220–240 VAC / 220–240 V~, 50/60 Hz.”
Compliant · highlighted in source
Compliance score 100/100
Move your cursor over the scene
THE ONE-MINUTE VERSION
The whole case before the detail — scenario, pain, solution, value.
SUBMITTED APPROVED INSTALLED
01
The scenario

On Hong Kong public electrical and mechanical works, a contractor cannot install a luminaire, cable or distribution board until the material is proven compliant. Each batch arrives as a pack of datasheets, test reports and certificates that a government reviewer must check against the General Specification, the project's Particular Specification and the works checklist.

? ?
02
The pain

One submission means 22 checkpoints found by hand across six documents and 200+ pages, including scans and dense tables. It is slow, a clause is easy to miss, two reviewers grade the same risk differently — and where an answer was found is never written down, so nothing can be re-checked later.

GS PS
03
The solution

GPTBots turns both specifications into one executable rule set, merged with the reason each rule governs. Every submission is parsed — OCR for scans, structure preserved in tables — then audited rule by rule. Each verdict carries the wording it was based on and the page it came from, and the reviewer confirms or overrides it.

TODAY AFTER P18 P31
04
The value

Reviewers confirm findings instead of hunting for them, so the human time per checkpoint falls sharply. Every conclusion is defensible to a page, risk grading stops drifting between people, and hundred-page packs stop falling back to manual review. Live in production with a Hong Kong government department today.

THE PROBLEM

The cost is not the judgement. It is the search.

Every batch of contractor material arrives as a stack of datasheets, test reports and certificates that has to be checked, clause by clause, against two specifications and a checklist.

WHAT A REVIEWER FACES TODAY 200+ pages, six documents ? ? ? Reviewer hours per submission WHAT THEY GET INSTEAD Reviewer Audit result P18 P31 none P20 Every line clicks back to its page The reviewer decides. The searching is done.
TODAY · BY HAND General spec Particular spec Checklist Datasheet Test report Certificates 200+ pages Read the requirement Guess which document Scan the pages Not there — open the next one × 22 requirements The loop runs once per requirement, per submission. Where the answer was found is never written down. WITH THE SYSTEM General spec Particular spec Checklist Datasheet Test report Certificates the same 200+ pages once Audit all 22 rules ✓ Supply voltage · P18 ✓ IEC 60598-1 · P31 ✕ Surge immunity · none ✓ IP65 rating · P18 …and 18 more × 1 review pass confirm or override One pass produces every verdict. Each line keeps the page it came from.
The documents are identical on both sides. What changes is the shape of the work — a search loop repeated once per requirement becomes a single pass the reviewer checks.

Evidence is scattered

One material pulls in the general spec, the project spec, the checklist, product literature, test reports and certificates — across PDF, Word, Excel and scans.

Files are long and messy

Submissions run to hundreds of pages of dense tables, scanned pages and test data. Handed to a model whole, they lose table structure, drop parameters or time out.

Rules override each other

The project spec may add to, override or contradict the general spec. What a reviewer needs is the final rule — and why that rule won.

A verdict must be provable

“Compliant” is not enough. The reviewer has to see which rule, which file, which page — and jump to the highlighted wording.

Reviewers disagree with each other

Risk grading, acceptance method and the wording of an opinion drift between people, which shows up later in reporting and internal re-checks.

WHY IT MATTERS

These verdicts gate works acceptance and carry compliance liability. A missed clause is not a bad search result — it is a material installed on a public project that should not have been.

THE SOLUTION

An agent that holds the rules and defends its own conclusions.

Not a document chatbot. Built for the material submission and approval process on electrical and mechanical works, the system carries a versioned, executable rule set, audits each submission against it, and produces a reviewable record where every finding is traceable to source.

Materials audited
  • LED luminaires — weatherproof battens, floodlights, road and amenity lighting
  • Low-voltage power cables — XLPE/SWA, flame-retardant and halogen-free types
  • Low-voltage distribution and protection equipment — MCCB boards, switchgear
New material types are added by loading their specification, not by rebuilding the system.
Evidence it reads
  • Product datasheets and series order codes
  • Third-party type test reports, including scanned originals
  • ISO 9001 quality certificates and certificates of conformity
  • Photometric and specialist test reports, material re-submission forms
PDF, Word and multi-sheet Excel — tens to hundreds of pages per submission.
What it checks against
  • The General Specification for the works
  • The project's Particular Specification, merged over the general one
  • The works checklist for that material category
  • The international standards those specifications cite — IEC 60598, IEC 60502, IEC 60947, ISO 9001
Contract and clause references are carried through to every verdict.
Material identification
Reads a submission pack, determines the material type, and selects the specifications and checklist that govern it.
Multi-format parsing with OCR
PDF, Word, Excel and scanned pages. Tables are restructured by code components so column relationships survive into the model.
Large-file handling
Above a configured page threshold a file is split, parsed in parallel, merged back, and its page numbers corrected — never truncated.
Structured rule extraction
Clauses become rules with requirement, acceptance method, risk level, checklist category, clause number and source — to a fixed JSON contract.
General + project rule merging
One executable set, each rule labelled added, overridden, conflicting or unchanged, with confidence, source reference and the reason it governs.
Rule-by-rule audit
Each rule produces a verdict, a written opinion and a risk grade, rolled up into a compliance score and an overall result.
Source location and highlighting
Every conclusion maps back to file, page and passage. Click a page reference and the viewer opens there with the wording highlighted.
Versioned rules and audit reports
Rule sets carry versions, change notes and their downloadable source file. Every audit record produces a structured, downloadable report.
Who it helps
The review engineer

Stops opening four documents to check one parameter. Starts from a drafted conclusion with its evidence attached, and spends the time on judgement instead of retrieval.

Who it helps
The department supervisor

Gets one house standard for risk grading, acceptance method and report structure, plus a dashboard showing what is waiting on a person and what is waiting on the system.

Who it helps
The contractor

Finds out precisely which requirement is unevidenced and which document would close it — instead of a general rejection and another submission cycle.

HOW IT WORKS

Three moves. Seven stages behind them.

Four stages exist so the system holds the rules. Three exist so a human can defend the verdict afterwards.

GENERAL PROJECT ONE RULE SET
STEP 1
Hold the rules

Specifications stop being documents to read and become a versioned rule set the system can execute. The general and project specs are merged into one final set, with the reason each rule governs.

Material identification Document parsing Rule extraction Rule merging
STEP 2
Audit the evidence

Every rule in the applied set is checked against the parsed submission. Each produces a verdict, a written opinion and a risk grade — and where nothing evidences a rule, the system says so rather than asserting it.

Material audit
P18
STEP 3
Defend the verdict

Each conclusion is mapped back to file, page and passage, and rolled into a report. The reviewer confirms, edits an opinion in place, or overrides a finding — and the record keeps what a person changed.

Source location Report output
RULE TRACK General Specification Particular Specification Works checklist Rule extraction clause → requirement, acceptance, risk, source merge Executable rule set added · overridden · conflicting · unchanged EVIDENCE TRACK Contractor submission 107 pages · PDF, scans, Excel Parse + OCR tables rebuilt, not flattened Structured content page numbers preserved Audit every rule against the evidence Verdict · opinion · risk compliance score File · page · passage click through to the highlight Audit report downloadable from the record The two tracks never mix until the audit: format problems are solved on the evidence track, rule conflicts on the rule track. When one fails, you know which layer to look at.
Specifications become one executable rule set; the submission is parsed separately. The audit runs one against the other, and every verdict keeps a route back to its page.

Four principles behind the design

These carry over to any “specification + evidence + accountable verdict” scenario, not just electrical and mechanical materials.

1
Parse first, reason second

Format problems are solved before the model sees anything, so parsing accuracy and reasoning accuracy can be diagnosed separately.

2
Contract before output

Fields, types, risk levels and error returns are agreed first; the model produces to that contract so the UI and report can consume it.

3
Verdict and evidence ship together

A conclusion arrives with its source, so a human can verify it in seconds. This is the principle that decides whether the customer trusts the system.

4
Split oversized input, never truncate it

An extra engineering layer — split, parallelise, merge, correct page numbers — is always preferable to silently dropping content.

TRY IT YOURSELF

Submit a material. See what the audit says.

Pick a material, choose which documents the contractor attached, and run it. The verdicts are computed from what you attached — leave a certificate out and watch which checkpoint fails.

1
Material submitted for review
2
Documents attached to the submission — click to attach or remove
3
Rule set applied
Merge the project specification into the general specification
64 general rules + 4 project rules → 68 executable rules
No audit run yet
Attach the documents you want to test with, then run the audit.
INSIDE THE LIVE SYSTEM

Four screens from the running system.

Captured from the environment your customer can open today. Everything below is real output, not a mock-up.

01 Dashboard

The whole workload on one screen

Projects, materials, pending items and active rule count, with running and queued audit tasks alongside project and material status distribution — so a supervisor can see what is waiting on a person and what is waiting on the machine.

Material Audit System dashboard showing project and material status
Sixty-four structured rules extracted from an LED luminaire general specification
02 Rules, not summaries

64 executable rules from one specification

Each row carries a requirement, the acceptance method that would let it pass, and a risk level. Rule sets are versioned with change notes, and the source file stays downloadable — so an auditor can always ask where a rule came from.

03 The screen that wins the room

Every verdict, one click from the page it came from

22 checkpoints, filtered by compliant, partially compliant, non-compliant or pending evidence. Each shows the wording the system extracted, the page chips it came from, and an editable audit comment. Click a chip and the viewer jumps to that page of the 107-page submission with the passage highlighted.

Compliance score and overall risk level on the header
Reviewer edits the opinion in place — the system never has the last word
Report downloads straight from the record
Audit record detail with extracted content, page references and highlighted PDF evidence
Audit flow configuration with PDF split page size and task concurrency
04 Operator controls

The large-file strategy is a setting, not a promise

Above a configured page count a submission is split into chunks, audited separately and merged back. Audit and rule-generation concurrency are tunable to the deployment's capacity, and ad-hoc reviewer requirements can be synced back into the project rule set as a new version.

BUSINESS OUTCOMES

Six things the customer gets back.

Reviewers confirm instead of hunt

The manual effort moves from finding and collating evidence to checking a conclusion that already has its evidence attached.

Fewer missed requirements

Standards, parameters, certifications and acceptance methods are covered systematically rather than from a reviewer's recall.

One house standard

Fields, risk levels, acceptance methods and report structure stay consistent between people, which makes internal re-checks tractable.

Defensible conclusions

Every verdict resolves to a rule, a file and a page — the evidence standard government and engineering compliance work actually requires.

Large files stay in the system

Hundred-page packs run to completion instead of falling back to manual review because parsing failed or content was truncated.

One party accountable

Front end, back end and AI capability are built and maintained by one team, so change requests and defects have a single owner.

RETURN ON INVESTMENT

Size it with the customer's own numbers.

The saving is not a percentage off the old process — it is the same checkpoints, counted twice. Once at the minutes it takes to find and judge each one from scratch, once at the minutes it takes to verify a verdict that already carries its evidence. Defaults are our estimate, not measured results from this deployment; change any of them in the meeting and the answer moves with you.

22 on the LED luminaire submission in the live system
find the parameter across the documents, judge it, write the opinion
read the extract, click the page reference, accept or override
whatever currency you brief in
2,200 reviewer hours returned per year
220,000 in loaded cost, same period
1.2 full-time equivalents freed
at 1,800 productive hours a year

Reviewer, today
5.5 h
Reviewer, after
1.1 h
The audit itself
mins

The audit runs in a background queue in minutes and costs the reviewer nothing — they open a submission that has already been checked. The only human time left is verifying what it concluded.

Counted above

Reviewer hours redirected from searching to confirming. The most defensible pool, because the customer already knows all three inputs.

Not counted — resubmission cycles

The contractor is told which requirement is unevidenced and which document closes it. Each cycle removed is calendar time off the works programme, not just review time.

Not counted — late findings

A clause missed at submission surfaces at acceptance, with the material installed. Usually the largest pool and the hardest to quantify: ask what one such event has cost them.

Two pools are deliberately left out of the arithmetic, so the number above is the conservative floor rather than the sales case.
DEPLOYMENT & ENVIRONMENT

How it fits into the customer's environment.

What goes in, what comes out, who can sign in and where it runs — the questions an IT reviewer asks before a business owner is allowed to say yes.

IN PDF · including scans Word documents Multi-sheet Excel Tens to hundreds of pages per submission CUSTOMER ENVIRONMENT Material audit application projects, rule management, audit records, reporting agent keys GPTBots agents parsing, rule extraction, merging, audit, source location Verified hardware ARM (GX10) and x86 (RTX 6000 Pro) — the GPU environment is faster and parses more accurately OUT Audit record + page refs Downloadable report Versioned rule sets Sign-in · GPTBots Workspace SSO
Documents in, audit records out. The application and the agents both run inside the customer's environment; nothing about the flow requires an external document system.
Accepted input
PDF including scanned pages, Word, and multi-sheet Excel. Submissions of several hundred pages are normal; scans are routed through OCR and tables are restructured before any reasoning.
Produced output
A structured audit record — verdict, opinion, risk level and page references per rule — plus a downloadable audit report. Rule sets are held as versioned structured data against a fixed field contract.
Sign-in
Single sign-on with a GPTBots Workspace account. No separate user registry to maintain.
Agent connectivity
The application talks to its AI capability through configurable agent keys, so the underlying agents can be swapped or re-pointed without touching the front end.
Deployment
Deployed inside the customer's own environment for this project. Verified on ARM (GX10) and x86 (RTX 6000 Pro); the GPU environment is faster and parses more accurately.
Operator settings
PDF split threshold, audit task concurrency, rule-generation concurrency, and whether ad-hoc reviewer requirements sync back into the project rule set as a new version.
Localisation
Departments, project categories and material types each carry Traditional Chinese, Simplified Chinese and English names, so the same records read correctly for local and international users.

A note on integrations

This deployment is document-in, record-out — it does not currently sit behind a document management system or ERP connector.

Where a customer needs submissions pulled from an existing system, or verdicts pushed into one, that is scoped as integration work on top of the GPTBots platform rather than something already shipped. Say so plainly in the room — it is a shorter conversation than walking it back later.

WHY THIS SOLUTION

Four things a generic document AI will not do.

If a competitor is pitching “chat with your documents”, these are the four questions that separate the two.

1
It gives evidence, not an answer

A summary cannot be signed. Every verdict here carries a rule number, a file, a page and the original wording, and the reviewer can click straight to the highlight. That is the difference between something interesting and something a government department can act on.

2
It merges specifications, it does not diff them

The first version of this system only reported what the project spec changed. Reviewers needed the final executable set and the reason each rule governs. That rework is already paid for — the merging workflow ships with change type, confidence and source reference.

3
It is engineered for the actual files

OCR for scans, code components for tables, and a split-parallelise-merge path with page-offset correction for oversized PDFs. Most failures in this category are parsing failures wearing a reasoning costume.

4
One team owns the whole stack

Front end, back end and AI capability are built and maintained by us. There is no seam between the agent vendor and the application vendor for a defect to fall into, and the customer has one number to call.

WHERE IT GOES NEXT

Same engine. A different rulebook.

Nothing in the seven stages is specific to lighting. Moving to another field of work means loading its specifications and its checklist — the parsing, the rule merging, the audit and the evidence trail are already built and already in production. A second project starts roughly where this one finished.

E&M material submissions GS + PS + works checklist LIVE Construction & engineering method statements, handover documentation, drawing conformity Procurement & suppliers tender responsiveness, supplier qualification, incoming test reports Compliance & audit market-entry dossiers, policy vs regulation, audit evidence Rule library — swapped per domain the specifications, the checklist and the risk grading for that field of work what changes Seven-stage audit engine identify · parse · extract · merge · audit · locate · report what stays
Only the solid domain is built today; the three dashed ones are where the same engine would dock. The engine itself is packaged as a GPTBots WorkSpace extension application, which is also why there is a working system to demonstrate before a customer has an environment of their own.

Use cases with the same shape

Every one of these is the same problem wearing different clothes: a rulebook on one side, a pile of submitted evidence on the other, and a verdict someone has to stand behind. If a scenario fills in these four columns, the engine already fits it.

Use case
Who reviews
The rulebook
The submission
E&M material submissionsLIVE
Government engineering regulator
General Specification + Particular Specification + works checklist
Datasheets, type test reports, ISO and conformity certificates
Method statement review
Project management, site safety
Works specification and the safety code for the activity
Contractor method statements and risk assessments
Tender responsiveness check
Procurement
The requirements schedule issued with the tender
Bidder proposals, technical schedules, compliance statements
Supplier qualification & incoming goods
Quality assurance
Approved supplier standard and the incoming inspection plan
Supplier certificates, certificates of analysis, test reports
Handover documentation acceptance
Asset owner, facilities
The handover requirements schedule for the contract
O&M manuals, commissioning records, as-built drawings
Policy against regulation gap check
Compliance, internal audit
The external regulation or standard in force
Internal policies, procedures and control documentation

Only the first row is built. The rest are scoped as rule-library work on the existing engine — bring one to the project team before promising a timeline.

How to recognise the next one

Three questions that qualify a scenario inside a first meeting. All three true is a strong match.

1

Written standards exist in layers or versions — national against company, general against project-specific.

2

One review means reading several long documents, and most of the time goes into searching rather than deciding.

3

The conclusion has to state its basis, because someone may re-check or audit it later.

FAQ

The eight questions you will be asked.

Is it actually live?

Yes — in production with a Hong Kong government department, with all seven stages in real use.

How large can a file be?

Typically tens to hundreds of pages. Beyond a configured page threshold the file is split, parsed in parallel and merged back together.

Can it read scans and tables?

Yes. Scans go through OCR; tables are restructured by code components before the model sees them.

How do you know the model is not inventing it?

Three constraints: rules are produced to a structured contract rather than as free text; every conclusion carries a rule number, file, page and original passage you can click back to; and the system is positioned as first-pass review — the reviewer signs the conclusion.

What if the two specifications conflict?

A separate merging workflow labels each rule added, overridden, conflicting or unchanged, and returns the reason, a confidence value and the source reference.

Can it be deployed privately?

This project was deployed inside the customer's own environment, verified on both ARM (GX10) and x86 (RTX 6000 Pro) hardware.

Are the hardware requirements steep?

Both environments run the full flow. The GPU environment is noticeably faster and parses more accurately, so plan the target environment early and validate against it.

How long to move it to another industry?

The capability is packaged as a WorkSpace extension application, so the work is rule and scenario adaptation rather than rebuilding workflows. Confirm timeline with the project team before quoting one.

WATCH IT WORK

The full flow, end to end.

A two-minute recorded run through the live system, on the real government deployment.

HK Gov material review — full walkthrough 1:58 · opens on YouTube in a new tab

Let the customer click through it themselves.

Open a project, look at the merged rule set, and click a page reference on a finished audit. Ten minutes in the live system does more than any slide.

material-audit.gptbots.ai Book a demo

Sign in with a GPTBots Workspace account. Sample projects, rule sets and a completed audit record are already loaded.

Material Audit System sign-in page
GPTBots Enterprise AI agents for document-heavy compliance work.
Use case · Material compliance audit