Event Schedule in Public Works: 10 Payment-Stage Precautions

Learn how to develop an event schedule for public works, define payment stages, and avoid improper unit-based measurement under lump-sum regimes.

Check it out!

The event schedule is the instrument that converts a construction scope into verifiable physical events to which payment percentages are assigned. In contracts procured on a lump-sum basis, it is not merely an alternative presentation of the schedule: it is a contract-engineering instrument that connects the Work Breakdown Structure (WBS), physical-financial schedule, estimate, progress measurement, and criteria for releasing payments.

Under Law No. 14.133/2021, this logic is especially relevant to lump-sum contracting, turnkey contracting, semi-integrated contracting, and integrated contracting. Under these regimes, measurement and payment should be associated with completion of stages in the physical-financial schedule linked to performance targets, rather than simply multiplying executed quantities by unit prices. A poorly structured event schedule can therefore distort the very execution regime selected.

Brazil’s Federal Court of Accounts (TCU) examined this topic in greater depth in the 2026 guide Cost Engineering in Public Works — A Guide of Questions and Answers. The document presents ten precautions for developing an event schedule and relates payment milestones to execution sequence, contractor financial capacity, physical integrity of the works, retention through acceptance, indirect costs, and the estimator’s responsibilities. This article turns those guidelines into a method applicable to public-works planning and inspection.

What is an event schedule in a public works project

The event schedule connects planning, scheduling, measurement, and payment and should therefore be understood within the broader architecture of procurement controls. See What the TCU reviews in construction and engineering services procurement.

The event schedule organizes the contracted scope into events or stages measured by completion, assigning each one a share of the lump-sum price. Its purpose is to enable the Administration to recognize useful and verifiable physical progress before releasing the corresponding payment.

The logic differs from measurement by unit quantities. Under unit-price contracting, payment is formed from the units actually executed: cubic meters, square meters, tonnes, installed units, or other quantities. Under lump-sum contracting, the focus of measurement is the completed stage, according to the structure established in the physical-financial schedule and procurement documents.

This distinction does not eliminate quantities, cost compositions, or unit prices from planning. They remain essential for developing and analyzing the estimate. What changes is how the contract converts physical execution into entitlement to payment.

For this reason, a technically useful event schedule needs to answer four questions:

what physical result characterizes each stage;
how much each stage represents in the lump-sum price;
which conditions must be satisfied for it to be considered complete;
which evidence allows inspection to recognize completion objectively.

O artigo sobre lump-sum versus unit-price contracting explores the difference between these two execution and measurement logics in greater depth.

Event schedule, physical-financial schedule, and WBS are not the same thing

The three instruments are related but serve different functions.

The WBS decomposes the scope into deliverables, work packages, and manageable components. The schedule organizes activities and dependencies over time, enabling analysis of precedence, critical path, constraints, and start and finish dates. The event schedule selects, within this architecture, the physical milestones that can function as measurement and payment events.

Instrument	Primary question	Unit of analysis	Primary use
EAP	Into which parts will the scope be decomposed?	Deliverables and work packages	Scope and control
Cronograma	When and in what sequence will each activity occur?	Activities, durations, and dependencies	Schedule and planning
Physical-financial schedule	How does physical progress relate to cash disbursement over time?	Stages, periods, and values	Financial planning
Event schedule	Which completed physical result creates entitlement to a given payment?	Verifiable events or milestones	Measurement and payment

The event schedule should arise from the same technical architecture that supports the estimate and schedule. Creating it in isolation after the rest of the planning is complete increases the risk of stages that do not represent execution logic or percentages that do not correspond to the costs actually associated with the work.

This integration is particularly important because the physical-financial schedule should not function merely as a disbursement curve. It needs to reflect the physical sequence the Administration intends to procure and control.

What Law No. 14.133 requires under lump-sum regimes

Article 46, paragraph 9, of Law No. 14.133/2021 establishes a structural rule for the execution regimes identified in that provision: procurement is based on a lump-sum price, and the measurement and payment system must be associated with stages of the physical-financial schedule linked to achievement of performance targets. The law prohibits remuneration driven by unit prices or referenced solely to the execution of quantities of unit items.

The practical effect is significant. It is not enough to call the contract “lump-sum contracting” and then measure each item during execution as though it were a unit-price schedule. The measurement method must be consistent with risk allocation and the economic logic of the selected regime.

TCU Decision 1,727/2025-Plenary examined an integrated contract and identified the inadequacy of “unitizing” payment criteria when schedule items were paid without effective linkage to specific, individualized stages of the works. The Court stated that this model may circumvent the logic of the execution regime.

In 2025, TCU Decision 2,470/2025-Plenary revisited the issue by formally noting distortion of lump-sum regimes when measurement and payment clauses are based on item quantities and unit prices, contrary to Article 46, paragraph 9.

This makes the event schedule a central instrument for giving practical effect to the selected regime. It creates the bridge between the contract’s legal definition and the objective method for recognizing physical progress during execution.

To understand when each regime is appropriate, relate this analysis to the decision tree for execution regimes under Law No. 14.133.

The TCU’s 10 precautions when developing an event schedule

The TCU Cost Engineering guide organizes the main precautions into ten points. They should not be read as a bureaucratic checklist: together, they form a measurement architecture intended to balance verifiability, cash flow, incentives to complete useful stages, and protection of the Administration.

1. Follow the logical execution sequence

Events need to respect the project’s construction logic. A stage should not be positioned merely because it is financially convenient; it needs to correspond to the order in which the work can technically occur.

This requires observing predecessors and successors and, especially, the critical path. If a foundation must be completed before the structure can proceed, the event architecture should reflect that dependency. Likewise, systems that depend on energization, watertightness, integrated testing, or area release need to be positioned according to their actual prerequisites.

When the payment sequence is disconnected from the execution sequence, distortions arise. The contractor may receive a significant payment for elements that do not create useful progress while stages critical to functionality remain incomplete.

The event schedule also needs to reflect the project’s construction strategy. In linear projects or those with multiple work fronts, the same discipline may be divided by segments or sectors, provided each division has technical usefulness and is verifiable.

2. Define discrete, easily verifiable stages

A good event has a clear boundary. Inspection should be able to determine whether it is complete without reconstructing the project’s entire quantity takeoff record.

The TCU suggests that, in vertical buildings, division may follow floors, while horizontal or extensive works may use sections, sectors, or segments. The specific choice depends on the project typology, but the principle is the same: the milestone needs to be physically identifiable.

Overlapping stages are particularly problematic. If the same physical element contributes simultaneously to two payment events, the risk of double measurement increases. If an event groups work without a clear technical relationship, it becomes difficult to define the point of completion.

Verification may combine visual inspection, photographic records, testing, certificates, quality reports, and acceptance documents. The construction progress measurement report should then record the evidence demonstrating completion of the event rather than merely reproducing spreadsheet percentages.

3. Align payment stages with the contractor’s financial capacity

The event schedule is also a cash-flow decision. Events that are too extensive may require the contractor to finance labor, materials, equipment, and subcontracting for an excessive period before reaching the milestone that releases payment.

The TCU recommends aligning the value and duration of stages with the contractor’s expected financial capacity and the economic-financial qualification requirements established in procurement.

An inconsistency arises when the Administration requires net worth or financial ratios compatible with a certain project size but creates milestones that force the company to sustain much greater financial exposure. In that case, the payment structure may restrict competition, increase bid prices, or raise the risk of demobilization and delay.

The opposite problem also exists: excessively small payment stages reduce the incentive to complete useful results and may improperly push a lump-sum contract toward a unit-price logic.

Therefore, event-schedule granularity should find a balance among verifiability, financing capacity, and integrity of the execution regime.

4. Pay only for fully completed events

Under the lump-sum regimes addressed by the TCU, the payment reference should be the completed event. Inspection should not convert a performance milestone into a sequence of percentage measurements merely because part of the work within that event has been executed.

If an event was defined as “ground-floor structure completed,” measurement needs to verify the established result for the structure. Paying 37%, 52%, or 84% of that event because some components have already been executed dissolves the boundary that justified creating the milestone.

When a stage takes too long to complete and this threatens cash flow, the problem usually lies in the design of the event schedule. The solution is generally to decompose the event in advance into smaller, technically discrete and verifiable milestones, rather than turning inspection into improvised unit measurement.

This rule needs to be clear before procurement. Changing granularity after award may affect equal treatment, distribution of cash flow, and the assumptions bidders used to develop their proposals.

5. Avoid splitting activities that may deteriorate

Not every technically separable activity should become an independent payment event. The TCU draws attention to work whose utility or integrity depends on immediate continuity with subsequent activities.

The classic example is a concrete structure. Formwork, reinforcement, and concreting may appear separately in the detailed estimate, but splitting them into independent payment events may leave components exposed if execution is interrupted.

The same reasoning applies to excavations that need stabilization, waterproofing that depends on mechanical protection, cables installed before closure and identification, piping before testing, systems installed without commissioning, or sensitive equipment stored under temporary conditions.

Whenever possible, the event should represent a stable or functional physical condition. This rule reduces the risk of the Administration paying for a portion that loses economic value or requires rework if the contract is interrupted.

6. Keep physical execution ahead of financial disbursement

The event schedule should not disproportionately front-load profit. If early stages concentrate payments far above the cost and physical value actually incorporated into the project, the contract creates an inappropriate economic incentive.

The practice known as front loading shifts remuneration toward the beginning of execution. In addition to weakening the relationship between physical and financial progress, it may increase the Administration’s exposure if the contractor later abandons the project.

The event architecture should seek to maintain reasonable financial protection: the amount paid should not advance artificially beyond the physical result delivered. This does not mean withholding amounts due without basis, but assigning percentages consistently with the cost structure and project sequence.

This control is more robust when the event schedule is derived from the public works estimate and the stage-by-stage cost record, rather than being distributed through arbitrary percentages.

7. Include provisional and final acceptance events

Physical completion of productive work fronts does not automatically close all contractor obligations. Testing, final documentation, correction of outstanding items, as-built documentation, commissioning, cleaning, demobilization, and acceptance requirements remain.

For this reason, the TCU guide recommends considering specific events for provisional and final acceptance. In the Appendix 2 example involving a 60-meter bridge, 9% of the total value is associated with acceptance: 4.5% provisional and 4.5% final.

This percentage is a technical example from the guide, not a rate established by Law No. 14.133. Elsewhere, the TCU mentions that ranges on the order of 5% to 10% may be evaluated depending on the case. The specific definition should be proportional to the residual scope, handover obligations, and the risk that the Administration is left with physically advanced works that are not ready for acceptance.

This logic also connects with performance bond with a step-in clause: both mechanisms address nonperformance risk, but they have different natures. The event schedule controls payment flow; the contractual guarantee covers obligations under the terms set out in the instrument and legislation.

8. Allocate indirect and ongoing costs across productive stages

Site administration, site maintenance, protective equipment, operational support, and other ongoing costs do not necessarily need to become isolated monthly events in a lump-sum contract.

The TCU recommends allocating indirect and ongoing costs across productive stages when this structure is compatible with the procurement. The reason is to avoid creating recurring payments disconnected from physical delivery.

If monthly site-administration remuneration occurs regardless of progress, a slowing project may continue generating disbursements without proportional results. Distributing these costs among events helps preserve the link between payment and progress.

This does not mean hiding costs. The estimate record must continue to identify and justify these amounts. Allocation occurs in the payment system, not in the transparency of price formation.

9. Align the event schedule with measurement frequency

Article 92, paragraph 5, of Law No. 14.133 provides that, in construction and engineering services contracts, whenever compatible with the execution regime, measurement will be monthly. This rule needs to be read together with Article 46, paragraph 9, which links certain lump-sum regimes to completion of stages and performance targets.

In practice, the contract may have monthly inspection and measurement-processing cycles without turning every event into an automatically payable monthly installment. If no specified milestone was completed during the period, the mere passage of a month does not create a physical result that does not exist.

Likewise, more than one event may be completed in the same period. Planning should make explicit how monthly measurement relates to physical milestones and how periods with no completed event will be treated.

This alignment needs to be included in the execution model and payment conditions. The Terms of Reference for construction that do not turn into change orders should make the system sufficiently clear before bidding, avoiding a rule that is only constructed during execution.

10. Assign development to professionals who understand estimating and planning

The TCU associates development of the event schedule with the estimator because of the mathematical relationship among stages, costs, and the lump-sum price. This assignment does not mean the instrument should be produced in isolation by a single discipline.

In practice, quality improves when professionals from estimating, planning, design, execution, contracts, and inspection participate. The estimator ensures that percentages align with price formation; the planner validates sequence and duration; designers check the technical integrity of packages; inspection tests verifiability and evidence criteria.

The result should be a document that can be defended simultaneously from four perspectives: engineering, schedule, cost, and contract.

The biggest mistake: turning a lump-sum contract into unit-price measurement

A contract may have been formally classified as lump-sum contracting and still operate in practice as a unit-price contract. This occurs when each spreadsheet component becomes a measurement item, with payment calculated from quantities executed during the period.

The problem is not merely terminological. The regimes allocate risks differently. Unit-based measurement transfers quantity variations to the Administration that, depending on the regime, should be covered by the lump-sum price and the contractor’s assumed responsibility.

TCU Decision 1,727/2025-Plenary uses the term unitization to describe payment criteria disconnected from achievement of specific stages. TCU Decision 2,470/2025-Plenary records cases in which payment clauses based on quantities and unit prices distorted lump-sum, integrated, or semi-integrated contracting.

The event schedule works as an antidote to this distortion when it contains:

stages identifiable in the schedule;
a defined physical result;
a previously assigned percentage;
an objective completion criterion;
acceptance evidence;
a clear rule for contract changes.

Inspection stops asking “how many units of this item were executed?” as the primary payment criterion and instead asks “was the specified contractual event fully completed and accepted?”.

Granularity: neither tiny events nor financially unworkable milestones

The central challenge of an event schedule is defining the right level of decomposition.

If the Administration creates hundreds of micro-events, each corresponding to a small portion of work, the instrument loses its management function and begins to resemble a unit-measurement spreadsheet. Inspection must also process a large volume of checks, records, and approvals, increasing administrative cost.

At the opposite extreme, if the Administration creates only a few very large events, the contractor may perform months of work before reaching a payment milestone. Cash flow becomes excessively burdensome and may be priced into bids.

Appropriate granularity depends on five factors:

expected event duration;
associated financial value;
ease of inspection and acceptance;
physical stability of the completed result;
usefulness of the milestone to overall project progress.

The TCU example helps illustrate how relative this choice is. On a 60-meter bridge, “substructure,” “intermediate structure,” and “superstructure” may be manageable stages. On a 600-meter bridge, the same categories would probably need to be subdivided into segments to avoid long periods without payment.

Therefore, there is no universal number of events. What is required is consistency among project size, execution strategy, and inspection capacity.

How the event schedule affects contractor working capital

A lump-sum price does not eliminate the need for financing during execution. The company mobilizes personnel, purchases materials, hires suppliers, maintains equipment, and incurs costs before measurement.

The greater the interval between private disbursement and the event that releases payment, the greater the working-capital requirement. This need may appear in the bid price through financial cost, risk, or a reduction in the number of companies able to compete.

For this reason, the Administration also needs to analyze the event schedule from a market perspective. A milestone may be technically perfect yet economically inappropriate if it requires the contractor to finance an amount incompatible with the established economic-financial qualification structure.

This analysis does not mean creating improper advance payments. It means structuring intermediate events that correspond to real physical results and reduce financial exposure without abandoning lump-sum logic.

A completed event needs acceptance criteria

The expression “100% complete” is useful only if objective criteria exist for recognizing completion.

An event such as “electrical installations completed” is insufficient when the scope includes multiple panels, circuits, tests, and interfaces. Inspection needs to know whether completion depends only on physical installation or also on labeling, testing, parameterization, energization, and documentation.

The event schedule should be read together with specifications, design narratives, drawings, and acceptance criteria. For each relevant milestone, it is advisable to define:

physical scope covered;
exclusions and interfaces;
required documents;
applicable inspections;
required tests;
parties responsible for verification;
record that formalizes acceptance.

This traceability reduces disputes in measurement and improves the quality of public works inspection.

Event schedule and indirect costs: how to avoid payment without progress

Indirect construction costs are real and need to be estimated. The risk lies in turning the analytical cost structure into an automatic payment structure.

Site administration, site facilities, safety, support, and contractor supervision may be required for several months. If each amount is paid merely because time has passed, the economic incentive becomes disconnected from physical results.

One solution is to allocate these costs across productive events according to documented criteria. When a stage is completed, its value then includes the proportional share of indirect costs needed to produce it.

This approach needs to be compatible with the reference estimate, the accepted bid, and any specific tender rules. The objective is not to eliminate visibility of indirect costs, but to prevent the measurement mechanism from turning them into remuneration disconnected from production.

Provisional and final acceptance as payment events

Closeout is a critical phase because the works may appear visually “complete” while still containing outstanding items that prevent operation, safety, maintenance, or formal acceptance.

By reserving an amount for provisional and final acceptance, the event schedule creates an economic incentive for the contractor to close the documentary and technical cycle. Depending on the scope, these events may require:

correction of nonconformities;
integrated testing and commissioning;
final cleaning;
demobilization;
operation and maintenance manuals;
as-built documentation;
closeout ART, RRT, or TRT where applicable;
team training;
delivery of warranties and certificates;
acceptance by authorities or utilities;
acceptance certificate.

The reserved percentage needs to reflect the importance of these obligations. Automatically copying the 9% from the TCU example would be as inappropriate as adopting any percentage without a technical basis.

The central point is that the contract should not release 100% of the price while essential deliverables remain outstanding.

Event schedule example: 60-meter bridge from the 2026 TCU Guide

Appendix 2 of the Cost Engineering guide presents a didactic event-schedule example for a 60-meter bridge with a total value of BRL 3,456,000. The structure shows how the lump-sum price can be distributed across major execution stages.

Stage	Percentage of lump-sum price
Preliminary services	3,85%
Mobilization	0,90%
Site setup	2,95%
Bridge — substructure	33,25%
Detailed design	4,23%
Substructure	29,02%
Bridge — intermediate structure	14,51%
Bridge — superstructure	32,52%
Superstructure	27,02%
Approach slab	5,50%
Finishes	4,44%
Complementary services	2,43%
Project acceptance	9,00%
Provisional acceptance	4,50%
Final acceptance	4,50%
Total	100,00%

The didactic value of this example is not in the individual percentages. It lies in the logical structure: the Administration can see which physical blocks represent the price, how much remains retained through acceptance, and how each stage relates to completion of the scope.

The TCU itself emphasizes that granularity would change if the bridge were much larger. This point is decisive: an event schedule is not a standard table to copy; it is a scope-specific model.

Workflow for developing a technically defensible event schedule

A practical sequence can be structured in eight steps.

Workflow for developing the event schedule from project scope, estimate, and schedule

1. Consolidate scope and designs

An event schedule does not correct an undefined scope. Before modeling milestones, it is necessary to understand the systems, construction elements, interfaces, constraints, and planned deliverables.

2. Estruturar a WBS

Decomponha o objeto até um nível que permita agrupar serviços em pacotes coerentes. A WBS é mais detalhada que o eventograma; nem todo pacote precisa virar evento de pagamento.

3. Link the estimate to the work packages

Percentages should not be invented. Each event needs to be traceable to the estimate record that explains how much of the lump-sum price is associated with its execution.

4. Integrate with the schedule

Validate sequence, critical path, predecessors, constraints, and expected duration. Events should be achievable at intervals compatible with expected cash flow.

5. Select verifiable results

Group work that forms a stable or functional condition and can be objectively inspected.

6. Define acceptance criteria

For each event, describe evidence, testing, documentation, and the condition for completion.

7. Test the financial profile

Compare cumulative physical progress with cumulative payments. Identify early concentration of remuneration, long intervals without disbursement, or milestones incompatible with reasonable financial capacity.

8. Incorporate the event schedule into procurement documents

The instrument should align with the schedule, estimate, execution model, measurement criteria, inspection, and payment clauses. An isolated table attached to the tender documents does not resolve inconsistencies among documents.

How to incorporate the event schedule into the Terms of Reference and tender documents

The event schedule needs to be contractually operational. This requires more than a list of stages and percentages.

The procurement documents should preferably establish:

unambiguous identification of each event;
associated percentage or value;
completion criteria;
minimum evidence;
responsibility for verification;
measurement frequency;
treatment of events completed in the same period;
rule for periods with no completed event;
relationship with provisional and final acceptance;
procedure for rescheduling resulting from contract changes.

O scope execution model is one of the places where this dynamic needs to be aligned with deadlines, work orders, measurement, and responsibilities.

A3A Engenharia works on structuring Terms of Reference for construction and engineering services and Technical Planning for Engineering Procurement, integrating requirements, estimating, risks, measurement, and acceptance criteria.

How to handle contract changes without undermining the event schedule

A change in scope or quantity may alter the relative weight of stages. If the contract undergoes additions, deletions, or material reconfiguration, keeping the original percentages without analysis may distort the relationship between payment and progress.

The TCU recommends that material changes be reflected in the physical-financial schedule and the event schedule, preserving the contract’s economic consistency. The review should assess:

which events were affected;
which costs were added or removed;
which milestones need to be split or consolidated;
whether the critical path changed;
whether cash flow is affected;
whether the change creates spreadsheet-gaming or schedule-gaming risk;
how to maintain traceability between the original and revised versions.

The review cannot be used to retroactively convert a lump-sum regime into a unit-price regime. The revised structure must remain linked to results and be technically justified.

A technical analysis of public-works contract amendments should incorporate this verification when an amendment changes stages, schedule, or the disbursement structure.

How inspection should use the event schedule

During execution, the event schedule functions as a payment-decision matrix. For each event, inspection should compare the contracted condition with field evidence.

A consistent routine includes:

identifying the events planned for the period;
verifying full physical completion;
checking tests, documents, and records linked to acceptance;
recording outstanding items that prevent completion;
updating the schedule and forecast of future events;
formalizing measurement only for accepted events;
maintaining a history of revisions and cumulative payments.

Inspection must also resist pressure to “measure something” merely because the month has ended. If the lump-sum contract was properly structured around events, an incomplete milestone remains incomplete. If this becomes recurrent, it is necessary to investigate whether there is contractor delay, an Administration-caused impediment, or a structural flaw in the definition of the stages.

The event schedule does not replace quantity control

The prohibition on unit-based remuneration under certain regimes does not mean abandoning quantities.

Quantities remain necessary to:

prepare the reference estimate;
assess design consistency;
analyze productivity;
control critical materials and services;
verify scope changes;
identify execution deviations;
support amendments and rebalancing where applicable.

The difference lies in function. Quantity is an engineering and control datum; the event is the contractual payment trigger.

This separation avoids a false dichotomy. A well-inspected lump-sum contract can maintain detailed quantity control without turning every recorded quantity into a payable item.

Event schedule and progressive planning

In complex projects, the required level of detail may change over the lifecycle. The 2026 TCU Guide recognizes progressive elaboration: near-term stages may be planned at a greater level of detail, while future work remains at higher WBS levels until additional information becomes available.

This flexibility does not authorize unilateral changes to the contract’s economic basis. Progressive detailing must respect the milestones, results, risks, and rules established in procurement.

The distinction is important: detailing an already-contracted event is not the same as creating a new payment logic after bidding.

When detailing materially changes cash flow, risk allocation, or acceptance conditions, the Administration needs to assess contractual effects and preserve equal treatment and economic-financial equilibrium.

Ten common errors when developing an event schedule

The TCU criteria reveal recurring failures:

copying another project’s event schedule without adapting typology, duration, and risks;
turning every estimate line item into a payment event;
creating stages that are too long for the contractor’s expected financial capacity;
allowing partial event payment without a pre-established rule;
splitting work that must be completed in sequence to avoid deterioration;
concentrating margin and remuneration at the beginning of the contract;
releasing nearly all of the price before acceptance, testing, and final documentation;
paying ongoing costs merely due to the passage of time, disconnected from progress;
creating percentages without traceability to the estimate;
changing granularity during execution without assessing equal treatment, risk, and cash flow.

These failures are not independent. A poorly designed event often creates several problems at once: disputed measurement, pressure for partial payment, need for rescheduling, and difficulty identifying responsibility when delays occur.

Technical checklist before approving the event schedule

Before incorporating the document into the process, the team can test each event with objective questions.

Check	Control question
Sequence	Does the event respect predecessors, successors, and the critical path?
Scope	Is it clear what is and is not part of the event?
Verifiability	Can inspection objectively recognize completion?
Stability	Can the result remain intact if the project is interrupted?
Duration	Is the expected interval until payment financially reasonable?
Value	Does the percentage derive from the cost record rather than arbitrary allocation?
Progress	Does the profile avoid financial payment artificially running ahead of physical progress?
Acceptance	Are tests, documents, or inspections clearly defined?
Handover	Do sufficient financial incentives remain through final handover?
Changes	Is there a rule for reviewing events if the contract changes?

If several answers depend on later interpretation, the event schedule is not yet ready to function as a contractual basis.

Relationship among event schedule, risk, and stoppage

The payment structure influences the parties’ behavior throughout the project. An event schedule that front-loads remuneration, leaves long periods without payment, or allows payments for incomplete results can amplify the impact of delays and stoppages.

In the event of interruption, the Administration needs to know how much of the scope has physical utility, how much has already been paid, and which deliverables remain necessary. Stable and verifiable events make this picture clearer.

This is one reason why event-schedule design should be addressed during procurement planning. The instrument is not merely a financial tool; it contributes to contractual resilience if execution does not follow the planned scenario.

O artigo How to write Terms of Reference for construction that do not turn into change orders shows how definition failures in the preparatory phase propagate into execution. The event schedule is one of the definitions that needs to be mature before tender publication.

Event schedule as a Cost Engineering deliverable

The 2026 TCU Guide places the event schedule within the Cost Engineering process because the document distributes the lump-sum price among physical stages. This distribution needs to be reproducible and auditable.

A development memorandum may record:

WBS used as the basis;
estimate and base date;
criteria for grouping work;
composition of each event;
percentage of allocated direct and indirect costs;
expected duration;
relevant dependencies;
acceptance criteria;
cash-flow assumptions;
justifications for acceptance events and retained amounts;
technical professionals responsible for development and review.

This memorandum transforms the event schedule from a “percentage spreadsheet” into an engineering document. It also facilitates revision when design, schedule, or estimate changes.

A Cost Engineering for construction and engineering services should jointly address quantities, cost compositions, cost structure, and payment logic when the selected regime requires stage-based measurement.

Final considerations

The event schedule is an integration instrument linking design, estimating, scheduling, contract management, and inspection. Its quality determines whether the lump-sum price will actually be measured by results or whether, during execution, the contract will be informally converted into a succession of unit-based measurements.

The ten precautions presented by the TCU form a coherent logic: respect execution sequence, create verifiable stages, balance working capital, pay for completed events, avoid deterioration, prevent excessive financial front-loading, retain an amount through acceptance, distribute ongoing costs, align measurement frequency, and assign modeling to professionals who understand estimating and planning.

The main conclusion is that the event schedule needs to be developed before procurement, integrated with the other documents. When its architecture is left to the execution phase, the contract becomes dependent on later decisions about one of the most sensitive points in the relationship between the Administration and the contractor: the moment when physical progress becomes payment.

A good event schedule does not seek to maximize retention or facilitate disbursement. It seeks to create a verifiable correspondence among physical result, economic value, and contractual entitlement to payment.

Technical references

[1] BRASIL. Lei nº 14.133, de 1º de abril de 2021. Public Procurement and Administrative Contracts Law. Brasília, DF: Presidência da República, 2021. Available at: https://www.planalto.gov.br/ccivil_03/_ato2019-2022/2021/lei/l14133.htm

[2] TRIBUNAL DE CONTAS DA UNIÃO. Cost Engineering in Public Works: A Guide of Questions and Answers. Brasília: TCU, 2026. Item 3.2.5, Chapter 7, and Appendix 2. Available at: https://portal.tcu.gov.br/publicacoes-institucionais/cartilha-manual-ou-tutorial/cartilha-engenharia-de-custos-de-obras-publicas-perguntas-e-respostas

[3] TRIBUNAL DE CONTAS DA UNIÃO. Acórdão 1.727/2025-Plenário. Reporting Justice: Minister Antonio Anastasia. Session of July 30, 2025. Case TC 022.299/2024-6. Available at: https://pesquisa.apps.tcu.gov.br/documento/acordao-completo/ACORDAO-COMPLETO-2692659.KEY/%2520/DTRELEVANCIA%2520desc%252C%2520NUMACORDAOINT%2520desc/0

[4] TRIBUNAL DE CONTAS DA UNIÃO. Acórdão 2.470/2025-Plenário. Reporting Justice: Minister Bruno Dantas. Session of October 22, 2025. Case TC 008.544/2025-5. Available at: https://pesquisa.apps.tcu.gov.br/documento/acordao-completo/%2A/NUMACORDAO%253A2470%2520ANOACORDAO%253A2025/DTRELEVANCIA%2520desc%252C%2520NUMACORDAOINT%2520desc/0

Frequently asked questions

What is an event schedule in a construction project?

It is the structure that divides the lump-sum price into verifiable physical events or stages, linking completion of results in the physical-financial schedule to release of payment amounts.

Is an event schedule the same as a physical-financial schedule?

No. The physical-financial schedule relates progress, time, and disbursement; the event schedule selects the physical milestones that function as measurement and payment events and assigns them percentages of the lump-sum price.

Under which regimes is the event schedule most important?

It is especially relevant under lump-sum regimes such as lump-sum contracting, turnkey contracting, semi-integrated contracting, and integrated contracting, in which Law No. 14.133 links measurement and payment to stages and performance targets.

Can an event that has not yet been completed be partially paid?

The TCU-recommended structure prioritizes payment for fully completed events. If a stage is too large and creates a cash-flow bottleneck, the solution should be to revise its granularity in advance, creating smaller, verifiable milestones instead of turning the lump-sum contract into improvised unit measurement.

Does Law No. 14.133 require every construction measurement to be monthly?

Article 92, paragraph 5, establishes monthly measurement whenever compatible with the execution regime. Under lump-sum regimes, this frequency needs to be reconciled with Article 46, paragraph 9, which links payments to completion of stages and performance targets.

What percentage should remain for provisional and final acceptance?

There is no universal statutory percentage. The 2026 TCU Guide uses 9% in the example of a 60-meter bridge and mentions reference ranges in certain contexts, but the actual value should be justified based on residual obligations, testing, documentation, and scope risks.

Who should develop the event schedule?

The TCU associates this responsibility with the estimator because of its mathematical connection to price formation. In practice, the work should integrate planning, design, execution, contracts, and inspection.

Why can unit-price measurement distort a lump-sum contract?

Because Law No. 14.133 establishes, for the regimes identified in Article 46, paragraph 9, a system associated with schedule stages and performance targets, prohibiting remuneration driven by execution of quantities of unit items.

Complementary technical materials