A portfolio quote folder can start with a handful of invoices and become an unstructured archive of contracts, forecasts, financial statements, and earlier bid versions. Giving more people access does not make that evidence more usable. The hotel needs a record structure that preserves account boundaries, permitted recipients, and the difference between issued and working files.
Within the procurement hub, this guide addresses the file lifecycle around a competitive request. It does not prescribe a particular storage product or add a submission form; the working repository should follow the customer’s own approved controls.
Which account structure should organize the room?
Assign a stable reference to each service point or documented account group. Keep legal customer, hotel, utility, fuel, service identifiers, and current supply position in the account register. Use that register to explain which records belong in the request.
A portfolio overview can help navigation but should not replace individual account evidence. An annual total, a contract schedule, and an interval export can each have a different boundary. Keep filenames and references meaningful enough for a bidder or replacement employee to find the original source.
The quote-input guide identifies the normal evidence categories. The data room adds the controls that determine which version and recipient uses them during an evolving purchase.
| Manifest field | Purpose | Example record category |
|---|---|---|
| Account scope | Identifies included service points | Account schedule |
| Source, dates and units | Defines measurement boundary | Bills or interval export |
| Version and issue status | Separates working from released record | Forecast summary |
| Recipient permission | Controls approved sharing | Authority or credit evidence |
| Correction reference | Links new and superseded information | Revised account or usage file |
How does utility consent differ from folder permission?
Ameren’s Share My Usage process provides a specific route for account-data authorization. Match the approved consent to the actual utility customer, data, and recipient. Another utility may require a different process.
Internal repository access is a separate decision. A person allowed to obtain utility records does not automatically need unrelated contracts, financial evidence, or portfolio plans. Conversely, a bidder invited into a folder still needs the appropriate permission for a utility to release records.
Document the intended actions and recipients at both levels. If someone requests broader access, identify the task that requires it and obtain the customer’s approval. Do not solve a missing-file problem by expanding every supplier’s permissions indiscriminately.
Which records should remain separately controlled?
Identify sensitive authority, financial, identity, and private-agreement material before inviting bidders. Ask what a recipient actually needs for the current stage. The customer’s own confidentiality and access rules determine the sharing route and restrictions.
Texas Rule 25.486 contains customer-protection and client-agent data provisions relevant to applicable Texas brokerage work. Use its specific scope rather than describing it as a nationwide repository-security standard.
Preserve an evidence summary where appropriate instead of distributing an entire private file unnecessarily. The summary must not conceal a commercial condition the reviewer needs. Have the authorized owner determine what can be shared and retain the actual approval.
What makes source files distinguishable from analysis?
Keep original bills and exports identifiable. Place standardized summaries, cleaned intervals, and forecasts in separate versions with a method note. A filename containing final does not establish that its quantity, period, or account coverage was verified.
DOE’s EMIS capabilities guidance distinguishes invoice validation, interval analysis, and other account functions. A system can integrate those functions while each still requires valid source information.
Label estimated or missing periods and the assumptions used to address them. A bidder should be able to distinguish observed consumption from a model without inspecting every formula. Record the analyst and reviewer for material transformations rather than presenting a polished spreadsheet as utility-origin data.
How are issued versions preserved?
Create a release manifest identifying files, versions, date, recipients, and response requirements. Once released, preserve that set even if working records change. A supplier’s quote should refer to a known account and assumption version.
The quote-document checklist can support the manifest. The data room’s added task is lifecycle control: who can change a file, what status it has, and how a recipient learns that it was superseded.
Avoid overwriting an issued file silently. Rename or otherwise distinguish a revised version through the approved repository process, and retain the correction explanation. This keeps the comparison reproducible if one supplier downloaded the old file before another received the update.
What can an assumed version mismatch demonstrate?
Assume a hypothetical release includes three service points and a twelve-month usage summary. A later review discovers that one service point’s summary omitted a month. No real account, consumption, or cost is implied.
The coordinator should preserve the original release and issue a corrected file linked to the affected row. Tell the invited bidders which period changed and ask whether they need to refresh their offers. Merely replacing the total can leave an earlier quotation based on different assumptions.
In a second assumed scenario, the account schedule changes from three service points to two. That is a scope correction, not just a filename change. The provider’s included-account response and the owner’s approval must be reconciled with the corrected request.
How should questions and corrections reach bidders?
Use a controlled clarification log. Identify the question, affected record, answer source, materiality, recipients, issue date, and any required response. The coordinator can distribute relevant clarifications consistently without publishing unrelated confidential information.
A bidder-specific credit request may need a separate route from a material forecast correction affecting every offer. Distinguish those cases rather than applying one universal distribution rule. The customer’s authorization and the actual purpose govern the recipient list.
PPL’s direct-access procedures show that supplier and utility account records also have defined transaction roles. An internal correction does not itself update a provider’s enrollment or confirm that the utility accepted new account information.
What belongs in the commercial release?
Include requested component boundaries, start assumptions, term alternatives, account exceptions, and response format. Keep the complete offered agreement tied to the relevant quote version. Identify where the bidder must state deviations rather than let a blank response cell appear favorable.
Request broker compensation information: payer, amount or method, units, and embedded or separate treatment. Preserve it with the comparison and count embedded payment once. A separate commercial folder can make this evidence easier to find without implying it has different authority from the approved purchase record.
The competitive bid guide covers the award process. The data room should serve that decision with controlled evidence, not become a substitute for comparing offers or approving obligations.
How should the room close and transfer to operations?
- Reconcile the account register and approved recipient scope.
- Preserve source files separately from analysis and forecasts.
- Issue a dated manifest and keep released versions.
- Record material corrections and affected quotations.
- Retain final offers, compensation and approval evidence.
- Apply approved supplier access and retention changes.
- Hand signed, enrolled and first-bill records to the operating owner.
Archive unresolved actions with their owners and next dates. Closing the bid does not close missing enrollment evidence or an unaccepted correction. The operating file should make those limits visible rather than hide them beneath a folder named completed.
The useful result is a repository another person can navigate and trust within its stated limits: whose account, which source, which version, which recipient, and which decision. That structure supports a reviewable purchase without claiming that more files or broader access produces a better offer.