Commissioning Readings to Record as a Baseline
Why this matters
The most valuable diagnostic data you will ever have on a unit is what it read the day it was new and working right. A year later, when it acts up, a baseline turns "I think this is high" into "this is twice what it was at startup." Without a baseline, every reading is a guess against a spec range; with one, you are comparing the unit to itself. Shops that record commissioning readings diagnose faster, win warranty arguments, and look like professionals. Shops that do not are re-deriving normal on every call.
The principle: capture the unit at its best
A baseline is a snapshot of a known-good state. The conditions at commissioning are the cleanest the unit will ever see: new components, clean filters and screens, correct settings, nothing worn or fouled. That is exactly why it is the reference point. Record it once, store it with the job record, and every future reading has something honest to be measured against.
Take baseline readings only after the unit is fully commissioned and running correctly under a real load, not at idle and not before setup. A baseline of a misconfigured unit is worse than none, because it enshrines the wrong values as normal.
What to record: the electrical baseline
For anything electrical, capture what the unit draws and is fed when running right.
- Supply voltage at the unit's terminals, under load, not just at rest.
- Operating current on each leg or major component while it runs at a real operating point.
- Control voltages the unit expects to see.
- Capacitor or component values where applicable, read and compared to nameplate at install.
These tell you later whether a part is loading up, a supply is sagging, or a component has drifted.
What to record: the fluid and pressure baseline
For anything that moves air, water, gas, or refrigerant:
- Operating pressures at the standard test points, with the conditions noted (because pressure means nothing without the conditions it was taken under).
- Flow rates where you can measure them.
- Temperatures in and out across the components that do work, and the difference between them.
- The ambient conditions at the time: outdoor and indoor temperature, anything that affects what "normal" should be that day.
A pressure or temperature reading without its conditions is half a data point. Always write the conditions next to the number.
What to record: the settings and configuration
The as-left settings are part of the baseline, because a future "it changed" might be that someone changed a setting, not that a part failed.
- Every adjustable you set: limits, cutouts, speeds, delays, output levels, with the value.
- The configuration: mode, size or capacity range, addressing, sensor matching.
- Anything you deliberately left at default, so the next tech knows it was a choice, not an oversight.
How to record it so it is actually useful
A baseline buried in a notebook in the truck helps no one. Make it findable and comparable.
| Practice | Why it matters |
|---|---|
| Store it with the job or equipment record | The next tech finds it without calling you |
| Note the conditions beside every reading | A reading without conditions is not comparable |
| Use the same test points every time | So a year-later reading is apples to apples |
| Date and initial it | So you know whose baseline and how old |
| Photograph the nameplate and any displayed values | Backs up the written numbers, catches what you forgot |
Consistency is the whole value. If you take the reading at a different point or under different conditions next time, the comparison is broken. Pick the standard test points and use them.
What a baseline buys you later
- Faster diagnosis. A drifted reading jumps out against the baseline instead of hiding inside a wide spec range.
- Trend instead of snapshot. Compare commissioning, last service, and today, and you see the direction, not just the moment.
- A warranty case. A part that read fine at startup and reads wrong now is documented evidence, not an opinion.
- A defensible recommendation. "This is running at twice its startup pressure" is a number the customer can trust, not a hunch.
The mental model to keep: you are not just starting the unit, you are recording the answer key. Take the readings while the unit is new and right, store them where they will be found, and you have handed your future self the fastest diagnosis on the next call.
References
- Manufacturer commissioning data sheets and recommended test points
- Trade-standard practice for startup documentation and equipment records
- See related: The Startup Sequence That Catches Install Errors; Deeper Meter and Gauge Reading (where applicable)
- See related: A Reading in Range but Still Wrong (decision tree)