A load profile shows electricity consumption or power demand over time for a defined property or group of loads. For a solar or battery proposal, it helps answer when electricity is needed, which demand overlaps solar production and what assumptions shape the forecast.
For someone considering residential solar installation, a monthly kWh total is a useful starting point. It does not show whether consumption occurs during daylight, after sunset or in short peaks. A profile adds the time dimension, provided its units and measurement boundary are understood.
This entry explains the time-series entity and how to read it. The electrical-load definition explains equipment demand, while the commercial solar data guide retains the fuller commercial data-package workflow. All numerical examples here are original fictional illustrations, not measured Sunburst household data or local utility rates.
What information belongs in a load profile?
A useful profile combines a time reference with a quantity and a defined scope. The values might describe electricity consumed in each interval, average power during each interval or another explicitly stated measurement. A modeled profile also needs its assumptions identified.
NLR’s REopt load-data guidance distinguishes simulated profiles, profiles adjusted using monthly or annual consumption, and actual interval records. It notes that measured intervals can have different durations and that access depends on the available meter and account data. NLR explanation of load-data types.
Before interpreting a graph, ask four questions: what quantity is plotted, over what interval, for which loads and from what evidence? The same-looking curve can represent whole-home demand, utility imports after solar or a generic building model.
A precise label could read “whole-property consumption in kWh per 15-minute interval for the stated dates.” That is more useful than “usage curve,” because it tells the reviewer how the values should be combined and compared.
How do you read the axes and units?
The horizontal axis usually represents time. The vertical axis represents the stated quantity, often power or energy per interval. Read both before comparing the height of two curves or adding values from a file.
EIA distinguishes power in watts or kilowatts from energy in watt-hours or kilowatt-hours. A profile’s unit determines whether you multiply by interval duration or sum already accumulated energy. EIA electrical measurement units.
| Profile value | Meaning | How to form energy over compatible intervals |
|---|---|---|
| Interval energy in kWh | Energy consumed inside each stated interval | Add the energy values |
| Interval-average power in kW | Average rate during each stated interval | Multiply each value by its interval hours, then add |
| Instantaneous power in kW | A sampled rate at a stated moment | Use an appropriate integration method and stated assumptions |
| Modeled interval value | A calculated quantity under a model | Preserve its unit and model assumptions |
Do not treat every kW sample as an interval average. A point measurement and a period average can look similar in a spreadsheet while requiring different interpretations. Ask the data provider what the field represents.
How do you convert interval energy to average demand?
Divide interval energy by its duration in hours. For an original illustration, assume four complete 15-minute intervals, each lasting 0.25 hours, with the energy quantities shown below.
| Interval | Energy consumed | Corresponding average demand |
|---|---|---|
| 1 | 0.50 kWh | 2 kW |
| 2 | 1.00 kWh | 4 kW |
| 3 | 0.25 kWh | 1 kW |
| 4 | 0.75 kWh | 3 kW |
The calculation for Interval 2 is 1 kWh ÷ 0.25 hours = 4 kW. Total energy across the hour is 2.5 kWh, and average demand across that hour is 2.5 kW.
Adding the four average-power values gives 10 kW, which is not the hour’s energy total. Instead, (2 + 4 + 1 + 3) × 0.25 = 2.5 kWh. The kilowatt and kilowatt-hour entries explain the underlying units.
The highest interval average in this invented record is 4 kW. That is not proof that instantaneous demand never exceeded 4 kW inside an interval. The data resolution limits what the record can establish.
Why can two equal daily totals have different solar value?
The total says how much electricity is used; the profile says when it is used. Different timing can change direct solar overlap even when the daily quantities match.
For an original illustration without storage, assume each prescribed block has a stated flow pattern that permits the direct-use amounts described. These are assigned flows, not values inferred automatically from coarse block totals.
| Time block | Household A use | Household B use | Assigned solar production |
|---|---|---|---|
| Morning | 4 kWh | 2 kWh | 0 kWh |
| Daytime | 4 kWh | 2 kWh | 8 kWh |
| Evening | 4 kWh | 8 kWh | 0 kWh |
| Daily total | 12 kWh | 12 kWh | 8 kWh |
Assume the daytime load is fully served by the assigned solar supply in each case. Household A uses 4 kWh directly and exports 4 kWh. Household B uses 2 kWh directly and exports 6 kWh. Their imports are 8 kWh and 10 kWh respectively.
The same daily consumption and generation do not produce the same direct-use result under these assumptions. Financial value still needs the actual utility rules. The solar self-consumption definition explains the generation-side ratio.
Can coarse intervals overstate apparent solar overlap?
Yes, if aggregation hides mismatched timing and the analysis assumes simultaneity that did not occur. Equal energy in a large block does not establish that generation and demand coincided inside it.
For an original one-hour counterexample, suppose solar produces 2 kWh during the first half-hour while household demand is zero. During the second half-hour, solar production is zero and household use is 2 kWh. Assume no battery and no other generation.
At the actual half-hour boundaries, direct solar use is zero. Solar exports 2 kWh in the first interval, and the home imports 2 kWh in the second. Yet the hour totals show 2 kWh of generation and 2 kWh of demand.
Taking the smaller hourly total would report 2 kWh of apparent direct use, which does not match the assigned chronology. This example does not prove every hourly model is wrong. It shows why the resolution and within-interval assumptions need to be disclosed.
Ask whether an overlap calculation uses measured flows, aligned interval averages or an assumed allocation. Keep that method beside the resulting percentage rather than presenting it as exact observed household behavior.
Is a utility-import profile the same as household consumption?
Not necessarily. A utility connection can report imports and exports after onsite generation or storage affects the flow. Whole-home consumption describes the loads, including energy served onsite. Confirm what the exported file measures.
For an original compatible-boundary example without storage, the loads consume 5 kWh in an interval, solar produces 3 kWh and all solar serves the loads directly. Utility imports are 2 kWh. The import profile alone would understate the defined household consumption if renamed “home use.”
A net-exchange field can introduce another distinction. Netting imports against exports does not necessarily preserve their separate quantities or the underlying load. Ask how the provider reports direction, signs and intervals.
For a property with existing solar or storage, identify production, utility exchange and household monitoring separately. Do not reconstruct load by adding unrelated quantities from different periods or measurement locations. The boundary should be documented before arithmetic begins.
What is the difference between measured and modeled profiles?
A measured profile records a quantity through a stated monitoring arrangement. A modeled profile estimates a time pattern from inputs and assumptions. Both can be useful, but a model should not be described as the homeowner’s observed behavior.
NLR’s End-Use Load Profiles project provides simulated building profiles, calibrated and validated against empirical datasets. Its individual model outputs contain a year of consumption at 15-minute resolution. Those files represent modeled building cases, not meter readings from the reader’s home. NLR end-use profile scope and limitations.
For an original proposal review, a generic residential profile is scaled to a homeowner’s annual bill. Label it “modeled household timing scaled to annual use.” Then identify why that shape was selected and what evidence suggests it reasonably represents the property.
Actual interval records also need review. A measured file can be incomplete, cover a different meter or reflect a prior occupant. “Measured” describes evidence origin; it does not automatically establish completeness or future representativeness.
Does matching monthly bills validate the modeled shape?
It validates a total only to the extent the periods and boundaries match. Scaling a model to the bill does not prove that its daily peaks, evening consumption or weekend pattern match the household.
SAM’s electric-load documentation describes scaling a time series to monthly consumption. It also notes limits when using this approach to represent commercial peak demand. That distinction supports checking shape separately from energy totals. SAM documentation on load-profile scaling.
For an original example, two modeled profiles each sum to 900 kWh in a month. One assigns more use to daylight; the other assigns more to evening. A 900 kWh bill cannot choose between those shapes by itself.
Request a sensitivity comparison when timing is uncertain. Hold the total constant and test a clearly labeled alternative shape. The difference in estimated direct use or storage operation can reveal which assumption deserves better evidence before an equipment decision.
Why do timestamps and the reporting year matter?
Time connects the consumption values to solar production and applicable price periods. A shifted or mislabeled timestamp can change apparent overlap while leaving the annual energy sum unchanged.
NLR’s REopt load-input tutorial specifically identifies the reporting year as relevant to preserving day-of-week alignment when applying a site’s rate. Its file-format instructions belong to that tool; they are not a universal rule for every utility export. REopt load-input and calendar guidance.
For an original alignment example, a file marks a value “12:00,” but it is unclear whether that means the interval starting at noon or ending at noon. Comparing it with a solar file using the opposite convention can shift one series by an interval.
Record the time zone, start-versus-end convention, actual duration and calendar year. Preserve the original file when transforming the data. A reviewer should be able to trace how a timestamp was changed rather than relying on an unlabeled plotted curve.
How should daylight-saving changes and irregular intervals be handled?
Follow the data provider’s actual time convention and the analysis tool’s requirements. Do not delete repeated clock labels or invent a missing interval before determining whether the file uses local time, fixed standard time or another convention.
For an original data-review case, two rows carry the same displayed local clock label. They might be duplicate records, different meter channels or distinct intervals represented under a clock change. The label alone does not resolve the question.
Likewise, a day with an unexpected row count needs investigation rather than automatic repair. Check interval identifiers, offsets, duration and provider documentation. A count suitable for one fixed-interval model is not proof that every raw export must contain that same count.
If a transformation is required, record the rule and its effect on energy totals and timing. Keep unresolved timing questions visible. Quietly forcing a file into a convenient shape can produce a clean-looking graph with an uncertain physical interpretation.
What is the difference between a zero and missing data?
A reported zero is a value under the file’s definition. A missing record provides no quantity. Replacing every gap with zero assumes no consumption occurred, which can materially change the result.
For an original hour, suppose four 15-minute energy records should be available but only three are present: 0.4, 0.5 and 0.6 kWh. Their known sum is 1.5 kWh. The missing interval does not become zero because the spreadsheet adds the three existing rows.
Do not present 1.5 kWh as the complete hour unless the missing value is resolved or the limitation is explicitly stated. If an estimate fills the gap, label it estimated and preserve the method.
The same discipline applies to duplicate rows and multiple channels. Adding a duplicate can overstate consumption; removing a legitimately distinct channel can understate it. Review identifiers and scope before editing the file.
How can interval totals be checked against bills?
Compare compatible quantities over matching dates and meter boundaries. The goal is to find unexplained differences, not to force every file to equal a bill by scaling it silently.
For an original reconciliation, the interval file covers calendar-month dates while the bill covers a different start and end date. A difference between their totals may be a period mismatch rather than a meter problem. Align the coverage before judging the result.
If the property already has solar, verify whether the bill quantity describes imports, exports or net accounting rather than total household consumption. Also preserve any estimated billing readings, corrections or meter changes that affect comparison.
Our commercial solar data guide retains the full acquisition and handoff workflow. For this definition, the useful principle is simple: a successful annual-total match does not erase unresolved timing, source or scope differences inside the record.
Why can an average day hide important operating conditions?
An averaged curve can summarize a period while concealing individual high-demand days and changes in occupancy or equipment operation. Read it as the summary it is, not as a promise that every day follows that pattern.
For an original same-clock comparison, one day records 2 kW and another records 8 kW at an interval. Their mean is 5 kW. The average curve contains neither the actual low nor the actual high value at that point.
For a battery or solar review, ask for the relevant range and representative operating cases alongside the mean. Separate weekdays from weekends or different seasons when those distinctions matter to the property’s operation.
No universal high-demand season or household schedule is assigned here. The actual record and known operating changes should guide the comparison. A household working from home and a vacant property can have different patterns despite similar annual totals.
Is a load-duration curve the same as a chronological profile?
A chronological profile preserves the order of demand over time. A load-duration view sorts demand values by magnitude. That can help describe how often different demand levels occur, but sorting removes the sequence needed to understand charging and later delivery.
For an original four-interval sequence, demand is 1, 4, 1 and 4 kW. Sorting gives 4, 4, 1 and 1 kW. Both contain the same values, but they do not preserve the same chronology.
A storage question depends on when energy becomes available and when the loads require it. Do not use a sorted chart alone to claim that a battery can recharge between every demanding interval.
Keep the chart’s purpose visible. A useful summary may support one question while leaving another unanswered. Ask whether the forecast retains the original chronology when evaluating solar overlap and storage operation.
How should solar production be compared with the load profile?
Align the units, intervals, time convention and measurement boundaries. Production and consumption can then support a stated flow model or measured comparison. Annual quantities alone do not establish interval overlap.
For an original simple no-storage interval, assume compatible energy quantities: production is 3 kWh, household consumption is 2 kWh, and the specified within-interval pattern lets solar serve the full load. Direct use is 2 kWh, with 1 kWh exported.
The last assumption matters. As the earlier half-hour counterexample showed, coarse totals alone cannot prove that allocation. Preserve the actual flow evidence or modeling method instead of hiding it inside a minimum-of-totals calculation.
The solar self-sufficiency definition explains the resulting share of household demand, while energy offset compares larger generation and consumption totals. Use the metric that answers the intended question.
What extra information does a battery comparison need?
Storage introduces charging, later delivery, losses, operating limits and opening or closing inventory. A household profile is one input; it does not identify all those conditions by itself.
For an original illustrative day, the profile shows a 6 kWh evening demand after the modeled solar surplus occurs. That demand is not automatically proof that a 6 kWh storage label will serve it. The proposed delivered-energy boundary, usable capacity, reserve, losses and power limits remain separate questions.
Ask which surplus is actually available to charge storage and what other loads or export conditions affect it. Preserve chronology and energy origin when grid charging is also possible. Do not add battery discharge to the generation total as if it were newly produced solar.
The battery quote comparison guide retains the buying decision. The round-trip efficiency definition explains the loss boundary. This entry does not recommend a particular battery or assign a universal storage benefit.
Is the normal whole-home profile the outage load profile?
It can inform the discussion, but outage operation may use a different set of loads and priorities. Selected circuits, managed equipment or changed household behavior need a separately stated outage scope.
For an original scope example, the normal profile includes vehicle charging and workshop equipment. The proposed backup group includes neither. Using the entire normal profile as the backup load would not describe the assigned design; using only the backup group as whole-home demand would also be misleading.
The critical-loads definition explains the selected group. Power support, startup behavior and the outage-capable electrical arrangement still require appropriate equipment and design evidence.
An interval-average curve may miss brief events important to that design. Our home electrical capacity guide retains the broader equipment and operating-state review. Profile data support the assessment without replacing the required electrical analysis.
How should future loads change a planning profile?
Add a documented scenario rather than multiplying every hour by an arbitrary percentage. A new device can change timing and peaks differently from the existing pattern. Keep present records and proposed future assumptions separately labeled.
For an original example, a planned load adds 4 kWh during a defined overnight period. Adding those 4 kWh to an annual total does not show their timing. Scaling daytime and nighttime use equally would represent a different assumption.
Record the exact proposed equipment when known, expected operation and the uncertainty around those choices. Compare a current case with the stated future case. If the device or schedule is not selected, use explicitly labeled alternatives.
A planning profile can then support the solar sizing process without implying that future behavior has been measured. Keep the calculation traceable so the assumption can be revised when the actual equipment is chosen.
What is locally relevant about a South Carolina load profile?
The definition is geographic-neutral, but the property’s records, meter capabilities, account rules and local operating conditions matter. Do not assign a statewide shape or assume every utility supplies the same interval file.
Start by asking the actual provider what account data are available and what the fields mean. If onsite monitoring supplies the profile, identify its scope and whether it sees existing generation or storage flows. Obtain data through the appropriate account access and retain the original export.
Financial interpretation needs current account-specific pricing and program conditions. A peak visible on a graph is not automatically a billed demand charge, and moving consumption is not automatically cheaper under every tariff.
No current rate, typical South Carolina household shape or guaranteed solar saving is assigned here. A useful local assessment combines the property’s actual evidence with the applicable utility documents.
What should you ask before relying on a load profile?
Use a short review sheet to make the important assumptions visible:
| Field | Question to resolve |
|---|---|
| Scope | Which meter, property or circuits do the values describe? |
| Evidence | Measured, modeled or scaled from another profile? |
| Units | Energy per interval, interval-average power or point samples? |
| Timing | What are the duration, time zone and timestamp conventions? |
| Coverage | Which gaps, duplicates or irregular intervals remain? |
| Alignment | How is the series matched to production and billing periods? |
| Changes | Which future loads or operating changes are assumptions? |
Ask which uncertainty would most change the proposal and what evidence would resolve it. A qualified limitation is more useful than a precise-looking forecast built on unexplained timing.
Want to connect your electricity pattern to a solar or battery proposal? Request a free solar assessment with your bills, available interval export and known equipment changes. The useful next step is a property-specific review of consumption timing and the proposed system’s role.
Sources and methodology
Primary references were checked on October 6, 2026. NLR’s REopt materials support the distinctions between measured, modeled and scaled inputs and the importance of calendar alignment. NLR’s building-stock project supplies the simulated-profile example. SAM documentation supports interval power-to-energy treatment and scaling limitations. EIA supports the units.
All calculations and counterexamples are original hypothetical records with explicit assumptions. No real household data, appliance-identification result, utility interval specification or local tariff is inferred. Commercial data acquisition, electrical capacity, sizing and battery buying guides retain their detailed decision scopes.
Frequently asked questions about load profiles
What does a household load profile show?
It shows electricity use or demand across time for a defined set of loads. The values may be measured or modeled. Read the unit, interval and scope before using the profile to assess solar overlap, storage operation or changes in demand.
Can a monthly bill reveal the daily load profile?
A monthly total does not reveal the full timing pattern. A model can be scaled to that total while retaining an assumed shape. Label the timing as modeled and request supporting evidence or a sensitivity comparison when it affects the proposal.
Is 15-minute kWh the same as 15-minute kW?
No. Energy in kWh can be divided by the interval’s hours to find its average kW. For a complete 15-minute interval, the duration is 0.25 hours. A power field still needs clarification about whether it is an interval average or a point sample.
Does an hourly profile show every appliance startup?
No. Averaging or aggregation can conceal events inside the interval. A startup-support question needs appropriate equipment or measurement evidence. The plotted interval value should not be treated as a universal instantaneous maximum.
Why can my import profile differ from home consumption?
Onsite generation or storage may serve part of the household load. Utility imports describe one supply flow rather than all consumption. Confirm the boundary and gather compatible production, storage and household records before reconstructing the load.
Should missing interval records be replaced with zero?
Only a documented data interpretation could justify that value. A gap is not proof of zero use. Preserve the original records, investigate the missing interval and label any estimate used to fill it, including the method and remaining uncertainty.
Is a generic building profile measured data for my home?
No. It can support a stated modeling scenario, but its shape remains assumed for the property. Matching annual or monthly totals does not prove matching timing or peaks. Keep the model origin and scaling method visible in the forecast.
Does a favorable profile prove a battery is worthwhile?
The profile is one input. Storage performance, losses, operating limits, reserve, costs and utility terms still need review. Compare traceable system scenarios rather than inferring a purchase recommendation from a single evening-demand or solar-overlap chart.