Automated quality checks and cross-cloud delivery for construction.

All file types are supported for metadata-based rules — naming convention, required metadata, allowed values, file format, freshness, list validation, numeric range, register cross-reference, and segment consistency checks work on any file in your CDE. PDF files are additionally supported for content extraction using zone templates with text-layer parsing and OCR.

A validation list is a reusable set of approved values you create once and reference from multiple rules. For example, store your project's approved discipline codes, originator codes, or your full MIDP/TIDP deliverables register as a list, then use it in List Validation or Register Cross-Reference rules. Lists are tenant-scoped so your whole team can share them, and you can paste values from Excel or type them directly.

Use the Register Cross-Reference rule. Upload your MIDP/TIDP register as a validation list (paste from Excel — one document number per line), then point the rule at your project folders. Foreman flags both missing files (in the register but not on disk) and unexpected files (on disk but not in the register), so you get a complete completeness picture at any milestone.

You define rectangular zones on a PDF page using the visual zone editor. Foreman downloads the PDF, extracts text from each zone using PdfPig for native text layers and Tesseract OCR for scanned documents, then compares the extracted text against your rules.

Yes. Foreman uses Tesseract OCR to extract text from scanned PDFs and images within PDF zones. 15 languages are supported including English, German, French, Spanish, Italian, Portuguese, Dutch, Polish, Czech, Swedish, Norwegian, Danish, Finnish, Turkish, and Romanian.

Configure a check to run on a recurring schedule using the visual schedule picker — hourly, daily, weekly, or monthly with day-of-week toggles and timezone support. Foreman runs the check automatically and sends email notifications with a summary of pass/fail results and violation counts.

Create an auto-trigger in the Triggers tab to listen for file uploads or modifications in your Autodesk project. When the event fires, Foreman automatically runs a QA check against the configured folders and rule set. Smart debouncing groups batch uploads into a single check to avoid duplicates. Auto-triggered runs appear in your History with a "Webhook" badge, and you can generate reports on-demand. Available on Business plans and above.

Yes. Every violation can be marked as Open, Acknowledged, Waived, or Resolved. You can re-run checks on failed files, export results to CSV or Excel, and track compliance trends over time on the dashboard.

Failed files are tracked as violations with detailed information including the rule that failed, expected vs actual values, and a zone preview for content rules. Each violation can be moved through a status workflow: Open, Acknowledged, Waived, or Resolved.

Yes. Select multiple rule sets and they all get evaluated together against every file. For example, combine an ISO 19650 naming rule set with a custom content-match rule set — both run in a single pass. In per-folder mode, each folder can have its own combination of rule sets, so architectural folders get architectural naming plus content rules while structural folders get a different mix.

Yes. Toggle per-folder mode to assign different rule sets and zone templates to each selected folder. Architectural folders get architectural naming rules, structural folders get structural rules — all validated in a single check run. Subfolders inherit their parent folder's assignment. Results show which rule set was applied to each file.

Create size variants of a zone template — one per sheet size (A0, A1, A3, ARCH D, etc.). Upload a sample PDF of that size and zones are copied from the parent with anchor-based repositioning, keeping title blocks pinned to the correct corner. During checks, each file is automatically matched to the right variant by page dimensions. If multiple variants share the same size, Foreman scores zone content coverage to pick the best fit.

Yes. Generate branded PDF reports with a configurable cover page, executive summary, health score trends, violations by rule and folder, detailed file results, and extracted content. Upload your company logo, customize the title, and choose which sections to include. Reports are downloadable with clickable links to files in Forma.

No. Foreman includes seven built-in system rule sets covering all 12 rule types: three naming convention sets (ISO 19650 Full, Core, and Basic Hygiene), Document Register Compliance (discipline/originator/form code validation with MIDP demo), Cross-Field Validation (conditional discipline-to-originator pairing), Metadata Quality (required fields, allowed values, freshness), and PDF Title Block Validation (content match, regex, extraction). Five ISO 19650 validation lists are also included. Clone any built-in set to customize — you can be running quality checks within minutes of signing up.

Rule sets are scoped to your tenant (organization). Any user within the tenant can use shared rule sets to run checks against their projects, ensuring consistent quality standards across the team without duplicating configuration.

Yes. You have three options. Switch to the Local Files tab on the Run Check page to upload files directly from your machine — drag and drop PDFs, DWGs, IFCs, or any other file type. Sign in with Microsoft 365 and run the same QA checks against a SharePoint site, library, or folder. Or sign in with Box and run them against a Box folder. All paths use the same rule sets, the same zone templates, and produce the same dashboards and reports.

Yes. Sign in with Microsoft 365, browse your SharePoint sites and libraries inside Foreman the same way you'd browse Forma folders, and run a QA check directly against a SharePoint folder. Same rule sets, same PDF zone templates, same OCR (15 languages), same dashboards, same branded PDF reports. SharePoint runs and Forma runs sit side-by-side in your check history.

Yes. Sign in with Box (OAuth — no admin consent needed; the app is already approved on the Box App Console), browse your Box folder tree the same way you would browse Forma folders, and run a QA check directly against a Box folder. Same rule sets, same PDF zone templates, same OCR. Foreman writes verdicts to a shared foremanQa Box metadata template, and violations can be pushed as Box Tasks on each source file.

Yes. The push dialog lets you choose any destination — Forma, SharePoint, or Box — regardless of where the file came from. Per-file decisions are explicit: a name that matches an existing file in the destination becomes a new version; a unique name becomes a new item, and you see the decision before pushing. Custom attributes (ACC custom attributes, SharePoint site columns, or Box metadata template fields) are filled from PDF zone values, filename segments, or carried over from the source. Auto-push on pass works on every cloud.

Naming convention, file format, PDF content match, content convention, content extraction, list validation (filename or PDF zone source), numeric range, register cross-reference, and segment consistency rules all work with local files. Metadata-dependent rules (required metadata, allowed values, freshness) are automatically skipped since Forma custom attributes are not available for local uploads.

Yes — files uploaded for local checks are retained so you can re-run rules against them, view violations in context, and regenerate reports without re-uploading. Retention is admin-controlled at the tenant level: your team sets how long local uploads stick around before they're purged, and a scheduled cleanup job enforces the policy automatically. ACC, SharePoint, and Box files are not stored — content streams through memory for QA extraction and is never cached.

Foreman estimates manual QA review at ~3 minutes per file (opening, checking naming/metadata/title blocks, logging results) plus ~20 minutes per batch for report generation. Time saved is the difference between this estimate and Foreman's actual check duration.

Yes. The 14-day free trial on the Business plan includes all QA features — naming, metadata, format, and content rules, AI regex builder, OCR in 15 languages, PDF zone extraction, CSV/Excel export, branded PDF reports, scheduled checks, and priority support. No credit card required.