This article analyzes deviations in an automation project. The article develops a more holistic view of the project organization, focusing on how deviations are managed. The case study demonstrates that the tools and methods suggested in the literature are rarely used, and shows the importance of the context of the project in terms of gathering information and sharing knowledge that is required to manage deviations. Furthermore, the case shows that there are a number of deviation-management tactics that are applied to different deviations, dependent on whether they are uncertain and/or ambiguous.