Whether Podany's advice to halt installation of J.D. Edwards's software, and his later stop-payment orders, fell outside the scope of the consulting engagement and therefore outside the consultant's privilege.
Holding
No. The challenged advice and orders fell within the express or implied scope of Podany's engagement.
Reasoning
Illinois recognizes a qualified privilege for consultants who give honest advice to their clients, even when the advice causes harm to a third party through a contractual breach. The privilege is limited, however, to advice that is within the scope of the consultant's engagement and is given in good faith for the client's benefit.
Podany was retained to conduct a rapid business-level review of SNE's project. His criticism of "reengineering in parallel" concerned a systems concept within that assignment. Because his view was that SNE should first define its business needs and only then install software, his recommendation to stop installing J.D. Edwards's software logically followed from his authorized assessment.
The court declined to define the scope of a consulting engagement so narrowly that a consultant could not identify and address a related problem within his competence. Just as a surgeon may appropriately address a significant condition discovered during an authorized procedure, a consultant ordinarily may alert the client to a related problem and recommend a solution, even if the solution affects an existing contract.
Podany's instruction to stop paying J.D. Edwards went beyond the original brief, but Massel had expanded the engagement by requiring approval from Podany for all computer-related purchases. That directive brought the stop-payment orders within the implied scope of Podany's enlarged authority.