A hotel’s energy contact can be experienced, responsive, and still lack authority to accept a contract. The purchasing process needs to distinguish work performed from obligations approved. Otherwise a familiar email address, a shared login, or a previous transaction can become an unsupported assumption about who may act for the customer.

Use the procurement hub to connect the account file with the wider purchase. This guide addresses the permission trail from initial data access through the approved agreement, with a particular focus on handoffs that can expand authority unintentionally.

Which customer entity will accept the obligation?

Copy the actual utility customer from current records and compare it with the proposed supply agreement. Identify the entity name, service accounts, and any trading name separately. An owner, operating company, management company, and franchise brand can all appear in hotel documents without having interchangeable authority.

Ask the customer’s authorized reviewer which evidence supports the proposed signer. Relevant evidence might include approved entity instructions or a management agreement, but the applicable documents determine the result. This website cannot infer a person’s authority from an organizational chart or supply its own legal interpretation of private agreements.

PPL’s direct-access procedures illustrate how supplier enrollment and customer authorization belong to a defined utility process. Completing that process is separate from verifying the hotel entity’s internal approval rules.

Which permissions should remain separate?

List the actions the hotel intends to authorize. Reading bills, retrieving interval data, inviting offers, discussing alternatives, approving commercial terms, signing an agreement, and submitting enrollment can require different evidence or people. The sequence should not assume that authority automatically grows as a project progresses.

Ameren’s Share My Usage process is a specific example of account-data authorization. It provides a useful distinction between sharing consumption information and purchasing supply. Another utility’s process may use different permission fields or identification requirements.

Permission register for one hotel purchase
ActionPermitted scopeApproval evidence
Retrieve recordsNamed accounts and approved dataAccount-holder consent
Request and discuss offersDefined bid assumptions and recipientsPurchasing instructions
Approve termsSpecified commercial version and limitsAuthorized decision record
Sign supply agreementActual customer and obligationConfirmed signing authority
Enroll accountsApproved supplier and service identifiersApplicable transaction authorization

The register is an internal control recommendation, not a claim that every jurisdiction mandates this exact table. Its value is making the intended scope intelligible to the people doing the work.

What does a broker authorization establish?

Read the document rather than relying on its label. A form called an LOA can contain a narrow data permission, broader negotiating powers, or client-agent language. Mark the intended actions and ask the authorized reviewer to resolve anything that appears to permit purchasing or binding the customer.

Texas Rule 25.486 requires a written broker-client agency agreement and specified information about permitted actions when a broker acts as a client agent. That is a meaningful Texas protection; it does not establish another state’s rule or prove an individual hotel employee has corporate signing authority.

The LOA guide explains the underlying instrument. Here, the key decision is where that instrument sits in the hotel’s permission register. A signed form must be matched to its actual customer, accounts, actions, and duration rather than treated as unrestricted project authority.

How does provider selection differ from internal approval?

Texas Rule 25.474 addresses retail provider-selection authorization and verification. Use the provisions applicable to the actual account and transaction. Do not substitute a universal hotel deadline or consumer right for the relevant rule and agreement.

A provider can require verification that an applicant requested selection while the hotel separately requires owner approval of commercial terms. Those checks serve related but different purposes. Passing one does not establish the other.

Record the submitted request, selected account identifiers, confirmation, and any rejected transaction. If the supplier asks a different person to complete verification, make sure that person’s permitted role is understood. A convenient handoff should not bypass the entity’s approval conditions.

What should be approved before a signature is requested?

Prepare the version the signer will actually execute. It should identify the included accounts, product components, start assumptions, term, credit conditions, volume treatment, material exceptions, and the complete agreement. A presentation summary can help the reviewer, but it should point to the governing documents.

Disclose broker compensation in the same commercial file. State the payer, amount or calculation method, relevant units, and whether it is embedded or separate. Approval of a headline energy rate without the compensation treatment can leave the reviewer approving a different economic proposition from the one intended.

The broker evaluation guide supports service and payment questions. Authority review remains the hotel’s own customer-entity task. A broker’s registration, experience, or supplier access does not independently authorize that broker to sign the hotel’s contract.

What can a hypothetical approval mismatch show?

Assume a hotel owner approves an offer for two identified accounts with a proposed October start. Before signature, the supplier’s agreement adds a detached building account and changes the start assumption. No price, saving, or real transaction is implied.

The original approval does not resolve the new account’s customer authority or the revised date. The coordinator should identify the differences, obtain the necessary evidence, and return the commercial version for the required approval. A faster signature would merely conceal the mismatch.

In a second assumed situation, the finance director can approve spending but the management agreement reserves execution to the owner. The process needs both steps. Combining them into a single approved status would incorrectly describe what has actually been completed.

How should absence and delegation be handled?

Identify foreseeable absences before bids arrive. Ask the customer entity to establish any delegation it intends to use, including its limits and effective period. Keep that evidence available to the coordinator and signer. A colleague’s willingness to help is useful, but it is not itself an authorization document.

If no authorized person can act before quote expiry, request refreshed terms or review another supported path. Do not amend a name, use another person’s access, or treat a previous signature as reusable permission. The exception should have an owner and a commercial consequence recorded.

For a management company, retain property-specific evidence even when central staff performs the work. The multi-property management guide explains why centralized purchasing and account-level authority must coexist.

What evidence should remain after execution?

  1. Identify the utility customer and intended contracting entity.
  2. List each permitted action and its account scope.
  3. Resolve private-document authority with the authorized reviewer.
  4. Match data and agent permissions to their actual forms.
  5. Approve the exact commercial and compensation version.
  6. Confirm the signer and any supported delegation.
  7. Retain selection, enrollment, and first-bill evidence separately.

Archive the final permission register with the signed agreement and decision record. Mark superseded drafts so a future employee does not mistake an old authorization for the current arrangement. If staff, ownership, or management changes, review the ongoing permissions instead of allowing an obsolete email trail to define access.

The useful outcome is a purchase another reviewer can reconstruct: who supplied evidence, who approved which terms, who signed for the customer, and which accounts were accepted. That trail supports accountability without claiming that a checklist creates legal authority.

The competitive bid process should use this permission trail when moving from recommendations to an award. Each approval belongs to the customer and commercial version actually being purchased.