Construction project management software holds the plan and everything that stops the plan from happening. It carries the programme and its packages, the short term lookahead that site teams actually work to, the drawings, approvals, samples and decisions that work is waiting on and who holds each of them, coordination between the parties involved, and the position across every live project when a business runs several. With Pentoggle, a contractor can describe its packages, agencies and approval chains and generate the starting application around them.
This page covers planning and coordination. The record of what actually happened each day and the measurement of progress against plan sit in progress tracking and DPR, and cost against budget sits in cost management. The three connect and they are separate jobs.
Many contractors already run a scheduling tool for the programme and an accounting system such as Tally. Scheduling tools handle logic, dependencies and the critical path well. What sits outside them is the list of things somebody has been waiting on since the eleventh, with an owner and an age against it.
Key takeaways
- Many project delays are caused not only by sequencing, but by decisions, drawings, approvals and other dependencies that remain unresolved.
- Site teams often work to a short-term lookahead derived from the master programme, and some systems do not capture that operational plan in the same workflow.
- Float gets consumed quietly as activities slip, and by the time it matters nobody can say where it went.
- Where a business runs several projects, the same scarce resources are promised to more than one of them by different people.
- A useful number is open items blocking work, grouped by holder and age.
What the programme and the weekly meeting do well, and where they stop
Most construction projects are planned properly. A programme is prepared, packages are defined, dependencies are worked out, and a weekly meeting runs through progress and problems. Experienced project managers hold an enormous amount of this in their heads and are good at it.
The limits are about what survives outside the room.
The programme ages faster than it gets updated
It is maintained by a planner, often not resident on site, working from information that arrives late. By the third month the version in circulation describes an intention rather than a plan.
Meeting actions live in minutes
Decisions are recorded in a document that is emailed and rarely revisited before the next meeting, so an item raised in week two is raised again in week five as though it were new.
Waiting items have no home
A drawing awaited, an approval pending, a sample with the consultant, a client decision on a finish. Each is discussed when it blocks something and forgotten when the conversation moves on. There is no list, so there is no ageing, so nobody knows that one of them has been open for six weeks.
Cross project reality is invisible
A business running four sites has four project managers each planning as though their resources are theirs. The crane, the shuttering set, the finishing crew and other shared resources are shared, and the contention only surfaces when two projects need the same thing on the same day.
What project management software holds
The programme and packages
Activities, packages, dependencies and durations, with the baseline preserved separately from revisions.
The short term lookahead
A rolling multi-week lookahead at the level of detail the site actually works to, with what each crew and agency is committed to.
The pending items register
Drawings, approvals, samples, decisions and instructions that work depends on, each with who holds it, since when, and what it blocks.
Coordination between agencies
Interface items between contractors, consultants and the client, with a named owner and a required-by date.
Meetings and actions
Actions carried forward with owners and status, so an item raised once does not need raising again.
Risks and issues
Things that have not happened yet and things that have, held with owners rather than in a document reviewed quarterly.
Resource commitments across projects
Shared plant, crews and key staff, and which project each is promised to and when.
The portfolio view
Every live project with its status, its critical blockers and its next milestone, on one screen.
Some important delays come from decisions rather than sequencing
In many projects, the causes of delay are not limited to sequencing. Decisions, drawings, approvals, access and other unresolved dependencies can consume significant schedule time.
A structural drawing revision that took eleven days. A material sample submitted and not returned. A client choosing between two finishes. An authority approval. A consultant's comment on a shop drawing. A variation awaiting sanction before work can proceed. Individually each is a few days. Cumulatively they are the schedule.
These are not tasks in the ordinary sense, because the contractor cannot do them. They are waiting items, and the only thing the contractor controls is whether they are visible, aged and escalated. That distinction matters. A waiting item can be modelled in scheduling software as an activity with a duration and a dependency, and on well planned projects it often is. What it usually lacks in practice is an owner inside the contractor's organisation and a record of how long it has been open, because nobody is doing the work and so nobody is reporting on it.
For some projects, a simple register of pending items can be more actionable than another round of scheduling refinement. What is pending, who holds it, and since when. Add what it blocks and the register sorts itself into priority order without anybody having to prioritise it.
The ageing is what gives it force. An item described as pending is easy to leave. The same item described as pending for twenty six days, blocking a slab, is a different conversation, and it is a conversation that can be had with a client or a consultant without accusation, because the record is simply a record. Where entitlement to time is at stake, the same register can form part of the contemporaneous project record supporting a claim, though whether an entitlement arises and what evidence is required are contract questions for your contracts team.
Site teams often work to the lookahead as much as the programme
Construction projects often use both a master programme and a short-term lookahead plan, but software coverage of the two varies.
The master programme covers the project and gets revised occasionally. The plan the site actually runs on is often a rolling multi-week lookahead, worked out in a weekly meeting, covering which crew is on which front, what material has to arrive, which drawings are needed and what has to be cleared by another trade. It is often on a whiteboard or a single sheet, and it is the real coordination instrument.
When a system only holds the master programme, it can sit outside the process the site actually uses, leaving the short-term coordination plan to be maintained separately. Anything built for construction project management benefits from holding the lookahead as a first class thing, because that is where commitments get made and where they get broken.
The useful discipline is recording what was committed for the coming week and reviewing what was actually achieved against it. A crew that committed to five items and completed two has told you something, and the reason for the three is nearly always one of a small number of causes: material, access, drawings, labour or a decision pending. Tracking those reasons over a few weeks produces a ranked list of what is really constraining the project, which is usually different from what the weekly meeting assumes.
This connects directly to the hindrance record in the daily report, since the two are the same information seen forwards and backwards.
Float belongs to the schedule and gets consumed when delays use available time
Construction programmes often contain activities with available float, which represents the amount of schedule flexibility before a delay affects a successor activity or the planned project completion date.
A supplier delivers a week late and may consume available float, reducing the schedule flexibility that could otherwise absorb a later delay. A drawing revision uses up the allowance held for a testing delay. A subcontractor starts three days late because it suits their other site. Each of these is small and reasonable in isolation, and each consumes flexibility the project may need later.
By the time the project is genuinely tight, the float is gone and no record exists of where it went. What remains is an argument in which each party believes the others consumed it, and none can demonstrate anything.
The response is not to police float, which is impractical, but to make its consumption visible. When an activity moves, recording why it moved and what absorbed the change takes seconds and creates a trail. Over a project this accumulates into an account of where time was actually lost, which is useful both for managing the current project and for planning the next one with allowances based on what happened rather than on habit.
Where project management looks different by business type
- General Contractor Software, where the programme is largely a sequencing problem across firms the contractor does not employ.
- MEP Contractor Software, where the plan is dictated by access granted by other trades and the lookahead matters more than the master programme.
- Infrastructure and Road Contractor Software, where planning is by stretch and the blocking items are frequently outside the contractor's control entirely.
- Interior Fit-Out Contractor Software, where programmes are short and a pending decision consumes a meaningful share of the whole duration.
- PMC Software, where the firm coordinates contractors on the client's behalf rather than delivering work itself.
Why contractors choose Pentoggle for project management
The pending register
Drawings, approvals and decisions with holder and age, making the sources of unresolved delay visible.
The lookahead the site uses
The rolling short-term plan held alongside the master programme rather than separately from it.
Reasons captured when commitments miss
Material, access, drawings, labour or decision, tracked so the real constraint becomes visible.
One view across projects
Shared resources and blockers across every live site rather than four separate pictures.
Works alongside your scheduling tool
Programme logic stays where your planner works. This holds coordination and what is blocking today.
The one number that runs project management
Open items blocking work, grouped by holder and age.
Most project reporting describes what has been done. This describes what cannot be done and why, which is often the part of the report that can be acted on this week.
Group by holder rather than by project, because the pattern is usually a party rather than a site. Twelve items sitting with one consultant is a specific conversation with a specific person. The same twelve spread across a status report is background noise.
Sort by age and work from the top. Items open longest are rarely the ones being discussed, precisely because they have stopped being new, and the oldest item on the list is frequently something everyone has quietly accepted as permanent.
The number depends on items being logged when they arise rather than when they become urgent. That is a habit rather than a feature, and it is easier to establish when the register visibly produces escalations rather than reports.
Ready to build project management software?
Nobody needs another Gantt chart. They need to know who is sitting on the thing that stopped work.