Months after an award, a hotel owner asks why a supplier was selected. The team has a spreadsheet, several quotation emails, and a signed agreement with a slightly different schedule. A useful decision file should explain the recommendation and those changes without depending on an employee’s recollection.
The procurement hub describes the wider process. This guide creates the approval memorandum that connects evidence, judgment, authority, and subsequent execution while keeping their status distinct.
What decision does the memorandum record?
State the customer, account group, proposed supply period, and decision requested. Identify whether the reviewer is approving a preferred offer, an execution-ready agreement, a specific exception, or another defined action. A generic approved heading can conceal important differences.
Write the recommendation in a few factual sentences. Name the offer version and the principal reasons it meets the approved requirements. Distinguish observed provider responses from analytical assumptions and unverified claims.
The competitive bid guide handles the request and comparison process. The memorandum should preserve its final decision, not retell every email exchanged during the auction or add an unsupported supplier-quality narrative.
| Decision element | Record to identify | Question answered |
|---|---|---|
| Account and period | Final schedule and start assumptions | What is being purchased? |
| Offer version | Dated quotation and complete agreement | Which commercial terms were reviewed? |
| Exceptions | Provider response and reviewer disposition | What remains conditional? |
| Economic treatment | Components and compensation record | What does the comparison include? |
| Authority and status | Approval, signature and enrollment evidence | Who accepted which action? |
How are assumptions made reproducible?
List the forecast, service dates, included meters, quantity units, and expected operating changes used in the comparison. Attach references to the original records and any cleaned summaries. The reviewer should be able to identify the boundary without opening every file.
DOE’s EMIS capabilities guidance describes account data, invoice validation, and analytical functions. These capabilities support traceability; software output does not independently verify the underlying account or forecast.
If an assumption was accepted despite incomplete evidence, identify it specifically. State who accepted the limitation and why it was appropriate for this stage. Do not hide a missing service identifier or uncertain opening date beneath a broad statement that all figures are estimates.
What should be said about rejected alternatives?
Record the material reason each relevant alternative was not selected. This could concern a differently structured price, an excluded account, an unresolved requirement, or a documented tradeoff. Keep the description neutral and evidence-based.
Avoid attributing motives or future performance to a provider. An offer lacking a required confirmation can be described as incomplete for the decision date without claiming the supplier is generally unreliable. Preserve the actual question and response that support the disposition.
Use the comparison worksheet for the economic detail. The memorandum explains how the customer used that detail and which exceptions affected the recommendation.
How does the governing agreement connect to the summary?
The Pennsylvania commission’s contract explanation identifies terms requiring careful reading. For the hotel, retain the actual commercial document and applicable customer provisions rather than universalizing the public summary.
Cross-reference the price structure, term, account schedule, credit conditions, volume treatment, and other material provisions. The recommendation should identify the complete agreement version considered. A supplier’s one-page offer can be useful, but it should not silently replace governing clauses.
If the final agreement differs from the quotation, write the differences before asking for signature. The file should distinguish an approved change from a variation that still needs review. This is especially important where an added account or changed start appears in an attachment rather than the document’s main heading.
Where should broker compensation appear?
Include payer, amount or calculation, applicable units, and embedded or separately billed treatment in the decision’s economic record. If the comparison already includes an embedded payment, count it once. Explain any material difference among proposals.
Texas Rule 25.486 provides specific broker disclosure and customer-protection requirements. Apply it where relevant to the actual Texas transaction; it does not establish every jurisdiction’s requirements or a particular firm’s status.
The memorandum should make the payment arrangement understandable without assuming a separate invoice exists. A statement that advice is free is not an adequate substitute for the actual compensation explanation supporting the customer’s approval.
What can a hypothetical version check demonstrate?
Assume a customer approves quotation version two for three identified accounts. The later agreement schedule includes four accounts and a revised start assumption. These are illustrative document facts, not a real supplier incident or a claimed financial outcome.
The coordinator should prepare a difference note: added service point, customer authority, forecast impact, commercial treatment, and required approval. Attaching the earlier approval to the new agreement without that review would make the file appear more complete than the evidence supports.
If the revised account is intentionally excluded after review, preserve that decision and its current service owner. The memorandum then explains both the accepted award and the remaining portfolio action.
How should execution and enrollment be distinguished?
Use separate status fields for recommendation, approval, signature, submitted enrollment, accepted enrollment, and first-bill reconciliation. Record dates and evidence for each. An unsigned recommendation can be complete as analysis without being a completed purchase.
PPL’s direct-access procedures demonstrate why utility-specific transaction evidence belongs after commercial selection. Apply the actual serving utility’s process and preserve service-point status rather than inferring enrollment from a signed supplier PDF.
When only some accounts enroll, describe the partial result. Assign rejected or delayed rows to a named person and keep their service arrangements visible. The award memorandum should not erase an operating exception by retaining a single complete flag for the whole group.
Which changes require renewed review?
Follow the customer’s actual approval rules and identify material commercial changes clearly. Typical review questions concern revised accounts, dates, components, term, credit, volume, exclusions, or compensation. This list is a management prompt, not a universal legal threshold.
Write the old value, proposed new value, supporting source, and reviewer action in a change log. Link the renewed decision to the revised version. Avoid leaving the signer to reconcile changes from several disconnected emails.
The quote-input guide supports the underlying evidence. A later corrected record can change the comparison; identify whether that correction was considered before execution or became a post-award exception.
How should the final file be handed to operations?
- Identify the exact customer, accounts and requested approval.
- Link the recommendation to comparable offer versions.
- Preserve assumptions, rejected alternatives and unresolved exceptions.
- Document compensation and governing commercial provisions.
- Record the authorized decision and any renewed review.
- Keep signature and accepted enrollment as separate evidence.
- Give the billing owner the approved component and account record.
The handoff should contain relevant support contacts, first expected service periods, open actions, and the location of the signed agreement. Sensitive access information belongs in the customer’s approved access process rather than a broadly circulated memorandum.
A useful award file answers the owner’s later question with evidence: what was proposed, why it was chosen, who approved it, what changed, and which accounts actually began the confirmed arrangement. That is a decision record another person can use, without inventing hindsight about market success.
Set a retention owner and a review trigger for customer or management changes. Preserve the document relationships so an archived approval remains connected to its account schedule, supporting assumptions, and later correction history.