Get decisions confirmed by the right people, with structured approvals
A general agreement is enough for some decisions. Others need the right people to sign off. Structured approvals give each approver a clear role and a personal, recorded approval, in the same decision log, whether the decision happens in a meeting or between meetings.
Group operating budget 2026
Full-year operating budget of €48.5M, reflecting the cost targets set in the autumn strategy review.
Recommend
DBDaniel Berg
Approved
Agree
PNPriya Nair
Approved
Decide
CDClaire Dubois
Approved
Every approval is real, and every one is on the record
Today, without clear approvals
- The agreement happens, but the record varies: written down, scattered across channels, or nowhere at all
- Who was actually involved is rarely captured, so later people remember it differently
- An "approved" status can hide who really weighed in, or who owned the decision
With structured approvals
- Every decision and its approvers land in one decision log, in a meeting or between them, so the record never varies
- The right people are named, each in a clear role, with every approval captured in their own name
- "Approved" always means that person weighed in personally, on the decision and documents in front of them
Bottom line: Structured approvals give the people who carry a decision a clear way to own it, and give the whole team a record they can rely on.
How structured approvals work
Choose the process
Choose structured approvals as your decision-making process, then shape the roles with RAPID, RACI, or a custom model of your own.
Propose the decision
Create a proposed decision on the agenda, or as a circular resolution between meetings. Attach the documentation approvers need, and select who approves.
Approve
Each approver responds personally, in their own name: approve, reject, or pending. Pending keeps the decision open when someone needs more information or a discussion first.
Record
The outcome is automatic: final once every approval is in, rejected if anyone rejects. Either way it lands in the same decision log with approver names, whether the decision was made in a meeting or between them.
Built to turn approvals into accountability
Run through your own framework
Approve through RAPID, RACI, or a custom model with your own role names, from one to nine roles, the same rules whether the decision is made in a meeting or between them.
Personal by design
Each role is assigned to one person, and every approval is given in their own name. Nobody can approve on someone else's behalf, so "approved" means the person was actively involved.
Everything documented
Title, decision framing, pre-reads, attachments, and custom fields travel with the decision, so approvers decide on the full picture and the reasoning is recorded, not remembered.
A record that locks
Draft, Published, then Locked when Final or Rejected. Approvals open when the admin chooses and close on the outcome, and after that a status can't change: an approval given can't later become a rejection.
Traceable across teams
The decision log shows who approved, in which role, and on what documentation, so months later you know exactly who to ask. Where your organization uses Advanced Reporting, it adds read-only oversight across shared teams.
Secure by where it lives
Every decision and its record stays inside your own Microsoft 365 tenant, not scattered across email and chat where things get lost or leaked. No third-party bots, nothing leaves your tenant. SOC 2 Type II and ISO 27001:2022 certified.
Learn moreFor any team where key decisions need a clear owner
Cross-team steering committees
Sign-off on scope, budget, and milestones, with clear ownership at every gate.
Boards & governance committees
Decisions that need a defined, documented approval path, with a record auditors can verify.
Project teams with heavy coordination
Many moving parts, and many people who need to know what was decided and by whom.
Teams using a formal model
RAPID, RACI, or your own, mapped onto how you already decide.