Automated document quality checks for construction.
Validate naming, metadata, and PDF content across every Autodesk Forma project — on a schedule, in minutes, without spreadsheets.
- PROJECT
- FOREMAN · QA / QC
- SHEET
- 00 / 16
- REV
- C
- SCALE
- NTS
- DRAWN
- FOREMAN STUDIO
- APPROVED
- 2026.04
The job is checking, not designing.
Document Controllers and QA Managers spend hours every week opening files one by one — comparing names, ticking metadata fields, checking that the PDF title block matches what's on disk.
It's the wrong work for the people doing it, and almost nothing gets caught until handover or audit.
Six things every document controller has dealt with.
REGISTER · 001Files with wrong naming conventions.
Thousands of documents uploaded inconsistently. Nobody catches it until handover.
Missing metadata fields.
Document Status, Suitability, Discipline left blank. No way to enforce completion.
Title block doesn't match metadata.
The PDF says Rev C, the file says Rev B. Mismatches go unnoticed until audit.
Missing or extra deliverables vs. register.
MIDP says 247, you have 232 — and 5 extras nobody planned for. A full day to reconcile.
Codes not on the approved list.
An originator code, discipline, or suitability slips through. Hard to spot at scale.
Manual spot-checks taking hours.
Open file, check name, check metadata, log result. Repeat. Every week.
The math of manual QA.
Industry rule of thumb: ~3 minutes per file to open, check naming, check metadata, check title block, log the result. Plus ~20 minutes per batch for reporting.
opened, checked, logged.
Foreman validates naming, metadata, and PDF content — automatically.
Three steps to automated document quality.
Define Rules
Start with seven built-in rule sets — naming, metadata, content, register compliance, cross-field. Clone and customise, or build from scratch. AI generates regex from example filenames.
Run Checks
Manually, on a schedule, or auto-triggered when files change in Autodesk Docs. Forma folders or local upload. Combine rule sets in one run, or assign different sets per folder.
Review & Act
Interactive dashboard. Track violation status from Open to Resolved. Push to Forma Issues in one click. Export CSV, Excel, or branded PDF reports.
A rule for every kind of validation.
CATALOGUE · 001File & Metadata
Naming Convention
Validate names against regex. AI generates patterns from examples.
Required Metadata
Mandatory attributes populated across every file.
Allowed Values
Restrict a field to a predefined list. Catch typos.
File Format
Block unexpected extensions in controlled folders.
Freshness
Detect stale files not updated within a period.
Lists & Ranges
List Validation
Check filename, metadata, or zone text against an approved list.
Numeric Range
Min/max with optional zero-padding.
Register Cross-Reference
Bidirectional MIDP/TIDP — flags missing AND unexpected.
Segment Consistency
Conditional cross-field rules (if discipline = ST, originator must be approved).
PDF Content
Content Match
Cross-validate zone text against CDE metadata — exact, contains, or date.
Content Convention
Validate zone content against regex, or verify zone has content.
Content Extraction
Extract text for reporting and audit — data capture only.
Mix & match across categories in a single check.
Extract text from any part of a document.
- 01Visual zone editor. Draw rectangles on title blocks, revision tables, approval stamps. Multi-page templates, reusable across projects.
- 02Live preview. See exactly what text is captured before you save the rule.
- 03Auto-detect text vs scanned. Native extraction for digital PDFs, OCR for scanned. You never have to choose.
Scanned drawings count too.
Tesseract OCR, auto-detected.
Native text-layer extraction for digital PDFs, OCR for scanned. Foreman picks per file — you never have to choose.
One template. Every sheet size.
Define zones once; Foreman re-anchors them per sheet size. The right variant is matched automatically by page dimensions during checks.
Naming rules without regex.
Paste an example filename. One click. Foreman generates the pattern that captures your naming convention.
Set it and forget it.
- WHKWebhook triggers. QA runs when files are added or modified in Autodesk Docs. No manual run.
- DBCSmart debouncing. Batch uploads grouped into one check — no duplicate runs.
- SCHSchedules. Visual day-of-week toggles, time picker, timezones. No cron syntax.
- EMLEmail digests. Pass/fail summary on completion. Failure alerts on by default.
Bridge Extension Phase 2
From finding to fixing — without leaving the loop.
QA finds violations
Foreman runs the check, flags the file + rule.
One click to Forma Issues
One issue per violation. AI drafts title & description on demand.
Routed to project members
Owner, due date, all the standard Forma fields.
Closed in Forma
Team works in the tool they're already in.
Status flows back
Reopen in Forma and Foreman knows about it next run.
No spreadsheets · No manual ping-pong · No lost violations
Full visibility into every check.
- DSHDashboard. Six interactive charts — violations by rule, time, folder, file type, repeat failures, time-saved.
- STAStatus workflow. Open · Acknowledged · Waived · Resolved.
- EXPExport. CSV, Excel, branded PDF with your logo.
- HUBHub roll-up. Compare projects on one chart. Spot recurring offenders.
Estimated at ~3 min per file plus ~20 min per batch report. Calculated automatically per check run.
Run checks on day one.
CATALOGUE · BUILT-INBuilt-in rule sets
ISO 19650 Naming (Full)
BS EN ISO 19650 with status & revision codes.
ISO 19650 Naming (Core)
7 core fields, no status/revision.
Basic Naming Hygiene
No spaces, no specials. Works with any standard.
Document Register Compliance
Discipline, originator, form code lists + MIDP demo.
Cross-Field Validation
Discipline-to-originator, form-to-discipline pairing.
Metadata Quality
Required fields, allowed status, freshness.
PDF Title Block Validation
Cross-validate drawing numbers and revisions between PDF zones and CDE metadata.
ISO 19650 lists
ISO 19650 Discipline Codes
ISO 19650 Suitability Codes
ISO 19650 Form Codes
Sample Originator Codes
Example MIDP Register
Clone any built-in set · Adjust patterns · Combine in one run.
Hours per project, every week — or minutes.
LEDGER · 001| TASK | WITHOUT FOREMAN | WITH FOREMAN |
|---|---|---|
| Quality checking | Manual spot checks | Automated, multi-rule-set per check |
| Naming convention | Inconsistent standards | Enforced patterns + AI regex |
| Metadata completeness | Missed fields | Required-field validation |
| PDF content | No content validation | Zone extraction + OCR + size variants |
| Pre-upload check | Check after upload only | Local file QA before pushing to Forma |
| Reacting to changes | Manual re-checks | Auto-triggers on file change |
| Time per project | Hours per week | Minutes across every project |
Stop approving documents manually. Let Foreman do it.
Automated naming, metadata, and content checks across every Autodesk Forma project — no spreadsheets, no checklists.