ARB Workflow runs your Architecture Review Board’s process, from finding the programs that may need architecture attention to following their conditions through go-live. This guide covers every part of the tool, role by role. The same guide is in the app, under Help at the top of every page.
On this page
- What the tool is for
- Roles and seats
- Finding a program
- Submitting a program
- The program register
- Criteria and the recommendation
- Asking the owner
- The clarification thread
- The relevance decision
- The worklist
- Review paths and checkpoints
- Evidence and ADRs
- Scheduling reviews
- Outcomes, sign-offs and conditions
- Links to other Useful EA tools
- Reports
- Export and import
- AI assistants
- ARB settings
What the tool is for
ARB Workflow runs your Architecture Review Board’s process from start to finish. It finds the programs that may need architecture attention, collects what’s missing from their owners, recommends whether each one is architecturally relevant, and lets an architect make the final call. Relevant programs then go through their reviews, usually a design-stage review and a pre-go-live review, with evidence, decisions, sign-offs and conditions recorded as they happen.
The tool assists; it never decides. The recommendation is never an approval, and only a person with the architect role makes the relevance decision. Every change is kept in the program’s history: who, when, what changed and why.
Roles and seats
ARB Workflow comes with your company’s 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. Your company’s administrators give people their ARB roles on Roles:
- Coordinator
- Runs the board: the relevance criteria, the review paths, the settings, and scheduling reviews. Sees every program in full, confidential ones included.
- Architect
- Adds and edits programs in the register, asks owners for information, and makes the final relevance decision.
- Board member
- Reads the register, reviews the evidence and records a sign-off at reviews.
- Confidential viewer
- An extra permission: sees restricted and hidden programs in full.
Coordinators, architects and board members each use one of the plan’s seats. Confidential viewer on its own doesn’t. Everyone else in your company can search the directory and submit programs without a seat, and program owners, project managers and anyone else you invite take part through secure links, with no account and no seat.
Finding a program
Directory is for everyone in your company. Search by name, number, business unit or contact to find out whether the ARB already knows about a program, where it stands and who to ask about it.
A program can be normal (anyone in the company finds it), restricted (the directory shows its number only, with no details, and says to ask the ARB coordinator) or hidden (only people who may see confidential programs find it). The same rule applies everywhere a program can appear: the directory, the register, the worklist, reviews, reports, exports and email.
Submitting a program
If the program isn’t there, Submit it: its name, a few sentences on what it is, the business unit, the sponsor, a contact and a backup contact, its stage and its key dates. As you type the name, programs with a similar name are listed, so you can check it isn’t already there. An architect then picks it up.
Tick This program is confidential if it shouldn’t show in the directory. The form warns you if nobody in your company can review confidential programs yet.
The program register
Programs is the company’s register, for everyone with an ARB role. Only architects add, change and delete programs. New program adds one; From the Capability Modeler starts one from a Proposed Portfolio program in a Capability Modeler model you can open, copying its name and a summary and keeping the link back. A program whose name is close to one already in the register gets a duplicate warning before it’s saved, more readily when both are in the same business unit.
Each program’s page has its details, its relevance questionnaire and recommendation, the links for its owner, the clarification thread, the decision, its review path, evidence and ADRs, reviews and outcomes, its Useful EA links, and its history.
Criteria and the recommendation
Each program has a relevance questionnaire, built from your company’s criteria. The coordinator keeps the criteria on Criteria: each one is either a trigger, which makes a program likely relevant on its own, or carries a weight, and a program whose weights add up to the threshold is likely relevant too. New companies start with ten criteria: five triggers (a new technology or pattern; security and resilience; an exception to a standard; over the company’s cost or risk threshold; material use of AI) and five weighted at 1, with a threshold of 2.
Changing the criteria publishes a new version. Answers keep the version they were given against, and every earlier version can be viewed.
From the answers, the tool recommends likely relevant, likely not relevant or insufficient information, and explains which answers and rules led there. The Still to answer list shows what’s missing. The owner never sees the recommendation.
Asking the owner
Under Links for the owner on a program, an architect makes a secure link for the program’s contact to answer the questionnaire, fill in the program’s details, or add evidence for a checkpoint. Each link is for one person, one program and one thing, and it expires (after 14 days unless you choose otherwise, and never after more than 60). The owner needs no account. You can email the link from the tool, or copy it once and send it yourself, and revoke it at any time.
An emailed invitation can bring reminders: weekly by default, at 09:00 in your ARB time zone, three times, then an escalation to the assigned architect and then the coordinators. An architect can change the cadence, the count and the escalation, pause them, or mark the contact as not working. Reminders stop when the owner has done what the link asks, when the program is decided or withdrawn, when the link is revoked, when the email service refuses the address, or when the contact is marked as not working.
No email from ARB Workflow carries a program’s details. Each one says something needs attention and links to the secure page.
The clarification thread
Each program has one clarification thread. An architect’s question emails the owner a link to read the thread and reply, without an account, and the reply comes back to the assigned architect (or the coordinators). The owner can read everything in the thread, so keep internal remarks out of it.
The relevance decision
An architect makes the decision under Decision on the program’s page: relevant (it goes on to architecture review), not relevant, more information needed (it goes back to waiting for its owner), a duplicate of another program, withdrawn, or deferred. A reason is required when the decision goes against the recommendation, or changes an earlier decision. That reason is internal.
The owner is told of the decision by default, through a secure page that shows the decision but never the internal reason. Add a message to the owner to explain it in your own words.
The worklist
Worklist shows what needs doing: programs needing triage, overdue owner responses, programs ready for a decision or ready to schedule, reviews coming up, overdue conditions, and programs heading for go-live without their reviews. Filter it by state, recommendation, architect, business unit, urgency and due date, and sort it by priority, target date, newest, last change or score. The filters stay in the page’s address, so you can bookmark a view.
Review paths and checkpoints
A relevant program gets a review path: the checkpoints it has to pass. The coordinator keeps the templates on Review paths. Every company starts with Design and pre-go-live reviews and a Fast track (one combined review), and can add its own. An architect applies a template to a program, with its dates worked out from the program’s own, or builds a custom path, and can change it later.
A checkpoint is planned, being prepared, ready, scheduled, completed or cancelled, and shows as overdue once its target date passes.
Evidence and ADRs
Evidence stays where your company keeps it. Under Evidence and ADRs, add a link to each document, diagram, set of requirements, test results or risk assessment, on the program or one of its checkpoints. ARB Workflow stores the address, not the file, and warns that readers need access to it where it lives. The owner can add their own evidence links through a link for that checkpoint.
An ADR (Architecture Decision Record) is linked by its address, with its identifier, status (proposed, accepted, superseded or rejected), date and the checkpoints it belongs to. If your company has an Architecture Repository whose metamodel has the Architecture Decision Record type, and you can edit it, an architect can choose New ADR in a repository to write the ADR there and link it in one go.
Once a checkpoint is completed or cancelled, its links can’t change.
Scheduling reviews
On Reviews, the coordinator schedules a review: when (in your ARB time zone), how long, where, the meeting and board-pack addresses, the agenda (which program checkpoints, in what order, with how many minutes each) and the participants (chair, reviewers and observers). Changing or cancelling a review updates the checkpoints on it.
Each program’s contact is told when their item is scheduled, moved or cancelled, and reminded two days before. Their page shows when and where, and their own slot, never the rest of the agenda, and it offers a calendar file for that slot. Everyone with a role can download a calendar file for the whole review.
Outcomes, sign-offs and conditions
Once a review has started, the chair or a coordinator records each item’s outcome: approved, approved with conditions, deferred, rejected, or review not required, with the board’s rationale and each member’s sign-off, abstention or dissent. There is no quorum rule: the chair records the outcome and the members’ positions are kept beside it.
Conditions and actions each have an owner, a role holder or the program’s contact, and a due date. Reminders go out as they fall due and once they’re overdue. Architects and coordinators mark them met or waived. Your ARB settings say whether a program may go on to its next checkpoint once it’s approved, or only once its conditions are met. A rejection holds the next checkpoint back until the program passes a review again.
The owner sees the outcome and their own conditions and actions, never the rationale. Add a message to the owner to explain it.
Links to other Useful EA tools
Under Useful EA links, an architect links a program to the capabilities, Benefit Dependency Network items, applications and Architecture Repository objects it affects, from your company’s own models that they can open. Everyone with a role sees the linked names; the link itself opens only for people who can open the object. Links are checked every night. One whose object has gone, or can no longer be reached, shows a warning with its last known name. It’s never removed without someone choosing to.
Reports
Reports shows where programs come from, how quickly owners answer and architects decide, how often architects agree with the recommendation (and the decisions that didn’t), the time from a relevance decision to each review, review outcomes, conditions, and programs that reached go-live without the required checkpoint. Each table downloads as CSV. The counts cover only the programs you can see in full.
Export and import
Export CSV on Programs saves every field of every program you can see, including the answers, the recommendation, the decision, the path, evidence, ADRs, outcomes and links. Architects can Import CSV in the same columns: each row is matched to a program by its id or number, or added as a new one, and the import first shows what it will do to each row, with any problems and look-alike warnings, before anything is saved. The Reviews and Reports pages have their own CSV downloads.
So that a spreadsheet never runs a cell as a formula, a cell starting with =, +,
- or @ is saved with an apostrophe in front.
AI assistants
If you connect an AI assistant such as Claude to Useful EA, it can read ARB Workflow for you: list the programs you can see, read a program’s details and status, and read its decisions, meaning the architect’s relevance decision and the board’s review outcomes, sign-offs and conditions. See Connect an AI assistant for how to connect one.
It sees what you see, and no more. Without an ARB role it searches the directory, as you would; reading a program and its decisions needs a role. A restricted program comes back as its reference number only, a hidden one doesn’t appear, and another company’s programs are never reached.
It can only read. Nothing in ARB Workflow can be changed from an assistant: it can’t submit a program, answer a questionnaire, record a decision or sign anything off. Your company’s AI setting must allow assistants; Read only is enough.
ARB settings
Settings has three choices, which the coordinator changes with a reason: whether a program marked confidential is hidden (the default) or shown as a restricted placeholder; the time zone for reviews and reminders; and when a program goes on to its next checkpoint. Coordinators and architects can also see the Email delivery history: whether each ARB email was sent, is waiting, or was refused, without its contents.
Still stuck? Email support@useful-ea.com.