Scientific foundation
The foundation behind VoortgangsRadar
VoortgangsRadar tests whether a status report gives a reliable steering picture or shows the pattern the Dutch Elias inquiry called a 'watermelon': green on the outside, red on the inside. Its seven-category rubric is drawn directly from recognised sources on status-reporting bias (Snow, Keil & Wallace; Keil et al.), the EIA-748 assurance standard, and Dutch assurance practice (the Elias inquiry, the Adviescollege ICT-toetsing). Scientific evidence shows that misreporting is a recognised contributing factor to project failure and that objective progress data does predict well — VoortgangsRadar therefore tests whether a report relies on those objective signals rather than on a favourably coloured summary.
How this assessment is grounded
The Body of Knowledge was built through deep research along six search lines; 108 claims were extracted from 24 sources, and the strongest top 25 were adversarially verified with three independent votes per claim (23 of 25 confirmed, 2 rejected).
The assessment categories and their foundation
1 Planning & milestones
Progress must be substantiated with objective milestones rather than gut-feel percentages (EIA-748 Guideline 7, adversarially verified). The longer a work package runs, the more subjective the measurement becomes — granularity is therefore a quality signal.
2 Budget & forecast
Variances should be reported at least monthly and traceable to the accounting system (EIA-748 Guideline 22, adversarially verified, 3-0). Batselier & Vanhoucke (2015) show that highly accurate time and cost forecasts are achievable with earned value management on objective data — the rubric therefore tests whether the report contains such a substantiated completion forecast.
3 Scope & changes
Supplementary research by the Dutch Court of Audit (2012) suggests that scope changes were a factor in a substantial share of rebaselined national projects, often with explanations too brief to trace the underlying cause. The rubric therefore tests whether changes are explicitly stated, with their impact on the baseline and a traceable explanation.
4 Risks & issues
Complex projects do not fail overnight but gradually, after numerous warning signs (Keil, Smith, Iacovou & Thompson 2014, adversarially verified). The rubric therefore tests whether the risk picture genuinely moves over time, whether issues are not left to age, and whether mitigations and registers are traceable.
5 Traffic-light credibility
The Elias inquiry documented the mechanism literally: 'steering information looks like a watermelon: green on the outside, red on the inside' (adversarially verified, 3-0). Snow & Keil (2002) advise executives to be sceptical of favourable status reports, especially on high-risk projects — the rubric therefore tests the colour status against the underlying figures, the original baseline and language masking.
6 Dependencies & environment
Supplementary research (Park, Im & Keil 2008) suggests that problems at an external supplier tend to be reported sooner than a project's own problems, turning blame attribution into a reporting bias. The rubric therefore tests whether external dependencies are explicitly stated with status, and whether the balance between internal and external problem attribution is credible.
7 Steering & escalation
Independent assurance is the institutional remedy against misreporting: IPA/NISTA applies 'constructive challenge' and, after assurance, replaces the self-reported rating (adversarially verified, 3-0); the Netherlands built the Adviescollege ICT-toetsing via the Elias inquiry (Wet AcICT, in force since 1 July 2024; adversarially verified, 3-0). The rubric therefore tests whether the report poses explicit decision questions to the steering group and leaves room for independent challenge.
Key claims from the research
Every claim below has been adversarially verified: three independent checks per claim, and only what held up was included.
60% of status reports in software projects contain bias.
Source: Snow, Keil & Wallace (2007) — Information & Management 44(2)
Complex IT projects do not fail overnight; they fail gradually, after numerous warning signs.
Source: Keil, Smith, Iacovou & Thompson (2014) — MIT Sloan Management Review 55(3)
The mum effect — reluctance to report bad news — is a recognised contributing factor to project failure; as a result, senior managers are often unaware of a project's real problems.
Source: Smith & Keil (2003) — Information Systems Journal 13(1); Park, Im & Keil (2008) — JAIS 9(7)
Executives should be sceptical of favourable status reports, especially on high-risk projects — status bias arises through a two-stage process of perception error and reporting bias.
Source: Snow & Keil (2002) — IEEE Transactions on Engineering Management 49(4)
Highly accurate time and cost forecasts are achievable with earned value management, provided it is applied to objective, reliable data.
Source: Batselier & Vanhoucke (2015) — Journal of Construction Engineering and Management 141(11)
Progress should be measured against objective indicators — milestones, physical deliverables — not subjective assessments.
Source: NDIA IPMD Intent Guide bij EIA-748 rev. D (2018), Guideline 7
Variances should be reported at least monthly and traceable to the accounting records; retroactive rebaselining that masks variance trends should not take place.
Source: NDIA IPMD Intent Guide bij EIA-748 rev. D (2018), Guidelines 22 en 30
The Elias parliamentary inquiry documented the mechanism literally: steering information can look like a watermelon — green on the outside, red on the inside; the SVB Tien project still showed green when it was halted.
Source: Commissie-Elias, Kamerstuk 33 326 nr. 5 (2014)
Independent assurance reviews with 'constructive challenge' are the institutional remedy against misreporting; in the Netherlands, the Elias inquiry led to the permanent Adviescollege ICT-toetsing (Wet AcICT, in force since 1 July 2024).
Source: GOV.UK IPA/NISTA assurance toolkit; Commissie-Elias, Kamerstuk 33 326 nr. 5 (2014)
Key sources
- Snow, Keil & Wallace (2007) — Information & Management 44(2)
- Keil, Smith, Iacovou & Thompson (2014) — MIT Sloan Management Review 55(3)
- Smith & Keil (2003) — Information Systems Journal 13(1)
- Park, Im & Keil (2008) — JAIS 9(7)
- Snow & Keil (2002) — IEEE Transactions on Engineering Management 49(4)
- Batselier & Vanhoucke (2015) — Journal of Construction Engineering and Management 141(11)
- Lipke e.a. (2009) — International Journal of Project Management (alleen begrensd bruikbaar)
- NDIA IPMD Intent Guide bij EIA-748 rev. D (2018)
- GOV.UK IPA/NISTA assurance toolkit
- Commissie-Elias, Kamerstuk 33 326 nr. 5 (2014)
- Rekenkamer, kst-30351-2 (2005)
Based on our Body of Knowledge, v1.0 (17 juli 2026)