Resource search

Search DataDrivenAEC

Type at least two characters to search.

Looking for live projects? Explore open projects or browse the feed.

Open the full search page →

← All workflows

AEC workflow

Coordinate & Deliver

Move issues from detection to an owned, traceable decision and verified project-document update.

197 resources shown.

Follow the process

How to move a coordination issue from detection to verified closure

Begin with aligned project information, turn observations into owned issues, and close them only against an updated design and explicit evidence. The aim is a traceable decision and coordinated revision, not a smaller count of open tickets.

Your deliverable: A coordinated issue register with decisions, owners, changed design references and evidence supporting closure or reopening.

Skip to the resource library ↓

Before you start

  • Current discipline models or drawings with revision and coordinate references.
  • An agreed issue scope, locations and project-specific priority criteria.
  • Named discipline owners and a person authorized to accept a resolution.
  • A shared issue register and a controlled route for distributing reviewed revisions.

  1. Align the coordination baseline

    Inputs
    Discipline files, drawing revisions, coordinates and the agreed review scope.
    Action
    Confirm which files belong to the review and check alignment before inspecting conflicts. Record missing or obsolete inputs. Distinguish a reference error from a real physical or information conflict so the team solves the right problem.
    Output
    A review baseline identifying included revisions, alignment checks and missing information.
    Review checkpoint
    Are all disciplines being compared against the same agreed reference and review date?
    Common mistake
    Reporting coordinate or revision mismatches as hundreds of separate design clashes.

    Resources for this step

  2. Turn observations into actionable issues

    Inputs
    Detected conflicts, drawing observations, field records and priority criteria.
    Action
    Create one issue for each distinct decision. Give it a location, source references, impact, owner and required response. Link duplicates rather than deleting their evidence. Separate a clash observation from the design change proposed to resolve it.
    Output
    An issue queue with identifiable locations, priority, ownership and next actions.
    Review checkpoint
    Could the assigned person locate the problem and understand the decision without another meeting?
    Common mistake
    Sending screenshots or clash lists without owners, design context or a requested decision.

    Resources for this step

  3. Agree the resolution and affected disciplines

    Inputs
    Issue evidence, design options, constraints and responses from affected authors.
    Action
    Compare resolution options with the relevant disciplines. Record the chosen action, why it was selected, affected documents and who authorizes it. Keep an issue open if the proposal shifts a conflict elsewhere or depends on unanswered information.
    Output
    A decision record assigning design changes, reviewers and required closure evidence.
    Review checkpoint
    Have the affected disciplines accepted the proposed action and its downstream consequences?
    Common mistake
    Closing an issue after one author proposes a change before the other disciplines have reviewed it.

    Resources for this step

    • Asana technology overview

      Compare another task-management route for decisions and handoffs; check the project’s required evidence links.

  4. Check the changed design against the issue

    Inputs
    Updated design revisions, the agreed action and explicit closure requirements.
    Action
    Inspect the changed location and affected interfaces, then repeat the relevant coordination checks. Where field evidence matters, confirm its date, location and visibility limits. Record whether the evidence supports closure or requires another action.
    Output
    A verification record linking the issue to the corrected revision and any remaining exceptions.
    Review checkpoint
    Does current evidence prove the agreed issue is resolved, not just that somebody marked a task done?
    Common mistake
    Using an old image or a view of concealed work as proof that all physical conditions are correct.

    Resources for this step

    • OpenSpace technology overview

      Review a vendor-documented field-capture option; an image has time and visibility limits and is not concealed-work acceptance.

  5. Issue the coordinated revision and retain reopening triggers

    Inputs
    Verified changes, remaining issues and the approved distribution list.
    Action
    Publish the agreed revision through the project’s controlled route. Retain issue history, unresolved items and recipient responsibilities. A changed model, site condition or design instruction should reopen affected issues instead of silently inheriting old closure decisions.
    Output
    A coordinated revision package and issue history with update and reopening responsibilities.
    Review checkpoint
    Do recipients know which revision to use and which issues remain unresolved?
    Common mistake
    Distributing revised drawings without the decisions and exceptions that explain the changes.

    Resources for this step

Worked journey: a service route conflicts with an opening

Synthetic training example only: the project, records and outcomes below are invented to explain the process. This is not evidence of a tested implementation, customer result or professional approval.

Baseline
The coordinator finds one obsolete drawing and replaces it in the review baseline before raising the physical conflict.
Triage
One located issue records the service route, opening reference, affected disciplines and response owner.
Decision
The authors compare a reroute with an opening change and retain the agreed option and required reviews.
Verification
The updated design is checked at the conflict and its interfaces. A remaining access concern keeps one action open.
Issue
The coordinated revision is distributed with the remaining concern and a rule to revisit the issue after another route change.

Coordination issue handover checklist

Select and copy the checklist into your project document. Complete it there; this page does not save project information.

Continue to the resource library ↓

Back to the coordination process ↑

197 connected resources

Explore this workflow

AEC technology profiles connected to this workflow.

Workflow pick

Asana

Collaborative work and project management platform

Open resource →Workflow pick

ClickUp

Combine tasks, documents, goals, forms, and automations for team delivery

Open resource →Workflow pick

OpenSpace

Visual Intelligence Platform for construction

Open resource →

3D Repo

Cloud-based BIM collaboration and clash detection platform

Open resource →

Ackcio

Wireless mesh sensor network for geotechnical and structural site monitoring

Open resource →

Agave

Connecting construction project and accounting records

Open resource →

Ailytics

AI video analytics that turns existing CCTV cameras into real-time construction safety and productivity monitoring

Open resource →

AItenders

AI copilot for AEC tender analysis, proposal writing, and contract execution tracking

Open resource →

ALICE

AI-powered construction scheduling and scenario optimization

Open resource →

Allsite.ai

AI-powered site design and grading optimization

Open resource →

Archdesk

All-in-one cloud construction management platform

Open resource →

ArcSite

Mobile on-site drawing, material takeoff, and estimating for specialty contractors

Open resource →
Browse technology directory →

A human decision first

Being data-driven goes beyond technology

It starts with good questions, trusted evidence, and clear decisions.

Book a conversation →