Case Study: Delivering Zero-Clash Shop Drawings for Complex Global Projects (Speers Point, Delnorth)

Demonstrating real-world execution capabilities across international construction projects.

Project Profiles

Speers Point Educational Facility (NSW, Australia): Approved by the New South Wales Government to transform an established educational facility into modern learning spaces.

Delnorth Commercial Warehouse

High-efficiency commercial warehouse requiring rapid structural detailing.

Platform and Boardwalk Decking

Specialized infrastructure featuring lightweight, corrosion-resistant Fiberglass Reinforced Plastic (FRP) gratings.

Execution Strategy & Deliverables

Constructed full 3D Tekla models, executed Master Plan Clash Detection, and generated detailed Marking Plans with North orientation arrows, grid elevations, purlin layouts, and Chemset/Trubolt anchor details. Produced accurate BOM/MTO reports to streamline material purchasing.

Lessons From the Two Projects

Both projects shared the same underlying challenge despite very different scopes: getting every trade's model into the same coordination cycle early enough that clashes were caught on screen rather than on site. The recurring lesson from both jobs was that a clash run done once at 90% completion catches far more problems, at far higher cost to fix, than the same clash run done every two weeks from 30% completion onward. Establishing that cadence from the start of the model — rather than bolting it on once the project team realizes conflicts are piling up — was the single biggest factor in hitting a zero-clash release on both jobs.

The other transferable takeaway was documentation discipline: every clash resolved in coordination was logged with the date, the change made, and which trade's model moved, so that when a similar conflict showed up on a later phase of either project, the team could check the log instead of re-litigating the same design decision.

What Made the Coordination Process Work

Neither project succeeded because of a single tool or technique — both benefited from a coordination cadence that was set at kickoff and held to throughout, rather than adjusted reactively as deadlines approached. Weekly clash runs against current MEP and architectural models, a standing RFI response-time commitment, and a shared model federation schedule meant that by the time each project reached its final drawing release, there were no large categories of unresolved conflict left to discover under schedule pressure.

The other consistent factor across both jobs was piece-mark and revision discipline: every change that came out of a coordination meeting was tracked back to a specific model revision, so the shop drawing set and the BOM never drifted out of sync with what coordination had actually agreed to, even as the projects moved through several rounds of design changes.

Applying These Lessons to a New Project

The specific numbers from any one project matter less than the process that produced them, and that process is largely portable to a new job regardless of building type. Setting a fixed coordination cadence from day one, logging every clash resolution with enough detail to reference later, and keeping piece marks synchronized between the model, the BOM, and every drawing set are practices that don't depend on the particular geometry of a warehouse or a boardwalk — they're workflow habits that pay off on any project where multiple trades and a fabrication schedule have to stay coordinated over months of changes.

Both projects also reinforced a simple scheduling principle that's easy to state and harder to hold to under deadline pressure: coordination time spent early is cheaper than rework time spent late. On neither job was there a shortcut that avoided this trade-off — the zero-clash outcome was a direct result of protecting the coordination schedule even when other parts of the project timeline were under pressure to compress.