I/O List Excel Template: Columns, Format, and Common Mistakes

A well-structured I/O list saves hours during commissioning. A poorly structured one creates confusion, delays loop checks, and forces rework when the control system integrator can't map your tags to their hardware.

This guide covers what belongs in an I/O list spreadsheet, how to structure it for downstream use, and the mistakes that cost teams the most time.

Essential columns

Every I/O list should include these columns at minimum:

Column	Purpose	Example
Tag Number	Unique instrument identifier per ISA 5.1	FIT-101, PSL-201
Loop Number	Groups related instruments	101, 201
Instrument Type	ISA function letters	FIT, PSL, TIC, XV
Signal Class	AI, AO, DI, or DO	AI
Description	What the instrument does	Flow Indicating Transmitter
P&ID Reference	Source drawing number	PID-001-A
Page Number	Page within the drawing set	3
Service / Process Area	Plant area or unit	Cooling Water, Unit 200

These eight columns are the foundation. Without any one of them, someone downstream will have to go back to the drawings.

Columns that save rework later

Beyond the basics, these columns prevent the most common back-and-forth during detailed design:

Column	Why it matters
Connected Equipment	Which pump, vessel, or exchanger the instrument serves (P-101, V-200)
Range / Span	0-100 PSI, 4-20mA — needed for scaling in the PLC
Fail Position	FC, FO, FL for valves — critical for safety reviews
Cable Type	Shielded pair for analog, standard for discrete
Panel / Cabinet	Where the signal terminates — needed for cable scheduling
I/O Module	Which PLC card the signal lands on
Alarm Setpoints	High, Low, HH, LL values if known
Notes	Field conditions, special requirements, deviations from standard

You don't need all of these on day one. But if you structure your spreadsheet to accommodate them from the start, you avoid reformatting later.

Formatting standards that matter

Consistent tag numbering

Pick a format and enforce it across the entire list. Mixed formats cause duplicate entries and missed instruments during QA.

Consistent	Inconsistent (problems)
FIT-101	FIT-101
FIT-102	FIT102 (missing separator)
FIT-103	Fit-103 (mixed case)
PSL-201	PSL-0201 (zero-padded vs not)

Signal class validation

Every instrument must map to exactly one signal class. Common errors:

• Control valves left as AI — A valve with a 4-20mA positioner input is AO, not AI. The signal goes to the valve.
• Switches classified as AI — A pressure switch (PSL, PSH) is a discrete contact. That's DI, not AI.
• Solenoid valves as AO — Solenoids are on/off. That's DO.
• Indicators with no wiring — A local gauge (PI, TI with no transmitter) may not be wired to the DCS at all. These need to be flagged, not classified.

Conditional formatting

Color-coding signal classes in Excel makes QA review significantly faster:

Signal Class	Recommended Color	Rationale
AI	Blue fill	Convention in most I&C departments
AO	Green fill	Output = action = green
DI	Amber/Orange fill	Discrete input = alert/status
DO	Red fill	Discrete output = command

This isn't cosmetic — it lets reviewers scan hundreds of rows and spot classification errors visually.

Common mistakes that cause rework

1. Duplicate tag numbers

Two instruments with the same tag number will cause conflicts in the PLC program and the cable schedule. This happens most often when:

• Multiple engineers work on different sections of the same P&ID set
• Tags are copied from a similar project and not fully renumbered
• Revision changes add instruments without checking existing numbering

2. Missing loop numbers

Without loop numbers, you can't group related instruments (transmitter, controller, valve) into control loops. This makes the loop check procedure nearly impossible to organize.

3. Inconsistent separators

FIT-101 vs FIT_101 vs FIT101 — pick one. Mixed separators break sorting, filtering, and VLOOKUP formulas. They also cause false "missing instrument" flags during QA when the formats don't match across documents.

4. Orphaned valves

A control valve (FCV, TCV, PCV) should have a corresponding transmitter and controller in the same loop. If your I/O list has a valve with no transmitter, either the transmitter is missing from the list or the valve tag is wrong.

5. No page reference

When someone finds an error in the I/O list, they need to go back to the source drawing. Without a page number column, that means flipping through an entire drawing set. On a 50-page project, that's a significant time cost per correction.

6. Mixing wired and non-wired instruments

Local gauges, sight glasses, and manual valves often appear on P&IDs but have no electrical signal. Including them in the I/O list without a clear flag inflates your I/O count and leads to phantom channels in the PLC configuration.

Structuring for PLC import

If your I/O list will feed into PLC programming software (TIA Portal, Studio 5000, etc.), structure matters even more:

• Tag numbers must be valid variable names — No spaces, no special characters beyond hyphens and underscores
• Signal class determines the module type — AI maps to analog input cards, DO maps to discrete output cards. Getting this wrong means wrong hardware orders.
• Group by cabinet/panel — PLC programmers organize by physical location, not by process area. Include a termination column early.

Quick checklist before submitting

Before sending an I/O list to the next discipline:

• Every row has a tag number, loop number, type, signal class, and description
• No duplicate tag numbers (sort and scan)
• Signal classes are correct (valves = AO or DO, switches = DI, transmitters = AI)
• Page references point to the correct P&ID revision
• Conditional formatting applied for visual QA
• Filter each signal class column and verify the counts match your expectation
• Check for orphaned control loops (valve without transmitter, or vice versa)

---