Tenura field guide

How to build a property maintenance history from email

Connect the fault, contractor, cost, outcome and source so past work remains useful years later.

By Tenura7 minute read

01

Maintenance history is usually present but unstructured

A landlord's inbox often contains a remarkably complete maintenance record. Tenants describe faults, contractors confirm visits, invoices record costs and follow-up messages reveal whether the work solved the problem. The information exists, but it is split across conversations and attachments.

A useful maintenance history reconnects those fragments. It gives each material job a property, issue, date, contractor, amount, outcome and source.

02

Define one record for each material job

Create one maintenance event for a repair or inspection that changed the property's condition or generated a meaningful cost. Routine scheduling messages can remain attached to the source conversation without becoming separate timeline entries.

Use a consistent description based on the actual work, not the filename of the invoice. 'Boiler pressure valve replaced' will be more useful later than 'Invoice 284'.

  • Property and area affected
  • Issue reported and date
  • Contractor or supplier
  • Work completed and completion date
  • Invoice amount and document
  • Outcome or follow-up status
  • Original email thread

03

Connect the explanation to the invoice

An invoice is reliable evidence of a charge, but it may be a poor description of the original fault or result. The email conversation often contains the language that makes the expense understandable.

Link both to the same event. This allows somebody reviewing the property later to see what was reported, what was done and how the amount was recorded without reconstructing the thread again.

05

Review patterns at property and portfolio level

Once repairs are connected to properties and dates, the history becomes useful beyond retrieval. You can review repeated work at one address, activity involving the same contractor, or all jobs of a particular type across the portfolio.

Patterns are prompts for investigation, not automatic conclusions. A cluster of boiler visits might reflect a recurring fault, routine servicing or incomplete records. Open the underlying sources before making a decision.

  • Repeated issue types at the same property
  • Multiple invoices connected to one reported fault
  • Contractors used across several addresses
  • Jobs with an invoice but no recorded outcome
  • Material spend with limited supporting detail

06

Use AI for reconstruction and retrieval

AI can help recognise contractor conversations, associate invoices with an address and turn years of email into candidate maintenance events. Natural-language search can then retrieve records without requiring the exact supplier or filename.

The workflow remains source-first: surface the event quickly, show why it was matched and preserve the original message and document for verification.

See the workflow

Your property history is already in your inbox.

Explore a working Tenura portfolio built from realistic email, documents, contractors and maintenance history.