My checklist for enterprise architecture documentation
This is a TOGAF-aligned documentation template I use for enterprise architecture projects. It's not a tutorial—it's a structured outline of every document you should produce during a typical TOGAF ADM (Architecture Development Method) engagement.
A comprehensive checklist covering:
- Preliminary Phase - Framework setup, governance charter, architecture principles
- Phase A: Architecture Vision - BRD, stakeholder analysis, architecture vision document
- Phase B: Business Architecture - Capability models, value streams, gap analysis
- Phase C: Information Systems - Data architecture, application architecture, SOA design
- Phase D: Technology Architecture - Infrastructure, networking, IaC, configuration management
- Phases E-H - Opportunities/solutions, migration planning, implementation governance, architecture change management
Each phase lists the documents you should create (e.g., "Business Requirements Document", "Data Governance Plan", "Application Inventory") with brief descriptions.
After my second EA project, I realized I kept forgetting which documents TOGAF expects at each phase. "Wait, does the BRD go in Phase A or Phase B?" "Where do I document data governance—Phase C or Preliminary?"
This template is my answer. It's the full TOGAF ADM document list in one file. I print it out at the start of every project and check off documents as I create them.
- Project kickoff - Review the template with stakeholders to agree on which documents are needed (not every project needs all 95 documents)
- Phase planning - Before starting each ADM phase, check which deliverables are required
- Documentation tracking - Use it as a checklist to ensure nothing is missed
- Handoff - At project end, verify all agreed documents are completed
Most EA projects use 40-50% of the documents listed here. The template covers 95% of scenarios, but you'll always need to tailor it.
Not a how-to guide: This tells you what documents to create, not how to create them. For that, read the TOGAF 9.2 specification or take a TOGAF training course.
Not prescriptive: Some projects don't need a full TOGAF ADM. Use what makes sense. Smaller projects might skip Phase B entirely.
Not the only way: TOGAF is one EA framework. Zachman, FEAF, and others exist. This template is TOGAF-specific.
I've used this on:
- 2 full TOGAF engagements (financial services, healthcare)
- 4 partial implementations (used Phases A-C only)
- Multiple architecture assessments
The most-used sections:
- Phase A (Architecture Vision) - every project needs this
- Phase C (Data Architecture) - data governance is always critical
- Phase D (Technology Architecture) - infrastructure documentation
The least-used sections:
- Phase G (Implementation Governance) - often handled by PMO, not architects
- Phase H (Architecture Change Management) - rarely formalized in my projects
If you spot missing documents or have suggestions, open an issue or PR. Just know I'm optimizing for "90% coverage" not "exhaustive TOGAF compliance."
Last updated: 2024
Status: Active reference
Best for: Enterprise architecture projects following TOGAF ADM, compliance-heavy environments