Sample Decision Pack

Open the sample Decision Pack. It needs no form and no email address. A sample Monthly Close shows the month after.

About Example Ltd

Example Ltd is an illustrative company. Its figures, teams and dates show the format of a Pack, and they describe that company, not yours.

What the sample contains

The sample reads top to bottom:

1. The first page. What to start now, the monthly saving, and who approves it by when.
2. The increase. Why the bill moved, by service and cause. Anything not yet explained is marked.
3. The ranked decisions. Four decisions in the sample, ranked by benefit, effort and risk. Two start now. Two wait for a sign-off or a date.
4. What to leave alone. A standby server at 4% CPU looks idle. It is the recovery copy, so the Pack keeps it and says why.
5. Owned and unowned spend. Spend with no clear owner, named.
6. Reservations. What ends soon, and what to buy only after the other changes land.
7. Scope and the call. What the Pack read, and what the 45-minute call with your engineer added.

A Pack has 3 to 5 decisions. Within the 7 days, engineering sees the findings 2 working days before finance.

What each decision carries

Part	What it tells you
Why	The evidence from the bill and the resources, and the monthly amount
Confidence and range	High or medium, with a low and a high monthly figure
Risk	What can go wrong, and how fast you can undo it
Who	Who is accountable, who implements, and who approves
Change note and test	The scope, the checks before the change, and the way back
How we measure	Which line on which bill shows the saving

Your team or your MSP makes every change. The Pack names the implementer as your own team.

How a finding reaches the Pack

1. An Infralign expert checks source coverage and reconciles the cost baseline.
2. The expert reviews candidate findings for duplicates, weak evidence, and operational constraints.
3. Your engineer adds architecture and business context on the 45-minute call.
4. The Pack keeps 3 to 5 decisions, and lists what to leave alone.

Nothing in the Pack changes an Azure resource. The two roles, Reader and Cost Management Reader, cannot change resources or configuration. Reading your Decision Pack explains the fields on each finding in the app. Savings measurement methodology explains when a saving counts.

---

Next: price and terms.