Baseline Scope and Schedule
The planned installation window, system configuration, work scope, and labor assumptions were placed against the field reality.
All case studies
Documented project | 581 Higuera | Automated Parking | Field Execution
Closing the Gap Between Design Intent and Field Execution
A three-system automated parking installation with 64 spaces looked ready on paper. Sustainable Gaps founder Erik Herring turned the staging, power, slab-tolerance, trade-access, and documentation issues found in the field into one usable project record that supported a change-order and payment-request package and future project budgeting.
- Recovery target
- May 15 → June 2
- Delay documented
- 424 hours
- Closeout
- End of June 2025
- Largest blocked-access category
- 28 workdays
June 2 was the recovery-planning target, not the final completion date. Principal installation work closed out by the end of June 2025, with testing and general-contractor change work remaining.
The delay matrix documents one total: 424 hours across three installation systems. The public case study does not convert that total into a separate day-based claim.
The project closed out by the end of June — the bulk of the contractor's work complete, with testing and change orders from the main general contractor the remaining items.
Scaffolding and elevator-trade access conflicts blocked key work areas for Systems 2 and 3 and became the largest single schedule pressure.
Deliverables
What the work produced.
Material and Component Inventory
The record clarified the real complexity of the system: structural, hydraulic, electrical, platform, chain, panel, and specialty components.
Delay Matrix
Site-readiness and access events were tied to cause, effect, and schedule consequence.
Recovery Schedule
A revised work path showed how the team could move from disruption to a practical recovery target.
Labor and Budget View
Hours, burn rate, blocked access, and productivity exposure were connected to the field conditions that created the impact.
Lessons-Learned Model
The case produced a repeatable planning model: readiness checks, storage requirements, trade coordination, power planning, and documentation discipline.
Results and lessons
What the available record supports.
- The project history moved from scattered field events to a clear cause-and-effect record.
- Field readiness, trade sequencing, and infrastructure planning became visible planning requirements instead of after-the-fact explanations.
- The team gained a practical model for documenting schedule impact, labor exposure, and recovery planning.
- Future installations gained a clearer basis for site-readiness checks, trade coordination, power planning, and documentation.
The record in practice
A representative view of the project record
The record connected each field condition to its effect on the work, the documented impact, and the response. This is the level of structure leadership could review instead of reconstructing events from memory.
- Condition
- Trade access
- Effect on the work
- Systems 2 and 3 could not advance as planned.
- Documented impact
- 28 workdays
- Response
- The blocked work was re-sequenced in the six-worker recovery plan.
- Condition
- Combined field constraints
- Effect on the work
- Staging, water, slab, power, and access interrupted the planned installation sequence.
- Documented impact
- 424 hours
- Response
- Each event was tied to its date, cause, and schedule effect.
- Condition
- Labor exposure
- Effect on the work
- The original labor allocation no longer reflected field reality.
- Documented impact
- 2,520 -> 4,740 hours
- Response
- The baseline was compared with the actual and projected labor picture.
This reconstruction uses figures supported by the project file. Correspondence, photographs, commercial terms, and named-party details remain in the project record.
The challenge
What made the work difficult.
The schedule said the project was ready. The field showed otherwise. The project record separated actual constraints from general updates so the team could see what happened, when it happened, why it mattered, and which decision had to come next.
The schedule said go. The field was not ready.
Automated parking systems do not succeed through equipment delivery alone. They depend on accurate concrete conditions, protected staging, utility readiness, clean trade sequencing, and access to confined installation zones.
At Higuera, those assumptions broke down in the field. The team faced an unprepared laydown area, water intrusion, slab tolerance concerns, delayed three-phase power, trailer relocation, equipment movement outside the planned staging sequence, and blocked access to Systems 2 and 3.
The issue was not effort. It was cause and effect.
Each condition created a different impact. Poor staging became material-handling delay. Water exposure became equipment preservation work. Slab tolerance became engineering review. Power limits became temporary infrastructure work. Trade overlap became blocked access.
Erik turned those conditions into a structured record instead of leaving them as memory or scattered updates.
The field record became the operating truth.
The work was organized around baseline scope, physical constraints, dated disruption events, schedule impact, labor exposure, visual documentation, and recovery planning.
The result was a project record leaders could review: a clear explanation of how design intent met field execution and which corrections were required.
The record outlived the installation.
Erik was brought in during December 2024 for an awarded project scheduled to mobilize in early January 2025. The field process, travel plan, lodging, per diem, and contingency approach were built inside that short preparation window.
Three months of on-site work produced a systematic record connecting each material condition to its cause, date, and effect. By the end of June, the contractor's principal installation work was complete, with final testing and general-contractor change work remaining.
The record remained useful after the installation. The contractor used the captured data to prepare a change-order and payment-request package and establish a budgeting basis for future parking-system projects.
The dates, events, and figures shown in this animated timeline are drawn from the project record.
The approach
What was done next.
- 01
Stand up the mobilization
Lodging, per diem, travel, and contingency plans were built for a crew that had never worked outside its commuting area — before the first system could be set.
- 02
Establish the baseline
The review started with the contract/SOW, planned schedule, system layout, inventory, installation scope, and the intended January-to-May delivery window.
- 03
Validate the physical scope
The true work included three system layouts, platform assembly, drive-over plates, frame disconnects, hydraulic parts, electrical components, chains, structural reinforcements, and specialty hardware.
- 04
Track disruption by cause and effect
Field events were separated by date, cause, work impact, and measurable effect instead of being treated as a general delay story.
- 05
Build the recovery view
The six-worker recovery plan used two 3-worker crews, Monday through Thursday 10-hour days, and alternating overtime Fridays. It connected access, power, staging, trade conflicts, labor exposure, and handover planning in one reviewable sequence.
Find the gap. Build the fix.
Could this experience help clarify a current situation?
Share one recent example from your organization. SG will determine which parts of this experience are relevant and explain whether an evaluation would be useful.