Skip to main content
In active development

Lumetra for Building Condition Assessment

Connect BCA scope, evidence, findings, review and capital planning.

Lumetra structures the Building Condition Assessment lifecycle so project teams can develop reviewed records and client outputs without separating the evidence from the decision trail.

Scope and hierarchy

Define the assessment before field work begins.

Projects start with buildings, systems, components, scope inclusions and required outputs configured to the engagement.

Building hierarchy

Buildings, systems and components are organized so every later observation and finding can be traced back to the place it belongs.

Configurable methodology

Use an ASTM/Uniformat-informed structure where reviewed and configured for the engagement. Taxonomies, rating scales and required fields are set before capture starts, not reconstructed during reporting.

Field evidence

Capture observations where they belong.

Each observation is connected to a location, component, photograph, note, author and status so evidence stays in context.

Linked media

Photographs, markups and notes are attached to the observation record and referenced from the related finding.

Authored records

Every observation carries author, timestamp and status so the field record can be reviewed against the approved method.

Status visibility

Draft, complete, flagged and confirmed states help teams see what still needs attention before findings are written.

Findings

Connect evidence to condition, priority and recommendations.

Findings carry condition, deficiency, priority, recommendation, timing and cost fields with visible authorship.

Structured finding fields

Condition rating, deficiency description, priority, recommendation, timing and cost assumptions are stored as structured data so reports can be assembled consistently.

Professional authorship

Each finding shows the author who created it and the reviewer who approved it, with revision history preserved for later review.

Review and QA

Distinguish working records from released outputs.

Review is recorded as assignment, questions, revision and approval states before any information is released.

Assignment

Review tasks are assigned with scope and criteria so reviewers know what to validate.

Questions and revision

Reviewers can raise questions, request revisions and track responses before approving a record for release.

Release control

Working drafts remain separate from released outputs. Release is a deliberate workflow step, not a default state.

Report and delivery

Assemble approved records into controlled outputs.

Reports are composed from approved findings and records, then issued through a controlled release step.

Lumetra helps teams produce consistent report sections, tables and client-facing summaries from the same governed record. It does not claim automatic completeness: the quality of the output depends on the quality of the approved inputs and the review performed by the responsible team.

Capital planning

Connect approved findings to longer-term planning.

When a workflow supports it, approved findings can feed timing, cost and scenario assumptions for capital planning.

BCA findings can carry cost and timing assumptions that inform planning conversations. The goal is to preserve the link between the original evidence, the finding and the planning assumption so the decision trail remains intact.

A separate Reserve Fund / Capital Planning module remains On the roadmap. It is intended to connect approved condition, timing and cost assumptions to long-term planning scenarios.

Implementation

Fit Lumetra to the way your practice works.

Building Condition Assessment is supported by two Orbis Structus service programs.

Deploy

Configure Lumetra around your BCA method, templates and review workflow. Deployment is shaped to your existing process, not a forced replacement of it.

Explore Deploy

Atlas

Structure building data, taxonomies and portfolio context so Lumetra has a reliable foundation for hierarchy, comparison and reporting.

Explore Atlas

Product demonstration

How one fictional BCA project moves through Lumetra.

Six moments from scope to released output. Every frame is fictional demonstration data.

Project and structured scopeFictional demonstration data
Scope, buildings, systems and required outputs are organized before field work begins.
Field observation with linked evidenceFictional demonstration data
Each observation carries location, component, author, date and linked evidence.
Structured findingFictional demonstration data
Evidence is connected to condition, deficiency, priority and recommendations.
Professional review stateFictional demonstration data
Reviewers see evidence, reasoning and revision history before approving release.
Report previewFictional demonstration data
Approved records are assembled into module-specific reports before release.
Client-facing released outputFictional demonstration data
Released outputs present controlled information to clients without exposing draft context.
Capital-planning directionFictional demonstration data
Illustrative direction for a future planning view. Not a statement of current availability.

Show us how your BCA workflow runs today.

We will map your stages, roles and deliverables to Lumetra's structure and identify where the evidence trail can be strengthened.