Brand or city energy reporting request

What should happen when the reporting request arrives?

Save the original message, attachments, portal instructions, and sender information. Verify the request through a known channel before sharing account data or granting access. Identify whether it comes from the brand, a city agency, the property owner, or a reporting representative acting for one of them.

Write a requirement summary with the property, reporting period, due date, requested fields, destination, and named owner. Mark unclear instructions as questions. A request for calendar-year consumption differs from a request for the last twelve billing periods, and a deadline for internal review can differ from an agency submission deadline.

The hotel energy markets hub provides context for regional programs. This situation response begins with the received request and the actual property file. It does not assume every hotel is covered by a city ordinance or that every brand uses the same reporting system.

How should a city requirement be verified for the actual building?

Use the agency’s current instructions, coverage records, official identifiers, and applicable reporting year. Search by the required building or parcel identifier rather than only the hotel’s trading name. Confirm whether the request concerns one building, several buildings, or a property containing multiple uses.

New York City’s current LL84 benchmarking page is a concrete example. As reviewed October 12, 2026, its 2026 covered-buildings information addresses calendar-year 2025 reporting and the May 1, 2026 deadline. It instructs users to review current coverage and distinguish the tax-lot identifier from the individual building reporting level. Those facts are specific to that program and period.

Use the hotel’s actual agency record and current instructions to resolve coverage questions. An older website summary or another property’s experience is not enough. Preserve the source version and any official clarification used in preparing the submission.

What should the first two days produce?

Add a gap log showing the missing item, responsible person, request date, and expected response. Distinguish missing data from unclear requirements. The former may be resolved through a utility request; the latter may need clarification from the receiving organization or a qualified reporting professional.

How should the property’s energy boundary be mapped?

Inventory electricity, gas, and other relevant energy sources within the requested boundary. Identify separate meters for amenities, tenants, parking, or adjacent facilities. Reconcile the inventory with account records and physical use so a total is not mistakenly presented as complete when it omits part of the building.

Record whether each account contains actual consumption, estimates, corrections, or gaps. Keep units and service dates attached to the data. Electricity consumption and dollar expense are different fields. A supplier invoice total may include charges and adjustments that do not describe the property’s energy use.

EPA’s Portfolio Manager benchmarking guidance describes tracking building energy and related performance information. Use the requested system’s data definitions and property-use instructions. The hotel benchmarking guide helps organize the preparation, while the receiving program determines its submission requirements.

What should be requested from utilities or other data holders?

Ask for the reporting-period consumption, account and meter scope, units, dates, corrections, and explanation of missing intervals. Confirm the required authorization and available delivery method. If a representative requests data, use the relevant provider’s approved permission process and limit access to the purpose needed.

DOE’s utility data access guidance discusses approaches to obtaining whole-building data and streamlining access. Availability and aggregation procedures vary by utility. Do not assume that every utility automatically sends complete hotel data to Portfolio Manager or that a connection eliminates the need for review.

Assign someone to reconcile delivered data against the meter inventory. A successful download can still omit an account, use the wrong reporting period, or contain a correction received later. Retain original files and a controlled working version so changes remain explainable.

How should property characteristics be checked?

Locate the source for floor area, property uses, room counts where required, and any other requested characteristics. Ask the responsible property staff to reconcile conflicting records. Do not copy a marketing description into a reporting field when the system defines that field differently.

For a hypothetical example, assume an internal file describes the hotel operation while a requested boundary includes a separately metered restaurant. The reporting owner must establish how the receiving program treats that space before finalizing the inventory and property details. Adding its bill total without resolving the boundary would not answer the full question.

Record changes in use or operating status during the reporting period. They may require explanatory information or system-specific treatment. A project closure should not be treated as an automatic exemption without current program instructions and any required official response.

What distinguishes data entry from an accepted submission?

Prepare the report, review errors, confirm permissions, and use the stated destination. Retain evidence showing what was submitted, when, by whom, and for which property and period. Where the receiving organization provides acknowledgments or status checks, keep those records with the file.

In the NYC example, the official instructions include connecting and sharing through Portfolio Manager. Completing a private spreadsheet is therefore a different step from following the city’s process. For another jurisdiction or brand, verify its own method instead of carrying over this workflow by assumption.

Create a final-review checklist covering property identifiers, dates, meter completeness, units, property characteristics, unresolved alerts, and destination. The reviewer should see the gap log. Unresolved issues should not disappear simply because the team reaches an internal deadline.

How should separate reporting and compliance questions be handled?

A benchmark, brand questionnaire, emissions filing, and building-performance assessment can be related without being interchangeable. The building-performance standards guide explains why the actual jurisdiction and program matter. Determine which request is in scope and who is qualified to assess additional obligations.

Keep reporting evidence separate from conclusions about compliance or operating performance. A complete consumption record may support later analysis, but it does not by itself prove an emissions limit was met, a score is certified, or an improvement was caused by a project.

The wholesale-market guide provides a different context for the supply system. Wholesale purchasing arrangements do not replace building-level reporting evidence. When procurement records are requested, clarify how they relate to the program’s defined energy and emissions fields.

What is an actionable first-response sequence?

1. Preserve and verify the reporting request.
2. Identify authority, current period, due date, boundary, and destination.
3. Confirm official property identifiers and applicable coverage.
4. Inventory meters, fuels, and required property characteristics.
5. Request missing data through authorized channels.
6. Reconcile units, dates, completeness, and system errors.
7. Submit through the required process and retain acceptance or status evidence.

At forty-eight hours, the reporting owner should have a requirement map, data inventory, and accountable gap list. The submission may remain unfinished while records arrive. State that status accurately and preserve the next actions. A useful first response creates a traceable reporting file rather than an unsupported declaration that the hotel’s obligations are complete.