For · QA/QC Managers
Stop spot-checking. Start proving compliance.
Manual QA means opening files one by one and hoping you catch everything. Foreman runs automated checks on a schedule, tracks every violation from Open to Resolved, and gives you the dashboard your auditors actually want to see.
14-day trial · Full access · No card on file
Sample project — example data.
PORTFOLIO HEALTH
Last 30 days
VIOLATION #412 — Title-block rev mismatch
Scheduled · Nightly 02:00
Export audit PDFManual QA · Breaks down
Questions you shouldn't answer from memory.
!Pain · 01
"When did we last run QA on Project X?"
You shouldn't have to answer that from memory, and the auditor shouldn't have to wait while you dig through emails to find out.
!Pain · 02
No audit trail between Open and Resolved.
A violation gets flagged, someone fixes it in Forma, nobody records what happened. When it recurs next month, there's no record to learn from.
!Pain · 03
Pass rates vary by project, and nobody sees the pattern.
Project A is 98% compliant, Project B is 72%. Without a dashboard, you won't spot the trend until the client does.
!Pain · 04
The auditor wants evidence. You have a spreadsheet.
Proving checks were performed is its own job. A branded PDF with cover page, scope, methodology, and findings is what they actually want — and you don't have time to build it manually.
12
Rule types
10
Report sections
Every night
Scheduled unattended
Full audit
Open → Ack → Resolved
How Foreman · Handles it
Automation, audit trail, evidence pack.
Everything a QA manager needs to stop firefighting and start showing the pattern.
Scheduled QA checks with execution history
Set a project to run QA nightly, weekly, or before every milestone. Every run logs what was checked, how long it took, how many files passed, and what failed. When someone asks "when did we last check?", the answer is one click away.
See scheduled jobsViolation status workflow with audit trail
Every violation moves Open → Acknowledged → Waived → Resolved, timestamped and attributed. You get a full history of who did what and when — for every issue, on every project.
See violation workflowDashboard with status, trend, and violations-by-rule
A status donut, a health trend line over time, and a bar chart showing which rules fail most often. Spot the pattern without opening a single file.
See dashboardBranded PDF reports (10 configurable sections)
Cover page, scope, rule set summary, health score, violations by rule, violations by folder, detailed findings, methodology — or any subset. QuestPDF-rendered, logo-ready, auditor-ready. Export from the run, email it to the client.
See PDF reportsPush violations directly to Forma Issues
Findings that need a designer's attention don't belong in a spreadsheet. One click creates Forma Issues with the file, the violation, and — optionally — AI-drafted issue descriptions. They land where work actually happens.
See Forma Issues integrationStale files + storage analytics
Find WIP files that haven't been touched in 90 days. Identify abandoned folders. Catch storage creep before it becomes a procurement conversation.
See storage analyticsEvidence packs on a schedule
Monthly client digests. Quarterly audit packs. An Attribute Extract nightly to Excel. Foreman's scheduler lines up the exports and reports you need, delivers them to your inbox, and keeps a history you can show later.
See Attribute ExtractFAQ · Questions from the field
Questions QA managers ask.
Q · 01
What happens after the 14-day trial?
Nothing automatic. We don't ask for a credit card up front, so we can't charge you without you doing anything. On day 15 your account goes read-only — your rule sets, check history, and violation workflow stay intact for 30 days while you upgrade, request an extension, or export.
Q · 02
How much does it cost?
Every plan includes a 14-day free trial with no card on file. See the full pricing breakdown on the homepage — Business is the plan most QA managers need, since it adds scheduled checks, branded PDF reports, Forma Issues push, and the Foreman Assistant (which works in Claude, Cursor, and Copilot too).
Q · 03
How do I get audit evidence out if we cancel?
Every workflow exports. Check runs and violation history export to CSV, XLSX, and branded PDF. Rule sets export to JSON. On cancellation you can trigger a full account export and we send the zip within 24 hours — your audit trail comes with you.
Q · 04
How do I keep different projects from stepping on each other's rule sets?
Rule sets are tenant-scoped — all users on your account can share them — but each project can run a different combination. You can even assign different rule sets to different folders within one project (WIP vs. Shared vs. Published).
Q · 05
Can I waive a violation without deleting it?
Yes. Violations move through Open → Acknowledged → Waived → Resolved, each timestamped and attributed. Waived means "we know, we accept it, don't flag it again" — which is exactly what auditors want to see documented.
Q · 06
What happens to the findings? Can my designers see them?
Push violations to Forma Issues with one click. File, location, violation description — optionally AI-drafted — all land in Forma where the designer is already working. No copy-paste, no forwarded spreadsheets.
Q · 07
Do I need to know regex to write rules?
No. The AI regex builder takes example filenames and generates the pattern for you. Twelve rule types cover naming, metadata, content, register compliance, cross-field validation, and more — most don't touch regex at all.
Free resource · QA managers
ISO 19650 QA Rule Pack
Importable JSON with the ISO 19650 full + basic rule sets and matching validation lists — ready to drop into Foreman or reference as-is.
The checks will happen either way.
Choose whether you run them — or the auditor does.
14-day trial · Full access · No card on file
ISO 19650 rule pack
JSON. Importable. Immediately useful.