A schedule can become more detailed and less truthful at the same time. Concrete foundations make the problem tangible: formwork, rebar, pour and strip are real tasks, but their changing overlaps do not always translate into dependable CPM logic.
“FRPS foundations” often represents a package of five to ten foundations, not one isolated object. Formwork and reinforcement crews move through zones, sometimes working alongside each other. One foundation may be poured while another is being reinforced and a third is being stripped.
Start with the overall plan: one resource-loaded FRPS bar, site access driving commencement, and a completion milestone tied to the next handover. The estimate’s quantities and labour-hours support its duration. Then break that package down outside CPM for daily field coordination, retaining the freedom to change foundation order without rebuilding the overall schedule.
Replacing that package with a neat chain of Formwork → Rebar → Pour → Strip can impose a sequence the field never intended. Replacing it with dozens of links and lags can impose precision the team cannot sustain. The challenge is not finding more tasks; it is finding the right boundary for a reliable dependency.
CPM can model overlap. The issue is not a mathematical inability to schedule foundations. It is whether the chosen activities, relationships, calendars and resource assumptions represent the execution method — and whether the organisation can keep that model current.
Ten foundations are one defined FRPS work package in the overall CPM schedule. Site access releases its start; its completion milestone releases the downstream scope. Daily crew moves stay inside that boundary.
The estimate provides the labour-hours and quantities; the assumed crew and productivity turn that effort into a duration: 4,480 ÷ (20 × 8) = 28 working days. This is an illustrative capacity check, not automatic CPM duration calculation. Validate crew mix, productive hours, calendars, overlaps, curing and inspection gates against the execution plan. Concrete volume alone does not represent all FRPS effort.
Break the package down for foremen and site engineers to coordinate daily crews, form sets, inspections, pumps and concrete deliveries. These short tasks are Level 5 progress and field-planning detail — not forty mandatory activities in the Level 3 network.
F01 → F10 is a convenient initial order, not necessarily a physical dependency. Move to a ready workface when access, materials or a pour slot change, without rebuilding the master schedule’s internal logic. This illustration swaps workface order while retaining the same capacity and package window; real resequencing must still respect readiness, safety and shared resources.
Keep the Level 3 start and finish interfaces stable while local choices remain inside them. If resequencing changes an external handover, available capacity or the package finish, feed that consequence back into CPM. A foundation with an independently significant release may deserve its own interface rather than being hidden in one bar.
Retain F01–F10 and their trade tasks against one stable Level 3 activity ID. Daily records capture quantities, actual hours, completed steps, remaining constraints and alternate workfaces. At each weekly / monthly data date, reconcile that evidence into the package’s progress and remaining-duration forecast — not a new network for every crew move.
| Day 12 field evidence | Level 3 update |
|---|---|
| 224 of 560 m³ placed; trade-level progress records retained. | 40% concrete quantity progress; assess overall FRPS progress with estimate-based trade weights, not pour volume alone. |
| For this example, verified weighted FRPS progress is also 40%; 1,900 actual labour-hours recorded. | 1,792 earned hours (40% × 4,480), distinct from the 1,900 hours spent. Investigate productivity and forecast hours to complete. |
| Assume 2,688 forecast hours remaining and 160 productive labour-hours/day available. | About 17 working days remaining: forecast finish near day 29 versus day 28 planned, subject to release gates and current productivity. |
| Local resequencing and missed pour slots logged against foundation IDs. | Retain the package activity and baseline; update actual start, progress, remaining duration and affected completion / handover forecast. |
The master schedule keeps one meaningful bar; the field retains the detail needed to deliver it. Monthly reporting reconciles the same records, rather than replacing weekly evidence. Neither hours spent nor concrete poured alone proves that the package is ready for handover.
Building a fully detailed CPM schedule is possible. The difficulty is maintaining dependable logic for 1–2 day tasks when the preferred foundation order changes daily. Compare the following trade-level abstractions with the field micro-plan above.
Splitting FRPS into four bars and linking them finish-to-start implies that all formwork must finish before any rebar starts. That may be true for a particular foundation or method — but is often false for a package with several workfaces. The gap before stripping represents an assumed curing / strength-release interval.
Here, rebar starts in a released zone while formwork continues elsewhere. The pour still waits for the relevant formwork, reinforcement and inspection release. Start-to-start and finish-to-finish relationships can represent genuine overlap, but a fixed two-day lag is not evidence that the next workface will actually be ready.
All diagrams, quantities, hours and progress figures are illustrative teaching examples, not project estimates or construction instructions. The micro-plan is not a resource-levelled or calculated CPM forecast. Durations, overlaps and cure intervals depend on design, temporary works, safe access, inspection requirements and verified concrete strength. FRPS excludes other gates such as excavation acceptance and later equipment-load release unless explicitly included in the package basis.
Finishing all formwork in Area A may not be necessary to start reinforcement on F01. Equally, starting formwork somewhere does not mean every reinforcement crew has access. Define the physical release, not merely a percentage complete.
An SS + 2 days relationship may approximate a stable production flow. It breaks down when access, crew size or quantities change. Where an inspection or release genuinely drives another party, model that gate explicitly rather than hiding it inside a lag.
Two foundations may be physically independent yet share a crane, form set, pump or crew. CPM dates alone do not guarantee capacity. Resource loading, levelling and short-interval coordination answer different questions; their assumptions must reconcile.
If reinforcement starts before the model says it can, out-of-sequence progress forces a scheduling choice. Retained-logic and progress-override settings can produce different forecasts. Investigate the actual workface sequence and record the decision, rather than changing settings to obtain an attractive date.
Booking concrete, sequencing trucks, reserving the pump, checking access, lining up inspections and agreeing the pour crew’s shift are not optional because they sit outside the master schedule. They are the micro-plan that makes its forecast possible. A booked truck is a commitment; it is not proof that a foundation is ready.
| Planning layer | What it owns | Connection back |
|---|---|---|
| CPM control schedule | Released drawings, excavation readiness, FRPS by meaningful area / package, strength release and downstream handovers. | Named owner, scope boundary, quantity basis, credible forecast and explicit external dependencies. |
| Look-ahead / make-ready plan | Foundation-specific constraints, materials, crews, temporary works, permits, inspections and plant availability. | Each workface maps to its parent activity; unresolved constraints feed the schedule forecast. |
| Daily / weekly commitments | F03 pour window, concrete volume, truck slots, pump position, crew assignments and readiness sign-off. | Actual quantities, dates and reasons for missed commitments feed the look-ahead and periodic CPM update. |
The exchange works in both directions: schedule handover dates set field priorities; field constraints and actual performance challenge those dates. Promote a detail item into the CPM model when it controls a material interface, independent workfront, contractual milestone or consequential forecast — not simply because someone needs to organise it.
A single “FRPS all foundations” bar may hide a late drawing for F04, a cancelled pour or a missing pump. Without workface records, it is difficult to establish what was blocked, what remained available and which downstream handover was actually affected.
A false finish-to-start chain can transmit a local delay through every foundation even when crews could work elsewhere. Stale overlaps, fixed lags and unmaintained crew assumptions can distort float and apparent criticality. More bars are not stronger evidence if their relationships were never real.
Example: F03’s concrete delivery is cancelled on Tuesday. F04 is ready and the crew moves there. Record the lost pour slot, the switch, the resources used and the revised F03 readiness date. A missed task does not automatically delay the project; a task with float can still consume contingency or affect a later interface.
Trace the event through the contemporaneous schedule and field evidence to the affected handover. Consider available workfaces, mitigation, resource limitations and the critical path at that time. Separate disruption / productivity loss from completion delay. Responsibility and entitlement require the contract and a suitable analysis method, not just a red bar.
Do not confuse a task that requires planning with an activity that requires its own place in the CPM network.
The foundation examples above are illustrative synthesis, not prescribed sequences from these publications.
GAO Schedule Assessment Guide — GAO-16-89GComprehensive scope, credible sequencing, realistic resources, durations and maintained schedule logic must be reviewed together.
Lean Construction Institute — Last Planner SystemCollaborative planning, make-ready work and reliable weekly commitments complement the master schedule.
Society of Construction Law — Delay and Disruption ProtocolContemporaneous programmes and records underpin delay and disruption analysis; the protocol is guidance, not a substitute for the contract.