Last month, this column introduced the concept of an “excessively long” commissioning action list (CAL). Once functional performance testing begins, the CAL (which could also be named a variety of other things) is the tool that commissioning professionals use to document and track resolution of deficiencies with, questions about, and/or differing opinions regarding system operation. A long CAL is bad for everyone on the project team, as detailed in my September 2014 column. This month, I want to begin exploring the multiple reasons why the CAL might get out of hand, who might be responsible, and what the commissioning professional might do about it.