The Shared Ownership Code is here. The hard part isn't the rules - it's the proof.
Housing associations are registering for the Shared Ownership Code in numbers. Adoption is the easy headline. Evidencing it, plot by plot, is the real work, and it's where most providers are quietly exposed.
There's a moment in every new piece of consumer regulation where the sector congratulates itself for signing up, and then discovers the obligation it actually agreed to.
The Shared Ownership Code, drafted by the Shared Ownership Council and now operated by the New Homes Quality Board, is at exactly that moment. Providers are registering. Press releases are going out. And underneath the announcements, operations teams are working out what "adopting the Code" means when a buyer completes on a Friday afternoon and the audit lands eighteen months later.
Because here is the part that doesn't make the press release: the Code puts the burden of proof on the provider.
What the Code actually asks for
Strip it back and the Shared Ownership Code is a set of promises a provider makes to a shared owner about information and fairness:
- A Key Information Document, in two parts, setting out for that specific plot: the share being bought, the rent on the unowned share, the service charge, the ground rent, the lease length remaining, the staircasing terms, the repair obligations, and the rules on alterations and pets.
- A Service Charge Information Document (SCID), now newly required, so the single biggest source of post-purchase disputes is disclosed up front.
- A fair sales process: a written reservation agreement, a 14-day cooling-off period with a full refund, and proper identification and support for vulnerable buyers.
- A quality floor: a pre-completion inspection, no completion with outstanding work beyond minor items, and a defects period of at least twelve months (with an aspiration to twenty-four).
- A handover that actually hands over: the demonstration, the warranties, the building-regulation certificates, the health-and-safety file, and a complaints route that works.
None of this is controversial. Most good providers believe they already do it. The problem isn't intent. The problem is evidence.
A folder of PDFs is not a defence
Every obligation resolves to the same underlying question: can you prove you did it, for this buyer, on this plot, at this time?
A shared drive can hold a KID. It cannot prove the KID that was issued was the right version for that plot's share and service charge. It cannot prove it reached the buyer before the cooling-off clock started. It cannot prove the buyer acknowledged it. And when the legal burden of proof sits with you, "we're sure we sent it" is not a position you want to be defending.
The Code is written in the language of evidenced disclosure. Most provider operations still run on the language of stored documents. That gap is the risk.
What governed handover looks like
The shared ownership pack (KID Part 1 and 2, the SCID, the reservation agreement, the EPC, the lease) needs to be instantiated per plot, not per scheme. A presence register that shows, for every plot, which obligations are met, which are flagged, and which are missing, with issuance tracked with read receipts, is the answer to the burden-of-proof requirement that "we're sure we sent it" can never be.
Beyond document assurance, the Code requires:
- Handover governance. Every plot moves through a controlled handover with the Code's required artefacts tracked to completion. Nothing completes with a gap, because the gap is visible before completion, not after the complaint.
- Quality inspections. The pre-completion inspection and the twelve-month defects period run with defect status and ageing visible to the people accountable for them.
- Compliance as decision-support. A handover-readiness score across documents and platform features shows your own team, before the buyer or the regulator does, exactly where the exceptions are, while they're still cheap to fix.
The providers who come out ahead won't be the ones who read the Code as cost. They'll be the ones who see what it's really standardising: a cleaner, more transparent, more provable customer journey. Disclose better and you get fewer disputes. Evidence handover and you get fewer defects escalating into complaints. Govern the process and the executive question stops being "did we send the KID?" and becomes "we can show, for every plot, exactly what we disclosed and when."
How Guided Home helps
Shared ownership schemes carry documentation obligations that standard market-sale handover processes were not built to handle — tenure-specific packs, staircasing information, service charge documentation and ongoing information rights that persist across the ownership lifecycle.
Guided Home's Document Assurance engine manages tenure-specific compliance checklists — shared ownership, affordable rent, market sale — validating that the correct documentation is present and compliant for each plot before completion. Document Intelligence auto-classifies incoming documents and maps them to the correct plot, while structured sourcing workflows chase missing items from delivery partners and managing agents.
For housing associations receiving units through S106 or partnership handovers, the Deal Room governs the B2B transfer — documents requested, sourced, validated and accepted — with an audit trail that persists past exchange.
Shared owners access their documentation through the Homeowner Portal, with Hugo answering questions about their property, their documentation and their obligations directly from the record.
If you are reviewing your shared ownership handover process ahead of the Code's enforcement, we would welcome a conversation.