Standard operating procedures are the documents buyers name most plainly. micro1’s data page lists SOPs and process documentation among the material it takes. That makes them the natural place to start if you want to sell company documents, and the natural place to get redaction right, because a procedure is written to be followed by people who know who “Dana in receiving” is.
Why do SOPs need redacting at all?
An SOP describes a process, but it is written inside a company. It names the person who owns it and the person who signs off. It tells the reader which supplier to phone and on which number, which shared drive holds the log, and sometimes which password opens the portal. None of that teaches a model anything about the process. All of it identifies people or opens a door.
Buyers de-identify too. Scale AI does it on the company’s own systems ahead of extraction, and the first thing on its excluded list is the identity of employees and customers. micro1 describes its own process for transforming sensitive material. Nyne promises de-identified data at release. Treat every one of those as a backstop, never as permission to skip your own pass.
What comes out first?
Work in three groups, in this order. The order matters because each group is easier to find once the one before it is gone.
People
- Owner, author, reviewer and approver names, including first names and initials.
- Employee IDs, extensions, direct phone numbers and email addresses.
- Supplier and customer contact names and numbers in escalation steps.
- Photos or screenshots with faces, badges or name tags in frame.
Access
- Passwords, shared logins, PINs and door codes, which turn up in setup and opening steps more often than anyone admits.
- API keys, tokens and VPN details.
- Internal hostnames, IP addresses, file paths and links to internal tools.
Accounts
- Customer account numbers and site addresses.
- Prices, discounts or contract terms tied to a named customer or supplier.
- Bank details in payment or refund steps.
What does a clean SOP step look like?
Replace, do not just delete. A step that reads “Call [removed]” is broken. A step that reads “Call the supplier’s account manager” still teaches the process.
| Before | After |
|---|---|
| Owner: first and last name, Operations | Owner: Operations lead |
| Phone the supplier’s named rep on a direct line | Phone the supplier’s account manager |
| Log it in a named shared-drive path | Log it in the receiving variance log |
| Tag a colleague’s handle for approval | Send to the shift supervisor for approval |
| Portal login written into the step | Sign in to the supplier portal |
Use the same replacement for the same person or system every time. A buyer can then still see that the same role approves three different procedures, which is part of what makes a set of SOPs useful.
Where do names hide after the text is clean?
This is where most first attempts fail. The body of the procedure is spotless, and the file still identifies half the team.
- Comments and suggestions. Google Docs, Word and Confluence keep comment threads with the commenter’s name. Resolve and delete them, or export in a format that drops them.
- Version history. Every past revision carries an author. Unless a buyer has asked for history and you have cleaned it too, license the current version only.
- File metadata. The “author” and “last modified by” fields in Office files and PDFs. Clear them in bulk before export.
- Headers and footers. Revision blocks often list who changed what, and when.
- Embedded files. A spreadsheet pasted into a procedure brings its own sheet of names.
How do you find all of it in a few hundred documents?
By machine first, by person second.
- Pattern search for anything with a shape: email addresses, phone numbers, Social Security and employee ID formats, card and account number formats, IP addresses, keys and internal domain names.
- List matching for names. Export your HR roster and customer list and search for every entry, including first names on their own.
- A human read of a random sample, 2% to 5% of documents, by someone who knows the business. They catch the indirect ones: “the Tulsa account,” “the night-shift incident in March.”
Record what you removed and how. If a buyer asks how the set was cleaned, a one-page method note answers the question and shortens the review.
What should not be in the set at all?
Some SOPs are not yours to license, however clean they are.
- Procedures written for a client under a services contract usually belong to the client.
- Procedures copied from a supplier’s manual or a paid template library belong to their authors.
- HR procedures that consist of case notes about individuals are about people, not process.
Drop these before redaction starts. It saves the work, and it keeps the set clear of claims you cannot back.
Does redaction change what the SOPs are worth?
It can raise it. A buyer’s own de-identification costs it time, and a set that arrives clean, consistent and documented is quicker to accept. micro1’s stated payment window opens at acceptance and runs 30 days, so a quicker review brings the money forward.
What redaction cannot do is turn a thin set into a deep one. Fifty one-page checklists are still fifty one-page checklists. The full redaction guide covers the other document types, and the order to work through them.
The cleanest procedure in the building is the one that still works after every name in it is gone.