Evidence4 of 6
A verdict stays a verdict
A decision approved on a comparison has to be explainable long after prices have moved. This is what a saved comparison keeps.
- Inputs, result, and every charge kept together
- Never priced again behind your back
- A change makes a new version beside the old
What a version keeps
Every time a use case is priced, the result is saved as a numbered version.
The inputs
Exactly as they were given.
The whole result
Every option, every charge, every warning and note.
The prices it used
Every charge as a quantity and an amount, with where its rate is in the provider’s price list, and which price list that was, with the date the provider gives it where there is 1, and how old it was on the day.
Every assumption
With the provider page it rests on.
What worked it out
The date the billing rules were last checked against their sources, and the release of CloudVerdict that did the calculation.
When
The date and time it was priced.
When prices change
A use case is priced
The result is saved as a numbered version, with everything above.
Prices move
The saved version is not priced again, and nothing edits it. What it showed on the day is what it shows now.
It is priced again
That makes a new version, with the prices in use then. Changing the use case makes a new version too.
The 2 are told apart
On Standard and Premium, where earlier versions are shown, the screen says what changed in the workload and how far the cheapest total moved.
What you can take away
A PDF report and a CSV file
On Standard and Premium, of any version, with every earlier version kept and listed.
An executive brief
On Premium, of any version: the decision in brief, for whoever signs off the cost.
A CSV can be imported
On every plan, to start a new use case from the inputs that plan takes.