The current file list may not describe what the service stores

A document workspace can display one current file while retaining earlier versions and generated previews behind it. Those objects may be operationally necessary, and a provider’s storage meter may count them. An estimate based only on current downloads can therefore miss a continuing dependency of the project.

This fictional example uses an inspected provider contract that meters the listed retained objects. It contains no real subscription price or promise about another provider’s billing. The calculation establishes what needs to be included in the planning inventory before the organisation compares actual costs.

Inventory the objects, not only the rows

The workspace shows three current documents. D-11 is 4 MiB, D-12 is 6 MiB and D-13 is 2 MiB. Looking only at that screen produces an estimate of 12 MiB.

The object inventory shows more:

Here MiB means 1,048,576 bytes. The example uses explicit units because a provider may present capacity differently. The calculation should reconcile to the provider’s actual meter and contract rather than assume that every “MB” label means the same thing.

Check why the extra objects exist

The earlier versions preserve the history required by the organisation’s approved document process. The previews support the current viewing interface. They are not all accidental duplicates waiting to be deleted.

The owner checks the retention rule and confirms that the listed earlier versions must remain for this stage of the project. Removing them merely to make the original estimate true would change the agreed operating model. Preview generation and replacement are also reviewed so the team understands which objects persist and which are temporary under the chosen service.

Backups are inspected separately. In this fixture they belong to a different agreed storage arrangement and are not included in the 28.5 MiB meter. They still need a cost and responsibility line in the project plan. Adding them blindly to this meter would be as misleading as forgetting them entirely.

Revise the estimate without inventing a fee

The selected planning baseline becomes 28.5 MiB for the inspected document objects, with separate entries for backup storage and future growth assumptions. Actual provider prices, minimum charges and included allowances must be read from the relevant account terms when the proposal is prepared.

The plan also records the behaviour that drives growth: how often documents gain new versions, whether previews are retained for every version and who can apply the approved retention policy. A single initial total cannot predict those decisions by itself.

The organisation chooses to retain the required history and budget for it. It does not reduce the accepted document scope or silently change the retention rule. If future costs prompt a different policy, that becomes a separate business and, where necessary, professional review.

Record the completed reconciliation

The fictional inventory totals 28.5 MiB and matches the selected provider meter for the listed objects. Each current document remains retrievable, the required older versions remain available to their permitted users and the previews still support the intended view.

The review identifies no deletion as part of correcting the estimate. D-13, with no earlier version, remains the useful control: its 2 MiB current file plus 0.5 MiB preview accounts for its full 2.5 MiB contribution. The discrepancy was caused by the estimate’s incomplete population, not by a mysterious provider charge.

The accepted project note now names who reviews storage growth and who may change retention. It also points to the actual account terms instead of embedding an unsupported price in the technical plan.

Look beyond storage in the same way

Language review, provider accounts, exception handling, recovery exercises and content maintenance can also sit outside a visible page count. Ask what must continue for the delivered task to remain useful, who performs it and which external contract governs it.

Pricing and scope explains how those responsibilities belong in a proposal. Maintenance and handover can help establish the ongoing inventory. The aim is an estimate that describes the service being operated, including the necessary work that the current-file screen does not show.