Podcast Episode 02: The Contract You Signed

U-Property PH is running a podcast-within-a-blog, and episode two drops you straight into a forty-three-page contract that one buyer skimmed in forty minutes before catching a flight to Dubai.

That’s the setup — and the episode uses two buyers, Maria and Jerome, to work through what a pre-selling Contract to Sell actually contains: the reservation fee structure, what ownership means before full payment, turnover date language, forfeiture clauses, and the gap between what an agent says and what the document says.

Let’s start with the moment the commitment is actually made — which turns out to be earlier than most buyers think.

The episode opens with a structural tension: the reservation fee — in Maria’s case, thirty thousand pesos paid on a Saturday — is not a down payment, but it reshapes every decision that follows.

The post is direct about why: “Paying the reservation fee is when the negotiation ends. Not when you sign the Contract to Sell. Not when you hand over the first amortization check.”

That’s the upshot — by the time the contract arrives, walking away is expensive. The thirty thousand is gone if you decline to sign, so the review window that looks like evaluation time is actually confirmation time for most buyers. Maria had twelve days in the Philippines, a departure date everyone in the showroom understood, and a review window that was generous in theory and meaningless in practice.

Jerome paid the same fee having already decided he was buying, which is a different animal entirely.

Right — he requested the draft contract before committing to the reservation. He spent a Sunday working through it, flagged fourteen clauses, and carried three into a Tuesday call with the agent. The fee, for him, was a confirmation. For Maria, it was the beginning of a process she hadn’t yet understood. The post makes clear the non-refundable character of the fee is a contractual provision, not an absolute rule — it can be negotiated — but that possibility requires knowing the negotiation exists.

Which most buyers discover roughly fourteen months after the Saturday in question.

And that timing matters, because what a Contract to Sell actually transfers is the next thing the episode unpacks — and it’s not ownership.

This is where the episode corrects a widespread assumption: the signing date feels like the purchase date, but legally it isn’t.

The post puts it plainly — a Contract to Sell is conditional. “Title does not move at signing. Ownership does not move at signing. What moves is the buyer’s obligation to pay, and the developer’s obligation to eventually transfer title once that obligation is fulfilled.”

So for the full payment period — three, four, five years of amortizations — the developer still holds the title.

Which has two concrete consequences the episode spells out. First, the developer’s obligations are ongoing throughout that period — construction completion, turnover timing, unit specifications — all governed by Presidential Decree 957. Second, the buyer’s remedies run through that statute’s administrative process, not through property rights directly. Filing with DHSUD, following an administrative timeline, appearing at hearings. The rights are real; they require the buyer to initiate them.

Maria’s question, after Jerome explained all of this in a group chat, was one line: “So what does the law give me until I finish paying?”

The episode’s answer is that PD 957 sets a floor of protections the contract cannot waive — including rescission rights if the developer fails to deliver within the statutory grace period. But those protections are administrative remedies, not automatic ones. None of that comes with the copy of the contract Maria put in her carry-on.

The turnover date clause is where those protections get tested — and where the contract’s language does the most quiet work.

Jerome spent the most time on the turnover date clause during his Sunday review — specifically on what came after the delivery commitment.

The core language was: the developer would “endeavor to complete and deliver the unit on or before Q4 2026.” Jerome’s first flag was the word endeavor — not “will deliver,” but closer to “will try to deliver.” What followed was a force majeure clause defining extension events to include acts of God, government action, changes in regulatory requirements, and, critically, “other causes beyond the Developer’s reasonable control” — an explicitly non-exhaustive list.

That catch-all is doing a lot of lifting. A delayed building permit, a revised environmental clearance, a new local government requirement mid-construction — any of those could qualify, which means the turnover date can move without triggering any buyer remedy.

Jerome asked the agent directly whether a delayed building permit would fall under government action for force majeure purposes. The agent said it probably would. The developer’s legal team, when the agent followed up, confirmed the clause was standard and cited a strong delivery track record — which Jerome noted was not a narrower interpretation of the clause, just a reassurance about how often it had been invoked.

Maria found the same clause on page thirty-one, sixteen months after signing, during a group chat conversation about a delay notice in a different project. She screenshot it and posted it. Jerome’s response was two words: “That one.”

What PD 957 adds is a statutory grace period — a developer cannot be held to rescission for non-delivery until twenty-four months past the contractual turnover date. That buffer runs both ways: it limits immediate buyer demands, but it also establishes that a developer who misses the date by more than two years has crossed into statutory remedy territory. The episode’s advice is to document the delay formally from the start, so the record is clean if rescission becomes necessary.

And if the buyer stops paying before that point — the forfeiture clause is waiting.

The forfeiture section is where the episode introduces the biggest gap between what most buyers assume and what the law actually requires.

The assumption is that stopping payment means losing everything. The episode is precise about how wrong that is — at least after two years.

Republic Act 6552, the Maceda Law, sets statutory minimum refund rights that override contractual forfeiture clauses. For buyers who have completed at least two years of installment payments, the law requires a refund of at least fifty percent of total payments made, increasing by five percent for each additional year, up to a maximum of ninety percent. The contract’s forfeiture clause cannot go below that floor. The episode is explicit: “The developer cannot waive the Maceda Law, and a buyer cannot waive it either.”

Maria did the math on her own contract’s forfeiture clause — which specified full forfeiture with a carve-out for amounts exceeding twenty-five percent of the total price — and found she’d recover significantly less than she’d assumed.

Jerome’s response was to ask whether she knew about the Maceda Law, then post a table comparing the statutory minimum refund at various points in a five-year payment schedule against what the contractual clause would return. At the two-year mark, the contract returned less than twenty-five percent in some scenarios; the statute required at least fifty. Three people in the chat screenshot the table. Maria noted the exact date she would cross the two-year threshold.

The episode also flags the procedural side: cancellation under the Maceda Law requires notarial notice — a formal, notarized written notice served on the buyer. A text message or email doesn’t constitute valid cancellation. The form matters because defective cancellations are legally defective.

And the episode closes this section with a line that captures the whole dynamic: “The statute wins. But you have to know the statute exists to invoke it.” Which brings the episode back to the gap between what the agent said and what the contract said — the place where most of this starts.

The episode is careful not to frame the agent-contract gap as fraud by default. Most of it is something more ordinary: a salesperson who understands projected timelines and product features but not the legal qualifications embedded in the documents they’re facilitating.

The agent who told Maria “Q4 2026” probably believed it. The force majeure language that qualified that date was in the contract, not in his mental model of the project.

Jerome’s approach was deliberate — he treated agent representations as sales-layer information, useful for understanding the product’s positioning, not its contractual structure. The episode grounds this in a legal principle most buyers haven’t encountered: the parol evidence rule. Under Philippine contract law, when an agreement is reduced to writing, the written instrument is the authoritative record. Evidence of prior oral representations that would contradict the written terms is ordinarily not admissible. The agent is not a party to the Contract to Sell. The developer is. “The developer is bound by what the written contract says. The developer is not bound by what the agent said.”

So if the agent said the forfeiture clause would take twenty percent and the contract says twenty-five, the contract controls. If the agent said the turnover date was firm and the contract qualifies it with a force majeure window, the contract controls.

The episode ends this section by returning to Maria and Jerome. Both are current on payments, both in the same building, same monthly amortization. What differs is what each of them has available — as leverage, as documented understanding — depending on whether they went through the Saturday afternoon version of the process or the Tuesday evening version. Jerome has a phone note from the week before he signed summarizing what the agent said about the force majeure clause, including the gaps. Maria has the group chat. The episode describes her first fourteen months as “not knowing I didn’t know.”

Which is, the episode suggests, the accurate description of where most pre-selling buyers are during the quiet middle — and the closing section makes clear that the middle is exactly where the contract is doing its work.

The contract, the statute, the administrative process — three separate documents, three separate layers, and you need all three to understand what you actually agreed to.

And the episode’s real question is still open: what happens when the system is tested — when the delay notice arrives and the filing has to happen. That’s where the next episode seems to be headed.

Jerome has a folder. Maria has started one. That might be the most useful sentence in the whole piece.

It’s a good place to pick up.