Asta Powerproject for UK Fit-Out PMs: How to Use It Properly

Most fit-out PMs have a programme. Fewer have a planning tool.

I have seen it many times across twenty years on UK fit-out and refurbishment projects. A Project Manager receives the programme from the planner at tender stage, files it after contract award, and then runs the project from memory and habit. On a simple project this sometimes works. When things go wrong, whether a trade running late, a client instruction changing the sequence or a delayed design decision, there is nothing to go back to. No baseline. No logic. No evidence. Just a static document that was already out of date on the day it was issued.

I have also seen site managers who knew their sites inside out but had never built a programme in their lives. They could not explain the programme in a client meeting even if they had to. That is a limitation I was not willing to accept when I moved into the PM role.

This article is not a tutorial on how to click through Asta menus. There are training manuals for that. This is about how to use Asta to build programmes that actually work on a live UK fit-out site, and how to use them when the project comes under pressure.

Why Asta and Not Microsoft Project

The question comes up at pre-start meetings. Here is the honest answer.

Microsoft Project is a general-purpose tool. It works across industries and is widely understood. Asta Powerproject is built for construction. That difference matters more than most PMs realise until they hit MS Project's limitations on a complex multi-floor fit-out.

I used MS Project in my early PM days. Since moving to Asta I have never used MS Project on a fit-out project again. The specific advantages that matter in UK commercial fit-out:

• •

  Resource histograms that are usable on site. Both tools produce them, but Asta's labour and resource histograms are faster to set up and read, so you can actually check whether your programme is asking for more people than can physically be on site at once. On a Cat B fit-out with several subcontractors working in parallel, that is a daily reality.

• •

  Summary bars and rollup logic. Asta lets you group activities under summary bars that automatically reflect the logic beneath them, so you can show a floor-by-floor summary to the client while keeping the full detailed programme underneath. In my experience the multi-floor structure is more intuitive to manage in Asta than in Project's outline levels.

• •

  Baseline comparison built for construction reporting. Both tools hold baselines, but Asta shows the original baseline, the current programme and actual progress side by side in a format that reads instantly in a progress meeting, with less manipulation to get a presentable output.

• •

  It is the UK construction standard. Asta is used by the large majority of UK contractors and is frequently expected or specified on building and fit-out work, so an Asta programme is what most main contractors and clients want to receive. On some projects a particular tool or format is named in the contract, so always check the requirements. I have had Asta specified directly on government estate projects.

One qualification: if your employer or client requires MS Project, use MS Project. A well-built Project programme is always better than a poorly built Asta programme. The tool is the vehicle, not the destination. If you are choosing which tool to invest time in learning and you work predominantly in UK fit-out and construction, invest in Asta.

The Setup Decisions That Determine Everything

The decisions you make in the first hour of building a programme affect every week that follows. Most of the programme problems I have had to deal with across my career started with a poor setup. Fifteen minutes of correct setup at the start saves hours of correction later.

Calendar setup. Your calendar defines what counts as working time. For most commercial fit-out projects, your base calendar is Monday to Friday, eight or nine hours per day. But there are three situations that require separate calendars:

• •

  Specific trades working Saturdays. Create a separate calendar and assign it only to those activities, not the whole programme.

• •

  Restricted access in occupied buildings. If core drilling is restricted to 08:00-12:00 by Section 61 consent from the borough, create a calendar that reflects this. A programme showing core drilling in a ten-hour working day when you only have four permitted hours is commercially misleading and will create problems at the programme review meeting.

• •

  Public holidays and site closures. Mark bank holidays, Christmas shutdown, and Easter at the very start. Do not rely on remembering them as the project progresses.

Section 61 of the Control of Pollution Act 1974 deserves specific mention. On most Cat B fit-out projects in London, particularly in occupied buildings, Section 61 consent is required before core drilling, concrete breaking, or other high-impact noisy activities can start. The local authority has 28 days to respond. In practice, allow four to five weeks from submission to consent. Section 61 must be a programme activity in its own right, linked logically to the start of the core drilling phase. If it is not in the programme, the delay risk is invisible.

Project structure. On a multi-floor fit-out, the most logical structure is floor by floor, with trades running through each floor as a separate section. The most efficient approach: build one floor fully in Asta, copy it, paste it for each subsequent floor, change the floor name, then apply a lag, typically one to two weeks, so each floor starts after the one above has progressed far enough for the key leading trade to move down. This cascade effect creates continuous workflow for each trade with no dead time and no crowding.

Activity naming convention. Agree a naming convention before you add any activities. On a 120-activity programme, inconsistent naming makes filtering and reporting extremely difficult. The convention that works best: [Floor - Trade - Activity]. For example: F3 - M&E - First Fix Cabling, F3 - DLN - Metal Stud Framing, F3 - SCR - Liquid Screed Pour.

The Four Dependencies That Cause the Most Failures

The logic links between trades are the single most important element of a fit-out programme. Get them wrong and the programme is useless from week three.

M&E first fix before drylining framing. This is the most common sequencing error on Cat B projects. The drylining contractor arrives, sees an empty floor, and starts framing. The M&E contractor arrives two weeks later, finds partitions already framed, and has nowhere to run their containment. Result: the drylining contractor is asked to open up framed partitions to allow M&E containment to pass through. Time lost: four to seven days. Abortive cost: real. Prevention: a single logic link in your programme that prevents drylining framing starting until M&E first fix containment is signed off in each zone.

Screed before underfloor services are complete. Sand cement or liquid screed cannot be revisited once poured. If underfloor M&E services are not complete and signed off before the screed gang arrives, you have two choices: delay the screed and lose your gang to another project, or pour and accept that any underfloor remediation later means breaking out and replacing the floor. The logic link between M&E underfloor sign-off and screed pour must be absolute.

Sprinkler distribution and pressure test before ceiling tiles. On any Cat B fit-out in a commercial office building with an existing suppression system, the sprinkler system will need adaptation. Two distinct stages must both be in your programme. First fix distribution, pipework and branch lines above the ceiling zone, must be coordinated with all other above-ceiling services and completed before the ceiling grid goes in. The second stage is the pressure test: before ceiling tiles are installed, the entire adapted sprinkler system must be pressure-tested and witnessed by the building owner's representative. Getting that inspector on site at short notice is often not possible. If the pressure test is not in the programme as a distinct activity with a defined date, you will arrive at the point of tiling and find you cannot proceed.

Decoration before dust-generating trades finish. Decoration shows every imperfection and every speck of dust. Decorating while plasterboard cutting, floor grinding, or joinery trimming is still happening in adjacent areas guarantees rework. The programme must reflect a real sequence: dust-generating works complete in a zone, then clean, then decorate.

The Ten Most Common Fit-Out Programme Failures

These are the failures seen repeatedly across fit-out delivery. None of them are inevitable. All are avoidable with a correctly built and actively managed programme.

• •

  No logic links: bars floating independently. A programme of floating bars cannot show the impact of a delay on the rest of the project. It is not a planning tool.

• •

  Unrealistic trade durations at tender. Durations compressed to win a bid become impossible to achieve on site. A Cat B office floor plate of 1,200 sqm with a typical cellular layout will have roughly 1,000-1,400 sqm of partition. A drylining gang of four will typically frame and board at 80-100 sqm per day: twelve to fifteen working days, not the six days that sometimes appear in tender programmes.

• •

  No baseline set before construction. Without a baseline, you cannot measure slippage, cannot demonstrate delay to an employer, and cannot support an EOT or compensation event claim.

• •

  Programme not updated after week three. A programme that stops being updated becomes an embarrassment and a liability.

• •

  Lead-in times and design approvals not in the programme. Bespoke joinery with a twelve-week lead time needs a twelve-week activity in the programme. If it is not there, the two-week slip is invisible until the joinery arrives late and there is no recovery available.

• •

  M&E first fix starting after drylining framing. The result is always the same: abortive drylining, rework, programme loss, and a dispute about who caused the delay.

• •

  Commissioning time underestimated. On a complex Cat B fit-out with integrated M&E, BMS, access control, fire alarm, and AV, commissioning takes longer than the programme allows. Always.

• •

  Slippage not addressed until it is too late to recover. Three days behind in week three is a minor management issue. Three weeks behind in week twelve is a crisis. Respond to slippage at the three-day mark, not the three-week mark.

• •

  Client decision delays not in the programme. When the client delays a decision that affects a programme activity, document it, issue an information request with a stated programme impact, and update the programme when the impact becomes clear.

• •

  Tender programme used as contract programme without review. The tender programme is a bid document. The contract programme is a management tool. They serve different purposes.

What a Good Programme Actually Does

Build the logic. Set the baseline. Update it weekly. Know your critical path. Respond to slippage early. A programme built correctly and updated honestly is the closest thing this industry has to a crystal ball. Use it.

A programme built correctly in Asta is not a bureaucratic requirement or a contract deliverable that gets filed and forgotten. It is the single most useful management tool on a live project. It tells you in real time what is happening, what is at risk, and what your options are. And when the commercial disputes that every project generates eventually need to be resolved, it gives you a defensible evidence trail.

The programme is only as good as the discipline behind it.

Related reading