An equipment list and an equipment schedule hold the same kind of information, the tagged equipment on a project, but they are different documents from different worlds. The equipment list is the standalone register a process plant keeps: every vessel, pump, exchanger, and package item, one row per tag, with service and design data, owned by the process or mechanical group for the whole project. The equipment schedule is the table an HVAC or building-services project draws on the drawing sheet itself: one schedule per equipment type, an AHU schedule, a fan schedule, a chiller schedule, carrying the selection data a contractor prices and installs from. Same job, a register of equipment. Different home, different grouping, different reader.
Key takeaways
- The equipment list is a standalone, project-wide register, one row per tag, ordered by tag or area. Process-industry usage.
- The equipment schedule is a table on the drawing, grouped by equipment type, carrying selection data. HVAC and building-services usage.
- The list serves engineering and procurement across the project. The schedule serves the installing contractor pricing and building from the sheet.
- Neither includes instruments. Those belong to the instrument index, and the wired subset to the I/O list.
- Both registers are only as good as the drawing revision they were last reconciled against.
The equipment list, a project register
On a process project the equipment list is one of the core engineering registers, alongside the line list and the instrument index. Every tagged equipment item on the P&ID set gets a row: tag, description, service, and the design data that matters for that item, design pressure and temperature, capacity or duty, materials, driver rating, weight. Each row points back to its P&ID and forward to its datasheet.
Because it is a standalone document rather than a drawing table, the list runs the full width of the project. Procurement counts and packages from it, mechanical checks nozzle and driver data against it, layout takes weights and footprints from it, and at handover it seeds the maintenance system's asset register. The working format is a spreadsheet, which is why a pre-formatted equipment list template is usually where a new register starts, and why building a master equipment list is mostly a reconciliation job across P&IDs and vendor datasheets.
The equipment schedule, a drawing table
On an HVAC or building-services project the same information lives on the drawings. A schedule is a table drawn on the mechanical sheet, one per equipment type: the AHU schedule, the fan schedule, the pump schedule, the chiller schedule. Columns are type-specific selection data, airflow and external static pressure for an air handler, flow and head for a pump, capacity and electrical characteristics for a chiller, plus a basis-of-design manufacturer and model.
The reader is different too. A schedule is a contract document for the installing contractor: it is what gets priced at bid, what submittals are checked against, and what the commissioning agent verifies in the field. The full column-by-column treatment is in the HVAC equipment schedule guide, and schedules locked inside drawing PDFs are exactly the tables engineers end up pulling back into Excel when the register has to live outside the sheet.
Side by side
| Aspect | Equipment list | Equipment schedule |
|---|---|---|
| Home | Standalone register, usually a spreadsheet | Table drawn on the drawing sheet |
| World | Process plants, oil and gas, chemicals | HVAC, building services, MEP |
| Grouping | One row per tag, ordered by tag or area | One schedule per equipment type |
| Typical columns | Service, design pressure and temperature, duty, materials, P&ID and datasheet references | Type-specific selection data plus basis-of-design model |
| Primary reader | Engineering and procurement across the project | The installing contractor and the commissioning agent |
| Lifecycle | Maintained through every revision to handover | Issued and revised with the drawing set |
When both show up on one project
The split is a naming convention, not a law. A large building project may compile a combined equipment list as a handover register on top of its drawing schedules, and a process package vendor may put a small schedule table on a skid drawing. When both exist, the practical rule is the one that applies to every paired register: decide which document is the master, and reconcile the other against it at each revision rather than letting the two drift apart.