PROPERTY
PERPETUITY
Log inSign up

Landlords · Originally published · Updated · 2 min read

Introducing property technology without making management harder

A practical method for testing digital tools against real property-management tasks, with clear ownership, accessible alternatives and a way to stop unsuccessful trials.

Property Perpetuity editorial illustration for “Introducing property technology without making management harder” — propertyperpetuity.com
Illustrative artwork · Property Perpetuity

Sign in to save this for later →

Facebook ↗LinkedIn ↗

A new digital tool should solve a recognisable management problem. Before adding another dashboard, describe what currently goes wrong: a repair is missed, documents are hard to find or tenants receive conflicting updates. That description gives a landlord a useful test of the tool, rather than an assumption that newer technology must be better.

Choose one workflow

Start with a limited task and a named owner. For maintenance reporting, for example, define who receives a report, who checks urgency, who appoints a contractor and who confirms completion. Ask a supplier to demonstrate the complete sequence using fictional records. A notification is only useful if someone is responsible for acting on it.

Keep the tenant experience practical

Explain how the system will be used and which contact route is appropriate for an urgent issue. Provide a workable alternative for someone who cannot use the app. Avoid asking tenants to repeat the same information across several channels without explaining which one is authoritative. Test the instructions with a person who has not seen the product before.

Check the information involved

List the records the tool will hold and the people who need access. The National Cyber Security Centre's small-organisations guide covers account security, devices, backups and suspicious messages. Apply those basics to a trial as well as to a permanent system. Do not upload real tenancy documents merely to see what an unfamiliar demonstration account looks like.

Measure an observable result

Choose a modest measure, such as whether outstanding repairs have an owner and a visible status. Compare it with the previous process and record any extra work the tool creates. Keep claims about savings or efficiency separate from results actually observed in your own trial. Review support quality and the ability to export records as well as the appearance of the screen.

Decide whether to continue

Set a review date and a clear exit plan. If the tool is adopted, document the workflow and train the people using it. If it is stopped, recover the records and close access appropriately. Technology earns its place when the process becomes easier to understand and manage. This is an editorial operating checklist, not a recommendation of a particular product. Reviewed 30 October 2026.

Source and further reading: https://www.ncsc.gov.uk/collection/small-organisations-guide-to-cyber-security

Reference source ↗