Programs · Managed QA
Forged’s managed QA team writes the program, runs it on the platform through your first audit, and stays on to operate it. You get a qualified program and a named QA Manager accountable for it from month one, at the point where hiring one would take longer than the opportunity allows.
Limited to a small number of concurrent engagements so the team stays qualified and available. Stage-gated: billing stops if you stop at a gate.
How it works
You bring the mandate and the order. We bring the people, the templates and the platform. Four stages, each one a gate you can stop at.
The managed QA team writes the QA program description and every procedure and form under it, scoped to your first nuclear order. Nothing is written speculatively: the requirement set comes from the framework and category that order actually names.
Training and qualifications, corrective actions, document control and records run on the platform from day one, with lewis reading each record as it lands. You see the same coverage number we do, because there is only one.
We prepare the audit package, sit in the audit with you and close the findings. The package is exported from the records rather than assembled for the occasion, which is what makes the second audit cheaper than the first.
Keep the team on an operate-mode retainer, or move to the guided or self-serve tier with the program intact. The graph, the procedures, the records and the history stay with you either way.
One requirements graph
Because Forged operates the program on the platform, you see the same coverage number we do. Nothing lives in a consultant’s inbox. When the engagement changes shape, the graph, the records and the history stay with you.
Illustration of a coverage matrix for CSA N299.3, pressure piping fabrication: 96 clauses covered, 31 partial, 15 missing. Five clause rows are shown. 4.2 quality program documentation and 4.4 document control are covered by an existing procedure. 4.9 nonconformance and corrective action and 4.11 procurement and supplier control are partial, each with a delta drafted. 4.14 internal audit is missing, drafted from a template. The panel is headed as run by the Forged QA team.
lewis · expert review
The team writing your program is not the team reviewing it. An independent qualified reviewer signs every issued procedure, and the attestation sits in your ledger alongside the records it covers. lewis drafts and flags throughout, and a person accepts every draft.
Every review carries the reviewer’s name and their own qualification record, and the reviewer is never the author.
The sign-off is stored in the same ledger an auditor will ask to see, alongside the procedure it covers.
lewis finds gaps and proposes drafts. A person accepts or overrides, and the acceptance is what gets recorded.
Who this is for
Managed is the right tier when the constraint is people rather than knowledge or hours.
Monthly on a term, plus the platform.
Quoted after a scoping call, and it steps down to an operate-mode retainer once the first audit is passed.
The team writing your program is never the team reviewing it. Independence between author and reviewer is a requirement of the standards, not a courtesy, and it is the reason managed carries its own reviewer rather than billing reviews as credits.
The other two tiers
Same templates, same requirements graph, same lewis, same expert review. The only thing that changes is who holds the pen.
Start from the audited template library and tailor it to your scope. lewis runs the gap analysis and drafts the deltas; your QA Manager holds the pen and buys expert review only where it matters.
A fixed-scope, stage-gated stand-up. Forged does the writing and the reviewing, your team makes every decision in the room, and the program is yours to operate when we step back.
Compare all three side by side — who holds the pen, what is included in each, and how each one is priced.
Built by operators, in production with
Built by engineers out of Ontario Power Generation, so the program it stands up is the one the organizations running the audits expect to see. Each customer runs its own isolated instance, in our cloud, in yours, or on-premise and air-gapped. SOC 2 Type II certified — request the report.
Questions
A team. A named Forged QA Manager is accountable for your program, sits in your audits and closes the findings. The difference from consulting is that the work runs in your instance, on your records, so nothing lives in a consultant’s inbox and nothing needs handing over.
Either keep the team on an operate-mode retainer, which costs less than the stand-up months, or move to the guided or self-serve tier with the program intact. The requirements graph, the procedures and the records stay yours in every case.
Managed is quoted as a monthly engagement on a term, with the platform priced separately per program workspace. It is stage-gated: billing stops if you stop at a gate. We quote after a scoping call because the scope of supply and the audit date both move the number.
The team has to stay qualified and available to the clients it already has. We run a small number of managed engagements at a time rather than hire ahead of the work, so a start date depends on capacity in the quarter you need.
No, it is the intended path. Your hire arrives to an issued program, a populated records ledger and an audit already passed, instead of a blank page. Moving to guided or self-serve at that point is a change in who holds the pen, not a migration.
We will tell you which framework and category apply, what the stand-up would cover, and whether we have capacity to start this quarter.
Prefer email? [email protected]