Architects: how to justify a fee amendment when hours exceed the fixed price

Requesting a fee amendment from a project owner is one of the most delicate exercises in the architecture profession. Not because the request is illegitimate -- it often is legitimate -- but because most project managers go about it the wrong way. Without factual data, without traceability of the causes of the overrun, the discussion turns into a power struggle. And in a power struggle without evidence, the architect always loses. This guide details the method for building a solid amendment case, identifying the right moment to initiate the discussion, and transforming this constraint into a management lever.

The problem with amendments without data: why most fail

The scenario is classic. A project in the PRO (detailed design) phase has consumed 340 hours against 220 budgeted. The architect can feel it -- teams are working late, deliverables are behind schedule, the margin is melting away. They eventually call the project owner to discuss an amendment. The response is predictable: "The contract is fixed-price. You committed to an amount. There's no reason to change it."

The problem isn't that the project owner is acting in bad faith. The problem is that the architect comes empty-handed. "I worked more than planned" is not a contractual argument. It's a feeling. And a project owner -- whether public or private -- doesn't sign an amendment based on a feeling.

Common mistake: Waiting until the end of the project to acknowledge the overrun and attempt retroactive negotiation. At that point, the project owner has no incentive to accept: the work is done, the deliverables are delivered. The negotiating leverage is zero.

The MOP law (law no. 85-704, now codified in the French Public Procurement Code) and the CCAG-PI (General Administrative Terms for Intellectual Services Contracts) frame the conditions for an amendment. Article 14 of the CCAG-PI provides that additional or modified services must be subject to a service order or amendment before their execution. In public contracts, the amendment must be justified by "unforeseen technical constraints" or program modifications decided by the contracting authority.

In other words, the legal framework exists. But it demands one thing: documented facts. A precise record of hours consumed per phase, correspondence tracing modification requests, a causal link between the additional workload and a decision or event external to the initial scope.

Key figure: According to consolidated feedback from the CNOA (French National Council of Architects) and professional organizations, firms that systematically document their hours obtain an amendment in 60 to 70% of cases where the overrun is linked to a program modification. Those with no data: less than 15%.

How to build a factual case to justify a fee amendment

A convincing amendment case rests on three pillars: the quantified assessment, the causal analysis, and the supporting documents.

Quantified assessment: hours consumed vs. hours budgeted

The first element of the case is a comparative table, phase by phase, between the initial hour budget and actual consumption. This table must be factual, without commentary, without justification -- just numbers.

Example for a public facility rehabilitation project, fixed fees of 95,000 EUR excl. tax:

A consumption rate of 155% in the PRO phase is an indisputable signal. But the figure alone isn't enough: you need to explain why.

Causal analysis: what caused the overrun?

The project owner will accept an amendment if they understand that the overrun isn't due to poor internal management, but to factors external to the initial scope. Acceptable causes fall into three categories:

1. Program modifications by the project owner: addition of rooms, change of use, modification of floor areas, new functional requirements communicated after validation of the previous phase.
2. Regulatory changes: evolution of the RE2020 (French energy regulation), new accessibility standards, requirements from Heritage Architects (ABF) not anticipated in the brief, unfavorable opinion from a safety commission requiring a redesign.
3. Unforeseen technical constraints: asbestos survey revealing more extensive contamination, geotechnical studies requiring a change in foundation system, discovery of uncharted underground utilities.

For each identified cause, quantify the impact in hours. "The program modification from March (addition of 120 m2 of community rooms) generated 85 additional hours in the PRO phase: plan revisions, structural load recalculations, update of architectural specification documents."

Supporting documents: the traceability that makes the difference

The third pillar is the evidence file. Each additional hour claimed must be traceable to a documented event. Here are the documents to compile:

• Meeting minutes mentioning modification requests
• Emails from the project owner or brief writer approving the changes
• Amended service orders
• Timestamped time records by team member and by phase
• Internal cost impact notes (estimated time vs. actual time spent)
• Comparative plans before/after modification (version overlay)

Key takeaway: The strength of an amendment case lies not in its volume, but in the causal link between each modification request and its measurable impact in hours. A well-structured 5-page file is worth more than a 40-page document without a connecting thread.

Template for presentation to the project owner

Here is a template for an amendment request letter, to be adapted according to the contractual context:

Subject: Amendment request no. 1 -- Project management mission -- [Project name]

Dear Sir or Madam,

Within the framework of the project management mission entrusted to us by [contract no. XX dated DD/MM/YYYY], we wish to bring to your attention the impact of the program modifications that have occurred since the start of the [PRO/EXE] phase.

1. Assessment As of [DD/MM/YYYY], the [PRO] phase shows a consumption of [725] hours against an initial budget of [520] hours, representing an overrun of [205] hours (+[39]%).

2. Identified causes This overrun is directly attributable to the following modifications, approved by you:

• Modification of [DD/MM/YYYY]: [description -- e.g., addition of 120 m2 of community rooms] -- Estimated impact: [85] hours
• Modification of [DD/MM/YYYY]: [description -- e.g., change of heating system following RE2020 update] -- Estimated impact: [65] hours
• [Other modifications]

3. Supporting documents enclosed

• Time records by phase and by team member
• Meeting minutes no. [X, Y, Z] mentioning the modifications
• Correspondence dated [DD/MM/YYYY] approving the program changes

4. Request In accordance with [Article 14 of the CCAG-PI / Clause XX of the contract], we request an amendment in the amount of [XX,XXX] EUR excl. tax, corresponding to [XXX] additional hours valued at the contractual hourly rate of [XX] EUR/h.

We remain at your disposal to discuss this at our next progress meeting.

This template works for both public and private contracts. The key is the structure: factual assessment, documented causes, quantified request.

The 3 key moments to initiate the amendment discussion

Timing is critical. Too early, the request seems premature and the project owner dismisses it. Too late, the work is done and the negotiating leverage is gone. Three situations justify initiating the discussion immediately.

As soon as the consumption rate exceeds 70% at mid-phase

If you've consumed 70% of your hour budget when the phase is estimated at only 50% progress, the mathematical projection is clear: you'll finish at 140% of budget. This is the moment to alert the project owner -- not yet to request an amendment, but to put the issue on the table.

A factual message is enough: "We wish to inform you that the APD phase shows a consumption rate of 73% for an estimated progress of 52%. We are analyzing the causes of this variance and will follow up with a detailed note at the next meeting."

This early alert has two benefits: it demonstrates your management rigor, and it psychologically prepares the project owner for a potential amendment request. A project owner informed in advance accepts much more readily than one confronted with a fait accompli.

When a program modification is requested by the project owner

This is the most favorable case legally. As soon as a project owner requests a substantial program modification -- adding floor area, changing the building's purpose, new technical requirements -- the architect must cost the impact before beginning the work.

Concretely, this means responding to the modification request with a letter or email stating: "We have noted your request for [modification]. The estimated impact on our mission is [XX] additional hours, representing an amount of [XX,XXX] EUR excl. tax. We suggest formalizing this modification through an amendment before launching the corresponding studies."

Key takeaway: In public contracts, Article 14 of the CCAG-PI requires that additional services be subject to a prior service order. Starting work without this service order significantly weakens your position in case of dispute.

In the event of a regulatory change impacting the mission

Changes in standards (RE2020, accessibility, seismic, fire safety) can require a significant rework of studies. Unlike a program modification, a regulatory change doesn't result from a project owner's decision. But it impacts the mission in the same way.

In this case, the amendment file must demonstrate that the regulations in force at the time of contract signing have changed, and that this change generates a measurable increase in workload. Administrative case law recognizes this as an "unforeseen technical constraint" within the meaning of the CCAG-PI.

Checklist: supporting documents for your amendment file

Before submitting your amendment request, verify that your file contains all of the following elements:

• Comparative table of budgeted vs. consumed hours by phase, with the consumption rate and variance in absolute value
• Detailed time records by team member, by week and by phase, timestamped and signed (or from a digital tracking tool)
• Causal analysis note identifying each overrun factor and its quantified impact in hours
• Meeting minutes mentioning program modification requests, project owner decisions, or unforeseen events
• Correspondence (emails, letters) tracing exchanges related to modifications
• Amended service orders already issued or requested
• Comparative plans before/after modification (if plan revisions are involved)
• Regulatory references in the event of a standards change (law, decree, circular, with effective date)
• Cost calculation memorandum detailing the amendment amount calculation (number of hours x hourly rate, broken down by type of contributor)
• Formal request letter addressed to the project owner, summarizing the entire file (see template above)

Key takeaway: Build this file as you go, not retroactively. Real-time traceability of time spent and exchanges with the project owner is the key. A file reconstructed after the fact will always be weaker than one built continuously.

Turning the constraint into an opportunity: the amendment as a management tool

The amendment is often experienced as an admission of failure: "the project went off track, we need to ask for more money." This is an error of perspective. Properly managed, the amendment is a proactive management tool that strengthens the relationship with the project owner rather than weakening it.

Moving from reaction to anticipation

Firms that integrate time tracking into their management process no longer suffer overruns: they anticipate them. The weekly time report isn't a tool for monitoring team members -- it's a navigation instrument that allows you to see obstacles coming before crashing into them.

Concretely, this means:

• Budgeting hours from the moment of signing, drawing on historical data from comparable projects. To explore the method further, consult our guide on architecture project profitability.
• Tracking the consumption rate each week, with an alert threshold at 70% consumption for 50% progress.
• Documenting every modification to the program as soon as it occurs, systematically costing its impact.
• Anticipating budget overruns instead of discovering them after the fact.

Building trust through transparency

A project owner who receives a structured, quantified, documented amendment file doesn't see a contractor "asking for more money." They see a rigorous professional who masters their mission and communicates transparently. This perception fundamentally changes the negotiation dynamic.

Several public and private project owners have reported that the presentation of detailed time records by phase gave them confidence in the seriousness of the request. One of them summarized: "For once, I wasn't asked to take someone's word for it. I was shown the numbers."

What case law says

Administrative courts regularly rule on disputes relating to project management fee amendments. The case law trend is clear: the administrative judge examines the project manager's ability to demonstrate the reality and cause of the additional workload. A precise time record, correlated with documented modification requests, constitutes a decisive piece of evidence.

Conversely, a project manager who cannot produce any trace of their working time will struggle to convince the judge that the overrun is attributable to the project owner, even if this is objectively the case. The absence of proof doesn't mean absence of right -- but it makes that right very difficult to enforce.

Key figure: In disputes examined by administrative courts, project managers with structured time records prevail in a significantly higher proportion than those without. Time tracking is not just a management tool: it's legal insurance.

Justifying a fee amendment is not a matter of rhetoric or power dynamics. It's a matter of methodology and data. Architecture firms that structure their time tracking by phase, document program modifications in real time, and initiate the discussion at the right moment no longer suffer fixed-price contracts: they manage them. The amendment ceases to be an admission of weakness and becomes what it should always be: a normal contractual adjustment, based on facts, serving a healthy and lasting project owner-architect relationship.