Planning the concrete floor cycle: form, pour, strip and reshore on a loop you can prove
The second floor is promised on the same cycle as the first. The formwork foreman has crane bookings that overlap another crew, and a release decision has not been confirmed. The schedule shows a loop, but the people delivering it have not tested all of its conditions.
Build the concrete floor-cycle plan with the formwork, reinforcement, concrete and coordination leads using the project’s approved methods and release requirements. Put preparation, inspections, lifting demands and engineering decisions into the sequence alongside the physical work. This is a planning exercise, not a stripping or reshoring procedure. Never turn a previous job’s elapsed days into permission to remove support on this one.
Test the whole loop before repeating it
- Collect the governing inputs. Identify the current structural information, approved formwork and reshoring arrangements, relevant specifications and the people authorized to confirm releases. Keep unresolved technical questions visible for those people.
- Map the work and checks. Have the responsible leads show layout, vertical work, deck preparation, reinforcement, embeds, required checks and placement in their actual sequence. Include each dependency rather than copying a generic activity list as a method.
- Separate time estimates from release conditions. Show forecast durations as planning assumptions and technical release criteria as conditions requiring confirmation. A planned date cannot certify that a condition has been met.
- Test crew and lifting demand together. Compare proposed crew use and crane requests across the activities that overlap. Confirm access and the booking process with the responsible leads; a crew plan that assumes the same unavailable hook time is not coordinated.
- Allow for preparation and response. Name who obtains the required inspections, information and material commitments. Put their notice and preparation actions before the work, with a route for rescheduling when a condition remains open.
- Learn from the first floors. Record actual starts, finishes, waiting reasons and release references. Review the loop with the leads before relying on it for later floors, preserving the technical controls when the planning pace changes.
Common mistakes
- Copying release periods from another building.
- Leaving inspections outside the cycle while assuming they happen on demand.
- Compressing the loop by deleting a required check instead of resolving its dependency.
Checklist
Before accepting the repeating cycle
- Governing technical information is identified.
- Every required release has a responsible confirmer.
- Crew and lifting demands have been coordinated.
- Notice and preparation actions have owners.
- First-floor observations will test the assumptions.
Check your understanding
The programme reaches the planned support-removal date, but the authorized release is missing. Does the programme allow work to proceed?
