What is an early warning system in construction?
An early warning system is a set of checks that runs on the facts of a project all the time, and raises a flag when something drifts from the plan. The term is in the early warning entry of the glossary. The point is timing: the warning arrives while the milestone can still be recovered, the overrun can still be negotiated and the buyer can still be called.
Most project reports do the opposite. A monthly pack or a weekly meeting describes what already happened. It is accurate, and it is late. An early warning system does not replace those reports. It makes sure that a deviation reaches someone who can act before it reaches the report.
What are the parts of an early warning system?
Every working system has the same six parts, whether it is a set of spreadsheet formulas or a dedicated tool.
- Facts: dated, sourced entries about progress, cost and payments. A warning is only as good as the facts behind it, and a missing fact should be visible rather than assumed away.
- A plan to compare with: the approved dates and amounts, which is the baseline of the job.
- Rules: each rule compares one fact with one part of the plan. For example, a milestone is past its planned date, or an item is forecast above its plan.
- Thresholds: the amount of deviation that is allowed before a rule fires. A threshold can be a number of days, a percentage of the plan or an amount of money.
- A signal: the warning itself, with the reason in plain words and the facts that caused it.
- A named person and a recorded action: who is responsible for the area, what they did about the signal, and when.
How does a rule turn a fact into a warning?
Take a budget item planned at 100,000. Its forecast is what has been invoiced plus what has been committed. Say the invoices are 40,000 and a signed order of 66,000 is committed, so the forecast is 106,000. That is 6% above plan. If the rule fires above 5%, the item raises a signal, and the reason is written in the signal itself: the forecast is above the plan by more than the threshold.
A schedule rule works the same way. A milestone planned to end on day 60 is forecast, from its actual pace, to end on day 68. That is 8 days after plan. If the rule fires after 7 days, the milestone is forecast behind plan. Nothing in either example is an opinion: each number comes from a fact and a threshold that anyone can read.
Which deviations are worth a warning?
The most useful warnings cover the places where a project usually drifts. The list below shows the checks that Reperline runs by default, and the owner can change the thresholds for the whole company or one project.
- A milestone is overdue: its planned date has passed and the work is not finished. High after 14 days.
- A milestone is forecast behind plan: at today's pace it ends more than 7 days after its planned date.
- A budget item is forecast over plan by more than 5%.
- Spend is ahead of progress: the invoiced share of an item's plan, divided by the progress of its phase, is above 1.2.
- A tender closes within 3 days, or its deadline has passed.
- An active phase is silent: no new fact for 7 days.
- A buyer instalment is overdue. High after 14 days.
- Two optional checks that are off by default: a big transaction above the owner's amount, and a transaction with no document number.
How is the priority of a warning decided?
Not every warning deserves the same attention, so each signal gets a priority from three parts. Impact is how much is at stake: the weight of the milestone in its phase, or the amount of money involved, which counts for more the larger it is. Urgency is how soon it bites: how many days late a milestone is, or how few days are left before a tender closes. Confidence is how sure the system is: a fact counts for more than an extrapolation, so a date that has passed counts for more than a forecast built from a pace.
The three parts are multiplied, so a warning that is weak on one side is weak overall. The score runs from 0 to 100. By default a score of 60 or more is critical, 35 or more is high, 15 or more is medium, and anything below that is low. The overview opens with the few signals that need a decision today, and the rest wait in the inbox. Because the score is built from parts you can read, a person can explain why one warning sits above another.
Who is told, and how often?
A warning helps only when it reaches a person who can act. Critical and high signals go by Telegram and by email to the roles the owner chooses, and only to people who may see that area and that project. By default the owner, finance and site managers receive critical signals, and finance and site managers receive high ones. Nobody sees a warning about a project they cannot open.
A signal that nobody has acted on is sent again. A critical signal is repeated after 24 hours, a high one after 48 hours, and any signal is sent at once when it gets worse. This keeps a warning from being lost in one busy morning, without flooding people with the same message every hour.
What happens after a warning fires?
A signal needs a response, and the response should be recorded. The person who sees it can take it with 'I am on it', snooze it until a date, or dismiss it with a reason. A taken signal shows who took it and since when. If the cause is still there after seven days, the person who took it gets a reminder, so an action does not quietly turn into a forgotten promise.
The record matters later. Each signal keeps its history: when it first fired, how its priority changed and what was done. That history is what lets you show, after the event, that a warning was raised in time and what the team did with it.
How does Reperline handle this?
Reperline is an early warning layer over the schedule, the budget, the tenders, the buyer contracts and the site reports. The rules run on the facts as they stand now. When the cause goes away, the signal goes away. A separate history keeps what was raised, when, and what was done about it.
Its limits are part of the design. A warning needs a fact, so Reperline cannot warn about a problem that no fact describes. A milestone with no progress has no forecast, and a missing report is shown as missing, not as on time. Reperline does not calculate earned value, the cost performance index or the schedule performance index. Its cost warnings use the forecast of each item and the spend ahead of progress instead, as described in the cost control guide. The signals module has the full list, the budget module and the schedule module show the facts behind it. The plans are on the pricing page, and a free trial with no card runs for 14 days.