What a repair audit trail must capture
A legally useful repair record must show: when the tenant reported the issue (date, time, description); when you acknowledged it; when you assigned a contractor; when the contractor accepted and scheduled; and when the job was completed. WhatsApp captures none of this in a legally meaningful way — messages are editable, deletable, and not independently timestamped.
Why WhatsApp threads fail as evidence
In a dispute, a WhatsApp thread has three weaknesses: you cannot prove messages haven't been selectively deleted; the timestamps are device-local, not server-verified; and the thread shows conversation, not structured status changes. A First-tier Tribunal or local authority inspector needs to see a clear timeline — not a chat history.
How FixRoute creates the audit trail automatically
FixRoute records every action against a repair ticket with a server-side timestamp: when the tenant submitted the report (including their photos), when the landlord assigned a contractor, when the contractor accepted and quoted, and when the job was marked complete. This record is stored permanently and can be exported. You never have to remember to document anything — FixRoute does it as a side-effect of running the repair.
Using the audit trail in a dispute
If a tenant claims a repair was never addressed, you can produce a timestamped timeline showing: report received on Day 1, contractor assigned on Day 2, contractor accepted on Day 3, job completed on Day 7. That record is far more persuasive than searching a WhatsApp thread and reconstructing a timeline from memory. FixRoute's audit trail is structured for exactly this use case — Section 11 compliance and deposit disputes.