Skip to main content
ARCOArchitecture · Consulting

02 — Manage · Project Delivery + Information Management

The keystone between information, teams, and decisions.

We define how information should be requested, produced, and reviewed, connecting what the project requires with the decisions it needs to make.

Build My BIM BriefRequest a Discovery Session
Arch with a red keystone connecting three elements. Information: reliable data to make decisions with confidence. Teams: aligned people, clear roles, collaboration without friction. Decisions: key decision points at the right time, with clear impact.
Clear requirements
What information must be produced, and why.
Identifiable information
What is current, what is missing, and what status it is in.
Traceable reviews
What was reviewed, what changed, and what was recorded.
Decision-ready information
Information that is available and prepared for the right review or decision.

Which of these situations describes your project?

Not every project needs to organize its information at the same point. Some start before procurement. Others start once several teams are already producing, reviewing, and delivering information.

Architectural drawings on a desk, with a pen and a hard hat.

I’m preparing for procurement

I need to define what information to request, how it should be delivered, and what must be verifiable.

Two engineers in hard hats and safety vests review a drawing in front of a building under construction.

The project is already underway

I need to organize responsibilities, deliverables, and reviews across multiple organizations.

A hand holding a pen over drawings, with a magnifying glass overlay and a construction site behind.

I’m receiving information

I need to identify what is current, what is missing, and what must be checked before reviewing or deciding.

A tablet shows a building model next to a digital model with one volume highlighted in red.

I need to connect project phases

Information has to carry through design, construction, handover, or operations without losing context or traceability.

Wherever you come in, we connect the missing steps.

From what the project requires to the decision that information must support.

ARCO designs the information management architecture that connects requirements, responsibilities, production, exchange, and review throughout the project.

Managing information is not just organizing documents or configuring a platform. It means defining what information the project needs, who should produce it, how it should flow and be reviewed, and what it needs to be available for.

  1. Request

    What information does the project need, and why?

  2. Produce

    Who should create it, and under what requirements?

  3. Review

    What must be checked before it is used?

  4. Decide

    Which review, approval, or decision must it be ready for?

Line drawing of a multi-storey building, with a red volume that runs through and connects two of its levels.

We can start before procurement.Or join once the project is already underway.

  1. Procurement

    Define what information should be required, how it should be delivered, and what criteria will be used to review it.

  2. Design

    Organize responsibilities, exchanges, reviews, and deliverables across the teams producing information.

  3. Construction

    Connect the information produced with coordination, tracking, review, and decisions during construction.

  4. Handover

    Prepare the information that must be retained, verified, and transferred at closeout.

  5. Operations

    Maintain continuity of the information that those receiving and operating the asset will rely on.

Wherever you come in, we connect the missing steps.

The level of support depends on where the project stands.

Not every project needs to start from scratch or change its entire way of working. We can step in on a specific need and connect the necessary steps from there.

  1. 01

    Design

    We define information requirements, responsibilities, processes, review criteria, and the structure the project needs to produce and receive useful information.

    An information management architecture defined around the project’s needs.

  2. 02

    Implement

    We turn that architecture into workable processes: workflows, statuses, exchange rules, information structure, and configuration for the project environment.

    Requirements and processes turned into a way of working that teams can use.

  3. 03

    Support

    We support its application, deliverable reviews, and requirements verification to maintain continuity between what was requested, received, reviewed, and recorded.

    Information that can be tracked during execution and used for the purpose it was required for.

The same architecture.At different points in the project.

Aerial view of an elevated metro station, with a train on the viaduct and a highway in the foreground.

Panama Metro — Line 3

From contract requirements to BIM implementation during construction.

The work ranged from assessing and defining BIM requirements to training teams, overseeing deliverables, and applying BIM during construction.

  1. Requirements
  2. Procurement
  3. Deliverables
  4. Construction
A tanker passes through a Panama Canal lock behind a tugboat.

Panama Canal Authority · Facilities Consolidation

From contract requirements to an operational information management architecture.

The work brings together BIM requirements, deliverable oversight, strategic assessment, workshops, and the architecture needed to connect processes, information exchange, review, and traceability.

  1. Contract
  2. Processes
  3. CDE
  4. Review
  5. Decision

Before procurement or with production already underway, the principle is the same: connect what the project requires with the information it needs to use.

First, we define what the information needs to solve.Then, how to solve it.

Methodology and technology are selected based on the project’s needs, stage, and environment.

ARCO integrates information requirements, responsibilities, production and exchange processes, review criteria, and tools into an information management architecture that fits the project.

  • Information Requirements
  • EIR
  • BIM
  • ISO 19650
  • CDE
  • BEP
  • Responsibility Matrices
  • Statuses + Metadata
  • Review Workflows
  • Traceability
  • Asset Information

Every tool has its place within a way of working designed for the project.

One need may call for more than one pathway.

Wherever you come in, we connect the missing steps.

You don’t have to transform everything to get started.

ARCO 30·60·90

A way of working to focus on one need, apply a solution to a real case, and decide how to move forward based on evidence.

Before we meet, pinpoint where your project stands.

Answer a few questions about your project’s stage, the information that already exists, and what you need to solve.

The BIM Brief will help you spot potential information management gaps and give us the context we need to start the conversation from your project.

Build My BIM Brief
A man in a suit carrying a briefcase walks through a concrete lobby past a red opening.

Let’s start from your project.

An initial conversation to understand the context, learn your starting point, and identify where ARCO could add value.

If you’ve completed the BIM Brief, we’ll use that information as the starting point for our conversation.

Request a Discovery Session

Information connected throughout the project.

From what is required to what is produced, delivered, reviewed, used, and transferred.

Wherever you come in, we connect the missing steps.

Build My BIM BriefRequest a Discovery Session