HOMEOWNER CARE2026-06-055 MIN READ

After the keys: the handover record builders wish they kept

Warranty season is decided on possession day. Why PDI items, deficiency lists, walkthroughs, and key handover deserve structured records — and how the CareOps pilot approaches it.

BY OPSPHERE TEAM · UPDATED 2026-07-09

Eighteen months after possession, a homeowner emails about a tile edge in the ensuite. Whether that email costs your team twenty minutes or two weeks was decided on possession day — by whether the pre-delivery inspection, the deficiency list, the walkthrough, and the key handover landed as records or as paper in a binder that has since moved offices twice.

Where meticulous builders go informal

Builders feel this every warranty season. The construction record is meticulous — drawings, RFIs, change orders, draw packages — and then, at the exact moment the customer relationship begins, the record-keeping reverts to clipboards. The PDI form is a PDF scan. The deficiency list is a spreadsheet someone owns personally. The walkthrough happened, and everyone remembers it differently.

The handover record set is small and specific

Per unit, the set is:

  • The pre-delivery inspection, with each item and its status.
  • The orientation record showing what the homeowner was shown.
  • The deficiency list with status per item and the trade responsible.
  • The walkthrough record.
  • The key handover — keys, fobs, mail keys, and the homeowner’s sign-off.

A complete set fits on a few screens. An incomplete set fits in nobody’s memory. What the structured version changes is the character of every later conversation: deficiency disputes become lookups — here is the item, logged at walkthrough, here is its closure. Trades get lists instead of forwarded photo threads. And when a warranty claim arrives, the question "was this present at possession?" has a documented answer instead of a negotiation.

Why the record maps to warranty windows

In BC, new homes generally carry home warranty insurance commonly described as 2-5-10: coverage periods that differ for materials and labour, the building envelope, and structure. The details are the warranty provider’s and vary by policy — consult yours — but the operational implication is the same everywhere: claims get evaluated against time windows measured from defined start dates, and against the question of what was present or noted at possession. A dated, itemized PDI and deficiency record is the builder’s side of that evaluation. Without it, every claim conversation starts from zero; with it, the conversation starts from the record.

The deficiency workflow between possession and closure deserves the same structure. Each item carries the trade responsible, a status, and dates — logged, assigned, scheduled, verified, closed. The verification step matters most: an item a trade marks done and an item the builder confirms closed are different facts, and the homeowner’s trust rides on the difference.

Where CareOps stands — precisely

This is the problem CareOps — the homeowner care module on the OpSphere platform — starts from. And it is worth being precise about its status, because we hold marketing to the same standard we hold records: CareOps is a pilot program, not a finished product. The handover record set works today: orientation and PDI capture, deficiency tracking with status per item, walkthrough records, key handover. The warranty layer — period tracking, service SLAs, appointments, vendor dispatch — is on the roadmap, and pilot builders are shaping its order.

Why join a pilot instead of waiting? Because the handover records you capture this year are the foundation the warranty workflows will stand on, and because pilot builders get a vote. The teams in the program are deciding, with us, what a service request should carry, how dispatch should work, and what the homeowner should see. That influence is the honest value of a pilot — along with knowing exactly what is live and what is not, because we publish it.

The practical on-ramp is deliberately small: start with one project nearing possession, run its PDIs and walkthroughs into the system, and compare the experience against the binder on the project running in parallel. Handover is a per-unit workflow, so piloting it does not disturb anything upstream — and one warranty season with a complete record set for even a single building makes the comparison unambiguous.

For builders running projects on ProBuild, there is a structural bonus: the unit that finishes construction is the same unit that enters homeowner care, on the same tenant, so the deficiency logged at PDI is connected to the project history behind it.

The binder version of handover works until the first hard question. The record version works on the day you need it most — eighteen months later, when the email arrives.

MORE IN HOMEOWNER CARE