Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/TR 26122:2008 — Information and Documentation — Work Process Analysis for Records
A Systematic Methodology for Identifying Recordkeeping Requirements Through Business Process Analysis
1. The Role of Work Process Analysis in Records Management
ISO/TR 26122:2008 provides a systematic framework for analyzing business work processes to identify what records need to be created, captured, and managed within an organization. Unlike conventional records management approaches that focus primarily on the end products of business activity, this Technical Report emphasizes the importance of understanding the processes themselves as the foundation for designing effective recordkeeping systems.
The fundamental premise of ISO/TR 26122 is that records are not created in isolation — they are the natural byproducts of business transactions and work processes. Therefore, to determine what records an organization should create and keep, one must first understand how the organization work is structured, sequenced, and executed. This process-centric approach aligns records management with broader business process improvement initiatives and ensures that recordkeeping requirements are embedded in workflow design rather than retrofitted after the fact.
Integrating records analysis into business process design from the outset is far more cost-effective than attempting to impose recordkeeping requirements on existing systems. Early engagement with process owners can reduce records management implementation costs by up to 60% while improving compliance outcomes.
The Technical Report distinguishes between two complementary levels of analysis. Sequential analysis examines the temporal flow of activities within a process, identifying decision points, approvals, handoffs, and document creation events. Functional analysis, by contrast, decomposes the process into its constituent functions and activities, revealing the logical structure of work without regard to timing. Together, these provide a complete picture of workflow dynamics and functional architecture.
| Analysis Dimension | Focus Area | Key Questions | Records Output |
|---|---|---|---|
| Sequential analysis | Temporal flow of activities | What happens first? Where are approvals required? | Records creation schedule, routing workflows |
| Functional analysis | Functional decomposition | What are the component activities? Who performs each? | Records classification scheme, metadata requirements |
| Transaction analysis | Discrete business events | What constitutes a complete transaction? | Evidence requirements, audit trail design |
| Contextual analysis | Regulatory environment | What legal or regulatory requirements apply? | Compliance requirements, access controls, retention schedules |
2. Methodologies for Analyzing Business Processes
ISO/TR 26122 provides practical guidance on conducting work process analysis using established techniques drawn from systems analysis, business process reengineering, and archival science. The methodology is adaptable to organizations of any size or sector and can be applied to both manual and automated processes.
Process identification and scoping is the first step, requiring analysts to define the boundaries of the process under examination. This includes identifying the triggering event, the expected output, the organizational units involved, and the interfaces with other processes. Proper scoping is critical because poorly defined boundaries can lead to incomplete records identification or analysis that is too broad to be actionable.
A common pitfall is defining processes too narrowly, focusing on a single department without considering cross-functional information flows. Records often serve multiple stakeholders across organizational boundaries, and process analysis must capture these relationships.
Information gathering techniques include structured interviews with process participants and managers, direct observation of work activities, review of existing documentation (procedure manuals, forms, reports), and facilitated workshops with cross-functional teams. ISO/TR 26122 emphasizes the importance of gathering evidence from multiple sources to validate process descriptions and ensure the analysis reflects actual practice.
Process modeling uses graphical techniques such as flowcharts, activity diagrams, and process maps to represent the analyzed process in a standardized format. This visual representation serves as both an analytical tool and a communication device for validating findings with process owners.
Records identification and specification is the culminating analytical activity. For each record, the analysis specifies its content, structure, context, and relationships. This specification forms the basis for system design, whether the records will be managed in a physical filing system, an electronic document management system, or a specialized records management application.
3. Implementing Process-Driven Recordkeeping Systems
The ultimate goal of the analysis prescribed by ISO/TR 26122 is to build recordkeeping systems that faithfully document business activity while meeting organizational and regulatory requirements.
Integration with electronic systems is a critical consideration in modern implementations. The process analysis identifies natural points in workflows where records should be automatically captured, categorized, and stored. Automated capture reduces the burden on employees to manually file records and improves the completeness and consistency of the organizational record.
Organizations that implement process-driven records capture based on ISO/TR 26122 analysis typically achieve 85-95% records capture rates compared to 40-60% for organizations relying on manual filing, significantly reducing legal discovery risks.
Metadata schema design flows directly from the process analysis. Each record identified should have metadata describing its business context: the process that created it, the transaction it documents, the organizational unit responsible, the date of creation, and its relationship to other records. This metadata is essential for retrieval, classification, retention management, and disposition.
Retention scheduling also derives from process understanding. ISO/TR 26122 analysis reveals when records are no longer needed for active business processes, providing evidence-based retention periods. Legal and regulatory requirements are overlaid on the process-derived retention framework to ensure compliance while avoiding unnecessary retention.
The Technical Report also addresses change management, recognizing that business processes evolve. The recordkeeping system must accommodate process changes through periodic review and update of the process analysis.
Frequently Asked Questions
Q1: How does ISO/TR 26122 relate to ISO 15489?
ISO/TR 26122 is complementary to ISO 15489. While ISO 15489 establishes principles and requirements for records management, ISO/TR 26122 provides the specific methodology for analyzing business processes to determine records requirements.
ISO/TR 26122 is complementary to ISO 15489. While ISO 15489 establishes principles and requirements for records management, ISO/TR 26122 provides the specific methodology for analyzing business processes to determine records requirements.
Q2: Can ISO/TR 26122 be applied to digital-only workflows?
Yes. The methodology is platform-independent and applies equally to manual, hybrid, and fully automated digital processes. In digital environments, it may also identify system-generated records such as audit logs.
Yes. The methodology is platform-independent and applies equally to manual, hybrid, and fully automated digital processes. In digital environments, it may also identify system-generated records such as audit logs.
Q3: What skills are needed for work process analysis?
Effective analysis requires analytical skills (process modeling, systems thinking), communication skills (interviewing, facilitation), and records management knowledge (classification, metadata, retention).
Effective analysis requires analytical skills (process modeling, systems thinking), communication skills (interviewing, facilitation), and records management knowledge (classification, metadata, retention).
Q4: How detailed should process analysis be?
The level of detail should be sufficient to identify all records that need to be created, but not so detailed that it becomes a full business process reengineering exercise. Typically, processes should be decomposed to 3-4 levels.
The level of detail should be sufficient to identify all records that need to be created, but not so detailed that it becomes a full business process reengineering exercise. Typically, processes should be decomposed to 3-4 levels.
