The parts of a coherent file.

The summary describes the option selected

The summary brings together the model, the number of units, the duration and the total in USD along with the details entered. It lets someone who was not involved in the choice understand what was ordered. Keep it with the project's technical justification and the name of the person responsible for following it up.

If your organization uses an internal reference, match it with the one in the Capordia file. This correspondence makes exchanges between purchasing, the technical team and the person handling payment easier, without turning the name given to the server into a unique identifier for the entire operation.

Separate the order, the payment and the receipt

The order describes a recorded request. The payment tracking indicates whether the payment has been reported or confirmed. The receipt confirmation covers delivery and expected operation. This information can be gathered in one file, but it answers different questions.

The downloadable summary is a tracking document. On its own, it is not a paid invoice or proof of delivery. For any documentary question, quote the order reference so the context of your request is preserved.

Keep what will be useful for the next period

At the end of the project, note the configuration actually used, the key settings and how the results were retrieved. The next choice of capacity can build on this file instead of starting the analysis over. A team also gains clarity by recording why it changes model or duration.