Examples of the work
Client work is confidential, so the examples below are demonstrations built with sample data. They show the format and the level of detail you would receive. Each one is labelled as a sample.
Executive dashboard
One screen for a programme director: performance indices, milestones at risk and package progress, with drill-down to the activities behind each figure. The version below is static sample data; the live build is interactive.
Illustrative dashboard using sample data. Each bar shows earned value as a percentage of the package budget; the white mark shows planned value to the data date on the same scale. Package SPI is earned value divided by planned value for that package: Package A 82% against 78% planned, B 61% against 70%, C 74% against 73%, D 45% against 44%, enabling works 100% against 100%, fit-out 28% against 40%. Programme SPI is total earned value divided by total planned value; CPI is earned value divided by actual cost.
What a reader does with it
- SPI 0.96 says the programme has earned 96% of what it planned to earn by the data date (61.4% complete against 64.0% planned, the same figures as the weekly report). The question for the meeting is which packages are driving it, which the package SPI column answers: Package B at 0.87 and fit-out at 0.70. The other packages are on or slightly ahead of their own plans.
- CPI 1.02 says cost is slightly under plan for the work done. Combined with SPI below 1.0, the likely story is slower progress rather than overspend.
- 1 milestone at risk links to the milestone register below, where it has an owner, a forecast date and a recovery action, and where a second milestone is on watch.
Schedule review findings
An extract from the findings table of an independent baseline review, built with sample data. The full report records every check against the contract requirements, with a recommendation and the evidence for each finding.
| Ref | Finding | Effect | Recommendation | Severity |
|---|---|---|---|---|
| F-01 | 38 activities have no successor, including 6 on the structural works | Critical path is unreliable; float on structure is overstated | Close open ends; re-run the critical path before acceptance | High |
| F-02 | Procurement activities are not linked to the installation activities they feed | Late deliveries will not move the installation dates in the schedule | Add finish-to-start logic from delivery to first installation for each long-lead item | High |
| F-03 | Two calendars in use with different Friday working; MEP activities on the 7-day calendar | MEP durations are understated by about 14% | Confirm the agreed working week and apply one calendar per trade | Medium |
| F-04 | Testing and commissioning is a single 20-day activity | No visibility of system-by-system readiness for handover | Break down by system; link each to its installation completion | Medium |
| F-05 | Resource loading present for labour only; no equipment or cost | Histograms cannot support the cash flow submission | Add cost loading at the agreed level before the first update | Low |
Scroll the table sideways to see all columns.
Milestone register
An extract from a contract milestone register kept in a Power Apps tool, built with sample data and sharing the same sample programme and data date as the dashboard and the weekly report. Each row carries the contract date, the current forecast, the variance and the owner of the recovery action, and the app sends a reminder before each contractual notice date. Status: achieved, the milestone is complete; at risk, the forecast is later than the contract date and the milestone is on the critical path; on watch, the forecast is later than the contract date but float remains; on plan, the forecast is on or before the contract date.
| Milestone | Contract date | Forecast | Variance | Status | Owner |
|---|---|---|---|---|---|
| Enabling works complete | 15 Jun 2026 | 12 Jun 2026 | -3 days | Achieved | Enabling works |
| Structure to level 10 | 30 Sep 2026 | 21 Oct 2026 | +21 days | At risk | Package B |
| Long-lead chillers delivered | 15 Nov 2026 | 15 Nov 2026 | 0 | On plan | Procurement |
| Facade watertight | 31 Dec 2026 | 14 Jan 2027 | +14 days | Watch | Package C |
Scroll the table sideways to see all columns.
Weekly report extract
The first page of a weekly progress report for a contractor client, built with sample data. The figures are generated from the schedule update; the commentary is written by the planner.
Summary
Overall progress 61.4% against 64.0% planned, 2.6 percentage points behind plan (SPI 0.96). The critical path runs through the level 10 structure, which is 21 days behind the contract milestone. A recovery programme has been issued for the engineer's review (ref. RP-03).
Critical path status
Structure to level 10 forecast 21 Oct 2026 against 30 Sep 2026. Cause: formwork crew reduced from three to two gangs in weeks 35 to 37. Recovery: third gang remobilised 28 Sep; forecast assumes the 6-day cycle is held.
Milestones
1 achieved, 1 at risk, 1 on plan, 1 on watch. See milestone register, rows 1 to 4.
Issues requiring the client's action
Approval of the chiller submittal (ref. SUB-114) is 9 days overdue. Each further week of delay moves chiller delivery, which is 12 days from the critical path.
Four-week lookahead
Level 11 and 12 slabs, start of facade bracket installation on the north elevation, MEP first fix levels 3 to 5.
Previous experience and references
The examples above are demonstrations. Our lead consultant has prepared and reviewed deliverables of this kind on capital projects in Saudi Arabia and the Gulf over more than 20 years; that is a personal professional record, not work contracted by Expert Systems. References for assignments contracted by Expert Systems will be published as they become available, with the client's consent. Until then we are happy to discuss relevant experience on a call.
Tell us about your task
Want to see the full version of any example, or discuss what yours would contain? Send a short note.