Category • Coordination • Models • Actions

Coordination Workflows

This page outlines practical coordination workflows for model-based projects. It focuses on linked model review, clash detection, issue management, action tracking, and the discipline needed to move from identified problems to closed coordination outcomes.

Linked models Clash detection Issue tracking Action ownership Close-out QA for coordination

1. Overview

Foundation

Coordination workflows are the structured processes teams use to identify, communicate, resolve, and verify model issues across disciplines. A strong workflow does not stop at finding clashes — it creates clarity around what the problem is, who owns it, what needs to happen next, and when the issue is truly closed.

Identify

Find the issue clearly and understand its real impact.

Assign

Make ownership and next action clear.

Verify

Re-check the change and confirm the issue is closed.

2. Coordination stages

Typical sequence
Typical coordination sequence
  • Review model inputs and linked model condition
  • Run or review clash detection
  • Filter and prioritise issues
  • Assign ownership and actions
  • Update models or information
  • Re-run checks and close out
Why sequence matters
  • Reduces noise from low-value clashes
  • Improves focus on meaningful issues
  • Supports accountability
  • Improves confidence in close-out decisions

3. Linked model reviews

Start with good inputs

Coordination quality depends on model input quality. If linked models are mispositioned, outdated, or poorly understood, the coordination process becomes less reliable.

Positioning

  • Check the linked model location
  • Confirm shared coordinates strategy if used
  • Avoid guessing alignment

Version awareness

  • Know which linked version is under review
  • Be aware of outdated reference models
  • Check if a coordination problem is already superseded

Scope awareness

  • Understand which discipline owns which geometry
  • Be clear on host vs linked responsibility
  • Review major interfaces early
Warning: A clash result is only as useful as the model inputs that produced it.

4. Clash detection workflows

Find the right problems

Clash detection should be used to find meaningful coordination problems, not to generate uncontrolled lists of everything that overlaps. The review process should focus on relevance, severity, and actionability.

Good clash workflow
  • Use sensible clash sets
  • Review clash results in context
  • Separate genuine issues from false positives
  • Prioritise high-impact issues first
Useful review questions
  • Is it a real clash?
  • Does it affect installation or access?
  • Who owns the next action?
  • Does it need immediate close-out or later review?

5. Issue management

From problem to action

Coordination improves when issues are recorded clearly. A useful issue record should explain the problem, show the location or context, identify the owner, and describe the expected next step.

Record clearly

  • Describe the problem simply
  • Give enough context
  • Reference location or model area

Assign clearly

  • Identify the responsible owner
  • Set an expected action
  • Set a review target if needed

Track clearly

  • Know what is open
  • Know what has changed
  • Know what is closed and why

6. Actions and communication

Make the next step obvious

Coordination workflows are much stronger when the next action is clearly communicated. The aim is to reduce ambiguity and prevent issues from being repeatedly rediscovered without progress.

Good action tracking
  • State what needs to change
  • State who is expected to act
  • State when it should be reviewed again
  • Keep the issue record easy to understand
Poor communication signs
  • Repeated vague comments
  • No ownership
  • No re-check date or trigger
  • Issues discussed verbally but not recorded

7. Close-out and re-checks

Confirm it is actually resolved

Closing an issue should not only mean that someone says it is fixed. Strong coordination practice means the change is checked again and the team is satisfied the issue no longer causes the same problem.

Before close-out
  • Confirm the model or information changed
  • Re-check the original issue context
  • Confirm the issue no longer affects the workflow
Good close-out behaviour
  • Close with evidence, not assumption
  • Keep the record understandable later
  • Be clear if an issue is deferred rather than resolved

8. QA expectations

Coordination quality

Coordination workflows benefit from QA just like models and drawings do. The process itself should be structured, consistent, and reviewable.

Input QA

  • Correct linked models
  • Correct scope of review
  • Known model limitations understood

Process QA

  • Useful clash rules
  • Useful filtering and prioritisation
  • Clear issue records

Output QA

  • Actions are tracked
  • Close-out is verified
  • Records support later review

9. Do / Don’t guidance

Quick reference

Do

  • Start with good linked-model inputs
  • Prioritise meaningful clashes
  • Assign clear ownership
  • Track actions and re-check changes
  • Close issues with evidence

Don’t

  • Treat every clash as equally important
  • Confuse identification with resolution
  • Leave actions vague
  • Close issues without re-checking
  • Rely on memory instead of records
Final takeaway: Strong coordination workflows create clarity, ownership, and confidence. The real value is not only in finding problems, but in making sure the right problems are acted on and properly closed.