Alberta homebuilders keep lot and quick-possession inventory in sync by treating each home as a unit record with one authoritative status, then linking every buyer, document, payment milestone, and open question to that unit instead of copying status into spreadsheets, sales tools, and inboxes. Inventory rarely goes wrong because a team lacks a system. It goes wrong because the same lot is described differently in three places, and nobody owns the difference.
This guide explains where inventory drift comes from in Alberta's current market, which system should own which fact, and a practical operating model that a sales, construction, and customer-care team can run together.
Key takeaways
- Inventory drift is a coordination problem, not a data-entry problem: the lot, the buyer, and the possession date change in different systems at different times.
- Give every fact one owner. The ERP or land/inventory system owns unit status and price; the CRM owns the sales relationship; the buyer file owns documents and conditions.
- Quick-possession and spec homes need tighter loops than presale lots, because the buyer's timeline is weeks, not months.
- A buyer-operations layer should read authoritative status and route discrepancies to an owner, never overwrite the system of record.
- Measure drift directly: count units where the sales view and the authoritative status disagree, and how long each disagreement stays open.
Why does inventory drift out of sync in Alberta?
Alberta has been building at a pace few teams were staffed for. CMHC data summarized by ATB shows the province reached a record of roughly 54,900 housing starts in 2025, with Calgary and Edmonton both setting records, and a 2026 outlook that remains above the 10-year trend even as starts ease (ATB, CMHC outlook). More releases, more phases, and more quick-possession homes mean more status changes per week.
The usual sources of drift:
- Holds and conditional sales. A lot is "held" in the sales tool while the ERP still shows it available, or a conditional sale collapses and only one system is updated.
- Spec and quick-possession conversions. A presale lot becomes a spec build, then a quick-possession listing, and its price, possession date, and selections change each time.
- Possession date changes. Construction moves a date; the buyer, the lender contact, and the sales team hear about it at different times.
- Showhome and agent channels. Area managers, showhome staff, and outside realtors each keep their own list of what is available.
- Exports that age. A Monday spreadsheet is accurate on Monday.
None of these require a new inventory system to fix. They require agreement about which system owns each fact, and a routine for catching disagreements before a buyer does.
Which system should own which inventory fact?
Use a simple ownership map before connecting anything.
| Fact | Usual authoritative owner | What other teams should do |
|---|---|---|
| Unit or lot status (available, held, sold, possessed) | ERP or land/inventory system | Read it; flag mismatches |
| List price and incentives | ERP or approved pricing sheet | Quote only the current approved version |
| Buyer relationship and sales stage | CRM | Link to the unit, do not re-key status |
| Purchase agreement, conditions, amendments | Document repository / buyer file | Track completeness and expiry |
| Deposit and payment milestones | ERP or finance system | Follow up from the ledger, not from memory |
| Possession date | Construction schedule, approved by an authorized role | Communicate only approved dates |
The table looks obvious. The value is in writing it down, because most drift starts when someone "helpfully" updates a status in the tool they happen to have open.
How do quick-possession homes change the workflow?
Quick-possession and spec homes compress everything. A presale buyer may wait a year between reservation and possession; a quick-possession buyer may sign and expect keys within weeks. That changes three things:
- Conditions resolve faster. Financing and sale-of-home conditions need owners and dates from day one.
- Documents are front-loaded. Identity, agreement, deposit evidence, and warranty paperwork all land in the same short window. See the document readiness matrix.
- Availability must be current to the hour. Two agents selling the same quick-possession home in the same afternoon is the most visible form of inventory drift, and the most damaging to trust.
For these homes, review status daily, and route any mismatch between the sales view and the authoritative status to a named person the same day.
A practical operating model for inventory and buyer status
The model below works with the systems you already have. It does not require replacing the CRM or ERP.
1. Make the unit the anchor
Every buyer conversation, document, payment milestone, and question should attach to a specific lot or unit identifier that matches the ERP. If the CRM and ERP use different identifiers, keep one mapping and give it an owner.
2. Read status, do not copy it
Teams should see the current authoritative status wherever they work, with its source and the time it was last observed. A copied status with no timestamp is how a sold lot stays "available" for a week.
3. Detect and route disagreements
When the sales stage, the unit status, and the buyer file disagree (for example, a buyer marked "firm" on a lot the ERP still shows as held), the workflow should open an exception with an owner and a resolution condition. It should not silently pick a winner.
4. Communicate only approved facts
Buyers should hear possession dates, prices, and availability only from approved sources. Questions outside policy, such as a price exception or a date change request, go to a person. See how to govern buyer status questions.
5. Review drift on a cadence
Track two numbers weekly: how many units have a disagreement open, and the median age of those disagreements. If the first rises during a release or the second grows past a few days, the process, not the people, needs attention.
Which inventory exceptions need human review?
Route these to a named person instead of letting a workflow resolve them:
- Two buyers or agents linked to the same lot or quick-possession home
- A price, incentive, or upgrade credit that differs from the approved version
- A possession date change that has not been approved by construction
- A conditional sale that expired or collapsed without the status being updated
- Any request to hold, release, or transfer a unit
The workflow can detect the disagreement and assemble the evidence. The decision belongs to sales administration, construction, or finance, depending on the fact.
What should a homebuilder look for in a tool that helps?
Look for software that connects to the CRM and ERP you already run, keeps them as the source of truth, links every buyer artifact to a unit, and turns disagreements into owned tasks. Be cautious of tools that ask you to migrate inventory into a new system before they show value. For a fuller comparison, read CRM vs ERP vs a buyer-operations platform and our guide to choosing buyer-operations software in Alberta.
Where Asterisko fits
Asterisko is software that assembles a persistent context for each buyer and unit from a builder's existing CRM and ERP, which stay the source of truth. It surfaces status disagreements, keeps documents and payment follow-up attached to the right unit, answers approved buyer questions, and escalates anything outside policy to the responsible person. It does not set prices, approve sales, or make financing decisions.
See the buyer-servicing workflow or read how to unify CRM, ERP, documents, and payments without replacing them.
Sources
- ATB Financial, CMHC housing market outlook 2026
- Canada Mortgage and Housing Corporation, news releases
