Working together

How I work

Most people who call me are somewhere between “we should write this down” and “we have an audit in six weeks.” Either way the questions are the same: what it costs, how long it takes, and what you have to do. Here are the answers before you have to ask for them.

Two ways to engage

Either way, start small. Most first projects are one line, one department or a single program, so you can see the work before committing to anything larger.

What it costs

Whatever the size, you get a fixed number in writing before I start. I do not bill surprises, and I do not bill for the first conversation.

What I need from you

Half a day on your floor, or a video walkthrough with the operator and a handful of phone photos if you are not in driving range. Either way, one person who knows the job well enough to correct me. That is genuinely it.

I do the writing. Your people review and sign off, because a procedure nobody on the floor has approved is a document, not a control.

Confidentiality

Working with one person instead of a firm

You get the person who does the work, every time. No account manager, no handoff to a junior writer, nobody new to re-explain your process to.

The trade-off is capacity. If I am booked I will tell you that rather than string you along, and I will give you a date.

I also come to you. Central Arkansas is inside a morning’s drive, and I would rather watch the job once than trade twelve emails about it. Further away, the operator walks me through it on video and someone sends phone photos of the machine and the current paperwork.

Questions people ask before they email

We are not in Arkansas. Does that work? Yes. Most of the work is the interview and the writing, not the drive. A remote job starts with a video call and whatever already exists: previous documentation, photos, CAD models, working files. The operator walks me through the job on video, and we run a review cycle on shared source files until your people sign it off.

You have never run our machine. How do you learn it? The same way a new hire does, faster: I watch it done, ask the operator what the procedure leaves out, and write the version he would sign his name to. He corrects me until it is right.

What do we actually get? Whatever format you work in. Word and PDF in your template and numbering, a clean starter template if you do not have one, or HTML, Markdown, Confluence and version-controlled pages in GitHub if that is where your documentation lives.

Who owns it? You do, outright, the day you pay the invoice. I keep nothing.

How many rounds of changes? Two rounds are included, and most procedures are right on the second pass because the operator was in the room for the first. Anything beyond that is quoted before I start it.

How long does one procedure take? About three days from the walkthrough to a document your people can sign off. A full package, a department, a safety program or a system, runs from weeks to months, and the range comes with the quote.

Do you take the photos? Either. I take them when I am on site; for remote jobs your people take them with a phone and I say what I need.