White Friday: up to 30% off your subscription 0days 0hrs 0min
Intagya
Pricing Blog Try free
← All articles

How do I know a project will be late before it is late?

| Intagya ERP Expert Team

How do I know a project will be late before it is late?
The short answer

Compare the real pace of work with the plan, not with spoken updates. In Intagya ERP the Delay warning works out every night how much of each project is done against what was planned for today, forecasts the end date if work keeps the same pace, and names the first cause: late materials, stalled tasks or one person on several late projects.

A fit-out contractor has three flats to hand over in the same month. At the Monday meeting he asks the site engineer whether they are on time. Roughly, comes the answer. Three weeks later the customer calls to ask why the kitchen is still not fitted, and the contractor finds out the marble has been ten days late from the supplier.

The marble was not the real problem. Nobody had tied the late marble to the delivery date.

Why do I only find out about a delay when it is too late?

Because most follow-up measures what happened, not what will happen. A list of late tasks tells you one task missed its date. It does not tell you the whole project is moving at a pace that will never reach the handover. A manager who asks how much is done hears a number, and not what that number means two months from now.

My advice: stop asking the team whether you will be late. Ask the figures how fast you are going.

How do I work out the real delivery date from the pace of work?

Take the days since the project started and divide them by the share that is done. The result is how many days the whole project needs if it keeps the pace it has shown so far.

Example: a project started 40 days ago and is 25% done. At that pace it needs 160 days. If the plan was 120 days, it is 40 days late, even though no single task is late yet.

Intagya ERP runs this every night for each open project with an end date. Progress comes from earned value when the project has a baseline with budgets, otherwise from the approved progress or from the share of tasks done. What was planned for today is a straight line from the start date to the end date.

What usually makes a project late?

Knowing a project will be late is half the answer. The other half is why. The tool looks for three causes and ranks them:

  • Late materials: purchase lines linked to the project that are past their receipt date and not fully received. They come first because they stop work outright.
  • Stalled tasks: tasks that should be moving and that nobody has updated for 10 days.
  • One person on 3 late projects or more: a good employee who is needed everywhere at once.

In the contractor's case the row would have said: marble not received, with the purchase order number. One call to the supplier, before the customer ever picks up the phone.

What should I do when a project shows as late?

Skip the meeting. Press Send the warnings to the managers, and the manager of each late project gets an activity with the forecast date, progress against plan and the causes. Nobody gets a second warning while the first is still open, so the inbox stays quiet.

Then start with the worst one. The table puts the latest project first, and a row turns red once the expected delay passes a week. Ask about the first cause only; fixing it usually moves the forecast at the next night's run.

Link each project's purchases to it, through the project field on the purchase order or its analytic account. Without that link the tool cannot see late materials, which are the most common cause.

Does the system change the project dates by itself?

No. The tool forecasts and warns. It never touches the project dates or its tasks. The decision is yours: add a worker, call the supplier, or give the customer a new date before they ask.

To me that is the whole point. You tell the customer, instead of the customer telling you.

Where do I start if my projects have no dates?

With the dates. A project without an end date is left out, because there is nothing to measure it against. And do not type an optimistic date to make the figures look good; type the date you promised the customer.

Tomorrow morning open the Projects app, then Overview, and on the Today tab look at Tasks without a deadline and give them dates. Set a start and an end date on every running project. After one night, open Decisions, then Delay warning, and see which project says it will be late.

FAQ

Does the delay warning need the AI assistant?

No. It is a calculation inside the system from your projects and purchases, and it uses none of the AI assistant questions.

When is the forecast worked out?

Every night. A project manager can press Recalculate now to see it straight after a change.

Does every employee see every project?

No. Each user sees only the projects they may open.

What if nothing is done yet?

If the project has not started, the plan stands. If time has passed while work was due and nothing is done, the system expects the project to need its whole planned span again from today.

Want to see IntagyaERP on your own workflow?

Book a demo, tell us how your business runs, and watch the system handle a real scenario from your company.

Book a demo