Why a complex development needs central management

A Tuesday on site, in an illustrative scene any developer will recognise. The window-frame truck pulls in at seven in the morning, on the agreed date. The façade is not ready to take the frames, because the cladding stalled while a design revision was pending. The units go into a storage bay rented in a hurry. Nobody breached their own contract. Even so, the project has just lost two weeks and picked up a bill that belongs to no one.

Brazilian law settled whose bill that is back in 1964. In Article 29, the Real Estate Development Act (Law 4,591/1964) defines the developer as the party "coordinating and bringing to completion" the development and answering for delivery of the finished works "at a set time, price and conditions". The verb the legislators chose was coordinate. Six decades later, it names the hardest job in any complex project.

Each contractor proves competence. Only the whole proves delivery. Engineering, design, permits, landscaping, hospitality and technology run on a single schedule. Value is decided at the seams between those fronts, where no specialist has either the view or the mandate. This piece shows how a central intelligence that answers for the whole actually works, and when it does not earn its keep.

The law concentrates liability even when execution is scattered

Article 43 of the Development Act is the starting point. When the developer contracts delivery at a fixed time and price, it is civilly liable for execution and must compensate buyers if the works are not finished or are delayed without justification. It may then recover from the builder at fault. In practice, the fault may lie with a third party, but the bill reaches the developer first.

The same statute requires regular accountability: every three months, the buyers' representative committee receives a statement on the state of the works and how it tracks the agreed schedule. The inspector appointed by the committee or by the lender monitors the works but takes on no liability for quality or for the delivery date.

If liability sits with one party and execution is spread over dozens of contracts, someone has to turn partial reports into a coherent picture every quarter. Without that role, the statement becomes a collage of supplier versions. With it, the statement becomes a decision tool.

Each new contractor multiplies interfaces rather than adding them

There is a rarely discussed arithmetic behind fragmentation. When every contractor has to deal directly with every other, the number of interfaces follows n × (n − 1) ÷ 2. Five fronts produce 10 interfaces. Fifteen produce 105. If they all run through a coordination hub, the lines drop to 15, one per contractor.

This is elementary combinatorics, not a market statistic. And it explains why good specialists stumble more often at the seams than within their disciplines. Road compaction collides with the landscaping planting window. The utility asks for a new route once the drainage is already in.

Without central coordination, these clashes surface on site, already turned into rework. With it, they surface in the weekly review of the integrated schedule, while they are still a sequencing decision. The difference lies in who sees all 105 seams at once and has the authority to set their order.

Specialists deliver the parts. The value of the project is decided at the seams between them.

97

Who answers for what: the map of warranties and changes

Each discipline has its own legally responsible professional, recorded in a Technical Responsibility Record, known in Brazil as the ART. A large project carries dozens of them. What is usually missing is the map linking each piece of the works to its contract, its professional and its warranty.

The Civil Code shows why that map is worth money. Under Article 618, a contractor supplying materials and labour answers for five years for the soundness and safety of the works. But the owner loses that right if it does not sue within 180 days of the defect appearing. A crack logged with date, photo and responsible party is a right preserved. Lost in an email thread, it has lapsed.

The next provision of the Code deals with changes. A contractor building to an accepted plan may only charge extra for alterations made on the owner's written instruction, unless the owner was constantly on site, knew what was happening and never objected. Putting every change in writing before it is built gives each change a cost with an owner.

The shared digital model is the common score

The Brazilian state has an official roadmap for what coordinating design information means. Decree 10,306/2020 phased in BIM, building information modelling, on the most relevant federal works. Since 2021 that has covered clash detection between disciplines and model coordination. Since 2024 it has covered budgeting, planning and control of construction, with an as-built model. From 2028 it extends to post-construction maintenance.

The rule applies to federal works, not to private developments, but it is a useful public yardstick. The point is not the software. It is having one reference model and someone accountable for keeping it true. A model each discipline updates whenever it likes is just one more file in the project folder.

Interface risk and construction money both need an owner

Brazil's public procurement statute popularised a concept that also works between private parties: the risk matrix, a clause listing the events that could upset a contract's economic balance and stating who absorbs each one. On a private project with many contracts, each document tends to handle its own discipline's risks well and stay silent on those born next door.

Who pays when the soil survey reveals ground unlike the forecast and three fronts slip at once? If no contract answers, the developer pays. The fix is a project-level matrix, sitting above each contract's own, drafted before signature.

Money follows the same logic. Under the ring-fenced asset regime, Article 31-D of the Development Act requires the developer to preserve the funds needed for completion and move them through an account opened solely for that purpose. Every payment must therefore match measured physical progress. When each front measures on its own spreadsheet, with different criteria and dates, cash can look healthy while the works fall behind. A single measurement yardstick lets you compare what was paid with what was built before approving the instalment.

Separating who builds, who coordinates and who audits is what makes the number credible. Within the group, that separation runs across distinct companies: IncorpBuilding handles development engineering and the digital model, C&S Engenharia builds, and Valida Auditoria provides independent verification. What matters is the principle, which any developer can set up with its own suppliers.

Time is the most expensive cost and the least visible

Delay has three layers that stack. The first is escalation on the work still to be built. Brazil's National Construction Cost Index, published as series 192 in the Central Bank's Time Series Management System, rose 6.61% from September 2025 to August 2026. That equals 0.535% a month, compounded monthly. Every month pushed back makes the remaining works dearer.

The second layer is the site that keeps costing: local management, equipment, security, technical staff. The third is legal. Article 43-A of the Development Act allows delivery up to 180 days after the scheduled date, if the contract says so clearly and prominently. Beyond that, a buyer who is up to date and keeps the contract receives 1% of the amount paid for each month of delay.

A worked example: eight months of delay against two

The figures below are hypotheses built to show the mechanism, not market data. Only the escalation index comes from a public source. The two scenarios differ solely in total delay and in the cost of coordination.

Escalation is compounded: R$ 20 million times 1.00535 to the eighth power, minus the principal, gives R$ 872,000. Simple interest would give R$ 856,000. Under these hypotheses, coordination costs R$ 1.2 million and avoids about R$ 2.34 million in delay costs. That leaves a net difference of R$ 1.14 million, or 2.3% of the budget.

The stress test exposes the weak point: everything hinges on hypothesis G. If coordination cuts the delay to five months, it still wins, at R$ 2.64 million against R$ 2.91 million. At six months it narrowly loses, at R$ 2.93 million against R$ 2.91 million. How compensation is counted also matters. If counsel reads the months as running from the original date, the fragmented scenario rises to R$ 4.71 million and the advantage exceeds R$ 2.9 million.

After handover, coordination becomes operations

Projects that blend residences, club and hospitality do not end at the occupancy permit. Discovery Land Company, founded by Mike Meldman in 1994, describes private communities with golf, clubhouses and residences paired with hospitality. Its site does not detail its internal management, and we do not presume it. But the demand is plain: when the product is a continuous experience, the as-built model, warranties and manuals must reach operations intact. Whoever kept that map during construction is the natural candidate to hand it over.

When it does not pay off to have central coordination

A coordination structure is a fixed cost, and there are cases where it does not pay for itself. Three deserve attention before any decision.

• A simple project with one general contractor. If the builder already integrates the disciplines under a lump-sum contract, the interfaces stay inside a single contract. Another layer tends to duplicate reports without reducing conflicts.
• Coordination without a mandate. If the central team cannot approve measurements, set the sequence of fronts or demand written changes, it becomes one more reporting layer that consumes time and changes no decision.
• Small avoidable delay relative to cost. On short projects, with little work remaining or a loose schedule, the delay coordination avoids may not cover its cost. In the example, saving only two months no longer pays for the structure.

Checklist for structuring coordination on your project

1. Map every contracted front and count the interfaces between them, with the planning engineer.
2. Check that each discipline has an ART recorded and tied to the right contract, with each contractor's responsible professionals.
3. Require every design change to be put in writing before it is built, with legal counsel and design coordination.
4. Consolidate a project risk matrix that covers interface events, with legal counsel and engineering.
5. Set a single physical measurement yardstick and tie every payment to it, with the builder and the finance team.
6. Verify that the quarterly statement to the representative committee treats works and cash by the same criterion, with the independent auditor.
7. Plan the handover of the as-built model, warranties and manuals to operations, with the team that will run the project.

Frequently asked questions about central project management

Does the central manager replace the builder or the designers?

No. Specialists keep executing and remain technically accountable for their disciplines, each with its own ART. The central manager organises sequence, information, measurement and interface risk.

Does hiring central coordination shift the developer's liability?

No. The developer still answers to buyers, with the right to recover from the builder at fault. Coordination lowers the odds of the problem and improves the evidence of what happened.

Is BIM mandatory for private developments?

No. The adoption phases apply to the federal administration. The uses they describe, such as clash detection and construction control, are a reference for anyone who wants to coordinate with method.

What happens to the buyer when the works run late?

If the contract provides for it clearly and prominently, delivery up to 180 days after the scheduled date carries no penalty. Beyond that, a buyer who did not cause the delay may terminate the contract or, keeping it, receive 1% of the amount paid for each month of delay.

Are the simulator's results guaranteed?

No. The simulator gives an order of magnitude from reference parameters, and the example uses stated hypotheses. The real outcome depends on the contract, the work still to build and, above all, the mandate given to coordination.

Legal basis

• Law 4,591/1964, Articles 29, 31-A, 31-C, 31-D, 43 and 43-A (development, ring-fenced assets, inspection and delay).
• Law 10,406/2002, Civil Code, Articles 618 and 619 (soundness warranty and design changes in construction contracts).
• Law 6,496/1977, Articles 1 and 2 (Technical Responsibility Record).
• Decree 10,306/2020, Article 4 (BIM adoption phases on federal works).
• Decree 11,888/2024, Article 1 (BIM BR Strategy and definition of BIM).
• Law 14,133/2021, Article 6, item XXVII (definition of risk matrix).