Collaborative Planning Workshops in Construction: How to Build a Programme Everyone Believes In

Long read, September 2026. By Andy Pritchard MCIOB, CIOB Construction Manager of the Year Gold Medal 2019. Every figure sourced inline.

Most construction programmes are written by one person and then defended by everyone else.

A planner or a project manager builds the logic in a back office. It gets issued as a PDF. The trades receive one or two lines of it, the ones with their name on. Nobody in the supply chain can see what moves around them, so nobody can warn you when it will not work. Six weeks in, the sequence has drifted, the programme is a history document, and the job is being run from memory and goodwill.

A collaborative planning workshop fixes that at source. It puts the people who will build the job in one room, in front of the drawings, and has them build the sequence together. The programme that comes out is not a document the project manager owns. It is an agreement the whole team has made.

This guide covers what a collaborative planning workshop is, why the evidence says it matters, who to invite, what to bring, when to hold one, exactly how to run it, and how a large contractor makes it the standard on every job rather than the habit of its best project managers. It draws on the method behind a CIOB Gold Medal project that finished six weeks and one day early after its programme had been judged too tight to sign off.

What a collaborative planning workshop actually is

A collaborative planning workshop is a structured session where the project manager, the designers, the key trade contractors and, where it helps, the customer build or review the construction programme together. Each party sequences its own work, agrees the durations and interfaces with the others, and commits to dates it believes it can hit. The output is a programme the whole team owns.

That definition matters because “collaboration” means different things in different places.

The Supply Chain Sustainability School treats collaboration mainly as a relationship question: moving from adversarial contracting and risk transfer towards cooperative business relationships, with ISO 44001 (published 2017) as the framework for forming and maintaining them. That work is valuable. But a collaborative relationship does not, on its own, produce a programme anyone can build to. You can sign a charter, agree to be open and honest, and still issue a plan that the dryliner has never seen.

At the other end sits the Last Planner System, the formal lean construction method for collaborative production control, with its master schedule, phase or “pull” planning, six-week lookahead, constraint removal, weekly work plans and its core measure, Percent Plan Complete. In the UK, lean collaborative planning also has a CITB short-duration training standard (Lean Construction Module 7, held by the Lean Construction Institute UK), whose learning outcomes end with delegates producing a real collaborative plan for their own project.

A collaborative planning workshop sits between the two. It is the practical event where the relationship becomes a sequence. You do not need to adopt the full Last Planner System to run a good one, and you should not confuse a workshop with the weekly discipline that has to follow it. But without the workshop, there is nothing for the weekly discipline to protect.

Why the lone-planner programme fails

The industry already knows the programme is where jobs go wrong. It just keeps writing programmes the same way.

I have made the long version of this case elsewhere, in Construction’s Biggest Cause of Delay is the One Thing Nobody Teaches and There Are Two Kinds of Planning. Most of Us Were Taught the Wrong One. Here is the short version.

When Cornerstone Projects surveyed industry professionals in 2022, 91% said they had been involved in a delayed project, up from 85% in 2016. The cause ranked top most often was poor original planning or an unrealistic programme, named first by 31.4% of respondents. The long-run UK industry performance series put the share of projects with time overruns at 42.1% on average between 2003 and 2018.

When it goes wrong, it goes to dispute over time. The RIBA and NBS Construction Contracts and Law Report 2022 found extension of time was the most common dispute subject, cited by 50% of those in dispute. The 2024 King’s College London and Adjudication Society report recorded 2,264 adjudication referrals in a single year and found inadequate contract administration to be the most commonly cited cause of disputes, again named by 50% of respondents.

The lean construction research explains the mechanism. The long-cited baseline from Glenn Ballard’s work on the Last Planner System is that on well-managed sites only about 54% of the tasks planned for the following week actually get done that week. A plan that is half-kept is not a plan the trades can organise labour and materials around.

And there is good evidence that working together changes the numbers. In Chile, mean Percent Plan Complete across companies adopting lean and the Last Planner System rose from 50% in 2001 to 76% in 2003 (Alarcón and colleagues, IGLC 2005). Closer to home, the National Audit Office measured public construction before and after the move to partnering, integrated teams and earlier contractor involvement: projects delivered on time rose from 34% in 1999 to 63% by the period April 2003 to December 2004, and projects delivered to budget rose from 25% to 55%.

There is an honest caveat, and it is the most useful finding of all. Research by Daniel and colleagues (Engineering, Construction and Architectural Management, 2017) found that what UK sites call “collaborative planning” often only partly implements the method. Teams hold the lookahead meeting and skip the constraint analysis, the make-ready work and the learning loops that make it work. Alan Wolstenholme’s 2009 review of the Egan agenda found the same pattern at industry scale: the tools worked where they were applied properly, and they did not spread.

The methods are proven. The gap is in how disciplined we are about running them, job by job.

I was the lone planner first

Before I write a word about how to do this properly, I should say that I did it badly for years.

On a £12m primary school in Croydon in 2016, the structural frame package grew from 10 weeks to 22 after a late design change. We had 2 weeks of buffer. That was a 10-week critical path delay. We recovered it with temporary waterproofing on every floor so the internals could start early, and a drylining partner who put up to 60 operatives on the job. We handed over 2 days late and the job made money.

It got called a recovery. It was really a lot of good people working far too hard to make up for a plan that lived in my head. The sequence was lost for the envelope and the internals. The programme was only really understood by the senior team, so the building managers did not have the knowledge of the plan they needed. On handover day we were trying to hand over the whole building at once, and test and commissioning teams damaged around £40,000 of finished work because there were no finished areas in sequence.

Everything in the rest of this guide was built because of that job.

A plan is three sequences that must agree

Most people think “the plan” means the programme. On a well-run job there are three sequences, and a collaborative planning workshop exists to make them agree.

The programme sequence is the order the building goes up.

The procurement sequence is the order packages are designed, bought, approved and delivered, including every contractor-designed portion.

The quality sequence is the order work is inspected, tested, commissioned, signed off and protected.

When any two of them disagree, the job pays. On the Gold Medal job I describe below, envelope completion ran 12 weeks late, mainly because window reveals from a design-and-build package were not delivered on time. The programme and the procurement sequence disagreed, and nobody tracked it tightly enough to see it coming. On the Croydon school, the programme and the quality sequence disagreed, and commissioning teams walked back into finished rooms.

When all three agree, the job runs. Testing and commissioning dates go into the orders before the trades start. Quality checks follow the same room order as the programme. Procurement is planned backwards from the date the programme needs the material on site, not forwards from the date the design happens to be finished.

A single planner in a back office cannot make three sequences agree, because the knowledge of each sits with different people. That is the real reason for the workshop.

Who belongs in the room

The project manager leads the workshop and is accountable for what comes out of it. If there is not enough time, someone else can hold the pen, but the PM still proof-reads it and signs it off. After that, invite as many of the right people as the room can hold. The more people feeding into a programme, the less will be missed.

The customer. How deep the customer goes depends on the relationship and the contract form. As a minimum they should see the parts of the programme where they carry the risk, and anything on or near the critical path. Their decision and approval times are part of the sequence, so they belong in it.

The designers. Architect, structural engineer and M&E designer, reviewing their information required schedules against the survey and each other’s plans, so each RIBA stage or Building Safety Act gateway ends coordinated and complete. For higher-risk buildings, the gateway periods are now among the biggest programme risks on the job, and they need to be planned with the people who produce the information.

The key trades. Treat these as a mandatory minimum: groundworks, frame, roofing and facade, M&E, drylining, carpentry, and demolition where it applies. They agree durations, sequence, access and storage, and the phased logistics plan. Bring in specialist experience early, from RIBA Stage 2 or 3 where you can, and read Building a Supply Chain That Wants to Work With You for why they will turn up. Common sense on a programme is really experience that has not been written down, and your trusted supply chain will often give that advice for free in the early design stages, provided they are not in competitive sales mode.

Your own team. Site managers, building managers and assistants need to be in the room for their areas, because they will run the plan day to day. A programme they watched being built is one they can defend. A programme they were handed is one they will work around.

One practical rule: do not put everyone in the same room for the whole day. Split the workshops by stage.

What to bring

A good workshop is prepared, not improvised. Bring the material the room needs to test the sequence against reality.

• The key drawings and specification, printed large enough to stick on the wall.
• Site conditions and access: surveys, existing records, utilities, boundary and neighbour constraints.
• The interfaces between trades, marked up where you already know them.
• The draft temporary works strategy and drawings.
• The contract and statutory conditions that dictate phasing or fix a timeline: sectional completions, planning conditions, Building Safety Act gateways, possession dates.
• A basic timeline or the key dates that cannot change, and nothing more.

That last point is deliberate. Do not arrive with a finished programme. People defend a finished programme. They improve a draft.

When to hold one: five moments across a job

A collaborative planning workshop is not a single event. The best jobs run them at five moments.

At tender. Even a short session with two or three key trades will expose the durations and interfaces a desk-top tender programme gets wrong. This is where the realistic programme is protected from the fudged one. The hardest and most important discipline in planning is a programme built by experienced people that tells the truth, even when the truth is unpalatable against the customer’s expectation or the business case.

Pre-contract, around RIBA Stage 3 or 4. This is the most valuable workshop on the job. An old hand taught my generation that a month extra pre-contract is worth six months on site, and I have never seen it proved wrong. It is also where you win buffer. On my own jobs I aim to secure 5% of the programme as buffer in preconstruction, 10% if possible, and add more by targeting the trades in the first third of the works.

At start on site. Confirm the sequence with the trades who will actually build it, and the logistics plan with the people who will actually use it. The pre-start meeting sets the behaviours. The planning workshop sets the sequence. Do both.

Through the job, at least quarterly. Bring all key supply chain trades back in to review the programme. Does the sequence still work? What have we learned? What can we improve?

Weekly, in the room. The best practice I know is two weekly collaboration meetings, one for internal trades and one for external trades, with the programme on the screen. Then your own team closes the week, completes the track and uploads it against the baseline. At this point the workshop has become a rhythm.

And one more: when the plan breaks. Almost every good recovery programme I have written was written with the key trades and designers physically in the room. A recovery mandated from the office produces claims. A recovery built in the room produces a plan. The project recovery page sets out how that works when a job is already in delay.

How to run the workshop: six moves

The method is simple. It is also the part most teams skip.

1. Fix what cannot move

Open by putting the fixed points on the wall: start date, completion, sectional dates, gateways, possession and access dates, any customer events that cannot shift. Everything else in the room is up for discussion. These are not.

2. Split the room by stage

Run one, two or three workshops to suit the job: full build, demolition to topping out, groundworks to watertight, then internals. The internals team should not sit for three hours listening to groundworks, and the groundworker has nothing useful to say about ceiling grid. A focused room is an honest room.

3. Put the drawings on the wall

Print the key drawings and stick them up. People plan better standing up, pointing at the building, than sitting down looking at a Gantt chart on a laptop. Mark the zones, the crane, the access routes and the storage areas on the drawings as the conversation goes.

4. Let each trade sequence its own work

Give every trade the post-its and let them lay out their own tasks: their durations, their logic, their access and storage needs. This is the heart of pull planning: work backwards from the milestone, and let each trade say what it needs to be finished before it can start.

5. Keep asking what they need from each other

This is the question that makes the workshop worth holding. “What do you need from each other?” is where the interfaces come out, the missing information appears, the access clashes surface and the realistic durations replace the optimistic ones. Ask it again and again. The answers are the constraints you now have to remove before the work arrives.

6. Type it live and issue it the same day

Best practice is to have the digital programme on a screen, typed up as the meeting progresses, so the team works on the final product live. That needs confidence in live programming, which takes time to build. Until you have it, use post-its and whiteboards, and update and issue the programme immediately after the meeting. If it is not issued the same day, it is not live.

The facilitator’s job is to chair, not to dictate

As a project manager, and later as a head of planning, my role in these rooms was rarely to come up with the ideas. It was to chair the meeting that brought the best out of everyone in it.

That changes how you behave. You ask more than you tell. You protect the quiet trade contractor who has spotted the problem from the loud one who wants their own dates. You react well when someone tells you the sequence will not work, because the moment you shoot the messenger is the moment people stop telling you. And you let the room reach the answer, because a sequence the trades built is one they will defend on site.

Mandating a plan down to the people doing the work does not produce buy-in. It produces claims, because trade contractors then plan only their own one or two lines and cannot see what moves around them. The positive way to avoid disputes is not better drafting after the fact. It is planning the work together so the dispute never forms.

From workshop to weekly rhythm: keeping the plan live

A workshop that produces a good programme and then goes quiet has wasted everyone’s morning. The value comes from keeping the plan live.

Run the programme in the meeting. The weekly supply chain meeting should have the programme on the screen, tracked and re-sequenced as the room talks. A programme updated monthly in a back office is a history document.

Give different people different levels of programme. The project manager owns the contract and delivery programmes for the whole job. Site managers own an area, internals, externals or a set of gridlines, working 6 to 8 weeks ahead. Trainees and assistants own the next 1 to 2 weeks, often as a list rather than a Gantt chart.

Put the programme on every desk. Every person in the project office, whatever the team size, should have their own six-week programme on their desk, refreshed every week. It sounds trivial. It is one of the clearest tests of whether a team is working to one plan.

Communicate in the right form for each audience. Gantt for managers. A lookahead and a list for site managers. Pictures, logistics boards and marked-up drawings for trades, which also cut straight through language barriers. Getting everyone to understand the plan is the talker’s job, not the listener’s.

Measure whether promises are kept. Track the share of committed weekly tasks that are actually completed. If it sits around half, the plan is not yet a plan. Track the reasons tasks were missed, and fix the causes rather than the people.

What it looked like on a Gold Medal job

Woodmansterne School in Streatham, south London, was a £22m secondary school built on a live site next to an operational primary school, with seven sectional completions including demolition, temporary classrooms, games areas and a 7,500m² four-storey concrete-frame block. At substantiation the programme was judged very tight, and a senior manager would not sign it off.

It was handed over 6 weeks and 1 day early. The ground floor was handed over 12 weeks early. It won the CIOB Construction Manager of the Year Gold Medal in 2019 and the national Considerate Constructors Most Considerate Site award for the £10m to £50m category.

The dates on the Gantt chart were not the difference. How many people understood the plan and owned it was.

The strategy was written by the people who had to build it. Before the work started, the team wrote twelve sequence booklets: groundworks, concrete frame, envelope, external wall, windows, parapets, finishing, waterproofing, roof openings, fire compartments, product protection and pattressing. Each booklet had a named owner on the site team and was written with the trades involved. The sequences were drawn, stage by stage, so a supervisor who never opened the programme could follow them. Because the building managers had written the booklets, they knew the sequence in full.

The three sequences agreed. The finishing sequence was written three months before the job started, so sectional testing and commissioning went into the supply chain orders. The building was split into areas of about 1,000m² with at least a week between them, and tested and commissioned floor by floor before the finishes went in. The electrical final certificate was issued five weeks before an already early completion.

The programme lived in the room. The team ran a standard week, with collaboration meetings for internal trades and external trades instead of one-to-one supply chain meetings. The trades answered each other’s questions, chasing dropped, and the right people were in the room every week. The delivery programme was tracked live on screen in every meeting. One building manager taught himself to track the programme live because he realised that if he wanted to chair the meeting, he had to be able to run the programme.

It went wrong too. The envelope finished 12 weeks late because the window reveals from a design-and-build package arrived late. The job still finished early, because the temporary watertight strategy let the internal trades start behind a dry envelope, the areas were sequenced with a lag, and buffer had been won early.

Almost nothing on that job was invented from scratch. In the preconstruction period I spent a day a week on other people’s sites, looking for what better teams were doing so I could adopt it. Our only real trick was to use it all.

Making it the standard across a Tier 1 business

Everything above works on one job with one good project manager. The harder problem for a large contractor is every other live job in the business.

In most Tier 1 businesses, collaborative planning already happens somewhere. One region runs pull planning sessions. One project director insists on trades in the room at pre-contract. One planner has built a lookahead routine the site teams trust. It is rarely the same thing twice, and it rarely survives the person who started it. That is the Wolstenholme finding again, at company scale: the method works where it is applied properly, and it does not spread on its own.

I learned this leading planning and project controls for a division of a major UK contractor turning over more than £150m. The method was not the problem. Some of our project managers already co-wrote their programmes with the trades and tracked them every week. Others relied on a planner to do it for them. Same business, same systems, completely different jobs.

The changes that moved it were plain. Project managers, not planners, became responsible for co-writing and tracking their own programmes. Every programme was tracked each Friday after a walk-round with the key trade representatives, with demolition, M&E, drylining, carpentry and fire stopping required to attend. Key partners were named in the programme and issued it weekly. And the measurement was done independently every Monday by the planning team, not self-reported by the job. The planners’ role moved from writing programmes to training, challenging and measuring them.

Four things make the difference between a good habit and a company standard.

Standardise the workshop, not the programme. Every job is different. The workshop does not need to be. Agree one format for the five moments: the same fixed points on the wall, the same split by stage, the same question asked of every trade, the same outputs issued the same day. A project director moving between regions should recognise the room.

Turn the planning function from authors into chairs. In a large contractor, planners are usually measured on the programmes they produce. The better measure is how well the programmes they facilitate are kept. That is a different skill. It means training senior planners and project managers to chair, to ask rather than tell, and to type the programme live while the room talks.

Use the framework supply chain you already have. Tier 1 contractors on frameworks and long-term partnerships work with many of the same trade partners job after job. That is a huge planning asset that most businesses waste. Bring framework partners into pre-contract workshops as a matter of course, and carry what was learned on the last job into the sequence for the next one.

Measure the promise, independently. Track the share of committed weekly tasks actually completed on every job, and the reasons for the misses, in the same form everywhere. Have someone outside the project team do it, because a self-reported programme is always on time until the week it is not. Read the portfolio view as a learning system, not a league table. The moment the numbers are used to blame a site team, the site team stops reporting honestly.

There is also a place for an outside chair. A trade contractor will tell an independent facilitator things they will not say to the project manager who approves their payments. That matters most at three points: the first workshops on a new framework or major bid, a job that is already in trouble, and while the internal team is learning to chair the room themselves.

Collaborative planning on JCT and NEC contracts

Collaborative planning works under any contract form. What changes is how the output is protected.

Under NEC, the programme is central to the contract. The accepted programme, the early warning process and the treatment of float all reward a team that has built its programme together and keeps it live. The early warning meeting and the collaborative planning meeting should feel like the same conversation.

Under JCT, the contract does less of the work for you, so the discipline has to come from the team. The principle is the same: keep the contract programme and the delivery programme honest with each other, record progress and change as it happens, and deal with notices and extensions of time in the open while the facts are fresh.

On either form, every project manager should have a copy of their contract within reach and know the handful of clauses that govern time on their job. And on either form, a buffer at the end of the programme, what NEC calls terminal float, is the difference between a job that can absorb a problem and one that cannot. The workshop is where that buffer is won and where the team agrees who owns it.

Seven mistakes that kill a planning workshop

1. Arriving with a finished programme. The room defends it or ignores it. Bring fixed dates and a basic timeline only.
2. No supply chain in the room. A planning workshop with only the main contractor present is a meeting with yourself.
3. Everyone in one session. Split by stage. Three focused hours beat a full day of people waiting for their turn.
4. The chair does the talking. If the facilitator is writing the sequence, the trades are not.
5. No drawings on the wall. Sequences built without the building in front of people miss the interfaces.
6. Not issuing it the same day. A programme issued a fortnight later has already drifted, and the room knows it was not listened to.
7. One workshop, then silence. The workshop is the start of a weekly rhythm, not a substitute for one.

Digital tools or post-it notes?

Both work, and neither is the point. The method is tool-agnostic: it runs in Asta Powerproject, Primavera P6, a cloud planning platform or on a whiteboard. Digital tools make live tracking, sharing and history easier, and remote whiteboards let dispersed teams take part. Post-its make it easy for a trade supervisor to pick up a task and move it.

What matters is that the people doing the work build the sequence, that it is recorded and issued the same day, and that it is kept live afterwards. Software is improving fast, and it will take more of the mechanical work away from site teams. The part it does not replace is the experienced lead who can write a plan, communicate it to a whole workforce in a form they understand, and motivate them to deliver it. Tools draw the bars. People build the building.

Frequently asked questions

What is a collaborative planning workshop in construction? A structured session where the project manager, designers, key trade contractors and, where useful, the customer build or review the programme together. Each party sequences its own work, agrees interfaces with the others and commits to dates, so the programme becomes a shared agreement rather than a document issued from the office.

How long should a collaborative planning workshop take? Plan on a half-day per stage. Splitting the job into stages, such as groundworks to watertight and then internals, keeps each session focused and keeps people in the room whose work is being discussed.

Who should attend? The project manager, who leads and is accountable; the architect, structural and M&E designers; the key trades as a minimum (groundworks, frame, roofing and facade, M&E, drylining, carpentry and demolition where relevant); your own site and building managers; and the customer for the areas where they carry risk.

Is a collaborative planning workshop the same as the Last Planner System? No. The Last Planner System is a full production control method, with phase planning, lookahead, constraint removal, weekly work plans and Percent Plan Complete. A collaborative planning workshop is one part of that picture: the event where the team builds the sequence together. The most effective teams follow it with a weekly rhythm that keeps the plan live.

How often should we hold them? At tender, pre-contract, start on site, at least quarterly with all key trades through the job, and whenever the plan breaks. Between workshops, run weekly collaboration meetings with the programme on the screen.

How does a large contractor make collaborative planning consistent across every job? Standardise the workshop format rather than the programme, train planners and project managers to chair rather than author, bring framework trade partners into pre-contract workshops as standard, and measure the share of weekly commitments kept in the same way on every job.

Does collaborative planning work on smaller projects? Yes. On a smaller job the room is smaller and the session shorter, but the principle is the same: the people who will build the job should build the sequence. On smaller jobs, where one lost week can take most of the margin, it matters more, not less.

Will trade contractors give their time for a planning workshop? In my experience, yes, when the workshop is well run and they can see it protects their own programme and productivity. A trusted supply chain will often contribute early advice for free, provided they are not being asked to price in competition at the same time.

The bottom line

The industry does not lack effort, and it does not lack methods. It lacks the discipline to put the people who build the job in a room, in front of the drawings, and let them build the plan together, then keep that plan alive every week until handover.

Run the workshop. Split the room. Put the drawings on the wall. Keep asking what they need from each other. Issue it the same day. Keep it live.

A programme is not a document. It is an agreement.

If you want to see how the method works end to end, read the Live Programme Method. If you want your project managers running these workshops on their own jobs, that is what Going for Gold teaches, starting in Module 1. If you want the workshops facilitated across your business, book a conversation.