Direct Answer
Tekla's built-in clash detection identifies intersecting objects in the model — two members occupying the same space, bolts that penetrate flanges, or heads that conflict with adjacent members. Running a clash check before issuing drawings is the single most efficient QC step a detailer can take, catching coordination errors that would otherwise surface during erection.
Full Explanation
Tekla's clash check tool (or the Trimble Connect integration) compares all objects in the model against each other and flags any geometry overlap. Results are presented as a clash list with object IDs and a 3D view of each clash. Common structural clashes: column flange conflicting with an adjacent beam, gusset plate interfering with a brace, stiffener plate conflicting with a bolt head. Each clash must be resolved in the model before drawings are issued.
What This Means for Your Shop
A detailer who runs clash checks before issuing reduces field RFIs by an estimated 30–50%. Request that your detailer deliver a clash report confirming zero clashes before the IFC package is issued.
Common Mistakes
Running clash detection only against other structural members, ignoring MEP. A structural model with zero internal clashes can still have dozens of MEP clashes in the federated model.
Recommended Process
Require the detailer to run a structural clash check and resolve all clashes before IFC. Then load the structural IFC into the GC's federated model for MEP coordination. Document the process in your QC plan.