Describe the system and sequence. Makeform creates a checklist for pre-start checks, readings, controls, deficiencies, and handover.
Send commissioning records to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a system, adjust its checks, or send the editable prompt to the builder.
Audience
Technicians starting commercial rooftop equipment
Format
Startup checklist with readings and functional tests
Prompt size
332 chars
Example checklist structure
Startup checklist with readings and functional tests
Project, unit ID, and nameplate details
Installation and pre-start checks
Electrical and operating measurements
Heating, cooling, and safety sequence results
Deficiencies, photos, and retest status
Suggested routing tags
Ready for test
Deficiency open
Commissioning complete
Label every reading with its unit, operating mode, and comparison reference.
Step 1
Identify
project, system, asset, technician, and references
Step 2
Verify
installation, pre-start condition, and prerequisites
Step 3
Test
readings, sequences, controls, and safeties
Step 4
Close
deficiencies, retests, status, and handover
A usable startup record
A structured checklist connects the asset, test conditions, expected reference, observed result, deficiency, and retest.
Confirm installation, access, piping, ducts, power, controls, and prerequisites before operation. Route not-ready answers for follow-up.
Capture readings in dedicated fields with units, test mode, and comparison reference.
Request evidence, severity, action, owner, due date, and retest for every failed point.
Fit the system
Conditional sections show relevant tests while shared identity, deficiency, retest, and status fields stay consistent.
Verify installation, power, drainage, fans, compressors, heat stages, controls, safeties, and performance.
Record fans, dampers, sensors, pressure, airflow, terminal ranges, reheat, and occupancy sequences.
Branch by equipment while capturing piping, flow, temperature, pressure, staging, and interlocks.
Test commands, sensors, setpoints, alarms, schedules, staging, and shutdown against the sequence reference.
Build the site workflow
Follow the technician from readiness review through startup, testing, correction, and retest.
Name systems, phase, assets, design values, references, and participants. Separate startup, functional, seasonal, and retest records when needed.
Sequence installation, pre-start, operation, readings, controls, safeties, deficiencies, and disposition.
Use equipment, mode, and results to show matching readings and follow-up. Require explanations for unable to test.
Send mobile submissions into the project workflow with status, owner, date, and retest fields.
Choose the right record
Choose whether results need structured links to assets, conditions, references, deficiencies, and retests.
Field guide
Use project references for exact tests; these six sections organize identity, testing, correction, and handover.
Project and asset identity
Capture enough detail to retrieve the record and understand its scope. Store document identifiers instead of retyping references.
Installation and pre-start
Follow the physical inspection path. Record pass, fail, not applicable, or unable to verify with an explanation.
Startup measurements
Separate raw readings from calculations. Capture mode, location, unit, and expected comparison value.
Functional performance
Break sequences into triggers and expected responses so failures identify the affected stage, alarm, or interlock.
Deficiencies and retest
Give every failed test a description, evidence, assignment, due date, and retest status.
Disposition and handover
Separate operating condition from commissioning status. Record receipt and remaining work without implying approval or certification.
Related tools
Use focused forms for inspections, maintenance, work orders, requests, and safety rounds.
Inspect mechanical-equipment condition outside commissioning.
Open toolFAQ
Answers for technicians and commissioning teams replacing paper startup sheets.
It records installation readiness, startup readings, functional tests, deficiencies, and retests for a specific system and date. Project documents and equipment instructions determine the required checks and expected results.
Include project and asset identity, personnel, references, pre-start checks, readings with units, control and safety tests, photos, deficiencies, owner, due date, retest result, equipment condition, and acknowledgment of receipt.
Yes. Use equipment type to reveal matching tests while sharing project, asset, technician, evidence, deficiency, retest, and status fields across every branch.
Give each reading a field for unit, location, mode, and expected reference. For functional tests, record trigger, expected response, observed response, result, and comments. Require a reason when testing is not possible.
Yes. Publish a mobile link and add uploads for nameplates, conditions, readings, deficiencies, and corrections. Follow the inspection sequence and reveal detailed fields only after a failure.
Open fields for deficiency ID, asset, test, observation, severity, evidence, action, owner, due date, and work order. Retests record date, tester, repeated result, evidence, and open or closed status.
Yes. Makeform provides unlimited free forms and responses for generating, editing, publishing, and reusing checklists. The paid tier removes the Makeform badge. Review checks against project and equipment references before use.
Yes. Send submissions through supported destinations such as email, Google Sheets, Slack, or Zapier. Structured asset, phase, status, owner, date, and retest fields help separate completed tests from open work.
Record startup and functional tests.
