HVAC startup report

HVAC Startup Report Template for New Systems

An HVAC startup report documents that a newly installed or restarted system was checked, tested, adjusted, and handed off with readings and observations the office can reference later.

Use this template after equipment replacement, new installation, seasonal startup, rooftop unit startup, heat pump commissioning, mini split installation, or major repair return-to-service.

Startup proof

Startup reports protect the install record

A clear startup report gives the customer and office a baseline for performance, safety, controls, and warranty context after a system begins operating.

When to use it

HVAC installers and service teams need a startup report that documents equipment condition and operating readings after startup.

What it should help capture

Customer, property, startup date, installer, technician, and equipment locationModel, serial, capacity, refrigerant, electrical, controls, thermostat, and accessoriesStartup readings, airflow, temperature split, voltage, amperage, pressure, and safety checksAdjustments made, deficiencies found, photos, warranty notes, and customer training

Copy-ready template

Startup identification

Identify the system being started and who completed the report.

Startup report #: [HVAC-SU-4100]

System: [AC, furnace, heat pump, RTU, mini split, air handler]

Location and equipment ID: [location, model, serial]

Completed by: [technician or installer] on [date]

Startup checks

Record the operational baseline after startup.

Electrical checks: [voltage, amperage, disconnect, breaker, grounding notes]

Performance readings: [temperature split, pressures, airflow, static, combustion if applicable]

Controls and safety: [thermostat, safeties, drain, float switch, gas, venting, condensate]

Adjustments made: [charge, airflow, settings, wiring, thermostat configuration]

Completion and handoff

Summarize startup outcome and customer communication.

Startup status: [passed, passed with notes, follow-up required, do not operate]

Customer handoff: [operation explained, filter size shared, maintenance recommended, warranty note provided]

Next step: [schedule inspection, send quote, monitor, enroll in maintenance, no action]

Use cases

Where this template helps in the field

Use the template when the office, customer, and technician all need the same job details without chasing scattered notes.

New equipment install

Record startup readings, settings, accessories, photos, and customer handoff.

Seasonal startup

Document system condition before peak heating or cooling demand.

Return to service

Confirm operation after a major repair, part replacement, or shutdown.

Included sections

What the template should include

These sections keep the document clear enough for customers, technicians, office staff, and payment follow-up.

Customer, property, startup date, installer, technician, and equipment location
Model, serial, capacity, refrigerant, electrical, controls, thermostat, and accessories
Startup readings, airflow, temperature split, voltage, amperage, pressure, and safety checks
Adjustments made, deficiencies found, photos, warranty notes, and customer training
Final status, recommended follow-up, maintenance plan, and office review

Performance readings

Creates a baseline for future diagnostics and warranty conversations.

Field note

Capture readings after the system has stabilized enough to make the numbers useful.

Adjustments made

Explains what changed during startup and why the final settings matter.

Field note

Avoid undocumented tweaks that future technicians cannot interpret.

Startup status

Makes it clear whether the system is ready for use or needs follow-up.

Field note

Use passed with notes when the system runs but still has watch items.

Service workflow

How to use this template inside a real service business

The best paperwork supports the job before, during, and after the visit, instead of becoming another file nobody can find.

1

Prepare equipment context

Review install scope, model, serial, accessory, and customer requirements before startup.

How Fieldified supports this step

Fieldified keeps approved scope and equipment details connected to the job.

Explore related capability
2

Record startup readings

Capture checks, settings, photos, and deficiencies while the technician is on site.

How Fieldified supports this step

Mobile job forms help technicians document startup details before closeout.

Explore related capability
3

Schedule future service

Use the report to set warranty reminders, maintenance visits, or follow-up work.

How Fieldified supports this step

Recurring workflows keep post-install service from being forgotten.

Explore related capability

Common mistakes

What weak templates miss

No baseline readings

Future diagnostics become harder when startup numbers are missing.

No deficiency list

Small startup issues should be documented before they become customer complaints.

No customer handoff

Customers need basic operation, filter, warranty, and maintenance information.

Startup reports connected to future service

Fieldified helps startup records stay useful after install day

Startup reports should become part of the equipment record, not a one-time file. Fieldified keeps readings, photos, warranty notes, and next steps connected.

FAQ

Questions field service teams ask about this template

What should an HVAC startup report include?

Include customer and equipment details, startup date, technician, readings, airflow, electrical checks, safety checks, controls, adjustments, deficiencies, photos, and final operating status.

When should a startup report be completed?

Complete it after installation, major repair, seasonal startup, or return-to-service when the system is operating and ready for verification.

Is a startup report useful for warranty?

Yes. It can provide a baseline record of equipment condition, startup readings, and customer handoff.