If you can't document it, you can't expect it

I recently got called in to take a look at a couple of distribution centers for a major plumbing and HVAC distributor. It was a pretty common request: "Will, give us your take. What do you see that we might be missing?" One of the first things I always ask for is simple: "Show me your documented processes and procedures."

Crickets.

At both sites, there were no formal SOPs. A few handwritten notes were taped to a workstation here and there, and maybe a tribal cheat sheet was passed between shift leads. But nothing structured, nothing official, nothing that would survive turnover or a tough audit.

Let me be blunt: if your goal is to deliver a consistent, positive customer experience, and in this industry, that should be the goal, then your internal processes must be just as consistent. And that only happens with documented, standardized, and regularly updated procedures.

The hidden cost of missing documentation

In the plumbing and HVAC industry, speed and accuracy matter. Contractors are counting on you to get that part delivered before the next job starts. If you can’t deliver on time, or worse, send the wrong item, you’re costing them time, money, and trust. And they don’t forget.

When warehouse processes are undocumented, what you're really doing is leaving execution up to chance. One shift might put away inventory one way, and the next shift another. One person picks using the RF gun menu, the other just memorizes where things are. When it works, it’s luck. When it fails, it’s chaos.

Documentation = fairness

Let me tell you what documentation really is: it's fairness.

When you write down exactly how a task is supposed to be done, step by step, with screenshots, system navigation, and safety checks, you’re not just covering yourself; you’re protecting your people. You’re giving them the tools to succeed and the clarity to know what's expected.

And when something goes wrong, and eventually, it will, you’re not flying blind. You’ve got a clear playbook. You can coach, retrain, or hold people accountable because you can point to what they were taught.

Change is inevitable. Documentation makes it sustainable.

Processes evolve. They should. Maybe you find a better way to stage outbound pallets or reduce steps in your quality check. Great. But if it’s not documented and version-controlled, your team won’t know what changed or why.

I always recommend a centralized process documentation strategy with version tracking, simple tools like SharePoint, Notion, or even a shared Google Drive can go a long way. Just make sure everyone knows where to find the latest version and when it was updated.

A real example: Plumbing parts gone wrong

At one of the DCs I visited, they were struggling with mis-picks of similar-looking parts, different fittings, same basic shape. Some SKUs were off by a fraction of an inch or had near-identical part numbers. Without a documented receiving and putaway process, the team was shelving parts incorrectly. And since there wasn’t a defined way to verify bin locations, the errors didn’t get caught until the wrong product showed up at a job site.

One customer lost a full day of work, and let’s just say they weren’t shy about calling it out.

After we walked the floor and reviewed the gaps, the VP of Operations pulled me aside and said, “Will, you’re right. We have to do the simple things like blocking and tackling before we can run those trick plays.” That mindset shift made all the difference.

5 elements of a great SOP

Want to build Standard Operating Procedures (SOPs) your team will actually use? Make sure they include:

1. Clear title and purpose
   Call it what it is: no fluff. Instead of something vague like “Refunds,” go with “Processing Customer Refunds in CRM System.” Right away, people know what they’re looking at. Your purpose should answer why this process exists and why it matters. For example, “To make sure refunds are handled the same way every time so we protect customer satisfaction and stay in compliance.” Also include who should use it, when, and in what situations. This isn’t just a formality, it helps people know they’re in the right place.
2. Step-by-step instructions
   Give people the exact steps, in order, like you’re walking them through it in person. Start each one with an action word, Click, Scan, Enter, Verify. Skip the jargon unless you’re going to explain it. For bigger jobs, break it into chunks: Setup, Do the Work, Verify It’s Done. Include what success looks like after a step is done, like “You should see a confirmation pop-up.” If it’s a task that happens often, put it in checklist form so they can run through it fast and clean.
3. Visual aids
   Screenshots, flowcharts, annotated pictures, whatever gets the point across. Show, don’t just tell. If there’s a specific screen in the WMS where people get confused, drop a screenshot right next to the step. If your process includes equipment, snap a photo of how it’s supposed to look. And when systems change, so should the visuals. Don’t let people follow outdated images.
4. Version control
   Make it clear when this SOP was last touched, who approved it, and where the official version lives. Add a version number like v2.1, and keep a short log of what changed and why. That way, when someone asks, “Why did we start doing it this way?” you’ve got the answer. Assign a process owner so everyone knows who to go to for questions or fixes.
5. Common pitfalls & tips
   You already know where people mess this up, so get ahead of it. Add quick reminders like “Don’t confuse SKU 523A with 523B, they look almost identical” or “Save progress every 10 minutes or the system logs you out.” Include quick troubleshooting steps too, like “If the scanner won’t sync, reboot and retry before calling IT.” Help your team win by giving them guardrails.

Additional elements to strengthen SOPs

• Roles and responsibilities
  Clearly define who is responsible for each step or phase of the process. For example, “The Warehouse Lead verifies inventory counts, while the Shift Supervisor submits the final report.” This eliminates confusion about ownership, especially in cross-functional processes. For complex SOPs, include a RACI chart (Responsible, Accountable, Consulted, Informed) to map out roles visually.
• Resources and tools
  List all tools, software, or materials needed to complete the procedure upfront (e.g., “Requires access to CRM software, a scanner, and Form XYZ”). Provide links to templates, forms, or login pages, and note any prerequisites, like training or permissions. This ensures users are fully equipped before starting and reduces delays from missing resources.
• Feedback mechanism
  Include a way for users to report issues or suggest improvements, such as a link to a feedback form or an email for the process owner. For example, “If this SOP is unclear or outdated, submit feedback via [link].” This keeps the SOP alive and evolving, ensuring it reflects real-world use and stays relevant as processes change.

Use generative AI to accelerate SOP creation

I get it—writing SOPs is tedious. It’s often nobody’s favorite task. But here’s the good news: generative AI tools like ChatGPT can help you build solid first drafts quickly. Feed the system your current workflows, software screenshots, and objectives, and it can lay out structured documents you can then tailor and train against.

You still need people to verify and walk the process, but AI helps speed up the grunt work.

Try this prompt to jumpstart your SOP:

"Write a step-by-step Standard Operating Procedure for [insert task here, e.g., 'receiving plumbing inventory into warehouse management system']. Include a clear purpose, scope, numbered instructions, and key visuals. Use concise language suitable for warehouse staff and include any common mistakes to avoid."

This prompt works great whether you're building from scratch or refining a process that's been stuck in someone’s head for years. It’s often nobody’s favorite task. But here’s the good news: generative AI tools like ChatGPT can help you build solid first drafts quickly. Feed the system your current workflows, software screenshots, and objectives, and it can lay out structured documents you can then tailor and train against. Security note: check with your IT group before putting sensitive information into a large language model, ensure your company data is secure first!

You still need people to verify and walk through the process, but AI helps speed up the grunt work.

Train everyone the same way

From receiving to putaway, cycle counting to shipping, everyone should be trained on the same process, the same way, from the same documentation. That way, you're not relying on institutional knowledge or hoping someone “remembers how Dave does it.”

Train consistently, then audit consistently. If someone deviates from the process, you’ve got the foundation to retrain or take corrective action fairly, and more importantly, constructively.

In our industry, our reputation is only as good as our last order. If you want consistency in customer experience, you need consistency in execution. And consistency in execution starts with documentation.

So, next time someone asks, "How do we do it here?" don’t just point. Hand them the playbook.