Adaptive reuse
Record structure, circulation, envelope, and selected systems before a new program is developed.
Current conditions / decision baselineBASELINE 03
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
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
Match the method to the uncertainty or decision it must resolve. Equipment and output follow from that use.
Record structure, circulation, envelope, and selected systems before a new program is developed.
Give teams a shared current reference where legacy backgrounds no longer match field conditions.
Preserve tie-ins, service zones, access paths, supports, and surrounding constraints.
Capture a defined area or system so future planning does not begin from scattered field notes.
Before productionSCOPE INPUTS
Controlled sequenceBASELINE 03
Identify the decisions the record must support and the date/site conditions it represents.
Translate included areas and interfaces into a capture and access plan.
Capture visible spatial conditions and agreed contextual imagery.
Register, organize, name, and segment data for practical navigation.
Create selected drawings or models only when included in scope.
Record exclusions, inaccessible zones, concealed conditions, date, coordinates, and appropriate use.
Project-definedOUTPUTS
No format or derived deliverable is automatic. The project scope confirms coordinates, detail, organization, software version, and the intended use.
A registered point cloud representing the visible conditions captured on the field date.
Agreed plans, sections, elevations, reflected ceiling information, or details.
Selected architectural, structural, MEP, or equipment geometry under a defined model scope.
Panoramic or viewer-ready context when the project needs visual site access.
QA / REVIEW
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
Technical answersFAQ
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.
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.
Often yes, with a plan for access, privacy, moving people, reflective or temporary objects, and the operating schedule. Site-specific rules must be confirmed.
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
Tell us what your team needs to decide, the conditions you need documented, and the software the information must enter.