Solving for disparate information, Pype Closeout helps Layton stay organized, track effortlessly, and improve relationships
July 8, 2019
Download Full Case Study
During a construction project, there are many moving parts that need attention at any given time. At the end of a project, often supervisors and program managers are working diligently to get the construction completed. Layton was lacking a uniform way to handle closeout procedures, and each project team was reinventing the wheel; sometimes a log was created in Excel to track changes, sometimes information was only sent and retained in emails, and sometimes communication was as archaic as highlighted specification (spec) sections. Nothing was centralized, and project information was frequently in two or three different places.
This disparate information was dangerous. According to Alonza McKenzie, Layton project engineer, “The more disparate your information, the harder it is to stay organized, and the easier it is to make mistakes.” The platforms Layton did use were siloed, isolating the data on each, and forcing the team to manually update each platform every time there was a change. In addition, they were using software meant for other purposes, like Excel, and trying to force it to become a documentation aggregator and tracker. This took time away from the project, as teams had to check and cross-reference information in several different places, or run the risk of acting on inaccurate and outdated information.
Pype Closeout a “Best in Class Solution”
After a short phone conversation with Pype, McKenzie hit the ground running with Closeout, finding it “really user friendly, both to get started with and to maintain.” He estimates the platform shaved at least two weeks off of their project closeout.
McKenzie’s team was already using Pype AutoSpecs to identify every submittal from the spec book, filter the log down to the closeout requirements, and then export them directly into CMiC. Based on the initial improvement AutoSpecs had on Layton’s closeout, the team was eager to ramp it up and try Pype’s closeout-specific solution. After a short phone conversation with Pype, McKenzie’s team hit the ground running.
McKenzie “loved that Pype Closeout focused on closeout; it’s the best at what it does.” Instead of trying to replace CMiC, Closeout worked with it to create a best-in-class solution that solved project closeout pain points. With a comprehensive approach involving automated outreach, powerful dashboards, and robust reporting, Pype helped ease the burden of closeout by streamlining their disparate processes into one, efficient workflow.