The fourth unit gets blamed because it is often where a landlord stops remembering every detail unaided. But the spreadsheet did not suddenly become bad. The portfolio became relational.
Give the spreadsheet credit
Where a spreadsheet is still the right tool
Spreadsheets are cheap, flexible, familiar, and exceptionally good at ad hoc calculation. They are useful for evaluating a purchase, comparing mortgage scenarios, modelling cash flow, planning a renovation, or creating a temporary checklist.
Use it to think
Projections, scenarios, one-off comparisons, and calculations that genuinely belong in a grid.
Use it when the system is simple
One property, stable tenancy, few expenses, and a landlord who reliably maintains the file.
Keep an export
A clean CSV remains valuable for portability, independent analysis, and accountant handoff.
The problem begins when the workbook becomes the tenant directory, rent ledger, receipt generator, maintenance tracker, document archive, notice calendar, and tax file simultaneously. Flexibility then becomes hidden architecture that only its creator understands.
The inflection point
What actually breaks past three units
One fact lives in several tabs
A tenant name changes, but the lease tab, receipt template, maintenance log, and contact sheet do not all change with it.
A status becomes a manual opinion
Paid, overdue, occupied, expiring, resolved, and served are operational states. A spreadsheet only knows them when someone updates the right cell.
Evidence separates from the row
The spreadsheet says a repair cost $640. The photos live on a phone, the invoice in email, and the tenant update in a text thread.
More units create more intersections
The risk is not four times the typing. It is the growing number of tenants, due dates, notices, vendors, receipts, documents, and exceptions that can collide.
The first failure
A spreadsheet stores values; a rental operation changes state
Consider one rent payment. In a workbook, someone types the amount, changes a status, perhaps updates a balance formula, creates a receipt, and saves evidence elsewhere. If the payment covers two months, includes a credit, is reversed, or belongs to the wrong tenant, the number is not enough. The system needs allocation, history, and correction without destroying the original trail.
The same distinction appears everywhere. A lease is not only a start and end date; it moves from draft to active to ended. A maintenance issue moves from reported to triaged to scheduled to resolved. A rent increase moves through eligibility, notice preparation, delivery evidence, and future activation. Software begins to earn its cost when those state changes matter more than the raw cells.
The second failure
Every link is a promise someone must maintain
A spreadsheet can link to a receipt, lease PDF, photo folder, or email. But the link does not know whether the file belongs to the right property, whether access will survive an account change, or whether the underlying record was replaced. At scale, landlords do not lose only files; they lose context.
The cost of a disconnected file is paid later, when you must explain what happened and the row cannot answer.
Connected property software should not merely upload documents. It should keep a receipt with the expense, a repair photo with the maintenance event, a tenant with the active lease, and a notice with its delivery record.
Side by side
What changes in DwellTrack
| Workflow | Spreadsheet | DwellTrack |
|---|---|---|
| Portfolio structure | Names and IDs repeated across tabs | Properties, units, tenants, and leases are connected records |
| Rent workflow | Manual status, formulas, and receipt templates | Charges, payments, allocations, receipts, and tenant history stay linked |
| Maintenance | One row plus links to outside files | Request, priority, messages, photos, expense, and resolution share one record |
| Documents | Folders and filenames depend on memory | Documents are generated or stored against the relevant tenancy workflow |
| Tax preparation | Rebuild categories and supporting detail | Property expenses and T776-oriented workpapers use records captured through the year |
| Change history | Latest saved version may hide who changed what | Operational events preserve a chronological record |
| Migration | Already familiar, but increasingly custom | Validated spreadsheet import maps the existing portfolio into connected records |
DwellTrack does not eliminate landlord judgment. It gives the judgment a better record: the relevant property, people, dates, money, messages, documents, and evidence stay connected while the landlord approves consequential actions.
The economic test
When is software worth paying for?
Do not compare software only with the price of a spreadsheet, which may be zero. Compare it with the time spent reconciling duplicate fields, finding evidence, rebuilding receipts, correcting formulas, preparing year-end records, and explaining the system to a partner, bookkeeper, contractor, or future owner.
Five signs the workbook has become expensive
- You enter the same tenant or property fact more than once.
- A missed reminder can affect money, notice timing, or tenant service.
- Supporting evidence lives outside the row that describes it.
- Only one person understands the workbook.
- You distrust totals until you manually audit formulas.
Switching without starting over
Migration is part of the product, not an afterthought
The strongest argument for keeping a spreadsheet is often not that it works well; it is that years of history already live there. Re-entering every property, unit, tenancy, payment, opening balance, and expense would turn improvement into a punishment.
DwellTrack's spreadsheet migration studio is designed around that switching cost. It lets landlords upload CSV or Excel files, identify worksheets, map source columns to DwellTrack fields, preview connected data, validate problems before commitment, download error details, and undo a completed migration when the imported batch needs to be reversed.
The spreadsheet still has a place after the move: export, analysis, and custom modelling. It simply stops being responsible for every operational truth.
Decision
Keep the grid; replace the fragile operating system
If a spreadsheet is genuinely calm, complete, and easy to audit, there is no virtue in replacing it prematurely. If rent, maintenance, receipts, notices, documents, and tax records have started forming separate versions of the same portfolio, the issue is no longer spreadsheet skill.
That is the moment DwellTrack is built for: not because the fourth unit is magical, but because the landlord now needs one connected account of what is true and what should happen next. Compare the broader DwellTrack feature set, review plans by managed-unit count, or start with the migration preview before changing any live record.