2-5-10 warranty management for BC builders

Every BC builder knows the shorthand: 2-5-10. Two years on materials and labour, five on the building envelope, ten on structure — the home warranty insurance that new homes in the province generally carry. What the shorthand hides is that the warranty is an insurance product with defined windows and processes, while the builder’s day-to-day warranty experience is an operations problem: requests arriving by every channel, trades to dispatch, and — on the day it matters most — the question of what was true at possession.

This post covers both halves: what the 2-5-10 framework generally means for a builder’s obligations, and the record-and-workflow discipline that separates builders who manage warranty season from builders who absorb it. The usual hedge applies with force: coverage terms live in the policy, the regulatory framework is administered under BC’s homebuilding legislation with BC Housing overseeing licensing, and your warranty provider’s documentation governs. This is the operational map, not coverage advice.

What 2-5-10 actually describes

In BC, new homes built for sale by licensed residential builders generally must carry third-party home warranty insurance — the framework commonly described as 2-5-10 after its three coverage bands: two years on defects in materials and labour (with sub-periods inside — some systems carry different terms in the first months than the first two years), five years on defects in the building envelope including water penetration, and ten years on structural defects. The insurance is issued by a warranty provider, not by the builder — but the builder is the party who repairs, and the provider generally looks to the builder first.

Three operational facts follow. The clocks run from defined commencement dates — generally tied to occupancy or transfer, per the policy — so knowing each unit’s exact start date is not trivia, it is the denominator of every later claim conversation. Coverage bands have exclusions and owner-maintenance expectations, which is why "is this warrantable?" is a policy question before it is a scheduling question. And claim windows are hard edges: a request that arrives inside a window and a request that arrives after it are different events, for the homeowner and for you.

The builder’s two warranty seasons

Operationally, warranty load clusters. The first season is the months after possession: the deficiency tail from handover plus the settling issues a new building produces. The second is the approach of window boundaries — homeowners are routinely advised to inspect before their first-year and second-year anniversaries, so requests spike as each cohort’s clock approaches a boundary. A builder with three projects completing in eighteen months has overlapping cohorts, each with its own set of live windows per unit. That is a portfolio of clocks — the same shape as lien holdback deadlines, and just as unsuited to memory.

The record set that decides claims

When a claim conversation gets difficult, it almost always lands on one question: was this condition present and noted at possession, or did it arise after? The builder’s side of that answer is the handover record — the pre-delivery inspection with items and statuses, the walkthrough record, the deficiency list with closure history, the key handover with sign-off. A dated, itemized record set turns the question into a lookup. Its absence turns it into a negotiation, conducted eighteen months after the fact, against a homeowner’s photographs.

From there, the working warranty record per unit is short: the coverage commencement date; every request with its intake date, description, and photos; the warrantability decision and who made it; the trade assigned and the appointment history; and closure with verification — because an item a trade marks done and an item the builder confirmed closed are different facts. That set serves three audiences at once: the homeowner (status without phoning), the provider (evidence without assembly), and your own trades (lists instead of forwarded photo threads).

The workflow, honestly scoped

The process discipline is unglamorous: one intake channel homeowners actually use, so requests stop arriving as texts to the site super; triage against the policy bands before scheduling, so trades are not dispatched to non-warrantable items; batching of non-urgent items into visit windows, because four trips to one unit is a cost the schedule never shows; and a weekly review of open items with aging, exactly like an RFI log. None of this requires software — binders ran warranty for decades — but every step produces records, and records that land structured at the moment of work are the cheapest evidence you will ever create.

This is the problem OpSphere CareOps is being built around, and we label its status honestly: CareOps is a pilot program. The handover record set — orientation and PDI capture, deficiency tracking with status per item, walkthrough records, key handover — works today; the warranty layer, including period tracking against coverage windows, service requests, and vendor dispatch, is roadmap, shaped by the builders in the pilot. For builders running construction on ProBuild, the unit that finishes the build is the same record that enters care. If warranty season is currently a shared inbox and a binder, the pilot is the honest on-ramp: capture this year’s handovers as records, and shape what the warranty workflows become.