How to reconcile and substantiate a road maintenance bill

On a road maintenance contract, the month's work is hundreds of small repairs spread along the corridor: potholes filled and patches laid, each a few square metres, most of them reported as a photo with a chainage and a size in the caption. Before the bill goes to the client, someone has to turn all of that into a quantity per contract item, with the proof for every patch. Whatever isn't found waits for next month's bill. Whatever can't be proved gets queried, and certification slows down. This guide walks you through that month-end reconciliation: capturing every patch, matching it to the right item, attaching the proof, and checking that nothing is missed or counted twice before you submit.

This guide covers maintenance contracts where repairs are paid by measured quantity against BOQ items. Performance-based contracts paid as a lump sum per kilometre are billed differently.

What a few weeks of pothole repair looks like

On one maintenance contract we've seen, the pothole repair item runs to tens of thousands of square metres over the life of the contract, so it's billed month after month as the repairs add up. In a few weeks after the monsoon, the site WhatsApp group carried a couple of thousand messages. Among them were several hundred patch measurements, each a photo captioned with a chainage, a length and a width. Together they came to around 3,000 sqm of repair, worth tens of lakhs at the contract rate. All of it existed only as captioned photos in a chat.

Two things made turning that into a bill harder than it sounds:

• No units. Most captions read like "Ch 212+350, Length 0.8, Width 0.6". Context usually settles it: the BOQ unit, and the units the same team writes elsewhere. But it's still a decision, and the record should show the unit was inferred, not written.
• Photo bursts. A captioned photo was often followed by several uncaptioned ones of the same patch. They're one patch, not several.

A patch nobody totalled is work done that never reaches the bill. A patch with no chainage, unit or photo is one the engineer can question. The rest of this guide is how to avoid both.

What the engineer needs to certify your bill

Your bill shows one figure per item: so many square metres of pothole repair for the month. Nobody is paid by chainage. But the client's engineer certifies that figure when every patch in it can be traced and proved, and for each patch that means five things:

• What: the BOQ item it's paid under.
• How much: the length, width and area, with units.
• Where: the chainage and the side.
• When: the date, so it falls in the right bill period.
• Proof: the before-and-after photos and the measurement.

Miss any of the five and the patch is queried, cut from this bill, or never claimed. The chainage is what makes the rest checkable: it lets the engineer find the patch, and it shows up the same patch counted twice.

Step 1: Capture every patch

Repairs get reported all month in different places: captioned photos in the site WhatsApp groups, the DPR and measurement sheets. Pull them into one register, one row per patch.

A typical item reads like this: "Filling Pot-holes and Patch Repairs with Bituminous concrete, 50mm. Removal of all failed material, trimming of completed excavation to provide firm vertical faces … back filling the pot holes with hot bituminous material … all as per clause 3004.2", paid by the square metre. The depth is fixed by the item, so each patch's quantity is its trimmed length × width.

Date	Chainage	Side	Length	Width	Area (sqm)	Photos
6 Feb	212+350	LHS	2.4 m	1.5 m	3.60	Before, after
6 Feb	212+410	RHS	1.8 m	1.2 m	2.16	Before, after
6 Feb	213+020	LHS	3.0 m	2.0 m	6.00	Before, after

The figures are illustrative.

• One patch per row. Several photos of one patch are still one row.
• Units written, not assumed. If the caption gives none, record the unit you used and why.
• Always record the side. Two patches at the same chainage on opposite sides are two rows. One patch reported twice is one.
• Only finished patches are billable. A pothole cut out but not yet filled isn't done.

Step 2: Match each patch to the right item

A maintenance BOQ often has several repair items that sound alike but differ in material, thickness or method. Match on the full item description, not a short name. A patch under the wrong item is billed at the wrong rate, or rejected. A repair that matches no item may be a variation: don't drop it, keep it on a separate list with its proof. (See claiming a variation from a site instruction.)

Then total the rows per item for the period. Those totals are your bill lines. (See our BOQ guide for how work done reaches a bill.)

Step 3: Attach the proof

For each patch, the engineer expects:

• A before photo showing the failure, and an after photo showing the finished surface, both dated and taken at the chainage.
• The measurement: the length and width, ideally with a tape visible in the photo.
• The joint measurement or measurement sheet, where the client's engineer measures with you.

Link each photo to its row by chainage and date. Photos gathered at month-end are the slowest part of the bill: they're buried in chats, sent by different people, often without captions. Collect them as the repairs are reported. For a patch with no photo, chase it before you submit, not after the engineer's query.

Step 4: Reconcile before you submit

Run five checks on the register before the bill goes out:

1. Every patch reported done is in the bill. Anything left out slips to next month's bill, or is forgotten.
2. No patch is counted twice. Watch for photo bursts, and for the same patch reported once as it's done and again in an end-of-day summary.
3. This bill follows from the last. Item by item, the cumulative quantity done to date (from the register), less the cumulative quantity billed up to the last bill, should equal what you're billing now. If it's more, repairs from an earlier month were never billed. If it's less, something was billed twice.
4. Each item is within its contract quantity. Compare the running total with the BOQ quantity, and watch the weekly rate, which swings with the season and peaks after the monsoon. If an item looks set to run past its quantity, raise it with the client early, with the records, not at the final bill.
5. Every row has its proof. A patch with no photo or measurement is the one the engineer will query.

Then package it the way the engineer will check it: the abstract of totals per item, then for each item the patch list by chainage, then the photos for each patch. The engineer can go from any total to the repairs and the proof behind it without asking you.

Mistakes that leave work out of the bill or slow certification

• Repairs reported in a chat or a DPR sentence that never reach the register. They can't be totalled, so they aren't billed.
• Every photo counted as a patch. The bill runs ahead of the work, and the engineer starts checking every line.
• Measurements with no unit. "Length 4, Width 3" is 12 sqm in metres and about 1.1 sqm in feet.
• No side. Two patches look like one, or one patch is counted twice.
• Patches billed before they're finished.
• Matching on a short item name. Two items called "patch repair" can have different thicknesses and rates.
• Mixed chainage references: design chainage in the contract, kilometre stones on the existing road. Pick one and say so on every record.
• Proof collected at month-end. By then, the photos take longer to find than the quantities.

Where Velora fits

Velora takes on the capture and matching from the updates your site teams already send. It reads site WhatsApp updates, including patch photos captioned with a chainage and size, and records each as work done against the stretch it belongs to (set up in Velora as a work front). The photos and the source message stay with the record. Where an update gives measurements, it works out the area for your team to confirm. With Billing Intelligence (early access), the work done is matched to the lines of your scope, such as the pothole repair item, so it's raised in this month's bill with its supporting documents. See Field Intelligence for the rest.

Frequently asked questions

How is pothole repair measured and billed?

A typical BOQ item, such as filling potholes with 50 mm bituminous concrete, fixes the depth and is paid by area. The failed material is cut out to firm vertical faces, and each patch is measured as length × width. The bill shows the total area for the period; each patch is recorded with its chainage, side, date and before-and-after photos so the total can be checked, and the running total should be tracked against the quantity in the bill of quantities.

How do you substantiate a road maintenance bill?

Back every bill line with the patches that add up to it and the proof for each. For each patch, record the BOQ item, the length, width and area with units, the chainage and side, the date, and dated before-and-after photos. Then package the abstract of totals, the patch list by chainage and the photos together, so the engineer can trace any total to the repairs.

How do you make sure no repair is left out of a monthly bill?

Capture every repair reported during the month (from site WhatsApp groups, DPRs and measurement sheets) into one register as it happens, one row per patch, and match each row to a BOQ item. Before submitting, check that every finished patch has a bill line, that nothing is counted twice, and that the cumulative quantity done to date, less the cumulative quantity already billed, equals what you are billing now. Any excess is work from earlier months that was never billed.