1,309
Projects received by the system
Catch the formal defects before the review does.
Armeta Permit
Every submission package is hundreds or thousands of pages of mixed documentation. Armeta Permit reads that package — including scans, stamps, seals, and tables — classifies what it is looking at, and returns a structured review: completeness, validity, ownership, authenticity of credentials, and cross-document consistency. The specialist makes the decision. The system prepares the evidence.
A structured review of the whole package — in minutes, not days.
Armeta Permit reads mixed documentation the way an intake specialist would: classify first, check completeness and credentials, then return findings with sources. Deployed in production with a national construction permitting authority.
Proven where the queue is real.
These are not lab metrics. They are the operating record of a system that already processes live submission packages.
864
Projects fully reviewed in production
6 min
Average review time per project
5 → 2 days
Completeness cycle compressed
The expensive failure is usually formal.
Contentious engineering questions deserve expert time. Missing seals, expired conditions, and incomplete sets do not — and they are what return most packages.
Most packages fail the first gate
More than half of submissions do not clear completeness on the first attempt — expired conditions, missing signatures, broken seals, composition gaps.
Formal defects burn calendar time
A completeness return is not a comment. It is days or weeks for the whole team while the package is rebuilt and resent.
Experts should spend time on engineering
Mechanical comparison of stamps, titles, validity dates, and set composition is necessary — and it is the wrong use of scarce specialist attention.
An assistant, not a judge.
Armeta prepares the structured breakdown: findings, statuses, and links to the exact documents. The specialist confirms every consequential call. Final authority never leaves the human reviewer.
Document classification
Recognize what each file is — narrative, design section, permit, survey, estimate — and place it in the package structure.
Completeness against the matrix
Compare the uploaded set with the required composition for the object type and the declared project contents.
Project ownership
Confirm that the documents belong to one project identity rather than a mixed or leftover archive.
Validity and currency
Flag expired technical conditions, outdated editions, and documents that are no longer current at submission.
Signatures, seals, and credentials
Page-level checks for signatures, seals, and machine-readable authenticity marks where the procedure requires them.
Cross-document consistency
Reconcile the narrative composition with the uploaded sections and surface what is declared but missing.
From upload to an exportable review protocol.
The working sequence mirrors how packages already move through intake — only the mechanical work no longer waits on a specialist's calendar.
Stage 01
Upload
Bring the full package as it will be submitted.
Design, permitting, surveys, narratives, and estimates in PDF — including scanned pages. Large packages are processed as one review unit.
Stage 02
Classify
Know what every file is before asking whether it is enough.
The system assigns each document to its role in the package so completeness and consistency checks operate on the right objects.
Stage 03
Check
Run the formal gates that usually return a package.
Completeness, ownership, validity, signatures, seals, authenticity marks, and reconciliation with the declared composition — returned as itemized findings.
Stage 04
Report
Hand the specialist a review protocol, not a black-box score.
Every finding cites the page, sheet, or clause. The expert confirms, rejects, or escalates. The decision stays human.
One platform. Four modules. One analysis cycle.
Completeness is live. Analyst, Expert, and Estimates extend the same evidentiary model into navigation, section review, and cost documentation.
Stage 01
Completeness
In production — the intake gate that catches formal defects in minutes.
Classification, completeness matrix, project ownership, validity, credentials, narrative reconciliation, and estimate checks against the applicable pricing libraries. The module that already runs on live submission packages.
Stage 02
Analyst
Structure the package so experts can navigate instead of hunt.
Turn the design set into a hierarchy from project to sheet, expose an interactive graph of relationships, and search the whole package in plain language — including title-block control.
Stage 03
Expert
Section-level engineering checks for the review disciplines.
Specialized review support across structures, architecture, networks, and planning — comparing design claims with surveys, climate data, areas, and territorial constraints.
Stage 04
Estimates
Cost documentation reviewed with the same evidentiary standard.
Recognize estimates of any origin, control arithmetic, check rates against pricing libraries, reconcile estimates with section specifications, and surface the economic justification behind claimed cost.
Built on the logic of a permitting authority — not a generic model wrapper.
Language models handle classification, extraction, and matching of wording. Deterministic algorithms own arithmetic and rule checks. Every finding carries a document reference and a regulatory basis.
Jurisdiction-specific matrices
Encode the consolidated intake rules for the authority and object types where the system runs.
Current and archival editions
Regulatory checks resolve against the editions that actually govern the submission.
Transparent to both sides
Applicants and reviewers can see the AI findings — the same evidence, the same references.
On-premise ready
Deploy inside the permitting authority or customer perimeter when packages cannot leave controlled infrastructure.
Continuous improvement
Every processed project strengthens the training signal for the next intake wave.
Connected Armeta stack
Works with Armeta Codes for regulatory lookup, Armeta Materials for item identity, and Smeta for estimate workflows.
Who uses it
Explore the Armeta product line.
See Armeta Permit on your own workflow.
Bring the documents, standards, and project context your team works with today.