A plot inside a masterplan is governed twice.

A plot inside a masterplanned community in a Gulf state is governed by the state's planning regime, as any plot is, and by a second regime the master developer administers: a design code that fixes what may be built and how it must look, a phasing plan that fixes when the roads, the utilities and the neighbouring phases arrive, a set of consents the master developer grants or withholds for each plot's design, programme and use, a community charge, and a set of covenants in the plot's title that bind every purchaser. The second regime has its own calendar and its own decision-maker, and the platform controls neither. A plot whose value depends on the plan's progress depends on the master developer building the road, the utilities and the neighbouring phases on a timetable the master developer can change, and a programme written as if the platform held the consent calendar has been written for a different plot. The value event on a masterplanned plot is the masterplan's own progress, and the platform's structure is designed around a decision-maker it does not control.

This note sets out what a masterplan is and why plots inside one are bought, the two regimes and how they stack, the design code and its consent, the phasing plan and its dependency, the master developer's standing and its incentives, the plot sale agreement's covenants, the community charge and the association, the programme under two calendars, the valuation of a plot on the plan's progress, the developer's reading, the lender's reading, the exit and the purchaser's reading of the plan, the onshore interface, a comparison, a worked plot as a type, cases, what each party holds, the sequence, questions, terms and what to read.

What a masterplan is

A masterplan is a large site, often state land or a single owner's, planned as one community by a master developer under a master plan the state approved, with zoning, infrastructure, phasing and a design code, and sold in plots to sub-developers who build within it. The master developer builds the infrastructure and the public realm, sells the plots, administers the code and the consents, and runs or hands over the community's management. Plots inside are bought because the plan brings what a raw parcel lacks: entitlement already granted at the plan level, infrastructure promised, a community whose value rises as it fills, and a location the plan created. The plan's promise is the plot's value, and the promise is the master developer's.

The two regimes

The state's planning regime grants the plan's overall approval and, for each plot, the building permit within it; the state's land registry records the plot's title and the covenants; the state's utilities connect on the state's terms. Above that, for every plot, the master developer's regime applies: the design code's requirements on use, height, density, setback, materials and appearance; the consent the master developer gives to each plot's design before the state's permit can be sought; the phasing plan's timetable for the plot's infrastructure; the covenants in the plot's title enforcing the code and the charge; and the community rules the association applies. The two regimes stack: the master developer's consent is a condition of the state's permit in practice, and the state's permit is a condition of building. A plot has two consent calendars and the platform holds neither.

Why the second regime is underweighted

The second regime is underweighted because it is private and its documents look like sales paperwork: a brochure with a code attached, a sale agreement with standard covenants, a phasing plan drawn as a marketing map. The state's regime has laws and offices and a permit with a stamp, and counsel reads it as law; the master developer's regime has a design review and a timetable, and the platform reads it as the seller's promises. But the code binds by covenant, the review is a condition of the permit, the phasing is the programme's critical path, and the master developer's decisions are enforced by the registry's record of the covenants. The second regime is law in effect, administered by a party with commercial incentives, and it is read with the weight of law and the scepticism of a counterparty.

The master developer's own programme

The master developer's programme is the plan's: infrastructure funded by plot sales, phases released as the market absorbs them, amenities built as the community fills. Its own lenders, its own state commitments and its own sales determine its pace, and the platform's plot is one of hundreds in a programme the master developer runs for the whole. A platform that reads the master developer's programme reads where its own plot sits in the master developer's priorities: a plot in a phase the master developer needs to sell is a plot whose road comes; one in a phase the master developer has deferred is a plot whose road comes when the phase does. The master developer's sales reports, where it publishes them, and its earlier phases' delivery against their plans are the platform's evidence.

The design code and its consent

The code is the master developer's document, amended by the master developer, applied by its design review, and a plot's design is consented or returned. The code fixes what the plot may be, which is often narrower than the state's zoning, and the consent process has its own time and its own discretion. A platform's programme that assumes a use the code permits and a design the review will pass has assumed the master developer's decision, and the master developer's review may take a season and may return the design twice. The code's amendment is the master developer's too, and a code amended after the plot's purchase changes what the plot may be.

The code's amendment

A code amended after the purchase changes the plot's permitted form, and the sale agreement says whether the master developer may amend and whether existing plot owners are bound. Most permit amendment and bind the owners, with a saving for designs already consented. A platform that has not yet obtained its design consent when the code is amended designs to the new code, and a programme that assumed the old code's density has assumed a number the master developer changed. The platform obtains the design consent early, because a consented design is the plot's entitlement under the second regime and an unconsented one is the code as it stands on the day.

The phasing plan and its dependency

The plan's infrastructure arrives by phase: the spine road, the utilities, the district cooling, the public realm, the neighbouring plots' development, each on the master developer's timetable. A plot in a later phase has its infrastructure promised for a date the master developer may move, and a plot's programme that assumes the road by year two is a programme whose year two is the master developer's. The plot sale agreement says what the master developer promises and what remedy the plot owner has if the promise slips, and most say little: a long-stop, a charge abatement, rarely a right to terminate, never damages of the scale the plot's programme suffers. The dependency is the plot's first risk, and it is a risk on a party that is not the platform's counterparty in any document the platform can enforce with effect.

The master developer's standing and incentives

The master developer is a state entity, a state-backed company, or a large private developer, and its incentives are the plan's whole: it sells plots in phases, builds infrastructure as sales fund it, amends the code as the market moves, and prioritises the phases that sell. Its standing is its capacity to finish, and a master developer whose sales slow builds slower. The platform reads the master developer as it reads a counterparty whose performance it depends on: its funding, its record on earlier phases, its other commitments, its relationship with the state. A plot in a plan whose master developer is well funded and has delivered three phases is a different asset from one whose master developer has sold the first phase and built the sales centre.

The plot sale agreement's covenants

The plot is bought under the master developer's sale agreement, which carries the covenants into the title: compliance with the code, payment of the charge, building within a period, no change of use without consent, the master developer's consent to transfer, sometimes a right of first refusal or a share of the resale gain, and the community rules. The covenants bind the platform and every purchaser, and they are the master developer's regime made permanent. The platform reads them as the plot's constitution, and a covenant requiring the plot to be built within a period is a forfeiture or a penalty if the programme slips, which the phasing plan may cause.

The community charge and the association

The plot pays a charge for the community's management, set by the master developer or by the association it forms, for the common areas, the security, the landscaping and the services. The charge is a cost of the plot for its life, its level is not the platform's to set, and its collection is secured by the covenants and in some states by a registered lien. The association, once formed, is the community's governance, with votes by plot, and the master developer usually retains control until a stated proportion is sold. The platform's plot is one vote, and the association's decisions on the charge, the rules and the common areas are the community's.

The programme under two calendars

The plot's programme runs on the state's calendar for the permit and the master developer's for the consent and the infrastructure, and the two are sequenced: the master developer's design consent, then the state's permit, then construction, which needs the infrastructure the phasing plan promises. A programme written on one calendar is wrong. The platform writes the programme with the master developer's review periods, its code's constraints and its phasing dates, with contingency for each slipping, and with the consequence of each slip on the platform's own term and on its lender's facility. The programme's critical path runs through the master developer's office, and the platform's project manager manages a party it cannot instruct.

The valuation of a plot on the plan's progress

The plot's value is the plan's promise discounted for the plan's progress: a plot in a delivered phase with the road built and neighbours occupied is worth the plan's price; one in a promised phase with the infrastructure on a drawing is worth the price less the risk. The valuer reads the phasing plan, the master developer's delivery to date and the plot's dependency, and values the plot accordingly, and a platform that carries a plot at the plan's price before the phase is delivered carries the master developer's promise as its own asset. The net asset value moves with the plan's progress, and the committee reads the valuer's assumption about the master developer.

The developer's reading

A developer appointed to build on the plot reads the code for what it may design, the review for how long and how often, the phasing plan for when it can connect, and the covenants for the building period. Its development agreement with the platform is drafted to the two calendars: its design obligations are to obtain the master developer's consent, its programme is conditional on the infrastructure, and its liability for delay excludes the master developer's. A developer that signed a programme assuming the road is a developer whose delay is the master developer's and whose contract says it is the developer's.

The lender's reading

A construction lender reads the plot's dependency on the master developer as its borrower's first risk and requires the infrastructure delivered, or the master developer's binding commitment with a date, as a condition precedent to drawdown for construction; it reads the covenants for the building period and the forfeiture; and it reads the master developer's consent to the charge over the plot, which the sale agreement requires. A lender that lends to build on a plot whose road is promised lends against the master developer's timetable.

The exit and the purchaser's reading of the plan

At exit the purchaser buys the plot and its building within the plan, and reads the plan's progress as the platform did at entry: the phases delivered, the community's occupancy, the charge's level, the association's state, the code's stability and the master developer's remaining obligations. A plan that delivered is a plan whose plots sell at the plan's price; one that stalled is a plan whose plots sell at what stands. The platform's exit price is the master developer's delivery, and the platform's structure recognises that it bought a share of a plan.

The onshore interface

The master developer's regime is private in form and public in effect: the code is a private document enforced by covenants the state's registry records, the consent is a private decision the state's permit process requires, and the charge is a private levy with a statutory lien in some states. Counsel in the state reads the state's law on masterplan communities, the registry's treatment of the covenants and the lien, the association's legal form and the master developer's statutory position, because in some states the master developer's powers are conferred by law and in others by contract, and the remedy for its failure differs accordingly.

By regime · by feature	The state's planning regime	The master developer's regime	Who controls
Entitlement	The plan's approval and the plot's permit	The code's permitted use and form	The state, then the master developer
Design	The building regulations	The code and the design review	The master developer
Consent calendar	The permit's period	The review's period and its discretion	The master developer, then the state
Infrastructure	The state's utilities on connection	The phasing plan's delivery	The master developer
Title	The registry's record	The covenants in the title	The registry, enforcing the master developer's
Charge	Municipal charges	The community charge	The master developer or the association
Transfer	The registry and the foreign ownership rules	The master developer's consent and any first refusal	Both
Remedy for delay	The state's process	The sale agreement's long-stop and abatement	The master developer's timetable

A plot, as a type

A platform buys a plot in the third phase of a masterplanned community in a Gulf state. Counsel in the state reads the sale agreement's covenants, the code, the phasing plan and the master developer's statutory position, and the platform reads the master developer's funding and its delivery of phases one and two. The phasing plan promises the third phase's spine road and utilities in eighteen months; the sale agreement gives a long-stop at thirty months with charge abatement. The programme is written on two calendars: design to the code, the master developer's review at four months with one return, the state's permit at three, construction conditional on the infrastructure, and a contingency of twelve months on the phasing. The developer's agreement makes its programme conditional on the infrastructure and excludes the master developer's delay from its liability. The construction lender's drawdown for construction is conditional on the road. The valuer values the plot at the plan's price less the phase's risk, and the committee reads the assumption. The road arrives at month twenty-two; construction begins; the building completes in year four; and the plot is sold in year six into a community whose third phase is occupied, at the plan's price, which the platform had discounted at entry.

The structure paper's page

The structure paper carries a page per masterplan the platform enters: the master developer's standing and record, the state's law on its position, the sale agreement's covenants, the code's constraints, the phasing plan's dates and the plot's phase, the review's periods, the association's form and the charge, the remedies for delay, the developer's and the lender's terms on the dependency, the valuer's basis, and the contingency. The page is written before the price and refreshed at each phase's delivery, and it is the page the purchaser's diligence reads at exit.

The second platform's reading

A manager's second platform is read against the first platform's masterplanned plots: whether the master developers delivered, whether the contingency held, whether the developers' and lenders' agreements carried the dependency, and whether the exits found the plans occupied. A first platform that bought a share of a plan and priced it as one is a platform whose investors accept the second's masterplan floor; one that bought a plan's promise at the plan's price is a platform whose investors ask which master developers the second will buy from. The master developer's record is the land door's evidence on this kind of plot, and the platform keeps it per plan.

Four cases, as types

A platform buys a plot in a later phase and writes its programme on the state's calendar, with construction starting at month twelve. The master developer's design review returns the design twice and takes nine months; the spine road arrives at month thirty; the developer claims for delay under a contract that did not exclude it; and the platform's term has consumed three years before the first pour.

A platform values a plot at the plan's price in a phase the master developer has not begun, and the net asset value carries it. The master developer's sales slow, the phase is deferred, the valuer marks the plot down at the annual valuation, and the committee reads the master developer's timetable for the first time.

A platform's plot sale agreement carries a covenant to build within three years and a first refusal for the master developer on resale. The phasing slips, the building period is breached by the master developer's own delay, and the master developer's forfeiture right and its first refusal are read together by the platform's counsel at the worst moment.

A platform reads the two regimes, the master developer's standing and the covenants before the price, writes the programme on two calendars with contingency, drafts the developer's and the lender's agreements to the dependency, and values the plot on the plan's progress. The plot was a share of a plan, and the platform priced it as one.

What each party holds

The platform holds the reading of the master developer, the sale agreement's covenants, the programme on two calendars and the contingency.

Counsel in the state holds the state's law on masterplan communities and the master developer's statutory or contractual position.

The developer holds its agreement drafted to the dependency.

The lender holds its conditions precedent on the infrastructure and its consent from the master developer.

The valuer holds the plot's value on the plan's progress.

The master developer holds the code, the review, the phasing and the covenants, and the platform holds none of them.

Where it surfaces

It surfaces at the sale agreement, in the covenants the platform cannot negotiate. It surfaces at the design review's first return. It surfaces at the phasing plan's first slip. It surfaces at the developer's delay claim. It surfaces at the lender's condition precedent on the road. It surfaces at the valuer's assumption about the master developer. It surfaces at the association's first charge increase. And it surfaces at exit, in the purchaser's reading of the plan's progress and the master developer's consent to transfer.

The cost of getting it wrong

A plot bought at the plan's price in a phase that stalls costs the platform the years, the developer's claim, the lender's deferral, the valuer's mark-down and the purchaser's discount, and none of it is recoverable from the master developer under a sale agreement that gave a long-stop and an abatement. The cost of reading the master developer, the covenants, the code and the phasing before the price is counsel's week and the platform's diligence on a counterparty it would diligence anywhere else; and the cost of the contingency in the programme is the honest price of a plot in a plan.

The committee's reading

The committee reads each masterplanned plot proposed for the master developer's standing and delivery record, the sale agreement's covenants, the code's constraints against the programme, the phasing plan's dates and the contingency, the developer's and the lender's agreements on the dependency, and the valuer's basis. It reads the plan's progress at each valuation against the phasing plan's promises. And it reads the association's decisions where they reach the plot's cost. A committee that reads the plot as a parcel reads the state's regime; one that reads it as a share of a plan reads the master developer.

A timeline, as a type

At design the statement admits masterplanned plots on a floor that names the master developer's delivery record and the phase's status. In month one the plot is proposed; counsel reads the sale agreement, the code, the phasing plan and the state's law; the platform reads the master developer's funding and its two delivered phases. In month three the price is agreed at the plan's price less the third phase's risk, and the programme is written on two calendars with contingency. In month nine the design review returns the design once and consents in month thirteen. In month sixteen the state's permit issues. In month twenty-two the road arrives, four months late and within the contingency, and the lender's construction drawdown begins. In year four the building completes. In year six the plot is sold at the plan's price into an occupied phase, with the master developer's consent to transfer obtained in the sale's conditions.

The sequence

1. The master developer is read as a counterparty: funding, delivery record, other commitments, statutory position.
2. The sale agreement's covenants, the code and the phasing plan are read with counsel before the price.
3. The programme is written on two calendars with contingency on the review and the phasing.
4. The developer's and the lender's agreements are drafted to the dependency.
5. The valuer is instructed to value on the plan's progress.
6. The exit is timed to the phase's delivery and the community's occupancy.

Questions a manager asks

Is a masterplanned plot safer than a raw parcel. Safer on entitlement and location, riskier on dependency; the two are priced differently and the statement admits each on its own floor.

Can the platform negotiate the covenants. Rarely; the master developer's sale agreement is a standard form across the plan, and the negotiation is on price and phasing dates, not the code.

What remedy for the master developer's delay. What the sale agreement gives, which is a long-stop and an abatement; the platform's real remedy is contingency and the price it paid.

Does the master developer's consent to transfer affect the exit. Yes; the purchaser needs it, and a first refusal or a resale share in the covenants is a term of the exit price.

How is the master developer's standing diligenced. Its accounts, its delivery of earlier phases, its funding commitments, its relationship with the state, and the state's law on what happens if it fails.

Who sits on the association. The plot owners by vote, with the master developer's control until the sale threshold; the platform's vote is one plot's.

Terms used

Masterplan: a large site planned as one community under a master developer's plan approved by the state.

Master developer: the party that builds the infrastructure, sells the plots, administers the code and controls the phasing.

Design code: the master developer's rules on each plot's use, form and appearance, applied by its design review.

Phasing plan: the master developer's timetable for infrastructure and phases, which the plot's programme depends on.

Covenants: the obligations in the plot's title enforcing the code, the charge and the master developer's consents.

Two calendars: the state's permit process and the master developer's consent and phasing, which the programme must sequence.

What to read

The master developer's sale agreement and its covenants; the design code; the phasing plan and the delivery record; the state's law on masterplan communities, the registry's treatment of the covenants and the association's form; the developer's and the lender's agreements on the dependency; the valuer's basis. On this site, the access, worked and developer rooms under Land.