Versioned, repeatable procedures.
An AOP is how a process stops living in someone's head. Triggered by schedule, inbound email, or a meeting; branching by entity, region, or account; versioned and auditable every time it runs.
A prompt is a suggestion. A procedure is an institution — the same steps, the same standards, every time, with a version number attached.
The procedure runs the moment its condition is met.
By schedule, by inbound email, or by a meeting ending — an AOP does not wait to be remembered. The trigger is part of the procedure, not a habit someone has to keep.
One procedure, every business context.
Procedures branch by entity, region, or account, so the same AOP adapts instead of forking into a dozen near-identical copies that drift apart.
Institutional memory you can roll back.
Every AOP is versioned and auditable. When a procedure changes, the change has an author and a date — and the previous version is still there.
| Rev | Change | Author | Date |
|---|---|---|---|
| v7 | Add FX revaluation branch | D. Rowe | 2026-06-02 |
| v6 | Split EMEA / APAC entities | Athena | 2026-04-18 |
| v5 | Tighten variance threshold | M. Okafor | 2026-02-09 |
Written once, run indefinitely.
- 01 Trigger
A schedule, an inbound email, or a meeting fires the procedure.
- 02 Branch
The AOP resolves the right path for the entity, region, or account.
- 03 Execute
Steps run across artifacts and systems, in order, with checks.
- 04 Version
The run and any change to the procedure are recorded and reversible.
One system, named in parts.
Turn a process into a procedure.
Bring your messiest recurring workflow and see what it looks like versioned.