Document pre-check

Check the document against your checklist — not the model's memory.

Upload a schematic or datasheet. AS Applied uses a defined engineering checklist to flag what is shown, what is unclear and what may need human review.

How it works

A five-step pathway from document to engineering review.

01

Upload document

PDF or image. The MVP currently supports hydraulic schematics and pump datasheets.

02

Defined checklist

The selected document type maps to a server-side checklist written and maintained by AS Applied.

03

AI evidence screen

The model looks only for visible evidence against those items and returns structured observations.

04

Internal preliminary report

Shown, unclear and not-shown items are presented with evidence locations and confidence.

05

RPEQ / engineer review

A human reviews the flags before the workflow becomes a paid customer deliverable.

Internal MVP tool

Upload a document for checklist-led screening

The AI is not asked what the Standards require. It only checks visible document evidence against the predefined AS Applied checklist.

Setup required
Pre-check setup is not enabled on this deployment. For local testing, add PRECHECK_DEMO_MODE=true to .env.local, then fully restart pnpm run dev.
1 Choose the document type
2 Upload the document
Current checklist scope

Hydraulic schematic

Preliminary review of pressure control, stored energy, movement risk, filtration and critical settings.

6 explicit checks only
Preliminary screen onlyHuman engineering review remains the next step.
What the MVP does

Structured screening before engineering judgement.

  • Checks only the defined items for the selected document type.
  • Looks for visible evidence and identifies uncertainty.
  • Keeps standard references attached to the human checklist, not generated by the model.
  • Creates a consistent review starting point for an engineer.
What it does not do

No approval, certification or automatic customer release.

  • It does not determine legal or Standards compliance.
  • It does not replace design calculations, verification or RPEQ services.
  • It does not know the project context that is absent from the document.
  • Stripe and paid report release are intentionally not connected in this internal MVP.
Data handling

Be explicit about where engineering documents go.

In this MVP, AS Applied does not intentionally save the uploaded file to a database or file store. The server sends the file to OpenAI for the requested analysis with response storage disabled.

Do not promise immediate deletion by the AI provider: standard API abuse-monitoring retention may still apply. Before public launch, the final privacy notice and retention process should be reviewed alongside your PI insurance and customer terms.