Forged Operations · Programs
Get a program written to the standard and handed over, check the one you already run against it, or move the whole thing onto the platform. Which of those you start with is a question about what you have today, not about which one you will need in the end.
Thirty minutes is enough to settle which framework and category apply, how much of your existing program carries over, and what it would cost.
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 the artefact all three tiers produce.
Where to start
You might have no qualified program, or one that was never written to the standard you are now held to. You might have one that works and takes three weeks to evidence. You might be ready to move the whole thing off spreadsheets. Those are three different places to start and they arrive at the same one, so the question is what you have today rather than what you will need in two years.
Forged assesses what you run today against the standard you are held to, runs the gap analysis, writes or rewrites the manuals to meet it, defines and assigns the controls, and builds the program structure around them. It is handed over at the end, not run on your behalf.
Upload the quality records and documentation you already produce. lewis reviews them against the standard, flags the gaps and the issues, and keeps monitoring between audits rather than only at them — so the team can see where attention is needed before someone else finds it.
Operational modules and workflows deployed for the work itself — document control, records, corrective actions, inspection and test plans, calibration, training, supplier qualification — with lewis reading across all of it. It touches more of the organisation than the other two, which is why it takes the longest to stand up and does the most once it has.
Build and Assure are on-ramps, not lesser products. Either one leaves you with the same requirements graph underneath, so moving to Operate later is a question of turning modules on rather than starting again.
Build · three ways to get it built
Build comes in three shapes. The program that comes out of all three is the same program, written from the same audited templates against the same requirement set. What differs is how much of the writing and reviewing you do, and that is a question about your team rather than about the standard.
Start from Forged’s CSA N299 and NQA-1 procedures and tailor them to your scope. lewis runs the gap analysis and drafts the deltas; your QA Manager holds the pen. Buy expert review as credits, only where it matters.
A fixed-scope stand-up: scoping, a Forged-run gap analysis, procedures tailored with your team in the room, expert review and a first internal audit. Stage-gated, and yours to operate when we step back.
A named Forged QA Manager writes the program, operates it through your first audit and closes the findings. For the case where hiring someone qualified in CSA N299 or NQA-1 takes longer than the order allows.
Compare
Read down the first column to find the row you actually care about. For most people it is the second one.
| Self-serve You build it | Guided , the tier most teams start with We build it with you | Managed We build and run it | |
|---|---|---|---|
| Who it is for | Teams with a QA Manager | A champion, thin QA hours | Executive mandate, no QA function |
| Who holds the pen | Your QA Manager | Your team, Forged writes | Forged’s managed QA team |
| Gap analysis | lewis, run by you | Forged-run and walked through | Forged-run |
| Program drafting | Templates plus lewis drafts | Built with your team | Written for you |
| Expert review | Bought as credits, as needed | Included in the stand-up | Independent review included |
| Internal audit | You run it on the platform | First audit run with you | Prepared, attended, closed |
| lewis | Included | Included | Included |
| Deployment | Your own isolated instance | Your own isolated instance | Your own isolated instance |
| How it is priced | Per program workspace, monthly | One-time stand-up, plus the platform | Monthly on a term, plus the platform |
| Check your readiness | Book a scoping call | Talk to us |
Quoted after a thirty-minute scoping call, because the framework, the category and the scope of supply move the number more than anything else does. There is no per-user and no per-module charge inside a program workspace; a second site or a second framework is a second workspace.
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
Pricing is quoted after a thirty-minute scoping call. The framework, the category and the scope of supply move the number more than anything else does, and all three come out of that call. What we can tell you now is the shape: self-serve is priced per program workspace monthly, guided adds a one-time fixed-price stand-up, and managed is a monthly engagement on a term.
Because a single number would be wrong for most of the people reading it. A CSA N299.4 scope and a CSA N299.1 scope are different programs, and how much of your existing procedure set carries over changes the work by a wide margin. The call is thirty minutes and you leave it with a number.
No. A program workspace covers one framework, one category and one scope of supply, and adding people or turning on more of the platform inside it costs nothing. A second site or a second framework is a second workspace.
Yes, in either direction, and the program comes with you. The requirements graph, the procedures and the records stay where they are; what changes is who does the writing and the reviewing. Most managed engagements are meant to end in a move to guided or self-serve.
One quality program: one framework, one category, one scope of supply. It holds the requirements graph, the procedures written against it and every record that answers a clause in it.
Yes. CSA N286 and CSA N299 are the Canadian standards, and ASME NQA-1 with 10 CFR 50 Appendix B are the US equivalents most reactor vendors and SMR developers work to. The four overlap heavily, which is the whole premise of the requirements graph.
Thirty minutes settles which framework and category apply, how much of your existing program carries over, which tier fits the team you have, and what it costs.
Prefer email? [email protected]