Enterprise ยท Delegation of authority
Delegation of authority, tested against practice.
Every gap between your authority matrix and what people actually do, confirmed by the people who decide.
No system access. One business unit. Five working days. Fixed fee from $25,000.
| Kind of decision | DoA says | In practice | Finding |
|---|---|---|---|
| Vendor contracts under $50k | Director | VP, 3 layers up | Above line |
| Pricing exceptions | Regional lead | CFO, 9 days | Above line |
| Credit notes over $10k | No row | Nobody accountable | Gap |
| Capital requests under $25k | Plant manager | Plant manager and controller | Overlap |
| New hires within budget | Department head | HR director | Above line |
| Customer refunds over $2k | No row | Decided twice, differently | Gap |
| Software renewals | IT director | IT director and finance | Overlap |
| Supplier bank changes | AP lead | AP lead | Matches |
Beside what you have
The step your DoA system can't take.
A DoA policy keeps the written limits. A segregation of duties test checks system access. Neither tells you whether people follow the limits.
How each case is routed
One kind of decision. Each case to the right people.
Your rules say who decides, by amount, by region, and who must agree. Code routes every case.
What you get in five days
An exceptions list audit can file.
Why now
Fix the document before an agent inherits it.
AI agents will act inside someone's authority. Today that authority is a DoA many people don't follow. Any agent you bring in starts from a table that's true.
How the week runs
Nothing to connect.
- Before day 1ImportYour authority matrix, from a spreadsheet.
- Days 1 to 2SurveyA few minutes per person, about real decisions.
- Days 3 to 4ConfirmEach decider confirms their rows on real examples.
- Day 5WalkthroughThe exceptions list, with the unit's leadership.
Making it stick
No new system for people to learn.
A corrected policy nobody follows is where you started. So each fix is carried by the person who owns the row, and checked.
Three 30-minute check-ins with us: before day 1 and at day 30 with the unit's lead, and at day 90 with its leadership.
How a first engagement is scoped
Fixed scope, fixed fee, written success criteria.
- Unit
- One business unit, function or region
- People
- Everyone in it, a few minutes each
- Days
- Five working days to the walkthrough
- Fee
- Fixed, from $25,000, set by the unit's headcount
- You keep
- The exceptions list and the confirmed decision table
- Day 90
- A re-run, side by side, for audit
- New leader
- A brief from the confirmed table, per hire or move
- After
- Optional Ask Olive, monthly: every answer from the confirmed table, every decision logged, including those in forwarded meeting notes
Questions about scope?
Tell us the business unit and its size, and we'll send back a written scope.
Write to usSecurity and data
What we touch, and what we never do.
- Survey answers, and the matrix you choose to send
- Roles and counts in everything we report
- When you leave, a full copy of your data; we delete ours 90 days after you confirm you have it
- Your security questionnaire, answered
- Access to mail, chat, ERP or HR systems
- Anything installed on your network
- Anyone's answers shown by name
Questions procurement asks
Frequently asked questions
What system access do you need?
None. The survey, and a spreadsheet of your authority matrix if you have one.
Who sees individual answers?
Reports show roles and counts, never who said what.
Is this a segregation of duties test?
No. Those test system access. This tests whether your written authority matches practice.
Why one business unit?
A fixed, paid first engagement with written success criteria. The next unit follows the same week.
What does it cost?
A fixed fee from $25,000, set by the unit's headcount and agreed in the order before day 1. It includes the day 90 re-run and three check-ins with us.
Will it work beside our own change team?
Yes. They get the exceptions list, who owns each exception, and the evidence of each fix.