Close-up of a co-development contract with a red pen highlighting concerning clauses
Co-Development

5 Red Flags Hiding in a Co-Development Contract

8 min read

The specific clauses that shift risk onto the homeowner. What to remove, what to negotiate, and when to walk away from the term sheet.

Key takeaway

Five specific contract clauses that shift disproportionate risk onto homeowners in co-development deals.

Covers: unlimited cost overrun liability, vague timeline with no penalty, unilateral design authority, title transfer before permits, and missing exit/buyout clauses. Each red flag includes the specific language to watch for, what it should say instead, and when the clause is a dealbreaker versus negotiable.

What this covers

  • unlimited cost overrun liability clause
  • vague timeline no completion penalty
  • unilateral design authority builder
  • title transfer before permits issued
  • missing exit buyout clause
  • negotiable vs dealbreaker terms
co-development contract legal red-flags multiplex

Most co-development deals that go sideways do not go sideways because of the market, the trades, or the permit process. They go sideways because of clauses the homeowner signed without understanding. Here are the five most common red flags I see in Vancouver co-development contracts, and the specific language you need to push back on.

Red Flag #1: Vague Unit Selection

The worst contract clause I’ve ever read said: “Homeowner shall receive two (2) residential units in the completed development, such units to be selected by the Builder at final strata registration, giving due consideration to Homeowner’s preferences.”

That is a “builder picks, homeowner hopes” clause. It is not a selection clause.

What you want instead: Unit selection specified by proposed strata lot number, referenced to a preliminary strata plan attached as a schedule. Minimum square footage, floor level, orientation, and finish specification all defined. Penalty clauses if the delivered unit deviates more than a small tolerance from the spec.

Sample language to insist on: “Homeowner shall receive Proposed Strata Lot 1 (ground floor, 1,215 sq ft, southeast exposure, finish schedule ‘B’ attached) and Proposed Strata Lot 4 (top floor, 1,180 sq ft, corner unit, finish schedule ‘A’ attached).”

Specific. Numbered. Measurable. Anything less is a builder option dressed up as a homeowner right.

Red Flag #2: Fake Performance Bonds

A real performance bond is issued by a surety company (Travelers, Zurich, Intact, and similar) and guarantees completion of the work to a defined standard, with the surety on the hook for a specified dollar amount.

A fake performance bond is:

  • A personal guarantee from the builder’s principal
  • A guarantee from a holding company with no disclosed financials
  • A letter from the builder’s bank saying they have a line of credit
  • An unsecured promise

I have seen all four called “performance bonds” in Vancouver co-development agreements. None of them are.

What you want instead: A Labour and Material Payment Bond and a Performance Bond, both from a surety licensed in British Columbia. Bond amounts must equal at least 50% of the contract value. You want to receive copies of the bond documents before breaking ground, not “when they’re ready”.

Verify: Google the surety company and check they’re regulated. A real surety will have a rating from AM Best or equivalent. If the “bond” comes from a numbered company, it is not a bond.

Red Flag #3: Broad Force Majeure

Standard force majeure clauses excuse performance for: acts of God, war, natural disasters, pandemics, government orders. That’s reasonable.

Bad force majeure clauses I’ve seen excuse:

  • “Unforeseeable supply chain disruptions” (code for: normal supply chain)
  • “Labour market conditions” (code for: can’t find trades, not our fault)
  • “Adverse weather” (in Vancouver, where rain is 6 months a year)
  • “Regulatory delays” (code for: we filed the permit late)
  • “Market conditions” (code for: we don’t feel like building right now)

Every one of those is a normal construction problem, not a force majeure event. If your contract excuses the builder from those, you have no contract.

What you want instead: Narrow force majeure that covers only truly exceptional events. Anything else the builder wants excused must be in a separate “permitted delays” section with defined time limits and cure periods.

Red Flag #4: Waterfall Payment Priority

In an equity JV, the profit distribution waterfall is where retail homeowners get cooked. A clean waterfall goes:

  1. Return of construction loan principal and interest
  2. Return of homeowner land capital ($1.8M in our example)
  3. Return of builder cash equity contribution
  4. Preferred return to both parties (8-12% annually)
  5. Developer fee to builder (capped, disclosed)
  6. Split of residual profit per agreed ratio

A bad waterfall I saw once went:

  1. Return of construction loan
  2. Developer fee to builder (10% of gross project cost)
  3. Return of builder equity
  4. Preferred return to builder only
  5. Return of homeowner land
  6. Split of residual

That homeowner signed away $400K of their capital position by agreeing the developer fee came before return of land. They didn’t understand that clause. Their lawyer didn’t flag it.

What you want instead: Read the waterfall aloud, in numbers, at two different sale price scenarios. If you can’t follow who gets paid when, you can’t sign it.

Red Flag #5: Registration Priority at LTSA

This is the most technical red flag and the most common.

Here’s what happens: You transfer your land to the SPV. The SPV borrows from a construction lender. The construction lender registers a mortgage on title. Your interest in the SPV is unregistered, or registered as a caveat junior to the mortgage.

If the project fails: the lender gets the lot. You get nothing.

What you want instead: Either (a) keep title in your name and grant the builder a registered option with priority over any future charges, or (b) transfer to an SPV where your interest is registered as a priority charge ahead of the construction lender, with a priority agreement signed by the lender.

This requires a lawyer who actually understands real estate and development finance. A notary will not catch this. A general-practice lawyer will often not catch this. You need someone who has structured co-development agreements before.

What To Do If You See Any of These

  1. Stop signing until the clause is fixed.
  2. Get independent legal review (not the builder’s lawyer, not a notary, not your cousin).
  3. Walk away if the builder refuses to revise the language.
  4. Remember: a builder who refuses to fix a red flag at the term sheet stage will not fix it later.

The One-Sentence Rule

If any clause in the contract makes you say “I’ll just trust them on that one”, remove the clause. A co-development is a partnership, but it is also a legal document. Trust is not a substitute for clear language.

Further Reading

Your lawyer earns their fee on the contract, not on the handshake. Pay for the review. Every time.

Frequently asked questions

What does a vague unit selection clause look like in a co-development contract?

A red-flag clause reads something like: homeowner shall receive two residential units in the completed development, such units to be selected by the builder at final strata registration, giving due consideration to homeowner's preferences. That leaves the builder picking the units and the homeowner hoping. A proper clause instead names the exact proposed strata lot numbers, square footage, floor level, orientation, and finish specification, with penalty clauses if the delivered unit deviates beyond a small tolerance.

What is a fake performance bond in a co-development deal?

A fake performance bond is a personal guarantee from the builder's principal, a guarantee from a holding company with no disclosed financials, a bank letter saying the builder has a line of credit, or an unsecured promise. A real performance bond is issued by a surety company such as Travelers, Zurich, or Intact and guarantees completion of the work to a defined standard, with bond amounts equal to at least 50 percent of the contract value, and copies should be provided before breaking ground.

What force majeure language should a homeowner reject in a co-development contract?

Force majeure clauses excusing unforeseeable supply chain disruptions, labour market conditions, adverse weather in a city where it rains half the year, regulatory delays, or market conditions are describing normal construction problems dressed up as exceptional events. A narrow force majeure clause should cover only truly exceptional events like acts of God, war, natural disasters, pandemics, and government orders, with any other delay the builder wants excused placed in a separate permitted-delays section with defined time limits and cure periods.

How can a payment waterfall clause cost a homeowner their land position?

A clean waterfall returns the construction loan first, then the homeowner's land capital, then the builder's cash equity, then a preferred return of 8 to 12 percent annually to both parties, then a capped and disclosed developer fee, and finally splits the residual profit. A bad waterfall pays the developer fee, calculated at 10 percent of gross project cost, ahead of the return of the homeowner's land, which in one real example cost a homeowner $400,000 of their capital position because they did not understand the clause and their lawyer did not flag it.

Why does registration priority at the Land Title and Survey Authority matter in co-development?

When a homeowner transfers land to a special purpose vehicle that then borrows from a construction lender, the lender's mortgage gets registered on title while the homeowner's interest may sit unregistered or registered as a caveat junior to that mortgage. If the project fails, the lender gets the lot and the homeowner gets nothing. The fix is either keeping title in the homeowner's name with a registered builder option that has priority, or registering the homeowner's interest in the SPV as a priority charge ahead of the construction lender, confirmed by a signed priority agreement with the lender.

What should a homeowner do if they spot one of these red flags in a contract?

Stop signing until the clause is fixed, get independent legal review rather than relying on the builder's lawyer or a notary, walk away if the builder refuses to revise the language, and remember that a builder who will not fix a red flag at the term sheet stage will not fix it later once construction has started.

What is the one-sentence rule for reviewing a co-development contract?

If any clause makes a homeowner think I'll just trust them on that one, the clause should be removed rather than accepted. A co-development is a partnership, but it is also a legal document, and trust is described as not a substitute for clear, specific language throughout the agreement.

Who should review a co-development contract before a homeowner signs it?

The contract needs a lawyer who actually understands real estate and development finance, not a notary and not a general-practice lawyer, because issues like registration priority at the Land Title and Survey Authority are technical and commonly missed. The advice given is direct: your lawyer earns their fee on the contract, not on the handshake, so pay for the review every time.

Free 12-page guide for Vancouver-area homeowners. Build, sell, hold, or partner — side-by-side comparison of the numbers, timeline, and risk on each path.

Verified phone required. We'll text you the link in 60 seconds.

David Babakaiff

David Babakaiff

Co-Founder, VanPlex | 25+ Years BC Construction

David Babakaiff is Co-Founder of VanPlex with 25+ years scaling BC construction. He led Alair Homes Vancouver to the 2024 HAVAN Award for Best Multiplex Unit in the GVRD. VanPlex’s PlexRank™ algorithm scores residential parcels across BC for multiplex conversion potential under Bill 44.

Want insights like this delivered weekly?

Join 2,500+ property owners getting ROI case studies, market data, and exclusive opportunities.

No spam. Unsubscribe anytime.