AFOS™ · ApexForm Operating System™
Keep the reasoning behind an important business decision.
A team is considering a second warehouse. It needs a clear record of the options, the reasons for its choice and what to check afterward. This example shows how a team could use AFOS for that job. The figures are fictional and the later results are left unfilled.
Reviewed
The business problem
The expansion proposal has moved through a spreadsheet, a presentation and several meetings. The team needs to bring the evidence and objections together before committing to a lease.
When the decision comes back for review, a colleague should be able to see why the team made the choice, who approved it and what evidence would justify changing direction.
What AFOS helps the team produce
The intended practical benefit is less work rebuilding the story for the next meeting or handover. That benefit needs to be measured against the team’s existing process; this example does not establish time saved or better business results.
- A decision record containing the question, options, supporting evidence and unresolved gaps.
- A recorded human decision, with the reasons and material objections retained.
- An executive memo drawn from the record, with the next action and review arranged separately.
1. Put the options and evidence together
The team compares a second warehouse with a smaller, temporary capacity trial. These are illustrative inputs supplied by the team, not figures calculated by an AFOS forecast.
- Warehouse utilisation: 94%. Order backlog growth: 28%.
- Proposed lease: $480,000 a year, with a $120,000 exit cost.
- Alternative: a 60-day overflow-capacity trial with a $60,000 spending cap.
- Evidence still needed: how much demand is likely to persist, and whether temporary capacity can meet it.
2. Record the objection before making the choice
The case for expansion is that capacity is tight and delays could cost the business customers. The objection to a temporary trial is that it might postpone an expansion the business already needs.
The record keeps that objection alongside the alternative. The decision-maker can consider the trade-off, and the reviewer can check it later instead of relying on someone’s memory of the meeting.
3. Record the human decision and next action
If a client is involved, agree the approval and information-sharing process first. A client-readable memo does not establish a separate client approval portal.
- Illustrative decision: defer the long-term lease and approve the 60-day trial within the agreed cap.
- Reason: test whether temporary capacity addresses the immediate problem before making the larger commitment.
- Record approval through the workspace’s authorised, qualified decision-maker.
- Assign the operations lead to track spending, demand and service performance, then prepare the review.
4. Hand over a memo people can use
The generated memo summarises the recorded recommendation or decision, rationale, dissent and sign-off. It can also show the agreed review interval. Before sharing it, the team adds the supporting evidence, confirms who owns the next action and sets the calendar review date.
- Example handover decision: run the temporary capacity trial before committing to the lease.
- Why: the team needs evidence about lasting demand and the effectiveness of the smaller option.
- Unresolved objection: a trial could delay an expansion that is already necessary.
- Team-added review plan: return in 60 days, or earlier if service performance crosses an agreed threshold.
5. Return to the evidence after 60 days
The team must collect the actual results. The review records what happened, whether the original reasons still hold and whether to continue, change or stop the trial. No successful outcome is assumed below.
| What to review | Starting point or commitment | Actual result |
|---|---|---|
| Trial spending | $60,000 cap | To be measured |
| Warehouse utilisation | 94% in the fictional starting case | To be measured |
| Demand and backlog | 28% backlog growth in the fictional starting case | To be measured |
| Service performance | Agree a baseline and threshold before the trial | To be measured |
| Next decision | Reconsider the lease after the trial | Human decision after reviewing the evidence |
Test the value on one of your own decisions
Choose an appropriate internal decision with a named owner and a review that will occur during the pilot. Agree what AFOS must do better than your current process before starting.
- Track total staff time, including setup, data entry and any vendor assistance.
- Ask a colleague outside the original discussion to find the decision, explain the reasons and identify the next action.
- Measure the work needed to prepare the memo and complete the later review.
- Afterward, decide whether the improvement justifies the subscription and the effort of keeping another tool up to date.
Common questions
Is this a real customer result?
No. It is a fictional example. The review results are deliberately unfilled because no customer outcome is being reported.
Why use AFOS if we already have shared documents?
AFOS is worth evaluating when maintaining the evidence, approval, memo and later review across your existing tools takes too much effort. If a shared document and your current process already do that well, a new subscription may not be worthwhile. Test the difference on your own work.
Can our team use its own decision process?
Bring an example to the pilot discussion. Agree which parts AFOS supports today, what manual work remains and what would require separately scoped changes.