Your employees don't care whether your Code passes an audit.
They care whether it answers the question they actually have, in the moment they have it. A Code is only as good as whether people read it, understand it, and can act on it. That's a higher bar than most organizations build to. It's the one I build to.
I start by telling you what's worth keeping.
Most Code rebuilds begin by throwing the old one out.
That's expensive, and it's usually wrong. Your Code may have real problems—structure, language, the fact that no one can find anything in it—without being a total loss.
So I read what you have first. If a Compliance Edit already flagged your Code, this is where that gets fixed. If it didn't, we start with a focused read of the Code itself. Either way, you get the same thing before you spend a dollar on the rebuild: an honest account of what works, what doesn't, and what's actually worth rebuilding.
What makes a Code worth using
When an employee opens your Code, they're not asking whether it satisfies a regulator, a lawyer, or an auditor. They're asking something more immediate.
Can I find the thing I need?
Do I understand it?
Do I know what to do next?
If the answer to any of those is no, you've lost them and the Code becomes a document your organization has, not one it uses.
Every Code I build is designed to pass that test:
Plain language, not legal boilerplate dressed up in your brand colors
Structure that maps to how people actually look things up
Role-relevant guidance, so the answer someone needs is the answer they find
A document people can get in and out of quickly, with the answer in hand
A leadership message that sets tone from the top and reads like a person wrote it
That last one matters more than most people think.
The half your employees never see.
A Code that reads well but contradicts your policies—or skips a topic they cover—is a liability with good typography. So while I'm making it usable, I'm making sure it's aligned: reading the Code against the policies you already have, flagging where they don't match, where something's buried, and where an important topic has no home at all.
Think of it as a second set of eyes on how your Code and your policies fit together. That work turns things up: a policy your Code references that doesn't actually exist, a topic your policies address that the Code leaves out. You get those flagged as we go — a running list of what the build surfaced, so the gaps become visible instead of staying buried. Rewriting the underlying policies is a separate engagement; here, the deliverable is a Code that's honest about where things stand.
How it works
Every Code engagement is flat-fee and scoped to your organization — its size, risk profile, and the state of what you already have. No hourly billing, no surprises. You'll know the number before we start.
Starting at $14,987.
You're not paying for a document. You're paying for a Code your people use.
Start with a read.
Send me your current Code — or tell me you're starting from scratch — and I'll tell you what it needs.