Consultant fees: the budget line that creeps

A development pays for a planner, an architect, engineers, a surveyor, a certifier and a dozen specialists nobody listed at the start.

Each engagement looks small beside the project. Together they form one of the largest lines you spend before the site earns a cent.

Scope the engagement, not just the fee

A fee proposal without a scope is a rate card. The number you agreed covers whatever the consultant assumed, and the gap becomes a variation.

The engagement names the deliverables, the number of revisions and who attends which meetings. Meetings and revisions cause most consultant variations.

Agree what happens when the scheme changes

A development changes design several times, and each change reopens work the consultant already finished. That work is legitimate, and your engagement should price it beforehand.

Your engagement names a rate for redesign and says who authorises it. Without that line you get a surprise invoice and an argument about instruction.

Track commitments, not invoices

Your accounts show what arrived. Your exposure is what you agreed, and the gap between them can run for months.

The committed fee goes on the record at signing, and invoices draw against it. The project then shows what it owes, rather than what it has paid.

Our guide to budget against actual covers the columns that show a line moving while you can still act.

Approve variations before the work, every time

A consultant variation approved after delivery is a payment decision, not an approval. By then the hours exist and refusing them costs you the relationship.

A threshold, with written approval above it, settles that. Most consultants prefer that arrangement, because it protects their fees as much as your budget.

Watch the ones paid by percentage

A fee set as a percentage of construction cost rises whenever the build cost rises. A ten per cent build overrun quietly increases several fee lines at once.

Those lines model against your current cost forecast rather than the original figure. Our guide to feasibility sensitivity covers testing that movement properly.

Keep the reports where the next person finds them

A geotechnical report bought once gets bought again two years later because nobody could find it. That happens more often than any developer admits.

Every report stores against the project, named so a stranger recognises it. The cheapest consultant fee is the one you already paid.

Pay on milestones, not on hours passing

A monthly fee draws down whether the work moved or not. A project that stalls for a quarter still pays several consultants for that quarter.

Payments tie to deliverables: the report issued, the application lodged, the drawings released. Both sides then know exactly what triggers an invoice.

It also gives you a clean position when a consultant underperforms. Your conversation is about a deliverable rather than about somebody's timesheet.

A milestone structure also shows you where a project really is. Four consultants who have not billed a milestone in two months are telling you something about the programme.

That pattern reads alongside the programme rather than in isolation. Consultants stall for reasons that usually sit with somebody else on the project. Consultants stall for reasons that usually sit with somebody else.

The fee you never commit to is the only one that cannot overrun.

What to change first

• Deliverables, revisions and meetings go into every engagement
• A redesign rate gets agreed, with a named person to authorise it
• The committed fee goes on record at signing, with invoices drawn against it
• Written approval above a threshold comes before the work
• Percentage based fees model against the current cost forecast
• Every report stores against the project, named for a stranger