The Three Readers of Architecture Documentation for the CCAR-P Exam

One document, three very different readers

Documentation is the handoff phase of the lifecycle: the part that keeps a deployment functioning after the architect is gone. The CCAR-P exam frames its foundation as a remember-level fact with real consequences, that architecture documentation has to serve three distinct readers at the same time, and that serving only one of them makes the document incomplete no matter how thorough it looks. The three readers are the handoff recipient, the compliance auditor, and the returning architect.

Each reader arrives at a different time, with a different question, and needs something the others do not. Writing for the reader you happen to have most in mind, usually the engineer inheriting the system, produces a document that is detailed and still fails the other two. Recognising all three audiences is what makes documentation complete rather than merely long.

The handoff recipient: decisions and their rejected alternatives

The engineer who inherits a deployment had no part in building it, so they need more than the shape of the system; they need the reasoning behind it. That means the decisions made, the alternatives that were seriously considered and rejected, and why each rejection happened. Without the rejected alternatives, a successor cannot tell why the design is shaped the way it is, and will either reverse the right decision for the wrong reason or defend the wrong one because they cannot see which trade-off it resolved. This is the reader served by decision logs with rejected alternatives.

The auditor: evidence, not assertion

The compliance auditor arrives later with one job: confirm that a specific control is live and accounted for. For this reader, an assertion that a control exists is worth nothing; they require demonstrable evidence that it operates. Each regulatory obligation needs to be paired with the technical control that satisfies it, the owner of that control, and an evidence artifact the reviewer can actually inspect. Documenting for the auditor is documenting evidence over assertion, which is the substance of the control register.

The returning architect: navigable without a briefing

The third reader is often the original architect, back months later with no memory of the design sessions. For them the document must stand on its own: decisions dated, assumptions explicitly labelled as assumptions rather than embedded as facts, and open items carrying owners and resolution criteria. The practical test is whether a competent architect who was not present can make a safe change after reading it, which is exactly the documentation completeness test. A document that only its author can navigate has failed this reader.

What the exam trips candidates on

The first trap is assuming a document is complete because it is thorough for the reader the architect had most in mind while writing. Thoroughness for one audience does not cover the other two, and the credited reading checks the document against all three readers rather than the one it was clearly written for.

The second trap is treating a detailed architecture diagram alone as sufficient documentation for all three readers. A diagram shows what the system is, but it carries no rejected alternatives for the recipient, no evidence for the auditor, and no labelled assumptions for the returning architect. The exam rewards recognising that a diagram, however detailed, serves none of the three readers fully on its own.

Common misreadings to avoid

How this shows up on the exam

Questions ask who architecture documentation must serve, or why a thorough-looking document is still incomplete. The reliable reading is that there are three readers, that each needs something specific, decisions with rejected alternatives, evidence over assertion, and standalone navigability, and that serving only one, or supplying only a diagram, leaves the document incomplete.

This foundation opens the documentation task statement and leads into decision logs with rejected alternatives for the recipient and control registers and evidence over assertion for the auditor, both judged by the documentation completeness test that the returning architect embodies.