What "percentage complete" actually means on an electrification contract

"We're 67% complete."

That sentence is in every monthly project report on every electrification contract anywhere in Kenya, Tanzania, Uganda, or Mozambique. It is also, in most cases, made up. Not in a fraudulent sense. In a "we needed a number for the client meeting and the project manager picked the one that felt about right" sense.

This article is about what a defensible contract progress percentage actually requires. Why it matters at milestone certification time. And how to get it without spending the week before each board meeting reconciling spreadsheets.

The numerator-denominator problem

Every percentage is a numerator over a denominator. On electrification contracts, both ends of that fraction are routinely fudged.

The denominator should be the contracted Bill of Quantities — the units of work the contract pays for, in the units the contract specifies. Connections, spans, kilometres of conductor, transformers, kVA. If your denominator is "scope" as a vibe rather than a specific BOQ aggregate, your percentage is editorial.

The numerator should be installed quantity, captured as the work happens. Not "work in progress." Not "civil substantially complete." Installed, in service, recordable as installed quantity against the same BOQ line that defines the denominator.

If the numerator and denominator are not pulled from the same data structure, the percentage is unstable. It will tell you one thing this month and a different thing next month, because the inputs were re-aggregated by hand each time.

What a defensible percentage looks like

The standard a working report has to meet:

1. The denominator is the contracted BOQ, frozen at contract signing.

Variations get added through a controlled process — variation orders, with their own BOQ lines. The base BOQ does not change month-to-month. Every percentage you have ever quoted on this project rolls up against the same denominator, so trends across months are real trends.

2. The numerator is per-line installed quantity, captured at the source.

The crew that installs records the quantity. The site supervisor confirms. The as-built closes out the line at the end. There is no "progress field" that someone updates separately — the installed quantity drives the progress, the schedule, the materials reconciliation, and the cost analytics.

3. The rollup is hierarchical and consistent.

Site percentages roll up to project percentages. Project percentages roll up to a portfolio. The same arithmetic at each level, with no manual stitching.

4. Cost variance is queryable at unit level.

Per-pole, per-connection, per-span. If the project is over-budget, you can see which BOQ lines are driving it — not just "we are over."

How InfraPro does it

The data structure InfraPro uses keeps the numerator and denominator linked at the BOQ-line level.

• BOQ items per project, with country-specific rates. Frozen at project setup; variations are tracked as additional BOQ lines, not edits.
• AssignedLsoWork — work assignments to a construction team against a specific BOQ item, with planned and completed quantity.
• As-built — final installed quantities per design element, recorded after installation, against the same BOQ line.
• Country progress reports, overall progress reports, and material usage reports — all generated from the same data, with no manual reconciliation step.

The percentage at any level — site, project, country, portfolio — is just an aggregate of the level below. There is no "progress percent" field anyone updates manually. If you wanted to invent a number, you would have to invent installed quantities — which is much harder to do undetected because those numbers also drive material reconciliation, schedule pace, and cost analytics.

What this changes for the project manager

The project review meeting changes shape:

• The percentage is the same percentage as last month, computed the same way
• The cost-per-unit metric is queryable per BOQ line, so over-spend is attributable
• The contract milestone certification is not an end-of-month assembly job — the data is already there
• Disputes with the client over progress shift from "trust us, we are 67%" to "here is the BOQ rollup; this is the as-built; this is the schedule"

That last shift, in our experience, is what changes the relationship with the client more than any other operational improvement.

Further reading

For the broader operational story — schedule, materials, safety, fleet — see our insights catalogue. For the platform that produces these reports as a side-effect of the work, see InfraPro.