For 10 years as a construction engineer, I would plan any package of work like this…

1. Lay out a structure

Break down the scope into logical chunks. Usually, these are physical components (Pile cap, headstock, bridge deck etc.). But not always.

However YOU think about the scope is best for the rest of the steps to flow.

Planners would call this the WBS, but who needs the jargon. 

2. List the tasks

Virtually build the components in your mind and just list the steps. Don’t worry about relationships, durations, calendars or anything else - it will only break your flow. Get the steps down in order.

3. Add relationships

Link together the tasks to make sequences. Focus on physical constraints (what planners would call “hard logic”) rather than sequences of crews or equipment.

For example, the road surface needs to be done between the line marking… that kinda stuff.

4. Estimate durations

Give your best guesstimate of durations for all the tasks. It’ll be wrong approximately 100% of the time, but you need to start somewhere. If you are completely at a loss, grab a foreman or site supervisor, they love estimating durations 😉

5. Add constrained resources

Don’t bother adding every resource each task needs (you don’t have the time). But, most engineers know if their project has a limited concrete supply, struggles to get enough electricians or has space constraints on site.

Add this information to your tasks and check for conflicts.

6. Verify durations and optimise the sequence.

Ok, now you need help. 

Get the most experienced people in your team together (sure, get your manager but supervisors and leading hands are better) and walk through the sequences. 

Ask for validation of durations and search for ways to pull things forward. This will usually kick off a discussion about crew sizes and their flow.

Add this to your plan as you update the durations.

Ps. This resource step is super easy if you are doing this in Aphex.

7. Prepare the plan for communication.

You have a plan that the right people are bought into. Now, you need everyone to understand it.

If you have subcontracted teams, assign them.

If you need a QA inspector, assign them.

If you need… you get it.

8. Communicate, communicate, communicate.

Host a briefing session to run through the plan, recap short-term sequences at pre-start meetings, consistently update the plan and reissue it to everyone.

Keep repeating the plans until you are sick of hearing your own voice.

For over a decade, I found this was the fastest way to build a workable plan. 

It works in Aphex, in a spreadsheet, on on a whiteboard, or using slate and chalk for that matter.