Download the HVAC submittal checklist
XLSX
HVAC submittal checklist (Excel)
Header block, 8 columns, Y/N drop-downs for required and included, rows that are required and not included in red, rows with a deviation in amber, frozen header row, filters and a How to use sheet.
CSV
HVAC submittal checklist (CSV)
The example rows as plain CSV (UTF-8), for Google Sheets or any other tool.
Both files are free under CC BY 4.0, with no form to fill in. The XLSX opens in Excel, Google Sheets, LibreOffice and Numbers. The CSV carries the table only; the header block is in the XLSX.
Use it on one submittal, before it leaves
An HVAC submittal is the pack of data an equipment manufacturer sends, through the contractor, to the design engineer to show that the unit selected meets the specification and the schedule. Reviewers send packs back for the same few reasons: something the specification listed is not there, the selection does not match the scheduled duty, or a difference was not declared. Each return costs a review cycle. This checklist is a last look at a single pack against the specification section it answers.
- Application and sales engineers at manufacturers and their representatives, who assemble the pack.
- Mechanical contractors' project engineers, who can run the same rows before forwarding a supplier's pack.
- Design engineers, as a first sort of what has come in.
It is not a register. To track many submittals with their dates and review actions, use the submittal log template. What a submittal must contain, and which performance certification or test method applies, is set by the project specification: some name an AHRI certification programme, others a different scheme. Check the governing standard or contract. See also HVAC equipment manufacturers.
Header block
| Field | Example |
|---|---|
| Project | Example Office Building, Level 3 fit-out (fictional) |
| Mechanical contractor | Example Mechanical Contractor Ltd (fictional) |
| Purchase order | PO-EX-8815 (fictional) |
| Specification section | M-240 Air handling units, Rev 2 (invented project specification) |
| Equipment schedule | Drawing M-601 Rev B (invented) |
| Equipment | Air handling unit AHU-03 (fictional) |
| Submittal no. and revision | M240-003 Rev 0 |
| Date | 2027-04-06 |
| Prepared by | Application engineer |
| Checked by | Sales engineer |
Example rows: an air handling unit submittal
| Item | What the specification asks for | Specification section | Required | Included | Document reference | Deviation | Remark |
|---|---|---|---|---|---|---|---|
| 1 | Duty point matches the equipment schedule: airflow, external static pressure, coil duties and motor size | M-240 2.1; schedule M-601 | Y | Y | Selection printout SP-EX-AHU-03 p.1 | Supply fan motor is one frame size larger than scheduled | Tell the electrical contractor. List it on the submittal cover sheet. |
| 2 | Selection printout from the manufacturer's selection software, at the scheduled conditions | M-240 1.4 A | Y | Y | SP-EX-AHU-03, 6 pages | None | |
| 3 | Performance certification reference, under the programme the specification names | M-240 1.5 B | Y | N | Certificate reference for the cooling coil is not in the pack. Add it before issue. | ||
| 4 | Sound data at the duty point, by octave band, to the method the specification names | M-240 2.6 | Y | Y | SP-EX-AHU-03 p.5 | Discharge sound power is above the scheduled figure in two bands | Price a discharge attenuator as an option and flag it for the acoustic consultant. |
| 5 | Casing construction, with leakage and strength classes as specified | M-240 2.2 | Y | Y | Casing datasheet CD-EX-11 Rev C | None | |
| 6 | Electrical data: supply, full-load current, starting method, drive type and wiring diagram | M-240 2.7 | Y | Y | Electrical datasheet ED-EX-AHU-03; diagram WD-EX-03 | None | Full-load current reflects the larger motor in item 1. |
| 7 | Controls: sequence of operation and points list for the building management system | M-240 2.8 | Y | N | Points list is with the controls subcontractor. Hold the submittal or agree a partial submittal in writing. | ||
| 8 | Dimensions, section split, operating weights and service clearances | M-240 1.4 B; layout M-301 | Y | Y | General arrangement GA-EX-AHU-03 Rev A | Unit is longer than the space shown on layout M-301; access side unchanged | Ask the contractor to check the plant room layout before approval. |
| 9 | Filters: type, size and filter classes as specified | M-240 2.5 | Y | Y | Filter datasheet FD-EX-07 | None | |
| 10 | Accessories: dampers, flexible connections, vibration isolators, access doors and lights | M-240 2.9 | Y | Y | Accessory list AL-EX-AHU-03 | None | |
| 11 | Warranty statement | M-240 1.7 | Y | Y | Warranty statement WS-EX-01 | Warranty period runs from delivery; the specification counts from practical completion | Raise with the contractor before the submittal goes in. |
| 12 | Operation and maintenance manual | M-240 1.6 | N | N | Asked for at handover, not with this submittal. Enter it in the submittal log as its own item. |
The casing, leakage and filter rows say "as specified" because those classes belong to the project specification, and the template states none. The specification section, the schedule and the unit are invented. Every example value is invented: the project, customer, bidders, purchase order, prices and every document, certificate, serial and report number do not exist. Standards are named but not quoted.
Columns and what to write
| Column | What to write |
|---|---|
| Item | Running number. |
| What the specification asks for | One item the specification section, the schedule or the contract requires in the submittal. |
| Specification section | The section and paragraph, or the schedule and drawing, that asks for it. |
| Required | Y if the specification asks for the item in this submittal, N if it does not or asks for it later (drop-down). |
| Included | Y if the item is in the pack, N if it is not (drop-down). Rows that are required and not included turn red. |
| Document reference | The document in the pack that covers the item, with its number, revision and page. |
| Deviation | Where what you submit differs from what is specified or scheduled, say how. Write None if it does not. Rows with a deviation turn amber. |
| Remark | What is still to do, and who needs to be told. |
How to check a submittal with it
- Fill in the header block: the specification section and its revision, the equipment schedule drawing, the unit tag and the submittal number.
- Read the submittals paragraph of the specification section and write one row for each thing it asks for. Then read the products paragraphs and the schedule for anything else that has to be shown.
- Set Required to Y or N. Use N for items the specification asks for at another stage, and say when in the remark.
- Go through the pack you are about to send. Set Included, and write the document, revision and page that covers each item.
- Compare the selection with the equipment schedule line by line. Where your unit differs from what is scheduled or specified, write the difference in the Deviation column, or None.
- Sort out every row that is required and not included, which turns red, before the submittal leaves.
- List every deviation on the submittal cover sheet. A deviation the reviewer finds first costs more than one you declared.
- Keep the checklist with your copy of the submittal, and update it when the submittal is revised.
Comparing the selection with the specification and schedule
Confirming that a document is in the pack is quick. Confirming that its contents agree with the specification takes longer: a motor size on the selection printout against the schedule, a sound figure against the acoustic clause. In OdysseyGPT's Tender & Quotation module, Datasheet Comparison (beta) sets your datasheet values beside the customer's, and Document Review reads the specification section and your submittal documents and lists where they differ, quoting the page on each side. The application engineer decides which differences are deviations. Tools marked beta are open on request, and we onboard each team ourselves.
See how OdysseyGPT reviews a tender
Tell us how your team reviews tenders today. We can walk through an example together.
