I help manufacturers build ISO 9001 systems that stay practical on the shop floor.
I’m Joe Robak, and I built IronClad ISO around a simple standard: an ISO system should help a manufacturer stay organized, pass audits, and keep production moving. It should not turn into binder-driven bureaucracy that nobody wants to maintain six months later.
Who I work with
My work is focused on machine shops, fabricators, contract manufacturers, industrial suppliers, and other operations that need ISO 9001 support in a real manufacturing environment where production still has to move.
What clients usually need
Gap assessments, lean QMS development, internal audit preparation, management review readiness, corrective-action discipline, and support getting through registrar audits without chaos.
What I am trying to prevent
Overbuilt documentation, weak ownership, thin records, audit surprises, and systems that technically exist but never become part of the daily operating rhythm.
Why manufacturers call me
Most companies that contact me do not need someone to dump a generic package of templates on the operation. They need someone who can look at how orders are reviewed, how documents are controlled, how inspection and calibration records are handled, how nonconformances are addressed, and how management review actually happens — then turn that into a cleaner, registrar-ready system.
That is how I work. I start with the real operation, not a canned toolkit. I look for what the company already does well, where ownership is weak, where evidence is thin, and where documentation is heavier than it needs to be. From there, I help build a system that matches the business instead of fighting it.
Clients usually reach out when customer pressure is rising, an audit date is getting closer, internal ownership is unclear, or the current system feels bloated and hard to maintain. My goal is not to make a manufacturer dependent on a consultant. My goal is to help leadership get control, create a system the team can actually use, and leave the operation stronger than it was before the project started.
How I think about the work
I care about clear ownership, usable procedures, strong records, practical training, and audit evidence that holds up when someone external starts asking questions. A good ISO system should make responsibilities clearer. It should make problems easier to spot. It should make audits calmer. It should not create more confusion than it solves.
That is also why I keep the work lean. Manufacturers already have enough to manage between production, customers, scheduling, purchasing, suppliers, maintenance, and staffing. The quality system has to support those realities. If it only works on paper, it is not a strong system.
1Assess the current state
I review documentation, records, process ownership, and the current operating rhythm to see what is already strong and what still needs structure.
2Build what the company actually needs
I help create lean procedures, forms, and controls that reflect the real workflow instead of forcing a generic system onto the team.
3Put the system into use
The work moves past documentation into implementation, training, and records generation so the company has real evidence before the audit window opens.
4Prepare for the audit
I help tighten internal audit activity, management review, corrective actions, and audit-day readiness so the registrar review is structured and predictable.
