Compare Building Energy-Audit Proposals by Scope Before Fee

An energy-audit proposal is an offer to perform defined work. Before comparing fees, understand which building, data, site activities and deliverables the offer covers. Two proposals can use the same title while promising materially different investigations. A lower price can be attractive, but it is difficult to interpret when one proposal leaves important work or expenses unresolved.

This guide gives a building owner a practical way to prepare a scope comparison and a focused clarification request. The example uses two entirely fictional proposals. It does not evaluate a real professional, estimate energy savings or decide which audit a building requires. Technical suitability, procurement requirements and contract interpretation need the appropriate people and current information for the actual project.

The output is a side-by-side account of included work, exclusions, owner responsibilities and open questions. It should help the team request comparable information before choosing an engagement. The comparison is separate from the eventual audit findings and from a decision to install equipment or pursue financing. Keep each decision tied to the evidence and authority it actually needs.

State the owner's question before requesting a fee

Describe why the assessment is being considered. The owner might want to understand energy use, investigate a particular operating concern or prepare information for a future improvement decision. Those purposes can require different data and analysis. A request that simply says energy audit leaves the proposer to infer the desired outcome, making later fee comparisons harder.

Identify the intended users of the deliverable. A facilities team planning maintenance and a team considering a capital project may need different explanations or supporting detail. Ask what decision the report should inform and what it must contain to be useful for that decision. Do not assume every report is suitable for every financing, compliance or engineering purpose.

Keep any external requirement explicit. If a lender, public program or other body has its own assessment criteria, obtain the actual current requirements and appropriate review. This guide does not determine which standard or audit level is mandatory. A familiar label on a proposal is not evidence that the work meets a separate organization's conditions.

Identify the buildings and boundaries

List the actual premises intended to be assessed, including any relevant distinction between buildings, suites, common areas and operating systems. An address can contain more than one building or occupant. A proposal should make its physical and operational boundary understandable so the owner can see whether the desired work is included.

Record any area figures with their definitions and sources. Different measures of floor area can create misleading comparisons if treated as identical. The fictional example does not calculate an audit fee per square foot because no comparable measured area is supplied. If an actual comparison uses such a metric, verify that the denominator describes the same scope for each offer.

Clarify shared systems and access limits where relevant. The owner may control some spaces while another party controls others. A proposer needs accurate information about what can be inspected and what data can be obtained through authorized channels. Do not promise access to tenants, equipment or records on another party's behalf without the relevant agreement.

Use the primary audit guide as background

Pacific Northwest National Laboratory's A Guide to Energy Audits, prepared for the U.S. Department of Energy in 2011, provides background on audit options, the audit process and hiring an auditor. Its publication date matters. Use it as a starting resource and obtain current applicable standards and project requirements rather than treating an older overview as a complete specification for every building.

The useful lesson for a proposal review is that the requested work needs a defined scope. The fictional comparison in this article is original teaching material; PNNL and DOE have not reviewed the offers or endorsed this worksheet. The guide does not establish what any real firm will deliver or what energy improvements a particular property can achieve.

Read technical labels in the actual proposal and ask for the standard, version and deliverables they refer to. Do not invent equivalence between differently named assessments or assume a label contains every service you expect. Where a technical distinction affects the decision, have a suitably qualified person review it. The comparison sheet helps locate that question rather than answering it by assumption.

Compare the requested utility and operating data

Identify the period, accounts and measures the proposer expects to review. Bills, interval data, operating schedules and equipment information can answer different questions. A proposal that requests one year of bills and another that requests two years may involve different work or simply different available inputs. Ask what each proposer needs and why before interpreting the difference.

Keep actual data availability separate from the desired data set. The owner may have some records and need authorization or time to obtain others. A scope comparison should show who will gather the data, identify gaps and determine whether the available information is sufficient for the agreed analysis. Do not treat a request for data as proof that complete records exist.

The separate utility-billing-period guide can help organize source periods and overlapping records. It does not perform an energy audit. Preserve the distinction between preparing reliable input records and conducting the technical assessment. A tidy spreadsheet of bills can still omit a meter, a fuel source or an important operating condition relevant to the actual project.

Clarify what the site work includes

Read the proposal's description of site activities. Does it specify a visit, the spaces to be accessed, the people to be interviewed or particular observations? Keep the actual commitments visible rather than assuming a site visit means a complete inspection of every system. A scheduled presence at the building is not a self-explanatory technical scope.

Ask about owner preparation and participation. Someone may need to arrange authorized access, provide records or explain operating patterns. Identify those responsibilities and any assumptions about availability. A proposal can appear inexpensive while relying on substantial owner effort that has not been planned. The right comparison includes both the professional's work and the relevant owner tasks.

Do not turn the proposal review into instructions for opening equipment, taking measurements or entering restricted areas. Use the property's appropriate access and safety processes and the qualified professional's agreed method. This article supplies no technical inspection procedure. Its purpose is to clarify what the parties intend to include and what remains outside the engagement.

Understand measurement and analysis commitments

A proposal may describe calculations, measurements, modeling or other analysis. Ask what information will be collected and what assumptions will be documented. A general phrase such as detailed review may not establish whether a particular concern is addressed. Request a clear description appropriate to the technical scope rather than relying on the apparent sophistication of the wording.

Separate a potential improvement identified for further study from a fully developed design or guaranteed savings result. The actual report may contain estimates with assumptions and limits. Ask how those will be presented and what further work may be needed before implementation. Do not assume an audit engagement includes engineering design, procurement, installation or ongoing performance verification unless those services are actually specified.

If a proposer uses a savings or payback illustration in a sales discussion, identify its basis and relevance. An example from another building does not establish the outcome for yours. Keep marketing material separate from a project-specific technical conclusion. Appropriate professional review is needed where the owner intends to rely on the analysis for a consequential investment or operating decision.

Read the fictional Proposal A

Proposal A describes one fictional building, a review of twenty-four months of supplied utility records, one site visit and a written report with a findings discussion. Its fictional base fee is USD 1,800, with USD 200 travel explicitly included as a separate line, producing a stated total of USD 2,000. These are invented offer terms, not market-price guidance.

The example deliberately leaves several technical details to clarification. It does not specify every system, the exact analysis method or the treatment of missing data. A concise proposal can still require questions. The comparison should record those gaps without assuming the proposer will include whatever the owner later decides would be useful.

A useful follow-up asks whether the written report will address the owner's stated question, what input gaps could change the work and how any additional services would be approved. Do not infer that the USD 2,000 total covers unlimited visits, redesign or implementation support. The stated scope and any subsequent approved terms need to establish those matters.

Read the fictional Proposal B

Proposal B describes two fictional buildings and twelve months of supplied records. It quotes a USD 2,200 base fee and USD 300 travel, totaling USD 2,500. Its report deliverables are less clearly described in the teaching example. The larger price and wider stated property count do not make it automatically better or worse than A.

The two offers differ in premises, data periods and output clarity. Dividing each fee by its building count would produce numbers, but it would not establish comparable value. The buildings may differ, and the promised work is not defined on equal terms. Avoid converting an incomplete scope comparison into an apparently precise ranking.

The first task is to clarify B's intended deliverables and align the comparison with the owner's actual desired scope. If the owner wants only one building assessed, ask for an appropriate revised offer rather than assuming half the fee applies. If two buildings are needed, ask A how that would affect its proposal. The actual providers must state their terms.

Keep fees, expenses and exclusions visible

Separate the quoted professional fee from travel, taxes, optional services or other costs where the proposal identifies them. Do not add a missing amount as zero merely because the total looks cleaner. Mark the item unresolved and ask whether it is included, excluded or calculated under a stated arrangement. The relevant treatment depends on the actual offer and agreement.

In the fictional examples, A's total is USD 2,000 and B's is USD 2,500, a USD 500 difference. That is a price difference between the supplied offers, not a proven saving from choosing A. The scopes are not aligned, no implementation outcome is known and no whole-project cost comparison has been completed.

Keep optional work distinct from the base offer. A later measurement visit or additional analysis may be offered separately. The owner should understand what triggers that work, who approves it and how its price is established through the actual process. This guide supplies no contract language or universal rule for fees; it helps identify what needs a clear answer.

Check the deliverable and review process

Ask what the owner receives and in what form. A written report, a data workbook, a presentation and an informal verbal summary are different outputs. Identify which are included and what opportunity exists to ask about the findings. The name report alone may not explain the level of detail or how the owner can use it for the intended decision.

Clarify whether there is a draft review and how factual corrections are handled. The owner may need to correct a building identifier or explain an operating condition without changing the professional's technical judgment. Distinguish factual input review from a promise to revise conclusions until they match the owner's preference. The actual engagement should preserve appropriate professional responsibilities.

Identify the limits on reuse, reliance or distribution in the actual terms where relevant, and seek appropriate advice about them. A report prepared for one purpose may not serve another party's requirements. Do not tell a lender, buyer or public program that an assessment satisfies its needs without checking its current criteria and the actual report scope.

Compare schedules with their dependencies

A proposed delivery date may depend on records, access or other inputs being ready. Ask when the stated schedule begins and what happens if an input is delayed. A two-week period from complete data receipt is different from two weeks after accepting the quote. Keep those conditions visible when planning a larger property decision.

Coordinate the audit with other work through the responsible team. A site visit during an unusual operating shutdown may require explanation in the assessment. The owner should provide accurate context and let the qualified professional determine its relevance. This article does not prescribe an inspection date or decide which operating conditions are technically adequate for the agreed analysis.

Avoid promising another party a completed assessment before the engagement and dependencies support that expectation. A tentative date can be useful if labeled tentative. If timing is material to a purchase, financing or program application, bring the actual requirements to the appropriate advisers. A planning worksheet should not silently become a contractual deadline or assurance.

Prepare one focused clarification request

Group the open questions by scope, inputs, site work, deliverables, fees and timing. Ask each proposer to respond to the same relevant owner requirements where possible. That makes the answers easier to compare without forcing different technical methods into a false equivalence. Keep the requested output clear and allow the professional to explain an appropriate alternative.

Use a short request rather than sending a long list of speculative technical demands. For the fictional offers, the essential questions concern the building boundary, required data period, report contents and treatment of extra work. Those questions arise directly from the comparison. Additional technical requirements should come from the actual project and suitable review, not from copying a generic checklist indiscriminately.

Record revised terms separately from your interpretation of them. If a provider confirms a point, preserve the response through the authorized process and ensure the final engagement reflects the agreed scope appropriately. An informal assumption in the owner's spreadsheet should not outrank the actual offer or agreement. Seek professional advice where interpretation is material.

Make a decision note proportional to the evidence

A useful note explains the owner's objective, the comparable scope, remaining differences and the evidence supporting the selected next step. It can recommend seeking clarification before selection. It does not need to announce a winner simply because two prices are available. An unresolved material scope question is a legitimate reason the comparison remains incomplete.

If the responsible team selects a provider, retain the agreed scope and relevant review record through the normal process. Distinguish selecting an audit from authorizing any later building improvement. The report may identify questions or opportunities that require separate analysis, design, approvals or procurement. Do not treat one engagement decision as permission for all subsequent work.

The strongest comparison is understandable rather than elaborate. Another person can see what was requested, what each offer includes and which assumptions remain. That clarity helps the owner have a better technical and commercial conversation. It cannot guarantee energy savings, a particular report finding or the financial success of an improvement project.

Use status labels that preserve unanswered questions

A blank cell should not mean included. Use a small, defined set of working labels such as explicitly included, explicitly excluded, optional and clarification needed. Link each material label to the proposal passage or response that supports it. These are the owner's comparison labels, not a certification of the provider or a substitute for interpreting the actual engagement terms.

In the fictional worksheet, Proposal B's report format is clarification needed. It would be inaccurate to mark the report excluded, because the offer has not established that. It would be equally inaccurate to mark a detailed written report included. The distinction gives the proposer a fair question to answer and prevents the owner's summary from creating a term that was never offered.

Use the same discipline when a revised offer arrives. A response can resolve one cell while leaving another question open. Record the revision and inspect the effect on the whole comparison before announcing that the offers are aligned. A tidy grid is useful only when its labels remain faithful to the supplied evidence and the responsible review.

Frequently asked questions

Are two energy-audit proposals comparable if they use the same title?

Not necessarily. Compare premises, inputs, site work, analysis, deliverables, exclusions and timing. Ask what standard or version a technical label refers to and obtain suitable review where the distinction matters. A shared title does not establish equal scope, suitability or compliance with another party's requirements.

Is the fictional USD 500 difference a saving?

It is only the difference between two supplied fictional offer totals. A and B cover different building counts and data periods, and B's deliverables remain unclear. The figure does not establish comparable value, energy savings or a lower whole-project cost. Clarify the scope before making a price-based conclusion.

Does an audit include design and installation?

Only the actual scope and agreed terms can establish which services are included. Do not assume an assessment includes engineering design, procurement, implementation or performance verification. Ask about the deliverables and any further work needed for the intended decision. This guide does not define a universal audit package.

Should I demand the same data period from every proposer?

Explain the owner's question and available records, then ask each professional what inputs the proposed work needs and why. Different periods may reflect different scopes or constraints. Keep gaps and owner responsibilities visible. The fictional twelve- and twenty-four-month examples are comparison inputs, not universal technical requirements.

Can the worksheet determine whether a report meets a lender's needs?

No. Obtain the actual current requirements from the relevant party and have the proposed scope and report reviewed appropriately. A report prepared for one purpose may not satisfy another. The worksheet organizes questions and offers; it does not certify technical adequacy, compliance or eligibility for financing or a public program.

What is the next step when scope remains unclear?

Send a focused clarification request tied to the owner's actual objective and the material gaps. Preserve the provider's response and use the appropriate professional review. Do not fill missing terms with assumptions or select a winner merely because a fee is stated. A clear unresolved question is more useful than an unsupported conclusion.