Quad Pattern
A documentation pattern using four complementary document types: rules, processes, requirements, and references.
Also known as: Rule-Process-Requirement-Reference pattern, RPRR pattern
Category: Frameworks
Tags: documentation, governance, frameworks, knowledge-management
Explanation
The Quad Pattern is a documentation and governance pattern that organizes knowledge and controls into four distinct but complementary document types: **Rules**, **Processes**, **Requirements**, and **References**. Together, these four elements create a comprehensive framework for managing how work is done, what standards must be met, and where to find authoritative information.
**The four components**:
1. **Rules (Policies)**: Mandatory constraints that define what must or must not be done. Rules set boundaries and non-negotiable standards.
- Example: 'All production deployments must be approved by two engineers'
- Example: 'Customer data must be encrypted at rest'
2. **Processes (Procedures)**: Step-by-step instructions for how to accomplish tasks. Processes describe the 'how' of work.
- Example: 'Deployment procedure: 1. Create release branch, 2. Run test suite, 3. Get peer review...'
- Example: 'Incident response procedure: 1. Acknowledge alert, 2. Assess severity...'
3. **Requirements (Specifications)**: Detailed criteria that deliverables must satisfy. Requirements define what 'done' looks like.
- Example: 'The API must respond within 200ms at the 95th percentile'
- Example: 'The system must support 10,000 concurrent users'
4. **References (Resources)**: Supporting materials, standards, and knowledge bases that provide context and guidance.
- Example: 'ISO 27001 security standard'
- Example: 'Architecture decision records (ADRs)'
**Why the Quad Pattern works**:
- **Separation of concerns**: Each document type serves a distinct purpose, reducing confusion
- **Completeness**: Together, the four types cover the full spectrum of 'what, how, why, and where'
- **Maintainability**: Changes to one type don't require rewriting others
- **Traceability**: Requirements link to rules (why), processes (how to verify), and references (context)
- **Governance**: Clear mapping between constraints (rules), execution (processes), outcomes (requirements), and knowledge (references)
**Applying the Quad Pattern**:
This pattern is particularly valuable in regulated environments, quality management systems, compliance programs, and mature engineering organizations where clarity about what must be done, how to do it, what standards apply, and where to find more information is essential.
Related Concepts
← Back to all concepts