Seven fields. Every number needs a source and a date. If a field has no source, label the number as an estimate and say so in the field, not in conversation.
One sentence. What is being approved, how much, and by whom.
One line per cost. Next to each line, the system, report or person the number came from.
| Cost line | Annual cost | Source (system, report or person) | Date checked |
|---|---|---|---|
A range, not a point. Low and high, and what drives the difference.
| What changes | Low | High | What drives the range | Source |
|---|---|---|---|---|
License, implementation, and the hours your own people will spend. Hours × hourly rate is a cost line too.
| Item | Cost | Note (quantity x rate) |
|---|---|---|
| Software, year one | ||
| Implementation or onboarding | ||
| Integration and IT effort | hours × rate | |
| Training | hours × rate | |
| Internal owner time | hours × rate | |
| Total year one | sum of the rows above |
When cumulative benefit crosses cumulative cost, and what the three-year total looks like.
| Year | Cost | Benefit | Net | Cumulative |
|---|---|---|---|---|
| Year 1 | ||||
| Year 2 | ||||
| Year 3 |
One assumption per line. Each with where it came from, who owns it, and when it was last checked.
| Assumption | Where it came from | Owner | Date last checked |
|---|---|---|---|
The two or three things that would break the case, and how you would know early.
| Risk | Effect on payback | Early warning sign | Owner |
|---|---|---|---|