Budget, scope and reporting in complex legal projects

A Comparison of Budget Models

Fixed price. A fixed price is suitable when the scope of work, assumptions, data availability and client obligations are clearly defined. Costs can be planned at an early stage; however, changes outside the agreed scope must be managed via a transparent change request.

Cap or cost ceiling. With a cap, invoicing is based on actual expenditure, but only up to an agreed limit. This model is suitable for projects where the overall direction is clear, but where individual work steps still involve some uncertainty. It is crucial to report at an early stage when and why expenditure is approaching the upper limit.

Phase budget or target corridor. Longer or dynamic projects can be broken down into clearly defined phases, each with its own budget and approval points. A target corridor can also provide a realistic range. This enables senior management to decide on scope, priority and the next investment after each milestone.

Retainer or performance-related component. Recurring project management can be remunerated via a retainer; a performance-related component is only added in suitable circumstances. Both models require a clear description of the services included and must not obscure which special tasks are to be charged for separately.

No model can replace a clear statement of work. Even a fixed price becomes unpredictable if assumptions and obligations to cooperate are missing. Conversely, time-based billing can be easily managed if a robust budget, warning thresholds and regular forecasts have been agreed.

Scope Control and Change Requests

The scope should not only specify the subject matter, but also the expected outcome of the work. A robust scope definition must first identify the jurisdictions, companies and business areas covered, as well as the specific deliverables. Equally important are the desired level of scrutiny, the key assumptions and the documentation on which the work is to be based. In addition, the topics that do not form part of the engagement must be explicitly stated. Obligations to cooperate, internal points of contact and decision deadlines form the organisational basis. Only once dependencies on tax advisers, auditors, banks or local counsel are identified can the workload be realistically managed.

A change request first describes what has changed from the agreed baseline and why the change is necessary. It then sets out which additional services are required or which existing ones are no longer needed as a result. On this basis, the implications for the budget, timetable and resources are made transparent. The client then explicitly decides whether the change should be implemented, deferred or accommodated by reprioritising within the existing budget.

Not every piece of new information automatically constitutes additional scope. Good project management distinguishes between a normal deepening of the task and a genuine extension of the mandate.

Status reporting and early warning indicators

Effective reporting links the financial status with technical progress. It shows which milestones have been achieved, which are next in line, and which decisions or information are currently missing.

In addition, it sets out the budget spent to date, the forecast up to the next milestone and the expected total costs. Risks, variances, change requests and contributions from external consultants are consolidated in such a way that the project management team not only receives figures, but is also able to make concrete management decisions.

Several early warning indicators have proven their worth in practice: one such indicator is a mismatch between the budget spent and the level of technical completion. Equally critical are a rising number of unplanned queries, repeated postponements of decisions or a growing reliance on documentation that was previously unavailable. Further warning signs include frequent scope changes, local counsel costs significantly higher than planned, an unusual concentration of effort on individual workstreams, and the repeated failure to meet milestones. Such developments should not only be reported but should also be accompanied by a recommendation regarding prioritisation, additional budget or a reduction in scope. The forecast should be updated whenever there is a significant change. A deviation is manageable if it becomes apparent at an early stage and triggers a decision.

Project Management Checklist

• Define objectives, deliverables and decision-making criteria.
• Document the scope, exclusions and assumptions in writing.
• Divide the project into phases and milestones.
• Agree on a RACI or similar accountability matrix.
• Select a budget model appropriate to the level of uncertainty.
• Set warning thresholds for the budget and schedule.
• Set up a change request process with approval authority.
• Plan internal and external resources according to seniority.
• Manage local counsel budgets and invoicing centrally.
• Agree on regular status and risk reporting.
• Report on forecasts through to completion rather than just actual costs.
• Upon completion, document lessons learnt for use in establishing standards and for future projects.

Budget baseline, assumptions and genuine management decisions

A budget is only robust if its assumptions are transparent. These include the expected volume of documents, the number of negotiation rounds, the availability of internal contacts, language and country-specific requirements, and the involvement of additional advisers. If any of these underlying factors change, more time should not be spent on the project without explicit approval. Project management must decide whether to adjust the scope, timeframe, quality or budget.

Good reporting therefore distinguishes between work completed, results achieved and remaining risk. A simple summary of hours worked does not show whether the transaction, investigation or contract implementation is actually making progress. A more useful approach is to combine budget utilisation, milestone status, outstanding decisions, new risks and a forecast through to completion. This not only documents deviations but also leads to a concrete management decision. Even a fixed-price contract requires change control. It protects the client within the agreed scope, not against every extension of the project. Conversely, a change request must not be used for every minor change in the work schedule. Clear materiality thresholds and a transparent justification of which new assumption or additional service triggers the adjustment are crucial.