ARB Workflow · For Architecture Review Boards
The Review Board Should Hear About a Program Before It Goes Live.
ARB Workflow gives your Architecture Review Board a front door. Programs that may need architecture attention land in one register. Their owners answer a short questionnaire through a secure link. The tool recommends whether each one is architecturally relevant, and shows why. Then an architect makes the call, and the relevant ones go through design-stage and pre-go-live reviews, with sign-offs and conditions tracked to the end.
Included in the Useful EA Corporate plan: $1,000 a year, or $100 a month, plus tax, for up to 25 seats, and free during the beta. Program owners and the people who submit programs never need a seat. See pricing →
- RegisterArchitects enter programs, employees submit them, or one starts from the Capability Modeler.
- Ask the ownerA secure questionnaire link, no account needed, with reminders that stop when it's answered.
- RecommendLikely relevant, likely not relevant, or insufficient information, with every reason shown.
- DecideAn architect makes the final relevance decision. Never the tool.
- ReviewA design-stage review, then a pre-go-live review, each with its evidence and ADRs.
- Follow throughOutcomes, sign-offs, dissent, and conditions with owners and due dates.
The review board is often the last to know
Picture the Friday go-live. The new customer platform uses a cloud service nobody in the company has used before. It moves payment data. It quietly needed an exception to two of your standards. The architects find out on Monday, from a help-desk ticket.
That isn’t architecture review. It’s an accident report.
Most review boards don’t fail on judgment. They fail at the front door: finding the programs, chasing their owners for the facts, and remembering what was decided, and what was promised, six months later. The questions the board actually needs answered are simple:
- Which programs are out there that we haven’t seen?
- Which of them actually need us?
- Who owes us an answer, and since when?
- What did we decide, and why?
- Which conditions are still open?
- What went live without its review?
The ARB process was the poor stepchild of the EA tool suite
I built an ARB at Microsoft IT. Then I did it again for a large distribution company. And again for a networking company. Every time, the review process itself got the least help from the tools. Everyone wanted a capability heatmap. Nobody had built a straightforward workflow for architecture review.
The expensive platforms can do it now, if you spend a month configuring them. When I went looking for an inexpensive tool that handles the whole process, from finding candidate programs through staged reviews and conditions, I came up nearly empty. (You can read that research in Low-Cost Architecture Review Board Tools Under $2,000 a Year.) So we built one.
From the front door to go-live
-
Get every program into the register
Architects add programs, anyone in the company can submit one, and an architect can start one from a Capability Modeler Proposed Portfolio program. A duplicate warning catches the same program entered twice.
-
Ask the owner, not the hallway
Send the program’s owner a secure link to its questionnaire. They need no account. Weekly reminders follow, and stop when they answer; then it escalates to the architect and the coordinator.
-
Get a recommendation you can explain
Your criteria are triggers or weights, and your coordinator sets them. The recommendation lists every answer and rule that led to it, and what’s still unanswered.
-
An architect makes the call
Relevant, not relevant, more information, duplicate, withdrawn or deferred. Going against the recommendation takes a reason. The owner is told through a secure page.
-
Review at the stages that matter
Design-stage and pre-go-live reviews by default, a fast track, or your own path. The coordinator schedules the board, sets the agenda and the time for each item, and everyone gets a calendar file.
-
Follow it through
Record each outcome with the members’ sign-offs, abstentions and dissent. Conditions get an owner, a due date and reminders, and they can hold back the next checkpoint until they’re met.
The board uses seats. Everyone else is free.
ARB Workflow is part of the Useful EA Corporate plan, which costs $1,000 a year, or $100 a month, plus tax, for up to 25 seats, and is free during the beta. It is not part of the Individual plans.
An ARB only works if people bring it their programs, so the people who bring them never pay to take part.
Uses one of the plan’s seats
- Coordinators, who run the board
- Architects, who assess programs and decide
- Board members, who review and sign off
Always free, no seat
- Program owners and project managers
- Employees who look up or submit programs
- Invited participants
Not every program belongs in the directory
Anyone in your company can search the program directory to find out whether the ARB already knows about a program, and who to ask. That’s the point. But an acquisition or a reorganization shouldn’t show up in a search box.
So each program is normal, restricted (people searching see only its number and are told to ask the coordinator) or hidden. One rule decides what each person sees, and it applies everywhere: the directory, the register, reviews, reports, exports and email. No email carries a program’s details at all; each one links to a secure page instead.
Everything the board needs, and nothing it doesn’t
One program register
Name, summary, business unit, sponsor, contacts, stage, key dates and the assigned architect, with duplicate warnings.
A directory for everyone
Anyone in the company can look a program up or submit a new one, on a phone too, without a seat.
Your criteria, versioned
Ten starter criteria, five of them triggers. Change, disable or add to them; answers keep the version they were given against.
An explainable recommendation
Every answer and rule that counted, shown beside it. It is never labelled an approval.
Secure owner links
One person, one program, one task, and an expiry. Owners answer, fill in details, add evidence and see decisions without an account.
Reminders that know when to stop
Weekly by default, with escalation. They stop when the owner answers, when the program is decided or withdrawn, or when an architect marks the contact as not working.
A clarification thread
Ask the owner a question; they reply through a link. One thread per program, kept with it.
Review paths
Design-stage and pre-go-live reviews, a fast track, or a custom path, with target dates worked out from the program’s own.
Evidence stays where it lives
Link the documents in your own document system. ARB Workflow keeps the link and warns when readers may need access.
ADRs, linked or written
Link an Architecture Decision Record by its address, or write it straight into your company’s Architecture Repository, where its metamodel has the ADR type.
Board scheduling
Agenda order, minutes per item, participants, meeting and board-pack links, and calendar files. Owners see only their own slot.
Outcomes and conditions
Approved, approved with conditions, deferred, rejected or not required, with sign-offs, abstentions, dissent, and conditions tracked to closure.
Linked to your models
Link a program to the capabilities, applications, Benefit Dependency Network items and repository objects it affects. Broken links are flagged, never silently removed.
Ask your AI assistant
Connect Claude or another AI assistant and ask it what’s in the register, where a program stands, and what the board decided. It reads only what you can see. It can’t change a thing.
Reports
Where programs come from, response and decision times, agreement with the recommendation, review outcomes, and what went live without its review.
CSV in and out, and full history
Every field goes out to CSV, and programs come back in with a preview first. Every change records who, when, what and why.
A review board’s workflow, not another platform
ARB Workflow doesn’t run your projects, store your documents or replace your project portfolio tool. It tracks what the board needs to know about a program, and no more. Every field it asks for is there because a review board needs it.
Use your PPM tool when the schedule is the point
Budgets, resources, milestones and status reporting for the whole delivery.
Use ARB Workflow when the architecture question is the point
Does this program need the board? What did the board decide? What did the program promise, and has it delivered?
Useful today, and honest about its limits
ARB Workflow opened in November 2026, and it is in beta. The register, directory, questionnaire, recommendation, decision, review paths, reviews, outcomes, conditions, reports, CSV and read-only AI assistant access work today.
One limit to know about: reminders stop when the email service refuses an address outright, but not yet when a message bounces later. An architect can mark a contact as not working to stop them. There is no single sign-on beyond your Useful EA sign-in, and no calendar sync; reviews come with calendar files instead.
Frequently asked questions
Which plan includes ARB Workflow?
Only the Useful EA Corporate plan: $1,000 a year, or $100 a month, plus tax, for up to 25 seats, and free during the beta. It is not part of the Individual plans. See pricing.
Who needs a seat?
Coordinators, architects and board members each use one of the Corporate plan’s seats. Program owners, project managers, employees who look up or submit programs, and invited participants are always free and use no seat.
Do program owners need an account?
No. They act through secure links, each for one person, one program and one task, with an expiry. Opening one never creates an account.
Does the tool approve programs?
No. It recommends whether a program is likely relevant, and explains why. An architect makes the relevance decision, and the board records the review outcomes. Architectural relevance and approval stay human accountabilities.
Can we change the relevance criteria?
Yes. Your coordinator can edit, disable or add criteria and change the threshold. Each change publishes a new version, and every answer keeps the version it was given against.
Where do our documents live?
Where they live now. ARB Workflow stores links to evidence and ADRs, not the files. An ADR can also be written into your company’s Architecture Repository, if its metamodel has the Architecture Decision Record type and you can edit it.
Can confidential programs stay out of sight?
Yes. A program can be shown as a restricted placeholder, with its number only, or hidden altogether. The same rule applies in the directory, the register, reviews, reports, exports and email.
Does it connect to the other Useful EA tools?
An architect can start a program from a Capability Modeler Proposed Portfolio program, and link a program to capabilities, applications, Benefit Dependency Network items and Architecture Repository objects. The other tools aren’t changed by it.
Can we get our data out?
Yes. Every field of every program goes out to CSV, as do the reviews and the reports.
Can an AI assistant read our ARB register?
Yes, and only what you could see yourself. Connect Claude, ChatGPT or another AI assistant to Useful EA and it can list the programs you can see, read a program’s details and status, and read its decisions: the architect’s relevance decision and the board’s review outcomes, sign-offs and conditions. Without an ARB role it searches the directory, as you would. A restricted program stays a reference number, and a hidden one doesn’t appear at all. It reads. It never writes: nothing in ARB Workflow can be changed from an assistant. Your company’s AI setting has to allow assistants at all.
The research, and how to use it
Nick Malik’s comparison Low-Cost Architecture Review Board Tools Under $2,000 a Year looks at the inexpensive ARB tools available today, what each one leaves out, and what a purpose-built ARB workflow should provide.
The ARB Workflow User Guide covers every part of the tool, role by role: the register and directory, criteria and the recommendation, owner links and reminders, decisions, review paths, evidence and ADRs, reviews, outcomes, reports and CSV.
The board’s job is judgment. Let the tool do the chasing.
Start with your next three programs: put them in the register, send their owners the questionnaire, and see what comes back.
Open ARB Workflow →