How we work

A clear process. Coordinated results.

We organise requirements, models, reviews, and decisions into a readable technical sequence—from initial analysis to the agreed delivery.

Defined requirements
Objectives, constraints, and responsibilities clarified before development.
Traceable decisions
Clashes, actions, and revisions remain connected and readable.
Reviewable delivery
Models, drawings, and reports aligned with the agreed project phase.
The process

From requirements to delivery, every step remains visible

Each phase starts with defined information, applies a focused review, and prepares the next activity. The result is a technical path that can be understood and checked.

01 / 05

Intake and analysis

We review the available information and define objectives, constraints, responsibilities, and review criteria before development begins.

ARV / 01MEP · BIM
COORDINATED WORKFLOW
Starting point
Requirements, available documentation, and project constraints.
Phase outcome
Shared scope, responsibilities, and review criteria.
02 / 05

Modelling

We develop discipline models around the agreed technical and information objectives while keeping structure and data consistent.

ARV / 02MEP · BIM
COORDINATED WORKFLOW
Starting point
Approved criteria and phase information requirements.
Phase outcome
Coherent discipline models ready for comparison.
03 / 05

Coordination

We review MEP systems, architecture, and structure together to test space, relationships, and compatibility between disciplines.

ARV / 03MEP · BIM
COORDINATED WORKFLOW
Starting point
Discipline models and shared reference information.
Phase outcome
A consolidated coordination review.
04 / 05

Resolution

We classify clashes, assign actions, and turn open issues into documented technical decisions.

ARV / 04MEP · BIM
COORDINATED WORKFLOW
Starting point
Classified clashes and open technical decisions.
Phase outcome
Tracked decisions and updated models.
05 / 05

Delivery

We review the consistency, status, and format of each output before assembling the information package required for the phase.

ARV / 05MEP · BIM
COORDINATED WORKFLOW
Starting point
Completed models, drawings, reports, and revisions.
Phase outcome
An agreed, organised, and reviewable delivery.
Control and collaboration

Quality comes from visible decisions

Coordination is not a final check. It runs through the work and makes responsibilities, changes, and review status understandable.

01
Requirements before development
Objectives, model uses, responsibilities, and review criteria are clarified before production.
02
Disciplines in one process
MEP systems, architecture, and structure are reviewed against the same technical reference.
03
Traceable decisions
Clashes, responsibilities, revisions, and outcomes remain connected to the process that created them.
04
Progressive reviews
Checks support every phase to reduce ambiguity before delivery.
Technical delivery

Outputs defined around their intended use

The delivery is structured around the project phase, responsibilities, and agreed level of development.

Output type, format, and level of detail are confirmed for each appointment. Nothing outside the agreed scope is assumed.