Skip to main content
Discuss Book a call
ChecklistPDF

Technology Architecture Review Checklist

Someone has told you the architecture is sound, and you would like to see why before you commit more money to it. This technology architecture review checklist lists what to ask to see, from dependencies and releases to recovery, ownership and the cost of leaving.

Download PDFVersion 1.0 · Updated October 20, 2026 · 88 KB

Free, and we don't ask for your email address.

Line drawing of a technology architecture review checklist as a long ticked sheet, with the final items open and one row unanswered.

What the technology architecture review checklist covers

  • Dependencies and boundaries: a current map with an owner, what crosses each boundary, and the outside suppliers whose failure would stop the business
  • Data and integration: a single system of record for each kind of data, a rule for when systems disagree, and an owner for every integration
  • Change and release: the same steps every time, releases that can be reversed, and an emergency route that gets reviewed afterward
  • Reliability and recovery: a restore proved from backup into a clean environment, and recovery steps that someone other than their author has followed
  • Security basics: access by person and role, secrets kept in a managed place, and logs somebody can read
  • Ownership and knowledge: decisions written down, named owners, and technical debt recorded and ranked
  • Cost and exit: what each major system costs to run and what it would cost to leave
  • Questions to put to the team in every area, and a review record with a line for each finding, its cost if it goes wrong, its owner and the decision

How to run a review with it

  1. 01

    Review with the people who run the systems

    Ask to be shown the evidence. A statement is true when someone other than its author can demonstrate it today.

  2. 02

    Write a line for every box you can't tick

    Give each one a cost if it goes wrong, an owner and a date for the decision.

  3. 03

    Read the questions aloud, not just the statements

    A statement lets a good deal slip past. The questions ask which system nobody dares change and which integration nobody could repair.

Limits

A review shows what was reported to you, not what is true of every system. The checklist asks questions and tests nothing. It isn't a security assessment or a penetration test.

On this page

What should you ask to see, and what does a gap sound like?

Every statement in the checklist can be answered with an artifact or with a shrug, and the artifact is the evidence. The table gives one request for each area, and the answer that tells you the box stays empty.

AreaAsk to seeA gap sounds like
Dependencies and boundariesThe dependency map, and the list of suppliers the business couldn't run withoutNobody has a current picture, and we find out when something breaks
Data and integrationThe rule for which system wins, and the log of differences it has foundFinance reconciles it by hand at month end
Change and releaseThe last release that had to be reversed, and how long that tookWe batch changes because each one needs a meeting
Reliability and recoveryThe record of the last restore into a clean environmentThe backups run, and nobody has restored one
Security basicsWho can change production without a second person seeing itA leaver's access lingers until someone notices
Ownership and knowledgeWhere decisions are recorded, and who could run the system if its expert leftOnly one engineer knows how that part works
Cost and exitA recent estimate of moving off the largest supplierWe've never costed leaving

What follows a technology architecture review?

The Technology and Architecture Risk Assessment on this site gives a quick reading of the same ground. The Technical Debt Register records what the review finds and ranks it. If the findings need an independent view, our technology and architecture advisory work starts from your review record.

What do people ask before running a technology architecture review?

Who should be in the room for a technology architecture review?

The people who run the systems, and not only the people who describe them. Ask to be shown the evidence, because a statement is true only when someone other than its author can demonstrate it today. Read the questions to the team as well as the statements.

What should I do with the boxes we cannot tick?

Write a line in the review record for each one, with its cost if it goes wrong, an owner and a date for the decision. The record becomes your list of findings, which a technical debt register can rank and an outside adviser can start from.

Does the checklist test whether our systems are secure?

No. It asks questions and tests no system, and a review shows only what was reported to you. The checklist covers security basics, but it is not a security assessment or a penetration test, so a full set of ticks is not proof of anything.

Which item should I ask to see first?

The restore into a clean environment. It is the easiest statement to assume and the costliest to get wrong, because nobody finds out a backup is unusable until the day it is needed. Ask for the record of the last restore and see who can produce it.

Reviewing a real architecture?

Tell us which system you would least like to see fail and who understands how it works. Someone senior reads it and answers with what we would want to see first.