Project context

Different roles. One shared set of project information.

Common project roles and work situations for technical delivery support, not a client roster or a claim of specific outcomes.

01
Role and task

Architecture and design

Existing conditions, model development, and discipline interfaces can shape what a design team needs to review next.

  • Revit content from supplied survey information
  • Model boundaries and reference alignment
  • Open conditions that need design team review
02
Role and task

Engineering and specialist trades

Discipline teams may need specified model or drawing production, or a bounded review of system interfaces against current project criteria.

  • MEP model and drawing production from engineering direction
  • Potential intersections and clearance findings
  • Reinforcement, structural, or precast detail packages
03
Role and task

Construction, owners, and facilities

Construction and asset roles may need information organized around the next exchange, handoff, or stated use of an existing conditions model.

  • Issue context tied to model versions and locations
  • Survey coverage and unverified conditions made visible
  • Receiving requirements and review ownership
Shared responsibility

Responsibilities stay explicit

Project participants establish design intent, technical criteria, field verification, design approval, and acceptance. The support scope should identify the people responsible for those decisions.

Describe the people and handoff involved.

Share your team's role, project stage, and the information that needs to move to its next reviewer.

Start a project enquiry →