Say, Do, Prove: How a Simple Mantra Can Transform Complex Documentation

Corporate documentation often has a reputation for being a bureaucratic burden—a collection of dense manuals and binders that are disconnected from the actual work being done. It’s seen as a tedious requirement, not a strategic tool. But in the world of high-stakes manufacturing, where consistency and safety are paramount, a simple and powerful three-part mantra offers a better way to think.

This framework is surprisingly straightforward: "Say what you do, Do what you say, and Prove it." This post will explore the key lessons this philosophy teaches us about creating systems that are not only clear and consistent but fundamentally audit-proof.

1. It All Starts with a Simple Mantra

The entire philosophy of a robust Quality Management System (QMS) can be distilled into one core, repeating loop. It’s a cycle that ensures intention is translated directly into action and that every action is verifiable.

Say what you do → Do what you say → Prove it

This model is effective because it transforms documentation from a passive archive into an active cycle of commitment, execution, and verification. "Say what you do" is the promise. "Do what you say" is the execution of that promise. "Prove it" is the evidence that the promise was kept. This simple loop builds a powerful foundation for consistency and accountability.

2. Great Documentation is a Pyramid, Not a Pile

Effective documentation isn’t a random collection of files; it's a logical hierarchy where every piece has a clear purpose and place. This structure ensures that high-level strategy flows down into concrete action, and evidence flows back up to verify compliance. This system is typically organized into four distinct levels.

• Level 1: The Quality Manual (The "Say") - This is the strategic overview, the highest level of your promise. It defines the system's scope, outlines core quality policies, and describes how major processes interact. Crucially, it also contains the organization's overarching Risk management framework and defines key Responsibilities & authorities.
• Level 2: Procedures (The "Say") - These documents explain what must be done and who is responsible for carrying out major system processes. This level covers the operational backbone of the business with procedures for Design & development, Purchasing & supplier control, Change management, Nonconformity control, and the Internal audit process itself.
• Level 3: Work Instructions (The "Do") - Here, the promise becomes granular action. These provide specific, step-by-step details on how a task is performed. For example, instead of a procedure simply stating "perform heat treatment," a work instruction defines the exact Temperature range, Holding time, and Cooling method. Other examples include a Welding instruction for a specific joint, Machine setup steps, or a Packaging method for corrosion protection.
• Level 4: Records (The "Prove") - This is the objective evidence that everything was done according to the rules. These aren't just random forms; they are categorized proof.
• Quality System Records: Training records, Audit reports, Management review minutes.
• Manufacturing Records: Material certificates, Traceability logs, Production travelers, Welding logs, Inspection reports.
• Improvement Records: Nonconformance reports, Root cause analysis, Corrective actions.

The power of this pyramid structure is its logic and traceability. It creates a clear line of sight from top-level corporate policy all the way down to a specific action taken on the shop floor, with a clear trail of evidence to support it.

3. The Stricter the Rules, the Higher the Stakes

At first glance, this level of documentation might seem overly rigid. However, the strictness of a quality system is directly proportional to the risk involved. A general-purpose standard like ISO 9001 has different requirements than a specialized one like API Q1, which governs manufacturing for the oil and gas industry.

The API Q1 standard is more rigid for critical reasons: it governs high-risk processes where failure can have catastrophic consequences. The system absolutely requires traceability to know the full history of every component, and it must provide irrefutable proof of conformity to support any potential failure investigations. This principle demonstrates that documentation isn't about control for its own sake; it's a critical tool for managing risk.

4. Failure Hides in the Smallest Details

While the system is strategic, audits and operational failures often happen at the ground level due to surprisingly basic mistakes. A brilliant system on paper is useless if it isn't maintained and followed meticulously in day-to-day operations.

Common documentation pitfalls often include simple but critical errors:

• Uncontrolled documents being used on the shop floor
• Outdated work instructions that no longer match the process
• Incomplete inspection records with missing signatures or data
• Poor traceability making it impossible to track a part's history
• Missing records of required risk assessments

To counteract these common failures, the API Q1 framework emphasizes simple, actionable best practices. The focus is on keeping documents simple and usable, training staff thoroughly on the procedures they use, and conducting regular reviews to ensure everything stays current. This highlights a crucial reality: the strength of the entire system depends on the integrity of its smallest, most routine parts.

Conclusion: From Burden to Bedrock

When viewed through the "Say, Do, Prove" lens, a well-structured documentation system is no longer a business burden. It becomes the very bedrock of consistency, reliability, and continuous improvement. It provides a framework where clarity flows from the top down, from strategic policy to specific action, and proof flows from the bottom up, from verifiable records back to the original promise.

How could the "Say, Do, Prove" model bring more clarity and accountability to your own work?

Share This Article

Found this useful? Share it with your network: