Joint Development Agreement for Developers in Malaysia: What to Lock Before Developing on Someone Else's Land

A developer can spend months testing a site before owning a single square metre of it. Concept plans are prepared. Consultants are appointed. Planning assumptions are modelled. Financing conversations begin. The landowner may be supportive throughout.

But goodwill is not project control.

If the joint development agreement only records the headline profit split and leaves access, approvals, title cooperation, financing permissions and exit mechanics vague, the developer can end up carrying the development risk without reliable control over the things needed to deliver the development.

For a developer, that is the central question in a joint development agreement: what must be contractually locked before substantial money is committed to somebody else's land?

First, make sure the deal is actually a joint development agreement

Labels are often used loosely. A landowner and developer may call an arrangement a "joint venture", "development agreement" or "joint development agreement" even though the legal and commercial mechanics are different.

A true joint development agreement usually involves both sides contributing something essential to the same development outcome. The landowner contributes the site and the cooperation needed to unlock it. The developer contributes development expertise, project management, capital or financing capability, and delivery. The parties then divide the agreed project economics, whether through units, revenue, profit, a guaranteed entitlement or a hybrid structure.

That is different from a more unilateral development-rights arrangement, where the developer is principally being granted the right to develop the land in return for an agreed consideration. If that is closer to your transaction, our guide to development rights agreements for developers in Malaysia addresses that structure specifically.

It is also different from an incorporated project joint venture where the parties use a special-purpose company and need shareholder-level governance. Where the project is being carried through a jointly owned company, see our guide to a joint venture shareholders agreement for land development. Our separate guide compares the two structures directly — see joint development agreement vs JV company.

The agreement should therefore be drafted from the actual project structure, not from the label on the front page.

What exactly is the developer being given control of?

A developer does not necessarily need title to the land on day one. It does, however, need enough contractual control to investigate, plan, obtain approvals for, finance and deliver the project.

That normally means mapping the developer's rights across the full project sequence rather than relying on a single clause saying it has "the right to develop". Depending on the project, the JDA may need to deal with:

• physical access for surveys, soil investigation and technical studies;

• appointment and instruction of planners, architects, engineers and other consultants;

• authority to prepare and manage planning and technical submissions;

• the landowner's obligation to sign documents that legally require the proprietor's involvement;

• site possession or access for enabling works once the relevant approvals and conditions are satisfied;

• project information and document custody;

• exclusivity so the landowner cannot grant competing development rights during the agreed period;

• marketing and sales authority where the project has reached the stage at which those activities are legally permitted; and

• the developer's ability to engage with project financiers within an agreed security framework.

Each right should have a beginning, a scope, conditions and an end. "Access to the land" before due diligence is not the same thing as possession for construction. Authority to submit a planning application is not the same thing as authority to charge, sell or transfer the land.

Verify the land before relying on the development opportunity

The commercial model can look attractive and still fail because the land itself cannot be used in the way the parties assumed.

Before substantial expenditure, the developer should verify the registered proprietor and title particulars and identify matters that may constrain the project. That may include restrictions in interest, existing charges, caveats, leases, easements, occupiers, access issues and other commitments affecting the site. Our dedicated guide to due diligence before a JDA covers this exercise, and the developer's own diligence, in full.

This is not a box-ticking exercise. If the land is charged, for example, the existing financier may have consent rights that affect what the landowner can promise. If a caveat or other third-party claim exists, the project timetable may depend on resolving it. Where the title carries a restriction in interest, the relevant State Authority consent may become part of the transaction sequence.

The JDA should then allocate responsibility. Matters controlled by the landowner should not simply become developer delay. If an encumbrance must be discharged, a consent must be obtained or an occupier must be dealt with before development can proceed, the agreement should identify who must do it, by when, and what happens if it cannot be done.

Make landowner cooperation an enforceable project obligation

One of the most underestimated JDA risks is not outright landowner default. It is slow cooperation.

A multi-year project can require repeated proprietor involvement. The developer may need title documents, corporate documents, signatures, statutory declarations, financier confirmations, authority forms, consent applications and responses to technical queries. If every item depends on informal follow-up with the landowner, the project can lose weeks at a time without anybody technically breaching a headline milestone.

The agreement should therefore convert cooperation into a process. It can identify nominated representatives, required response times, the documents the landowner must provide, escalation where a request is not answered, and the consequences of delay caused by a party that controls the missing input.

The developer should not assume a contract can bypass a statutory signature, proprietor consent or authority requirement. The point is to make the landowner contractually responsible for giving the cooperation that the law and the project process still require.

Who controls Kebenaran Merancang and the approval strategy?

Kebenaran Merancang, or planning permission, is often where the commercial assumptions in the JDA first meet the regulatory reality of the site.

The developer usually needs practical control over design development, consultants and submission management because the development concept is part of its commercial model. The landowner, however, may still need to authorise or sign documents as the registered proprietor.

The JDA should therefore answer questions such as:

• Who appoints and instructs the planning team?

• Who bears the cost of the application and supporting studies?

• What level of landowner approval is required before a design is submitted?

• What happens if the authority approves a materially lower density or different use than the feasibility assumed?

• Who bears additional premiums, contributions or redesign costs?

• Who controls an appeal, resubmission or variation strategy?

• Is obtaining an acceptable approval a condition precedent or a long-stop milestone?

• What happens if planning permission cannot be obtained on commercially acceptable terms?

The planning regime also depends on where the land is located. The Peninsular Malaysia framework under the Town and Country Planning Act 1976 is not the planning law for every Malaysian jurisdiction, so a JDA should be structured around the actual approval regime governing the site. Our dedicated guide to Kebenaran Merancang in a JDA covers this risk allocation in full.

Should the developer receive a power of attorney?

A developer may ask for a power of attorney because repeated landowner signatures can become a practical bottleneck. That does not mean the developer needs unrestricted authority over the land.

A sensible starting point is purpose. What acts genuinely need to be performed without waiting for a fresh signature each time? In some projects, a specifically drafted authority for identified planning, technical or administrative submissions may make the process more workable.

The risk appears when a narrowly needed administrative authority is replaced with broad wording that reaches sale, transfer, charging, financing documents or other dealings the landowner did not intend to delegate.

If a POA is part of the structure, the JDA and the instrument should be aligned on permitted acts, express exclusions, duration, document-control safeguards, revocation or irrevocability issues where relevant, and what happens immediately on termination or developer default. Our dedicated guide to power of attorney in a JDA covers this negotiation in full.

That is a separate risk-allocation exercise from simply saying "the developer may act for the landowner".

Make the JDA bankable without giving away unnecessary land control

A development project may be commercially sound but unfinanceable if the JDA does not anticipate what a lender will ask for.

The developer needs to know, before approaching financiers, what security and protections the landowner is prepared to permit. The landowner needs to know how far financier rights can reach into the land and project if the developer defaults.

The negotiation can involve permitted charges or other security, caveat positions, assignments of project proceeds, direct agreements, lender notice and cure rights, step-in rights, priority arrangements and release mechanics. Not every instrument is available or appropriate in every structure, and a contractual JDA does not itself guarantee that the developer or financier has a registrable land interest. Our dedicated guide to financing a joint development project covers this security architecture in full.

The important point is sequencing. Do not leave the security conversation until financing is already a condition for the developer to continue. If the business model assumes project finance, the JDA should define the financing envelope before the developer becomes dependent on lender terms the landowner has never agreed to.

Define the landowner's entitlement so the developer can model the project properly

A headline percentage is not enough.

The landowner may receive completed units, a percentage of gross revenue or gross development value, a share of net profit, a minimum guaranteed amount, fixed tranches, or a combination of these. Each structure can produce a very different cash-flow and risk profile for the developer.

The agreement must define the formula behind the number. If the entitlement is linked to revenue, what counts as revenue? How are rebates, discounts, incentives and unsold units treated? If it is linked to profit, which project costs are deductible, how are financing costs allocated, and what happens with related-party contractors or management charges? Our dedicated guide to landowner entitlement under a JDA covers this definitional discipline in full.

The developer should also understand when the entitlement becomes payable and whether those payment dates match actual collections and project cash flow. A generous landowner entitlement payable before the developer has received the corresponding project proceeds can create a financing problem even where the overall economics look profitable.

Separate day-to-day developer control from genuine landowner reserved matters

A project stalls when every operational decision requires joint approval. It also becomes commercially dangerous for the landowner if the developer can change the project economics without meaningful consent.

The JDA should distinguish the two.

The developer normally needs room to manage consultants, procurement, construction programming, sales execution and ordinary project administration. The landowner may reasonably require approval over decisions that materially alter the bargain: a major change in use or density, a change that reduces the landowner's entitlement, financing outside the agreed parameters, abandonment of a phase, a material related-party contract, or a disposal of rights that was never contemplated.

The exact list depends on the structure. The objective is not to recreate a shareholders agreement where no company exists. It is to identify which decisions are operational and which decisions change the landowner's economic exposure.

If the project includes housing, identify the HDA layer before sales begin

A JDA can be a private commercial contract between landowner and developer while the development it produces is subject to a separate statutory housing regime.

Where the project falls within the Housing Development (Control and Licensing) Act 1966 and its regulations, the parties need to identify that compliance layer early. It can affect developer licensing, advertising and sales, purchaser documentation and project-account requirements, among other matters. Our dedicated guide to the Housing Development Act inside a JDA covers this in full.

This matters to the JDA because the project cannot be structured as though sales, purchaser money and housing-development obligations are merely private matters between the landowner and developer.

The agreement should also be clear on which party is responsible for maintaining the licences and approvals required for the regulated development and what happens if those requirements cannot be met or cease to be maintained.

Put milestones and money in the same project sequence

A developer should resist a payment schedule that runs only by calendar dates where the ability to proceed depends on approvals or cooperation controlled elsewhere.

A more useful sequence is usually built around actual project events: signing and exclusivity, title and legal due diligence, satisfaction of landowner conditions, acceptable planning and technical approvals, financing conditions, agreed access or site handover, commencement of works, construction milestones, sales milestones and distribution milestones.

That does not mean every risk can be pushed to the landowner. The developer should carry the risks it actually controls. But the JDA should not require irreversible developer expenditure while a critical dependency controlled by the landowner remains unresolved without an agreed consequence.

What if the landowner delays or changes position?

Developers often focus on the landowner's promise to provide the land and overlook the smaller obligations that can make that promise usable.

The agreement should deal with competing transactions, refusal to sign necessary documents, failure to satisfy agreed title conditions, obstruction of access and delay in giving project cooperation.

Depending on the commercial bargain, protections may include exclusivity, negative covenants, suspension of affected developer obligations, extensions of time, cure procedures, termination triggers, and agreed treatment of costs that were incurred because the project was expected to proceed.

The important drafting point is integration. A termination right is of limited value if the agreement says nothing about consultant appointments, approval documents, security releases, site possession or money already spent.

What if the developer cannot proceed?

A bankable JDA must also work when the developer is the party in difficulty.

Financing may fail. A long-stop date may be missed. A developer SPV may become insolvent. Construction may stop. If the agreement gives the landowner no credible remedy, the land itself can be trapped in a failed development structure.

A developer should therefore negotiate realistic cure periods and, where financing is involved, appropriate lender step-in mechanics. It should also plan for an orderly exit: handover of project documents, treatment of approvals, site possession, work already carried out, consultant appointments, release or withdrawal of security and caveats where applicable, and a clear accounting of amounts still due. Our dedicated guide to developer delay, abandonment and insolvency covers this unwind from the landowner's perspective in full.

Those provisions protect the developer as well. An undefined unwind often produces a larger dispute than the original default.

What should survive termination?

Termination does not make the project history disappear.

Depending on how far the development has progressed, the parties may still need to deal with confidentiality, accrued payment rights, intellectual property and licences in project documents, return of original title or corporate documents, termination of authority or POA, possession of the site, financier rights, release of security, consultant records, treatment of approvals and pending authority applications.

If the project has already entered purchaser sales or another regulated stage, the unwind must also account for obligations that cannot simply be cancelled by agreement between the landowner and developer.

Developer-side JDA checklist before signing

• Structure: confirm whether this is really a JDA, a development-rights arrangement or an incorporated JV.

• Land: verify title, ownership, restrictions, charges, caveats, leases, access and occupiers.

• Control: define investigation rights, exclusivity, site access and the developer's operational authority.

• Cooperation: identify the documents and signatures the landowner must provide, with response times and consequences for delay.

• Approvals: allocate responsibility for KM, technical approvals, authority conditions, redesign and long-stop risk.

• POA: if needed, give only the authority the project genuinely requires and define how it ends.

• Financing: agree the security envelope, lender rights and release mechanics before financing becomes critical.

• Economics: define entitlement formulas, project revenue and cost treatment, payment timing and information rights.

• Governance: separate ordinary developer control from decisions that genuinely require landowner approval.

• Housing regulation: identify the HDA compliance layer early where the project falls within it.

• Milestones: tie major commitments to verifiable project events and dependencies.

• Default and exit: draft cure, termination and project-unwind mechanics for failure by either party.

When should the developer move from commercial heads to a full JDA?

Before the project becomes expensive to reverse.

If the developer is about to incur substantial consultant fees, rely on the landowner for authority submissions, pay a non-refundable amount, seek project financing, carry out material works on site or make commitments connected with public sales, the core JDA rights should already be settled.

The agreement should not merely confirm that both sides want the development to happen. It should allocate the control, cooperation, approvals, financing permissions, economics and failure risk that determine whether it can happen.

Frequently asked questions

What is the difference between a joint development agreement and a development rights agreement in Malaysia?

A development-rights arrangement is commonly structured around the developer receiving rights to develop the land in return for an agreed consideration. A JDA is more naturally used where the landowner and developer are sharing project economics or development risk. The actual rights and obligations matter more than the label used.

Can a developer obtain Kebenaran Merancang if it does not own the land?

The project can be structured so the developer manages the planning process, but the legal requirements for the application and proprietor authority must still be satisfied. The JDA should state exactly what the landowner must authorise or sign and who controls the consultants and approval strategy.

Should a landowner give the developer a power of attorney?

Not automatically. A specifically drafted POA can sometimes reduce repeated-signature delays for defined project tasks, but the authority should match the genuine operational need. Broad authority over sale, transfer, security or other land dealings should not be treated as a routine consequence of appointing a developer.

Can a developer finance a JDA project using the land as security?

That depends on the title position, the security instrument, required consents and what the landowner has agreed to permit. The JDA should define the financing and security framework before the developer assumes the land will be available as lender security.

Does the Housing Development (Control and Licensing) Act 1966 apply to every JDA involving residential land?

No single answer should be assumed from the JDA label alone. Where the resulting project falls within the statutory housing-development framework, the relevant licensing, sales and purchaser-protection requirements must be considered as part of the project structure.

Does signing a JDA automatically give the developer an interest in the land?

No. The developer's contractual rights under a JDA and any registrable or caveatable interest are separate questions. They depend on the rights actually created, the title position and the relevant land-law requirements.

Who pays stamp duty on the JDA?

Stamp treatment depends on the instruments used and how the transaction is structured. Our separate guide explains stamp duty on a development agreement in Malaysia.

This article is for general information only and does not constitute legal advice. Every transaction and every set of facts is different. Obtain specific advice from a qualified adviser before acting on any part of it.

Legal That Works advises landowners and developers on structuring, negotiating and documenting joint development agreements, including project control, approvals, entitlement, financing, security and exit mechanics.