Why Most Implementations Struggle

In our 10+ years working with Ontario housing providers, we've identified one pattern that predicts implementation failure more reliably than any other: starting to configure Yardi before you truly understand the client's operations.

It seems obvious when stated plainly. Yet the pressure to show progress — to demonstrate that something is happening — consistently drives implementation teams to skip or rush discovery. The result is configurations built on assumptions, workarounds that compound over years, and eventually the painful realization that the foundation needs to be rebuilt.

What Discovery Actually Means

Discovery is not a two-hour intake call. For a Yardi implementation in the Ontario housing context, genuine discovery means:

• A comprehensive walkthrough of every active database across all modules
• Documentation of every workaround currently in use — and understanding why it exists
• Assessment of how tenant types are actually coded vs. how they should be coded
• Review of charge codes, unit types, and GL structure for downstream impacts
• Staff interviews to understand what frustrates them daily
• Assessment of reporting gaps — what the client wishes they could see but can't

"If you don't know what's broken, you can't know what to fix first. And in Yardi, fixing the wrong thing first can make the right thing harder."

The Ontario Housing Context

Generic Yardi consultants often miss the Ontario-specific nuances that define how housing providers must operate. RGI calculation methods, SMIR reporting requirements, service manager compliance standards — these shape how a Yardi database needs to be configured in ways that standard implementation guides don't address.

Discovery in an Ontario housing context means assessing not just the system state but the compliance state. Are tenant income records accurately reflecting actual income? Is the SMIR data clean enough to submit without manual corrections? Are affordable and market units properly separated at the charge code level?

The Deliverable That Changes Everything

A proper discovery engagement delivers a prioritized audit report that maps every finding to its business impact, identifies dependencies between issues, and provides a phased roadmap for resolution. This document becomes the contract for the entire engagement — both sides aligned on what needs to happen, in what order, and why.

At Business Solutions, this is what we call the Yardi Operational Review (YOR). It's not a sales tool — it's a working document that drives everything that follows. Some clients commission a YOR and implement the findings internally. Others engage us for the full implementation. Either way, the clarity it creates is invaluable.

The Opportunity Is Real. The Complexity Is Real Too.

Ontario's affordable housing sector has never seen more funding activity. Between CMHC programs, City of Toronto open calls, regional incentive programs, and provincial initiatives, there are more pathways to develop or participate in affordable housing than at any point in recent history.

But the volume of opportunity creates its own challenge: organizations chase every open call, spread their capacity too thin, submit proposals without truly understanding the scoring criteria, and wonder why they keep losing to the same handful of established players.

The Strategic Framework That Works

Before pursuing any RFP, the most effective housing organizations ask three questions: Does this match our organizational capacity today? Do we have a credible track record in this type of project? And can we build the partnerships the evaluator is looking for?

If the answer to all three is yes, that's a go. If one is no, it's a strategic development opportunity — not an immediate pursuit. If two or more are no, the resources are better spent strengthening capacity for the next cycle.

"The organizations that win the most RFPs don't apply to everything. They apply selectively, build relationships before the RFP drops, and invest deeply in the opportunities that fit."

Partnership Is the Differentiator

In Ontario's current environment, almost every significant affordable housing RFP rewards partnerships. Municipalities want to see experienced nonprofits partnered with capable developers. Funders want to see wrap-around service delivery alongside housing supply. The organizations that have built those relationships before an RFP is published have an enormous advantage.

This is why relationship development can't be an afterthought. Organizations that wait until an RFP is published to start calling nonprofits are always starting from behind.

Where We See the Best Opportunities

In the current Ontario landscape, we're watching several program areas closely: the City of Toronto's Rental Housing Supply Program, Peel's Affordable Rental Incentives Program, York Region's expanding housing programs, and CMHC's MLI Select and Seed Funding streams. Each has different eligibility criteria, different scoring models, and different partnership requirements.

From Patterns in the Field

After supporting Ontario housing providers through complex Yardi implementations, the same patterns appear repeatedly. These aren't theoretical — they're what actually happens when implementations go sideways.

1. Skipping the Discovery Phase

Covered in detail in our discovery article — but it bears repeating. Jumping into configuration before documenting current state is the root cause of most implementation pain.

2. Coding All Tenants as RGI by Default

This is shockingly common. When Yardi is first set up without proper guidance, it's often easiest to set all tenants to RGI and use manual overrides for exceptions. This poisons your data for years — you can't report on tenant types, your SMIR is wrong from day one, and fixing it retroactively is an enormous undertaking.

3. HST in the Wrong Field

Maintenance staff entering HST as a materials line item rather than a tax field creates cascading financial reporting problems. It seems minor until month-end reconciliation reveals the discrepancies.

4. Training After Configuration Instead of During

Staff need to understand why the system is set up the way it is, not just how to use it. When training comes after configuration, staff often revert to workarounds because they don't understand the underlying logic.

5. Ignoring the Downstream Impact of GL Setup

General ledger decisions made in Phase 1 affect every financial report you'll ever run. Changes made later are expensive and risky. Getting your CFO deeply involved in GL design from day one is non-negotiable.

6. Underestimating Change Management

The best Yardi configuration in the world fails if staff don't use it correctly. Change management isn't a soft add-on — it's as important as technical configuration, especially in organizations where staff have been using workarounds for years.

7. Treating the Implementation as a Project Instead of a Journey

Yardi implementations don't have an end date. They have a go-live date, followed by a period of optimization, followed by new requirements, followed by platform upgrades. Organizations that build a long-term relationship with their Yardi support partner consistently get better results than those that treat each engagement as a one-time project.

Not All Organizations Need the Same Support

One of the most common mistakes housing organizations make when engaging Yardi consultants is defaulting to a contract structure that doesn't match their actual usage pattern. An organization with occasional questions doesn't need an annual retainer. An organization in the middle of a complex implementation doesn't need zero-hour support.

The Zero-Hour Model

On-demand support without a minimum commitment works best for organizations that have strong internal Yardi capacity and only occasionally encounter problems they can't solve internally. It's also a good starting point for organizations testing a new support relationship before committing to a longer-term arrangement.

Fixed-Period Agreements

Six or twelve month agreements with committed hours provide predictability for both parties. The client knows what support they have available; the consultant can plan resource allocation. This model works well for organizations with ongoing but manageable support needs, or those working through a defined list of system improvements.

Annual Partnerships

Full-service partnerships go beyond reactive support. They include proactive system monitoring, strategic planning sessions, and a deep familiarity with your organization that makes every interaction more efficient. The consultant isn't learning your organization from scratch each time — they know your databases, your team, and your history.

"The right support model is the one that matches your organization's Yardi maturity, your internal capacity, and your current priorities — not the most expensive option on the menu."

Your Structure Is Your Credential

In Ontario's affordable housing sector, how you're organized matters as much as what you've built. Municipal funders, service managers, and nonprofit partners evaluate your organizational structure before they evaluate your proposal. A developer approaching the sector with a for-profit corporate entity and no nonprofit arm is starting from a significant disadvantage.

The Three Key Questions

Before entering the affordable housing space, organizations need honest answers to three structural questions: Do you have an entity that can receive operating subsidies and rent supplements? Do you have a governance structure that satisfies municipal partnership requirements? And does your brand position you as a credible housing provider — not just a developer?

Models That Work in Ontario

The most successful models we see combine a development entity, a foundation or nonprofit arm, and in some cases a dedicated property management vehicle. This mirrors what organizations like WoodGreen (foundation + service delivery), Daniels (EVOLV nonprofit), and Tridel (Del Property Management) have built over years. The specific structure matters less than ensuring each component exists and is properly constituted.

"We've seen organizations lose RFPs not because their proposal was weak — but because the evaluator couldn't find evidence of nonprofit housing delivery experience in their entity structure."

The Manual SMIR Problem

Walk into almost any Ontario housing provider's office in the weeks before SMIR reporting is due and you'll find the same scene: a staff member manually opening each tenant record, transcribing income and rent data into a spreadsheet, cross-referencing against paper files, and praying nothing has changed since the last time they checked.

This is not a process problem. It's a data configuration problem — and it's entirely solvable in Yardi.

Why the Data Is Usually Unreliable

The root cause of manual SMIR reporting is almost always one of three configuration failures: tenants miscoded (all as RGI when some are affordable or market), income data entered inconsistently across staff, or no flagging system distinguishing verified income from placeholder income. When any of these conditions exist, automated reporting produces unreliable output — so staff default to manual verification.

The Fix

Resolving manual SMIR reporting requires addressing the data quality issues first, then building the automated report on top of clean data. At Business Solutions, this is typically a Phase 2 item in our implementation roadmap — following the tenant classification cleanup in Phase 1, which is itself a prerequisite for everything downstream.

The result: SMIR reporting that takes minutes, not days, and produces output you can submit with confidence rather than anxiety.