Current conditions / decision baselineBASELINE 03

A current record of what exists, organized for what happens next.

The deliverable should answer a defined question about the site. Capturing everything without deciding how the information will be used creates a large file, but not necessarily a useful baseline.

DIRECT
ANSWER

What does this service do?

Existing-condition documentation creates a current, reviewable record of visible physical conditions before design, renovation, retrofit, fabrication, or facility work. The record may combine registered point clouds, imagery, drawings, models, or viewer access according to the project need.

USE / FIT

Start with the project condition

When this workflow earns its place.

Match the method to the uncertainty or decision it must resolve. Equipment and output follow from that use.

01

Adaptive reuse

Record structure, circulation, envelope, and selected systems before a new program is developed.

02

Tenant or floor renovation

Give teams a shared current reference where legacy backgrounds no longer match field conditions.

03

Equipment replacement

Preserve tie-ins, service zones, access paths, supports, and surrounding constraints.

04

Facility record

Capture a defined area or system so future planning does not begin from scattered field notes.

Before productionSCOPE INPUTS

Four decisions that keep the data useful.

01Baseline purpose
Design, demolition, coordination, facilities, fit-up, documentation, or another use.
02Included conditions
Architectural, structural, MEP, equipment, civil, envelope, or selected interfaces.
03Record form
Point cloud, viewer, 2D drawings, BIM model, photographs, or a combined package.
04Review need
Who will use the record, in which software, and which conditions are decision-critical?

Controlled sequenceBASELINE 03

From requirement to reviewed handoff.

  1. 01

    Frame the baseline

    Identify the decisions the record must support and the date/site conditions it represents.

  2. 02

    Map coverage

    Translate included areas and interfaces into a capture and access plan.

  3. 03

    Document

    Capture visible spatial conditions and agreed contextual imagery.

  4. 04

    Assemble

    Register, organize, name, and segment data for practical navigation.

  5. 05

    Derive

    Create selected drawings or models only when included in scope.

  6. 06

    Qualify

    Record exclusions, inaccessible zones, concealed conditions, date, coordinates, and appropriate use.

Project-definedOUTPUTS

Files are selected for the receiving workflow.

No format or derived deliverable is automatic. The project scope confirms coordinates, detail, organization, software version, and the intended use.

01

Spatial baseline

A registered point cloud representing the visible conditions captured on the field date.

02

Existing-condition drawings

Agreed plans, sections, elevations, reflected ceiling information, or details.

03

Existing-condition model

Selected architectural, structural, MEP, or equipment geometry under a defined model scope.

04

Remote review

Panoramic or viewer-ready context when the project needs visual site access.

QA / REVIEW

A baseline needs a date, scope, and boundary.

Useful documentation states when capture occurred, what was included, what was inaccessible or concealed, how the data is coordinated, and which derived outputs were produced. That context prevents a future team from treating the package as more complete than it is.

Scope boundariesREAD BEFORE USE

What the workflow does not automatically establish.

  • Conditions may change after the capture date.
  • Access restrictions and line of sight can leave documented gaps.
  • Drawings and models are interpretations of the agreed data and scope, not automatic scan exports.
  • Verification of materials, hidden construction, code compliance, or legal status requires separate work.

Technical answersFAQ

Questions project teams ask before they commit.

When should an existing building be scanned?

Scan before consequential design or fabrication decisions, while needed areas are accessible, and early enough for the project team to review the data before commitments are made.

Is existing-condition documentation the same as as-built drawings?

The terms overlap in practice, but they should not be treated as universal. Define whether the need is a captured point cloud, measured drawing set, model, record of installed work, or another deliverable.

Can occupied spaces be scanned?

Often yes, with a plan for access, privacy, moving people, reflective or temporary objects, and the operating schedule. Site-specific rules must be confirmed.

How often should a facility be rescanned?

Rescan when the decision value of a current baseline exceeds the cost of relying on an obsolete one, such as after major modifications or before a new capital project.

Next coordinatePROJECT / SCOPE

Define the site. Define the output. Then plan the capture.

Tell us what your team needs to decide, the conditions you need documented, and the software the information must enter.