Build Pearls logo

Supplemental review page for Suffolk BOOST 7.

From Lessons Learned to Risks Prevented.

This page shows how Build Pearls turns field experience into structured Pearls that can be searched today and eventually surfaced from project schedules and workflows before the same mistake is repeated.

Why this matters

Construction judgment is still trapped in conversations.

Construction teams do not need another place to store generic advice. They need hard-earned judgment surfaced at the moment a similar decision, risk, or coordination problem appears on another project.

Experienced construction judgment is often trapped in individual people, trailer conversations, and lessons learned after mistakes. Build Pearls captures that judgment and structures it into reusable lessons: failure mode, root cause, consequence, preventive action, best user, and best workflow moment.

Workflow Integration

The long-term vision: Pearls surfaced inside the construction workflow

Today, Build Pearls lets users search structured expert lessons. The long-term product direction is to surface those Pearls directly inside the workflows where construction teams already work, prompted by project context and live schedule.

This is the distinction that matters for Suffolk BOOST: the archive is the starting point, but the product vision is a workflow-aware knowledge layer.

Concept MockupTap to expand
Concept mockup: a schedule-triggered Build Pearls alert appears on a project home page before a high-risk activity begins.
Concept MockupTap to expand
Concept mockup: clicking the alert opens the relevant Pearl, recommended actions, risk context, responsible workflow moment, and review status.

Conceptual workflow mockups only. Build Pearls is not affiliated with, endorsed by, sponsored by, or officially integrated with Procore or any other third-party construction management platform.

Workflow validation

"That's true value, then, because now you don't wait until you have a problem or look for it. This has given you a flag when you need it"

Joe O'Farrell

Construction Executive

Dana Farber Cancer Institute

His feedback reinforces the same point: Build Pearls is strongest when it turns past project experience into timely, usable guidance for active project teams.

Real Pearl Example

Brian Hayes' data-center commissioning Pearl.

Presented here as structured construction judgment, not raw transcript text.

data centercommissioningenergizationshort-circuit coordinationMEP

Short-circuit coordination before energization

Contributor / Role

Brian Hayes / MEP Coordinator & Commissioning Lead, JT Magen - Silicon Valley data center projects

Project Type

Data center

Workflow Moment

Commissioning / energization / short-circuit coordination

Quality Score

91/100

Failure Mode

On a mission-critical data-center project, a short-circuit coordination study relied on assumptions that did not match the final field condition.

Consequence

Late-stage rework risk, delay exposure, and avoidable uncertainty around the energization sequence.

Preventive Action

Force early alignment between the latest single-line, equipment submittals, KAIC ratings, protection settings, and commissioning/energization planning before the project reaches the late commissioning window.

Best User

Commissioning lead / electrical PM / MEP coordinator

Best Workflow Moment

Pre-energization readiness review

Root Cause Chain

The single-line information, late design changes, submittal information, and protection strategy were not fully aligned before energization planning.

Why this Pearl matters

This example shows the wedge clearly: repeatable, expensive data-center coordination risks can be captured as structured judgment and surfaced before the same late-stage issue repeats.

Why data centers first

A focused wedge where lessons repeat and mistakes are costly.

Repeatable risks across portfolios.

MEP-heavy coordination and handoffs.

Commissioning-heavy closeout pressure.

Expensive mistakes and late rework.

High schedule pressure around energization.

Transferable lessons for owner/operators and GCs.

Owner-side validation

"I can tell you right now, Jack, I see a benefit.... You're really onto something here."

Joe O'Farrell

Construction Executive

Dana Farber Cancer Institute

This feedback matters because Joe is not merely validating a generic lessons-learned database. As an owner-side leader on a $1.7 billion Cancer Institute project, he is responding to the core Build Pearls workflow thesis: hard-earned field experience becomes more valuable when it surfaces at the moment a project team is about to face a similar risk.

Live Archive Signal

The archive is already becoming structured construction memory.

These metrics are derived from the same Firestore archive records and quality-scoring logic used by the internal archive review queue.

17

Interviews

11

Pearls created

1

High-value Pearls

11

Roles represented

Counts update as archive records grow. Where a field is not available in the data model, the page avoids fake precision.

Suffolk BOOST Fit

What Suffolk BOOST would help validate

BOOST would help Build Pearls move from early validation to a focused pilot: capturing high-quality Pearls from credible experts in a repeatable project type, structuring those lessons, and testing whether they can be surfaced at the right workflow moments for construction teams.

Validate the first focused workflow: data-center commissioning, MEP coordination, energization, closeout, or another repeatable high-risk phase.

Recruit a small panel of credible construction experts.

Generate a high-quality Pearl database from real experience.

Test which workflow moments create the most value.

Determine whether owner/operators or GCs would sponsor a pilot.

Early Validation Stage

Prove expert judgment can surface before repeat mistakes happen.

Build Pearls is currently in the early validation stage. The goal is to prove that expert construction judgment can be captured, structured, quality-scored, and eventually surfaced inside the workflows where repeat mistakes happen.