How to Run a Productive Architecture Review Board (ARB) Meeting (Free Templates)
This week we're looking at the Architecture Review Board meeting, usually shortened to the ARB meeting: the formal checkpoint where an engineer presents a proposed system design to a panel of technical peers before the commitment to build it is made. As an organization grows, the alternative to an ARB becomes increasingly untenable: you can no longer stand up a new service somewhere in a corner, ship it, and only have security or operations review it three months later. An ARB meeting moves that conversation to the cheapest possible moment, before any of the project exists. Below we'll cover what the meeting is for, when to hold it, how long it should take and how to run it, then walk through a free template you can make use of.
TL;DR: An Architecture Review Board meeting is a 60 to 90 minute review where an engineer presents a proposed design and a small panel of senior peers checks it for scalability, security, fit with existing systems and long-term maintenance. Aim to hold it after the design is drafted and before a build-or-buy decision, send the design out in advance, and end with a recorded outcome: approved, approved with changes, or revise and resubmit. We discuss a free architecture review board meeting template for Knowtworthy, Word, Excel and Google Docs further down.
What is an Architecture Review Board Meeting?
An Architecture Review Board (ARB) meeting is a structured review of a proposed technical design by a panel of senior technical peers. The person or team proposing a new system, a major change to an existing one, or a new piece of infrastructure presents the design. The board questions it against the company's technical standards, security requirements and scalability needs, and then decides whether the design can go ahead, or what revisions are needed.
The board itself is usually small and cross-functional. AWS's guidance on building an effective architecture review board suggests drawing members from security, development, enterprise architecture, infrastructure and operations, so that each design is looked at by the people who will have to secure it, run it and support it. In a smaller company the "board" might be just three people: your most senior engineer, the point person for infrastructure, and a security professional. Especially in larger organizations, forming this board draws from many teams and takes time and effort. But the more qualified the board, the fewer issues you’ll run into later on, so make it a priority to assemble a strong team if you want to run effective ARBs.
You'll also see this kind of meeting being called a design review, a technical design review, or an architecture review. The ARB name usually signals a more formal version, with a standing panel, and potentially a regular and pre-defined slot.
What is the main goal of an Architecture Review Board Meeting?
The main goal is to catch expensive design mistakes while they are still cheap to fix. Changing a diagram can feel annoying but only costs one employee an afternoon; redesigning a production system can cost a team a quarter. Put simply, an ARB meeting is the point where the people who know the rest of the system have the opportunity to comment "this will break when traffic doubles" or "we already have a service that does this" before the business dives into the expensive implementation.
There are a couple of additional goals worth keeping in mind alongside the main one:
- Preventing siloed decisions. A single team can make a choice that is sensible on its own but fits poorly into the organization as a whole. For example, adopting an entirely new tech stack outside of what exists currently at the organization might make development of the product quick but maintenance unjustifiably expensive. The board gives visibility to these kinds of choices.
- Keeping the roadmap's technical debt under control. Questions about maintenance and decommissioning can feel far away when plans for a new product are proposed, but ignoring them adds to the organization’s tech debt, so they are definitely worth considering early on.
The meeting should leave the presenter with a clear decision and a short list of changes. It works best when the board resists redesigning the proposal live or re-arguing company standards, and avoids ending on a vague "the board has concerns."
When should you schedule an Architecture Review Board Meeting?
Schedule the review once the design is written but before you commit to building or buying anything. Late enough that there is a real design to review that won’t waste the panel’s time, but early enough that changing it is cheap. This is a bit of a balancing act as spending a lot of time on working out every detail of the implementation can be quite costly, but try to arrive at a position where the panel reviewing the plan can be maximally helpful but in a way that doesn’t require rounds of revisions. Some teams will also add an optional second, shorter review just before deployment, to confirm that what was built matches what was approved at the ARB.
Notably, not every change needs a meeting. A useful rule is to bring the board the decisions that are hard to reverse: a new service or data store, a new third-party vendor, a change to how systems talk to each other, anything that touches authentication or customer data. Smaller, easily reversed changes can be reviewed asynchronously and upon request.
For the cadence, this can vary, but some teams hold a standing slot so that designs don't wait around for extended periods of time in limbo without a meeting. For example, the team behind Architecture Reviews Without The Hassle at Andela ran theirs every two weeks, specifically so the backlog of designs waiting for review never grew too long. If your board meets too infrequently, this piles on blockers and you’ll find that teams start to route around it, which defeats the point.
How long should an Architecture Review Board Meeting be?
Book 60 to 90 minutes for one design. Our template is laid out for a 90-minute session, which gives a significant design enough room for the presentation, some stress testing, and a decision. A small or well-understood change can often be handled in 45 to 60 minutes, so as we recommend with most meetings, book the time slot knowing the agenda.
Two things to keep in mind so the meeting stays at a length that respects everyone’s time:
- Send the design out ahead of time. Share the design document and the high-level diagram at least a couple of working days in advance, and ask reviewers to read it and have their questions before the meeting. Presenting everything for the first time in the meeting costs a lot of time and might leave many stones unturned.
- Review one design per session. It's tempting to stack proposals into one meeting if they sound short, but in practice if you overrun on the first one, the next ones in line will be rushed. Alternatively, ensure that you are very diligent with time boxing, though in practice this is a common challenge.
If the review clearly needs more time, we recommend that you end on "revise and resubmit" with a list of open questions for the team rather than running over. A second, shorter session on a revised design will generally be a better use of time.
How is an Architecture Review Board Meeting Run?
An ARB meeting usually has three roles:
- The presenter, normally the engineer or tech lead who owns the design. They walk the board through the problem, the constraints, and the proposed solution. They then answer any questions posed.
- The board, the small panel of senior reviewers. Their job is to evaluate the proposal, ask the hard but necessary questions, and provide actionable feedback if revisions by the presenter are needed.
- The chair, who keeps time, makes sure everything in the agenda gets the attention it needs, and (crucially) calls the decision at the end. This role can be held by someone either in or outside of the panel itself. In smaller companies, the chair is often the most senior architect or the CTO. In the event that there’s a disagreement within the board about a given proposal’s status or next steps, the chair will need to make the final resolution.
Someone also needs to take notes, as a record of ARB meeting decisions is very valuable to maintain. Every ARB decision should be written down, including the reasons a design was sent back, any exceptions to standards that were granted, and the follow-up actions.
Many engineering teams record the outcome as an Architecture Decision Record (ADR): a short, one-page document that captures a single decision, its context, and its consequences. It’s a good idea to keep this kind of record formatted consistently, and you can find an example in Martin Fowler's overview of Architecture Decision Records, which includes the convention of storing ADRs alongside the code and superseding an old record with a new one rather than editing it. If your team already writes ADRs, the ARB meeting (or the write-up right after it) is where a "proposed" record becomes "accepted."
Think back to a major design decision made in the last six months or so. If questioned, would anyone be able to find out why it was made? If the answer is no, or not easily, a written and searchable record of every ARB outcome should get you that answer within minutes.
Additional Resources about Architecture Review Board Meetings
- AWS Architecture Blog: Build and operate an effective architecture review board, on who should sit on the board, when reviews should happen, and how to record decisions and exceptions.
- Architecture Reviews Without The Hassle, a short account of a lightweight, two-weekly review process with a clear decision maker.
- Martin Fowler: Architecture Decision Record, a good reference for writing down each architecture decision in a single page.
- Our own post on what goes into a great meeting action item, for turning the board's requested changes into tasks that have follow-ups and will actually get done.
A Simple Template for Architecture Review Board Meetings
You should always adapt any meeting template to your particular needs, as all teams and organizations are different, but below we have some free templates for you to get started with. Every engineering team and every system is unique, which can make design reviews a challenge, but the overall structure and the questions that a good review asks stay much the same from one design to the next.
We'll go over every section in the templates attached in this article, so feel free to follow along with whichever version below suits you. The Word and Excel versions are free downloads, and the Google Docs version can be copied straight into your own Drive. The Knowtworthy template can just be opened in the browser and is editable immediately. If you hold on to the link you’ll retain access to that file for later use as well.
- Free Knowtworthy Architecture Review Board Template: https://knowtworthy.com/templates/69a647715399b05a16350fd8/
- Microsoft Word Architecture Review Board Template: https://templates.knowtworthy.com/production/templates/69a647715399b05a16350fd5/3f5c87d12c573b8c0b8e29a072168f28
- Microsoft Excel Architecture Review Board Template: https://templates.knowtworthy.com/production/templates/69a647715399b05a16350fd5/0291d02770a49baa9d4cd78c317821c3
- Google Docs Architecture Review Board Template: https://docs.google.com/document/d/1wz4zgz1jqdOh79PRNMhbnQzcRIrV3EoS/edit?usp=sharing&ouid=114292313754172363182&rtpof=true&sd=true
If these templates don't suit your needs, you can check out our dedicated templates page where you can access all of our free templates and find one that works better for you!
Meeting Information
At the top of the template, list the details that let anyone reading understand the review at a glance: the name of the design or project, the presenter, the board members attending, the date, and a link to the design document. Put the project name in the meeting title and try not to keep it generic ("ARB: Payments service migration" rather than "Architecture Review"), so the notes are easy to find in the future by people who may not have been at the meeting itself.
Meeting Purpose
The template doesn't come with a fixed purpose line, because the purpose of each review depends on the design in front of the board. However, we'd recommend writing one sentence for every session. A general version might be:
Evaluate the proposed design for scalability, security and fit with our existing systems, and decide whether it can move to build.
As with the title of the meeting, we recommend making this concrete. As an example:
Decide whether the proposed move of order processing to an event queue can go ahead this quarter, and agree on any changes needed before the build starts.
A specific purpose keeps the board focused on the decision it must make, and can be useful to refocus the room if the meeting starts getting derailed on tangents.
Meeting Agenda
The meeting itself should move through a few key phases, which we list in the agenda below. You can add notes under each item and change how much time you give each one, but we've provided a rough baseline for a 90-minute session.
1. Context & Business Logic (10 minutes)
Start with why the design exists. The template asks two questions here:
- What business problem does this architecture solve?
- What are the mandatory constraints: budget, vendors, deadlines?
This section is short, but glossing over it entirely would be a mistake. It’s crucial that everyone has a handle on the unchangeable constraints before considering the design as a whole. A design that looks overbuilt can make perfect sense once the board knows there's a contractual uptime requirement, and a design that looks elegant but is a significant undertaking can be the wrong answer if the deadline is a couple of weeks away.
2. Design Presentation (25 minutes)
The presenter walks the board through the solution, in two parts:
- Review the High-Level Design (HLD) diagram, meaning the overview of the main components, the data flows between them and the external systems they touch.
- Discussion and Q&A.
Ask the presenter to keep the walkthrough to about ten minutes and leave the rest for preliminary questions. If reviewers read the design in advance, the presentation can focus on the parts that changed or that are most likely to be contested, instead of reading the document aloud.
3. The "Stress Test": Scalability & Security (20 minutes)
This is the heart of the review. The template's prompt is to discuss where the design would break under pressure. Useful questions include:
- What happens at ten times today's load? Which component fails first?
- What happens when a dependency is slow or unavailable?
- Where does sensitive data live, who can access it, and how is it protected?
- What is the worst thing a malicious user could do with this design?
The point is to find the weak spots together. Every design that has to fit constraints will always have weaknesses, so keep in mind that finding and discussing weaknesses here is an indicator of a successful meeting, not a mark against the presenter.
4. Integration and Maintenance (15 minutes)
A design can be sound on its own and still be a poor fit for the company in the context of everything else. The template asks three questions:
- How does the design fit into the current ecosystem?
- What does it take to maintain this design?
- How could this be safely decommissioned if needed?
The last question is easy to skip since it feels far out, but you’ll be wishing you hadn’t down the line. Every system eventually needs replacing, and if nobody can describe how this one would be turned off, the design probably has dependencies that need more careful consideration.
5. Review and Feedback (15 minutes)
End the discussion with a decision. The template gives the board three possible outcomes to consider:
- Approved: the design can go ahead as presented.
- Approved with small changes: the design can go ahead once the listed changes are made, without coming back to the board.
- Revise and resubmit: the design needs significant changes and a second review.
Have the chair state the outcome out loud and make sure the notes record it, along with the reasons. "Approved with small changes" is only reasonable if the changes are written down clearly enough that everyone agrees later on whether they were made.
6. Create Action Items (5 minutes)
Finish by turning the board's feedback into action items, each with an owner and a due date. For an approval with changes, these are the changes. For a resubmission, they are the open questions the revised design has to answer, which can be pulled up at the next meeting with ease. Our post on what goes into a great meeting action item covers how to write these so they don't get lost.
Other templates you might find useful
If you run design reviews, you'll probably also run other formal engineering meetings. A few of our templates that pair well with this one:
- The Security Audit/Review Meeting Template, for the recurring review of your security posture rather than a single design.
- The Incident Retrospective (Post-Incident Review) Template, for when a system breaks in production and you want to learn from it without blame.
- The Decision-Making Meeting Template, for bigger choices that need a structured discussion and a clear decision, technical or not.
After the Meeting
Send the outcome to the presenter and the board the same day: the decision, the reasons, any exceptions granted, and the action items. Then file the notes somewhere the whole engineering team can find and open them, next to the design document or as an ADR in the repository. We have a separate post on the best practices for handling your meeting notes afterwards, which you can read here: So you took notes during your meeting, now what?
These notes become the record of why your systems look the way they do. They help new engineers understand past choices, and they save the board from re-arguing a decision that was already made for good reasons. Written and saved properly, these notes will pay off in the long run.
Depending on how you write your notes, you may need to share them over email. With a cloud-based meeting platform like Knowtworthy, you can share a link to your notes instead, so everyone sees any later changes without you updating them by hand, and nobody’s inbox gets more cluttered.
In this post we covered the basics of Architecture Review Board meetings and went through a simple template to get you started. As we mentioned above, there's no one-size-fits-all meeting template, and different types of meetings need different kinds of templates.
So if you're interested in other free meeting templates, check out the list of articles we've written on the subject here: meeting template articles. We also host a blog all about meeting and project management best practices, which you can find here: the Knowtworthy blog.
We'll be back with more articles like this one soon, so if you found this one helpful, please feel free to subscribe or share the post!