What Is a Lighting Audit?
- LumaQuote
- Apr 14
- 18 min read
Updated: May 4
What is a lighting audit? A lighting audit is a structured review of a building’s existing lighting system. It captures fixture counts, lamp and driver details, operating hours, controls, energy rates, and site conditions so a team can identify waste, calculate savings, estimate rebates, and build an accurate retrofit proposal.
What a lighting audit actually does
A lighting audit is not just a count of fixtures. Its job is to answer five practical questions:
What is installed now?
Fixture type, lamp type, wattage, quantity, controls, and condition.
How is it being used?
Daily hours, occupancy patterns, shift schedules, and after hours use.
Where is energy being wasted?
Overlit areas, outdated lamps, inefficient fixtures, or lights running when spaces are empty.
What can realistically be upgraded?
LED retrofit options, fixture replacements, sensor opportunities, daylight response, and controls by area.
Can the job be priced and sold properly?
A real audit supports material takeoff, labour assumptions, savings calculations, rebate workflows, and final proposal output.
That is the key difference between a rough walkthrough and a real audit.
Basic fixture count | Real lighting audit |
Counts fixtures only | Captures fixture, lamp, driver, controls, hours, and site conditions |
Good for a rough first look | Good for pricing, savings, rebates, and proposal creation |
Often done building wide | Done area by area |
Misses control opportunities | Identifies sensors, schedules, and daylight zones |
Weak support for ROI | Strong support for payback and financial analysis |
Example
A warehouse has 120 high bay fixtures. A simple count tells you there are 120 units.
A real audit tells you much more:
Audit input | Example |
Fixture type | 4 lamp T5 high bay |
Input wattage | 216 W each |
Quantity | 120 |
Hours of use | 16 hours per day, 6 days per week |
Controls | No occupancy sensing in low use aisles |
Mounting height | 24 ft |
Condition | Several dirty lenses and mixed lamp ages |
Opportunity | LED high bay replacement plus aisle based sensors |
That difference matters. A count gives you a rough equipment number. An audit gives you scope, savings logic, controls opportunities, and a proposal you can defend.
A strong audit also needs to support what happens after the site walk. If your team is comparing process options, this breakdown of what lighting audit software for contractors should actually help you do shows where manual workflows usually start slowing quoting and proposal work.
What information is collected during a lighting audit
The best audits gather data in layers. That keeps the field team focused and gives the estimator enough information to build a credible retrofit plan later.
Site and building details
This is the operating context behind the lighting system.
You usually want:
Building type
Site name and address
Gross square footage if available
Area types such as office, corridor, warehouse, exterior, washroom, stairwell, or parking
Business hours and shift patterns
Occupancy patterns by area
Utility account details if available
Notes on ceiling height, access difficulty, and tenant restrictions
These details change the economics of the job.
For example, 50 fixtures in a storage room used 2 hours per day do not carry the same savings value as 50 fixtures in a production area used 18 hours per day. Same quantity. Very different retrofit priority.
For smaller projects, a template may be enough, but teams handling repeat retrofit work should understand when lighting audit software and templates serve different purposes.
Fixture and lamp details
This is the core of the audit.
For each area, teams usually record:
Fixture type
Lamp type
Lamp count per fixture
Ballast or driver type
Wattage or estimated input wattage
Quantity
Mounting type
Mounting height
Lens, reflector, or housing condition
Notes on failures, colour mismatch, or aging components
A few common examples:
Area | Existing fixture | Qty | Approx input watts | Notes |
Office | 2x4 fluorescent troffer, 3 lamp T8 | 84 | 88 W | Mixed lamp ages |
Warehouse | 4 lamp T5 high bay | 120 | 216 W | No controls |
Exterior wall pack | HID wall pack | 26 | 175 W | Runs dusk to dawn |
Washroom | CFL downlight | 18 | 26 W | Frequent switching |
This is where weak audits usually break down. If fixture details are vague, the proposal gets vague too.
“Fluorescent fixture” is not enough.“2x4 troffer, 3 lamp T8, electronic ballast, 88 W input, recessed, office area” is useful.
Control and daylight details
Controls are often where extra value is hiding.
A lighting audit should document:
Occupancy sensors already installed
Areas with no controls but clear sensor potential
Scheduling practices
Lights left on after hours
Daylight zones near windows or skylights
Exterior control method such as photocell, timer, or manual switching
Spaces with intermittent use such as storage rooms, meeting rooms, washrooms, and utility rooms
This matters because many jobs are under scoped when controls are ignored.
A common example is a building with 300 interior fixtures, where only 40 to 60 fixtures are strong controls candidates. That still may produce a meaningful savings lift and improve payback without changing the full project scope.
Financial and utility inputs
This is where the audit becomes useful for business decisions, not just technical notes.
Key inputs include:
Demand charges if relevant to the analysis
Utility tariff details when available
Rebate program rules
Incentive caps
Required documentation for rebate submission
Customer budget targets or payback expectations
Without this layer, teams often make one of two mistakes:
They show savings without using the real utility cost
They miss rebates that could materially change close rate
That is one reason many teams eventually move from paper forms to lighting audit software. Once audits involve area by area data, controls, rebates, and proposal output, structure starts to matter.
For teams still tightening their field process, a lighting audit template can help standardise data capture before moving into a full software workflow.
How a lighting audit works step by step
A strong lighting audit follows a repeatable process. That matters because the value of the audit depends on the quality of the inputs. If the data is inconsistent, the retrofit plan, savings model, rebate estimate, and proposal will all be weaker.
Prepare before the site walk
Good audits start before anyone enters the building.
The first step is to understand the site at a high level. That usually means reviewing the building type, approximate square footage, operating schedule, and any known goals from the customer. Some clients care most about reducing energy use. Others care more about maintenance issues, rebate eligibility, or improving light levels in specific spaces.
It also helps to know what kind of output is expected at the end. A rough budgetary estimate requires less detail than a client ready for a full proposal. That distinction affects how much data needs to be captured in the field.
What should be confirmed before arrival
At minimum, the team should know who the contact is, which areas need to be audited, whether lifts or special access may be required, and whether utility bills or rebate information are available. Even one missing piece can slow down the entire workflow.
For example, if a site has a locked electrical room, a warehouse mezzanine, and an exterior yard that are not accessible during the walk, the audit may end up incomplete. That usually leads to assumptions later, and assumptions are where quote quality starts to slip.
Capture fixture data by area
The core of the audit happens on site, area by area.
Instead of treating the whole facility as one block, a strong audit breaks it into usable zones such as offices, corridors, washrooms, warehouse aisles, stairwells, loading docks, parking areas, and exterior perimeter lighting. This makes the final analysis more accurate and much easier to explain to the client.
A single building may contain five or ten different lighting use cases. Each one can have different fixture types, different hours, different mounting conditions, and different retrofit options.
Why area based capture matters
A corridor with 24 hour operation should not be treated the same way as a boardroom used a few hours a day. A high ceiling warehouse zone should not be grouped with a low ceiling office. When audits flatten everything into one line item, they hide the real value drivers in the job.
Here is a simple example:
Area | Existing fixture | Qty | Hours per week | Likely retrofit path |
Office | 2x4 fluorescent troffer | 84 | 50 | LED troffer or retrofit kit |
Corridor | 2 lamp strip | 36 | 168 | LED strip plus controls review |
Warehouse | T5 high bay | 120 | 96 | LED high bay |
Washrooms | CFL downlight | 18 | 70 | LED downlight plus occupancy sensors |
The more mixed the building is, the more valuable this structure becomes.
Record hours and controls
Once fixture data is captured, the next job is to understand how the lighting actually operates.
Two buildings with the same fixture count can produce very different savings outcomes because operating hours and controls conditions are different. This is why a real lighting audit is more than a hardware inventory.
Hours of use are one of the biggest value drivers
A fixture that runs 80 hours per week burns much more energy than one that runs 15 hours per week. That sounds obvious, but it is still one of the most common sources of bad audit data.
Hours should be based on how the space is used, not just what the building owner guesses on the spot. In many facilities, different areas operate on different schedules. Offices may run during business hours, while warehouse zones or exterior fixtures may run much longer.
Controls should be reviewed as part of the same workflow
This is also the point where the auditor should note whether lights are controlled manually, on schedules, by photocell, by occupancy sensor, or not controlled well at all.
A storage room with lights on all day, an always lit break room, or a perimeter office with strong daylight and no dimming control may all represent missed savings. These are not side notes. They directly affect the retrofit opportunity.
Review utility and rebate data
After the site walk, the audit becomes an analysis exercise.
The fixture and controls data now needs to be matched with utility cost assumptions, rate information, and rebate rules where applicable. This is where many manual workflows become slow, because teams start moving data between notes, spreadsheets, and proposal templates.
Utility context changes the financial story
A project can look average under one electricity rate and much stronger under another. Demand related considerations may matter in some projects, while in others the simple energy rate is enough to estimate value.
Rebates can also shift the decision. A project with a three and a half year simple payback may become much easier to approve if incentives reduce the upfront cost meaningfully.
That is why good audits do not stop at counts and wattages. They connect technical findings to financial reality.
Turn the findings into a retrofit plan
Once the existing conditions are clear, the audit turns into scope development.
This means selecting proposed replacement products or retrofit approaches, matching them to each area, and deciding where controls should be included. It also means documenting exclusions, special conditions, installation assumptions, and anything that could affect pricing or project delivery.
The audit becomes the backbone of the quote
At this stage, the team should be able to answer the questions that matter to the buyer. What is being replaced. Where is it being replaced. What are the expected savings. Are there rebates. What will the project likely cost. What should happen first if budget is limited.
This is also where a structured workflow pays off. Teams that move from audit straight into proposal usually work faster and make fewer errors than teams re entering everything manually later. That is one reason pages like sample lighting retrofit proposal tend to resonate with buyers evaluating how a professional process should look.
What happens after the audit
The audit is not the final deliverable. It is the foundation for everything that follows.
A good lighting audit feeds directly into retrofit recommendations, savings calculations, rebate planning, pricing logic, and proposal creation. If the audit is weak, every downstream output becomes less reliable.
Existing versus proposed fixture mapping
The first post audit step is to compare current conditions with recommended replacements.
This is usually done area by area so the client can see what exists now and what is being proposed instead. The goal is not just to show a product swap. The goal is to show why the replacement makes sense in context.
Example of how this looks in practice
Area | Existing | Proposed | Reason |
Office | 3 lamp T8 troffer | LED retrofit kit | Lower wattage, less maintenance |
Warehouse | T5 high bay | LED high bay | Better efficiency and longer life |
Exterior | HID wall pack | LED wall pack | Lower energy use and improved reliability |
Washroom | CFL downlight | LED downlight with sensor | Reduced burn hours and maintenance |
This mapping is what starts turning raw audit notes into a decision ready scope.
Energy savings calculations
Once the proposed fixtures are selected, the team can estimate how much energy the new system is expected to use compared with the existing one.
The basic logic is simple. Existing wattage, proposed wattage, quantity, and hours of use determine the energy difference. But the quality of the result depends entirely on the quality of the audit inputs.
Why this matters commercially
Savings figures are often one of the first numbers a buyer looks at. If they are based on rough hours, generic wattages, or incomplete counts, the proposal loses credibility. If they are tied to actual site conditions, the proposal becomes much easier to trust.
Rebate calculations
Where incentives apply, the audit data is used to estimate available rebates and gather the information needed for submission.
This can include existing fixture type, proposed fixture specification, control strategy, quantity, and site level project data. Rebate requirements vary, which is one reason teams handling larger retrofit pipelines often outgrow spreadsheets quickly.
Rebates can change project priority
In some cases, a project that looks marginal without incentives becomes an easy next step once the rebate is included. In other cases, the rebate is small, but still improves the client conversation by reducing the payback period.
The important point is that rebates are not separate from the audit. They depend on it.
Payback and ROI
Once energy savings and rebate values are known, the project can be framed financially.
Some clients want a simple payback number. Others want annual savings, total project cost, and return on investment. Larger organisations may want a more formal capital justification. The audit is what makes those conversations possible.
A credible financial view depends on complete inputs
If the audit is missing hours, rate data, controls assumptions, or fixture detail, the payback model becomes weak. That is why experienced teams do not treat the audit as paperwork. They treat it as the commercial backbone of the job.
Proposal creation
The final post audit step is turning the analysis into something the customer can approve.
That proposal usually includes the existing conditions summary, proposed scope, savings estimate, incentives if relevant, cost, assumptions, exclusions, and next steps. In strong workflows, the audit feeds directly into this output instead of forcing the team to rebuild everything manually.
This is where the gap between a checklist and a system becomes obvious. A checklist helps collect field notes. A structured process helps turn those notes into a proposal that can actually win work.
Common mistakes that weaken lighting audits
A lighting audit does not need to be complicated to be good. But it does need to be complete enough to support decisions. The most common failures are not technical. They are process failures.
Missing hours of use
One of the biggest mistakes is using a generic hours assumption across the whole building.
That may be acceptable for a very rough early conversation, but it weakens any serious proposal. Different spaces behave differently. Offices, corridors, storage rooms, exterior lighting, and production areas rarely follow the same schedule.
Why this creates bad outputs
If hours are wrong, energy savings are wrong. If savings are wrong, payback is wrong. That means the financial story being shown to the client is shaky from the start.
No utility rate in the model
Another common mistake is calculating energy reduction without translating it into cost.
A customer may care about kilowatt hours, but most buying decisions still come down to dollars. If the audit does not include a realistic utility rate, the project becomes harder to prioritise.
Even a good technical audit can fail commercially
A contractor may identify the right fixtures and the right controls, but still lose momentum because the customer cannot clearly see the financial impact. Good audit workflows connect the technical case to the business case.
Incomplete fixture details
Vague fixture descriptions create problems later.
A note like “fluorescent light” may seem fine in the field, but it is not enough when the team has to choose the right replacement, estimate labour, or calculate rebates. Missing wattage, missing lamp count, or unclear mounting conditions often force the estimator to guess later.
Small missing details often turn into revision cycles
Every guess increases the chance that the proposal needs correction. That slows down the job and makes the process look less controlled.
Ignoring controls
Many audits focus entirely on fixtures and miss the controls layer.
That leaves savings on the table and can understate the value of the retrofit. Occupancy sensors, scheduling improvements, and daylight response are not relevant in every area, but they should always be reviewed during the audit.
Controls are often the easiest hidden win
Spaces such as washrooms, storage rooms, meeting rooms, and low traffic back of house areas often have simple control opportunities that materially improve the project economics.
Using a rough estimate instead of area by area data
This is the mistake that causes the most downstream problems.
A whole building estimate may feel faster, but it usually breaks once the project becomes more detailed. Mixed fixture types, different hours, varied mounting conditions, and uneven controls opportunities all get blurred together.
Rough estimates are where proposals start drifting
The result is usually a proposal that looks clean on the surface but is weak underneath. Quantities are less reliable, savings are more generic, and scope revisions become more likely.
That is why many teams start with a lighting audit checklist or lighting audit template for simple jobs, then move into a more structured workflow as project complexity increases.
When a checklist or template is enough
Not every job needs a full software workflow.
There are still situations where a checklist or template does the job well, especially when the project is small, the building is simple, and the goal is to qualify the opportunity rather than produce a final proposal on the spot.
Small, simple jobs
A small retrofit in a single tenant unit or a compact retail space is often straightforward enough that a structured template works.
If the job has one or two fixture types, limited controls considerations, and no major rebate complexity, the team may not need anything more advanced than a clean field form and a consistent process for turning the notes into a quote.
Example of a job where a template can be enough
A 2,500 square foot office has:
Area count | Details |
1 main office area | 24 recessed 2x4 troffers |
2 private offices | 6 troffers total |
1 kitchenette | 4 downlights |
1 washroom | 2 downlights |
There are no unusual controls, no exterior lighting, and the client mainly wants a budget range for an LED upgrade. In a case like this, a template may be perfectly reasonable.
Early discovery stage
Templates also work well at the very beginning of the sales process.
Sometimes the goal is not to finalise a retrofit scope. The goal is to understand whether the site is worth pursuing, whether there is enough savings potential, and whether a second, more detailed audit should happen.
At that stage, speed matters more than polish.
What a template can do well in early stage work
A good template can help the auditor capture the essentials fast. It can keep counts consistent, reduce forgotten details, and make sure the team does not miss obvious information such as operating hours or basic fixture types.
That is often enough to answer early questions like these:
Is there a meaningful retrofit opportunity here?
If the site is mostly older fluorescent, HID, or CFL lighting with long operating hours, the answer is often yes.
Does the site justify a deeper analysis?
If the building has many zones, mixed fixture types, controls opportunities, or likely incentives, then the answer may also be yes.
Where templates start losing value
Templates are useful, but they have limits.
Once the project starts involving multiple areas, several fixture families, controls strategy, rebates, and a formal proposal output, the manual process starts slowing the team down. What felt simple in the field can become messy in the office.
A template collects information. It does not manage complexity for you.
The real issue is not field capture alone
The problem usually appears after the walkthrough. Someone has to organise the notes, verify fixture assumptions, calculate savings, layer in rebates, build pricing, and format the proposal. That is where paper forms and basic spreadsheets start creating rework.
For teams still tightening their field process, a lighting audit checklist or lighting audit template can still be useful. They are often a good starting point. They are just not always the best finishing point.
When software is better than paper or spreadsheets
Software becomes more valuable when the audit needs to move cleanly from field data to analysis to proposal without repeated handoffs.
That usually happens sooner than many teams expect.
Multi area facilities
The more zones a building has, the more fragile a manual workflow becomes.
A school, warehouse, office complex, retail chain location, or mixed use facility may have dozens of distinct lighting conditions. Each area can carry different fixture types, different operating hours, different mounting heights, and different retrofit options.
That is manageable in theory inside a spreadsheet. In practice, it is where quote quality often starts slipping.
Why complexity compounds fast
A building might include:
Area type | Typical complication |
Offices | Troffers, panel lights, varying hours |
Corridors | Long burn hours, possible controls opportunity |
Warehouse aisles | High bays, high mounting, access considerations |
Exterior | Photocell or timer logic, weather rated fixtures |
Washrooms | Frequent switching, occupancy sensor potential |
Stairwells | Multi level layout, code and control considerations |
Each of those conditions affects recommendations, savings assumptions, labour, and proposal clarity. A structured lighting audit software workflow is usually far more reliable once that level of variation enters the job.
If your team is still pricing audits and retrofit jobs in spreadsheets, it is worth looking at Excel vs lighting proposal software to see where spreadsheets still work and where they start creating rework, inconsistencies, and slower proposal turnaround.
Rebates and controls layers
Rebates and controls are two of the biggest reasons teams outgrow spreadsheets.
Rebate programs often need specific fixture data, quantities, wattages, control details, and supporting documentation. Controls add another layer because they can change both savings and incentive eligibility.
This is where manual workflows create friction
When rebate information sits in one document, fixture counts in another, and proposal pricing in a separate sheet, the team spends too much time reconciling information instead of moving the job forward.
The same thing happens with controls. If occupancy sensors, schedules, and daylight zones are treated as side notes instead of part of the audit structure, they are easy to miss or under scope.
Proposal output and revisions
The last major reason software wins is proposal production.
Most teams do not struggle only with capturing audit data. They struggle with turning that data into a clean, credible client proposal without rebuilding the job every time a revision happens.
Revisions are where spreadsheets become expensive
A customer asks to remove one area, phase the work, compare two fixture options, or include an alternate with controls. In a manual workflow, that can mean editing multiple tabs, rechecking formulas, adjusting savings assumptions, updating pricing, and then reformatting the proposal.
In a structured workflow, revisions are usually much easier to manage because the audit, analysis, and proposal are connected.
A simple comparison
Workflow factor | Paper or spreadsheet | Software based workflow |
Field data capture | Possible, but less structured | Structured by area and fixture type |
Controls tracking | Easy to miss | Easier to build into the workflow |
Rebate handling | Manual and fragmented | Easier to align with audit data |
Proposal creation | Often separate and manual | More connected to audit output |
Revisions | Time consuming | Usually faster and cleaner |
Version control | Weak | Stronger |
That is why teams working on larger commercial projects often pair their lighting process with tools built for the wider audit workflow, such as commercial energy audit software. Once the project touches energy analysis, incentives, and customer facing output, structure stops being optional.
It also explains why a polished sample lighting retrofit proposal matters. Buyers are not only evaluating fixture recommendations. They are evaluating whether your process looks controlled, accurate, and easy to trust.
Final takeaway
A lighting audit is the foundation of a strong retrofit project.
It is the step that turns a building walkthrough into something useful: a real understanding of existing conditions, a credible retrofit scope, a defendable savings model, and a proposal the customer can act on.
A strong proposal starts with a strong audit
If the audit is vague, the proposal will usually be vague. If the audit misses hours, controls, fixture detail, or utility inputs, the financial story weakens and revision risk goes up.
A good audit does the opposite. It gives the team clean area by area data, makes retrofit decisions easier, improves savings accuracy, supports rebate work, and helps proposals move faster.
If your team is already handling multi area audits, controls, rebates, and proposal output, the main question is no longer whether the process needs structure. It is whether your current workflow is costing time and creating avoidable revisions. You can review LumaQuote pricing and the 14 day free trial if you want to see what a more connected audit to proposal workflow looks like in practice.
FAQ: What is a lighting audit?
What is a lighting audit in simple terms?
A lighting audit is a structured review of the lighting in a building. It records what fixtures are installed, how they are used, how much energy they likely consume, and what upgrade opportunities exist before a retrofit proposal is created.
Who typically needs a lighting audit?
Lighting audits are commonly used by electrical contractors, retrofit companies, distributors, facility managers, property owners, and energy consultants. They are most useful when someone needs to assess existing lighting conditions and build a clear upgrade plan.
What is the difference between a lighting audit and a simple fixture count?
A simple fixture count only tells you how many fixtures are in a space. A lighting audit goes further by collecting fixture details, operating hours, control conditions, energy inputs, and site specific information that support savings calculations, rebate estimates, and proposal development.
What information is collected during a lighting audit?
A typical lighting audit includes building details, fixture type, lamp or driver information, wattage, quantity, mounting conditions, operating hours, control strategy, utility information, and rebate related inputs. On more detailed projects, it may also include daylight zones, maintenance issues, and area by area notes.
Why is a lighting audit important before a retrofit proposal?
A retrofit proposal is only as strong as the audit behind it. The audit helps define existing conditions, identify upgrade opportunities, estimate savings, support rebate calculations, and reduce errors in pricing and scope. Without good audit data, proposals are more likely to need revisions or miss important details.
How long does a commercial lighting audit usually take?
The time depends on the size and complexity of the building. A small site may take less than an hour, while a large commercial or industrial facility may require several hours or multiple visits. The more areas, fixture types, and controls conditions involved, the more time the audit usually takes.
When is a checklist or template enough for a lighting audit?
A checklist or template can work well for small, simple jobs or early stage discovery. For example, a small office with only a few fixture types and no complicated controls may not need a full software driven process. As project complexity increases, manual methods tend to become less reliable.
When should a team use lighting audit software instead of paper or spreadsheets?
Lighting audit software becomes more useful when the project includes multiple areas, mixed fixture types, controls opportunities, rebates, revisions, or formal proposal output. In those cases, software helps reduce re entry, improve consistency, and connect the audit more directly to the quoting and proposal process.
