Field Records

A job record has four layers

Leave the next technician a connected record—not a pile of screenshots.

A job record has four layersFour stacked record layers show authority, equipment identity, evidence and customer handover. Each layer remains separate but belongs to the same job. The finished pack is a field record, not a compliance certificate.Authority1Identity2Evidence3Handover4
Record structure, not a certification checklist. Required certificates and product commissioning remain separate.
Explore the numbered points

POINT 1

What was the approved intent?

Keep the approval, current design, applicable network requirements and exact manufacturer instructions together.

POINT 2

What was actually installed?

Record full models, firmware, serial or asset references and configuration so the evidence attaches to the right equipment.

POINT 3

What was observed and changed?

Preserve the as-found state, named conditions, measurements, actions and final state. Keep time, method and responsible person with the result.

POINT 4

What did the customer receive?

Record operating limits, backed-up circuits, monitoring access, emergency and support information, plus any outstanding actions.

Use it in the field

FROM THE DIAGRAM TO THE JOB

Keep these checks with you.

  1. Capture before changing

    Keep active alerts, relevant settings and visible equipment condition before resets, updates or configuration changes.

  2. Make references durable

    Store photos in the business's approved system and record a stable reference. Keep source documents with the job.

  3. Close the open actions

    Name the owner and due date of unfinished work. A printed Wattbench report does not replace required compliance documents.

A useful record explains the job without claiming to certify it.

Read the guide's sources

Start a job record

Give it a job or site name. Wattbench will open the right evidence prompts.

Start job record
Sources listedReviewed July 2026Our methodology
Article details and scope
Topic
Commissioning records
Applies to
Solar, battery and backup systems
Audience
Installation businesses
Neutrality
Manufacturer-neutral
Read the full explainer
Key takeaways
  • Record the approved design and equipment identity before recording results.
  • A useful test entry names the point, condition, method, result and person responsible.
  • Keep as-found state, changes, final state and customer handover together so the record survives staff and platform changes.

The pack has four layers

Authority is the approval, current design, applicable network requirements and manufacturer instructions. Identity is the exact installed equipment, firmware, serial or asset references and configuration. Evidence is the timestamped observation, measurement, action and outcome. Handover is what the customer received and was shown.

If one layer is missing, the next technician is forced to reconstruct intent from screenshots and labels. A strong pack makes the job legible without claiming that the report itself is a compliance certificate.

Capture as found before changing anything

Record system state, active alerts, relevant settings, monitoring status and visible equipment condition before resets, updates or configuration changes. This preserves the evidence that explains why the work was required and prevents the final “all green” screen from erasing the fault history.

Make every result interpretable

For a reading, name the measurement point, phase or circuit, operating condition, unit, instrument or method and time. For an action, record who performed it, the supporting instruction or approval and the before-and-after state. For a photograph, store the image in the business’s approved system and put its stable file reference in the job pack; Wattbench deliberately does not create a new cloud photo store.

Product commissioning remains product-specific

Enphase publishes an Australian commissioning guide and installation checklist that include device provisioning, validation and documented checks. Tesla publishes model-specific installation documents and limits installation to certified installers. These demonstrate why a generic checklist cannot replace the exact product workflow.

Close with a handover record

  • Final equipment and settings record.
  • Completed test and validation evidence.
  • Backed-up circuits, export arrangement and operating limitations.
  • Monitoring access confirmed with the customer.
  • Shutdown, emergency and support information supplied.
  • Outstanding actions, owner and due date.

For the owner, the Owner Handover Card prints on one page the codes their equipment may show, the reviewed owner action for each, when to call you and what to send.

Where the job removed or replaced equipment, record where it went. The End-of-Life & Battery Return Pathway links each state's agency pages, the stewardship status and the manufacturer return pages.

Create a saved Wattbench job, file calculators and references to it, add structured evidence, then print the field report. The report is a durable field record—not a quote, engineering specification or certificate.

New to the jargon? Browse the glossary.

Sources

Best next action

Did this help you move the job forward?

Tell us what is missing
Good to know

Frequently asked

Does the Wattbench report replace required compliance documentation?
No. It is a field evidence record. Required certificates, network forms, manufacturer commissioning and the licensed design remain separate authoritative documents.
Why does Wattbench store a photo reference instead of the image?
It avoids creating another cloud repository for sensitive site photographs. Keep images in the business’s approved storage and record a stable reference in the evidence pack.