A solar array can produce for months without anyone reading the inverter. The utility bill shows a net result, not whether a string is underperforming. A performance log fixes the reading times, the weather context, and the fault history in one place. It gives the owner a way to question a decline before the annual true-up. The log also turns a service visit into a comparison rather than a guess.
Key takeaways
- List the array, inverter, meter, and monitoring account.
- Fix daily and monthly reading times and the units recorded.
- Record production beside the weather and the household load.
- Log every fault with its code, time, and service response.
- Review the trend before the utility true-up and the warranty date.
List the array, inverter, and meter points
Start with a diagram that shows the array orientation, the string layout, and the inverter location. Record the panel model, the count, and the commissioned capacity. Note the meter or current transformer that measures production and the meter that measures import. A log that mixes the two meters will produce a misleading total. Label each reading point with the name used by the monitoring portal.
Record the inverter make, model, serial number, and firmware version. Note the monitoring account owner and the login recovery contact. Capture the communication method, because a lost signal can look like a production failure. Add the rapid-shutdown device and the disconnect locations. A technician should be able to find every point from the diagram.
List the battery or storage system separately if the property has one. Record the usable capacity, the reserve setting, and the backup circuits. Note whether the inverter can island the house during an outage. A production log that ignores storage can misread the household's use of solar. The storage record should be as specific as the array record.
Add the utility tariff, the billing period, and the true-up date. Record the net-metering arrangement and any export limit. Note the meter reading dates so the log can be reconciled with the bill. A production figure without the billing period cannot be compared with a charge. The two records should meet at the same date.
Set a daily and monthly reading routine
Set a daily reading at a fixed hour that reflects the same part of the solar day. Record the inverter production, the household consumption, and the battery state where available. Note the weather and any unusual load such as a pool pump or an electric vehicle charge. A single daily number is weak, but a consistent series is useful. The routine should take only a few minutes.
Set a monthly reading on the same day as the utility meter read where possible. Record the cumulative production, the export, the import, and the peak demand if the meter reports it. Note the number of days in the period and any missing days. A monthly total without the day count is hard to compare. The monthly row should reconcile with the daily rows.
Record who took each reading and from which portal or meter. Note any estimate or backfill and who approved it. A reading that was reconstructed should be marked rather than blended with observed data. The log should show the difference between a measurement and an estimate. That difference matters when a warranty claim is made.
Keep the monitoring screenshots or exports with the log. Store them by month so a later reader can find the source. Note the time zone used by the portal, because a daily total can shift across midnight. A time-zone error can move production from one day to the next. The record should state the time zone once and apply it consistently.
Record production against the weather
Record the weather for each reading with enough detail to explain a change. Note cloud cover, rain, snow, and any shading from trees or a new structure. A drop on a cloudy day is expected, while a drop on a clear day needs a question. The weather note should be written at the time, not reconstructed later. It is the context that makes the series readable.
Record the household load beside the production, especially when the property is occupied or empty. Note a pool heater, an irrigation pump, or a guest house that was switched on. A production figure that looks low may simply reflect a quiet house with little demand. The comparison should use similar occupancy where possible. The log should name the occupancy state for each monthly summary.
Note any change to the array, the inverter setting, or the tariff. A firmware update, a string repair, or a new export limit can move the series without a weather cause. Record the date and the person who made the change. A change that is not logged becomes an unexplained step. The series should be split at the change rather than averaged across it.
Compare the monthly production with the same month in the previous year when the data exists. Note the weather difference and any change in the system. A year-on-year comparison is more useful than a month-on-month one for a seasonal property. The log should show both the raw number and the comparison. A decline that survives the weather check deserves a service call.
Log faults and service responses
Record every fault with the inverter code, the time it appeared, and the time it cleared. Note whether the fault was self-clearing or required a reset. Capture a screenshot of the event log before it rolls over. A fault that is only remembered cannot support a warranty claim. The event log should be exported at least monthly.
Record the service request, the vendor, and the response time. Note the diagnosis, the part replaced, and the proof of the repair. Keep the work order with the fault entry. A repair without a linked fault is hard to audit. The record should show the whole chain from symptom to close.
Note any period when monitoring was offline and how production was estimated. Record the meter reading that covers the gap if one exists. A communication outage is not the same as a production outage, but the bill will not make that distinction. The log should explain the gap in plain language. The owner should not discover it at the true-up.
Record any safety issue, such as a hot connector, a damaged conduit, or a ground fault. Note the isolation step and the person who authorised the shutdown. Keep the photo and the vendor report together. A safety entry should be closed by evidence, not by reassurance. The log should show that the array was returned to service only after the check.
Review the log before the utility true-up
Read the daily and monthly rows together before the true-up and look for a sustained gap. Check whether the missing production is explained by weather, outage, or curtailment. Compare the meter total with the utility bill and note any difference. A reconciliation before the deadline leaves time to correct a meter or billing error. The review should produce a short written summary for the owner.
Check the warranty dates for the panels, the inverter, and the workmanship. Record the next expiry and the evidence required for a claim. Note any maintenance the manufacturer recommends before that date. A warranty that expires without a service record is harder to use. The log should connect the service history to the warranty terms.
Set the next review date and the person who will export the data. Record the steps so the review does not depend on one login. Test the export before the person who owns the account goes on leave. A review that cannot access the portal is not a review. The method should survive a change of staff or vendor.
Use the review to decide one operational change, such as shifting pool heating to the middle of the day or clearing a new shade source. Record the change and the date, then compare the next period. A single change with a measured result is more useful than a list of intentions. The log should show whether the change helped. That is how the record earns its keep.