SheetC-01
FieldCONSTRUCTION
StatusCURRENT
Version03
Your project history is your prequalification.
Every prequal, bid-day package, change order narrative, and closeout turnover draws on the same body of knowledge, and is rewritten from scratch each time. That knowledge already exists: in Procore or Autodesk Build, in Bluebeam markups, in coordination models and spool history, in the accounting system, and in the people who ran the job.
The information exists. What is missing is a decision about which version is authoritative, who owns it, and what may be reused without asking. Design-build, design-assist, and hard-bid work describes itself differently every time, in offices that do not share what they learn.
C-01 · S00Approved company knowledge
Built in week two
APPROVED COMPANY KNOWLEDGE LAYERK01
Company
Capabilities and approved overview
People
Current roles and expertise
Prior work
Examples, outcomes, evidence
Standards
Policies, procedures, controls
Brand
Voice, terminology, templates
Context
Client history and known constraints
Everything downstream starts from the same approved record. Once those facts are settled and kept current, the downstream work stops starting from zero.
C-01 · S01Prequalification response / general contractor package
Sequential against structured
The same prequal, drawn as a schedule.
SequentialEach step waits on the one before it
Work itemD01D02D03D04
D05D06D07D08D09D10
D11D12
Unstructured — sequential, dependent on who is available
Structured — drawn from prepared knowledge
Vertical rule = human review
Both paths end at the same submission and the same reviewer. The searching, verifying, and deciding happened once, in advance, and was written down. Measured before and after time comes in week four, from the workflows built during the engagement.
C-01 · S02Offices that do not share what they learn
Multi-location
Every office writes the same paragraph differently.
The same capability, the same market, the same system type — described four ways because
four people wrote it from memory in four buildings.
Precedent does not travel.
What the crew learned on a lab fit-out in one region sits with a person, and that person is on a job. The estimator pricing a similar one in another office starts over.
The fabrication record is the deepest asset and the least indexed.
Spool history, coordination decisions, and what prefab actually cost are the strongest evidence a
self-performing contractor has. Almost none of it reaches a proposal.
One record, read by every office.
The structure built in week two is shared. The workflows built on top of it produce the same answer
in every location, which is the point.
C-01 · S02bBridging Preconstruction and the Field
From the spec to the checklist
The Field Bottleneck.
A superintendent manually parsing a 1,200-page job specification file to build localized installation checklists.
The Operational Danger.
Misinterpreted pressure parameters, missed valve log criteria, or using obsolete revision codes.
The System Solution.
The system processes active engineering documents inside your environment to automatically generate structured field checklists (e.g., piping pressure test charts) tailored to local project variables. Preconstruction data feeds the field without a manual data entry loop.
C-01 · S03Applied workflows
Built during the engagement
What gets built, and where human review stays.
WorkflowInputApproved source
OutputReview
PrequalificationBusiness development
GC prequal form or RFQMarket, system type, project size
Project record and personnelComparable installs, current resumes, safety record
Completed responseApproved capability language
RequiredCase studyMarketing
Substantial completionOne project record
Project record and brand standardsOne set of numbers
Study, page, postsConsistent across all three
RequiredChange order narrativeProject management
Scope change or field conditionRFI, directive, or coordination conflict
Contract, model, and field recordWhat was bid, what was coordinated, what changed
Justification packageTraceable to the contract documents
PM sign-offCloseout turnoverProject management
Substantial completionSubmittals, warranties, as-builts
Submittal and equipment recordApproved products, serial data, service terms
O&M packageIn the owner's required format
RequiredPortfolio structuringFoundational
Two decades of workDrives, Procore, marketing
—This workflow creates the source
One authoritative recordEvery other workflow reads it
LeadershipC-01 · S04Where this applies
Surface area, not savings
Eighteen places the same problem repeats.
Every one of these is the same operating pattern: work that recurs, depends on knowledge the company already holds, and currently starts from zero. Marked items are where a four-week pilot typically starts — highest frequency, clearest source, and a reviewer already in place.
PreconstructionEstimating & budgeting
Comparable install precedent
Scope gap and exclusion review
Budget narrative and assumptions
Business developmentPrequalification
GC prequal responses
Bid-day qualification letters
Owner and CM relationship history
Virtual design & fabCoordination
Prefab and modular precedent
Coordination issue history
Shop drawing standards
Project managementDelivery
Change order narrative
RFI drafting and tracking
Submittal review preparation
Safety & qualityCompliance
Incident and observation summaries
Toolbox talk preparation
Lessons learned capture
Closeout & serviceTurnover
O&M and warranty assembly
As-built and equipment record
Service handover to maintenance
Typical first pilot scope
Reached as the structure extends
Departments vary. The pattern does not.
Your project history is already an asset.
Ten questions, about three minutes, and a straight answer on what to fix first.
Contact
nate@heilmanops.com
Hopkinton, Massachusetts