LLCR Academy is open: landlord compliance courses for England, with a certificate on completion. Browse courses

For letting agents

Rent is easy to prove.
Compliance is the hard part.

When a tenant alleges a missed gas copy, or a landlord asks what you held at a given date, what do you hand them? LLCR is the property compliance system for agencies. For a managed book, that means a tamper-evident evidence record you can export.

Download a sample Defence Pack to see the deliverable

Why agents carry risk

Enforcement and redress land on the agency

Under the Renters' Rights Act 2025, duties fall on relevant persons, which includes anyone acting on the landlord's behalf. A civil penalty can land on the managing agent directly, not only the landlord. The Property Ombudsman and other redress schemes expect you to show what was done and when.

A missed gas safety copy, an expired EICR, or a gap in prescribed information is not only a landlord problem. It becomes an agency problem when you cannot produce a dated, ordered record of what you held.

Most agencies are built to collect rent, not to prove compliance across hundreds of properties. That gap is where the exposure sits.

What you hand them

A Defence Pack and a tamper-evident audit trail

Two deliverables when someone asks for proof: a structured PDF bundle and a record whose integrity can be checked independently.

Compliance Defence Pack

An indexed PDF evidence bundle: certificates, statutory checks, service evidence, document register, activity timeline, and cryptographic verification data. Structured for solicitors, redress panels, and council enquiries.

Tamper-evident audit trail

Every compliance action is hashed with SHA-256 and chained entry to entry. Daily summaries are anchored via OpenTimestamps. Designed to show what you held and when, with verification anyone can run.

LLCR Compliance Defence Pack page with a property selector and cards explaining how the pack helps with council investigations, tenant disputes, and court proceedings
Generating a Defence Pack for a property in LLCR.

Sample deliverable

See what a Defence Pack looks like

Request a fictional demo pack — a demo property with random details — to review the structure before a call.

We use your email to send the sample and occasional follow-up about LLCR. See our Privacy Policy.

Used by letting agencies managing compliance across managed books.

Agency pricing

Priced for a managed book

From £39/month for up to 20 properties

Then £1 per additional property per month + VAT. Provisioned after you book a call or contact us.

Founder

Built from a compliance evidence perspective

I am Tauhid, the founder. I hold an LLB and work as a paralegal in property law and civil litigation. I built LLCR because compliance has become an evidence problem, not a filing one. The platform starts from what a council, redress panel, or solicitor would need to see, not from rent collection alone.

Common questions

Objections we hear from agencies

We already use a PMS

Property management systems handle lettings workflow. LLCR sits alongside them as the compliance system: structured Defence Packs, hash-chained audit trail, and certificate tracking designed for what you need to hand over.

We use spreadsheets today

Spreadsheets track dates but do not produce a tamper-evident record or an indexed Defence Pack. When someone disputes what was held, a spreadsheet is hard to defend and easy to challenge.

Onboarding a new system takes time

We provision agency accounts after a short call and help you import your book. Smart Document Capture reads key certificates from uploads. You do not need to re-key every date manually on day one.

My team will not adopt it

LLCR is built for compliance leads and branch managers who need one view across the book. Certificate uploads, expiry monitoring, and Defence Pack exports are designed to fit existing workflows rather than replace your PMS.

Weighing LLCR against another compliance tool? See how LLCR compares, including LetCompliance and LandlordOS.

Evidence

Evidence and audit trail

LLCR records what you held and when you held it in a cryptographic chain you can verify independently. Not a promise of outcomes. A structured record with integrity you can check.

Audit trail

What is hashed, and why alteration breaks the chain

See how it works

Every compliance action in LLCR (adding a certificate, uploading evidence, updating a record, logging proof of service) creates a SHA-256 hash of that event. Each new hash includes the hash of the entry before it, forming a continuous chain.

If anyone changed a single past record, its hash would no longer match. Every subsequent hash in the chain would break. The mismatch is visible immediately when you verify the chain, without asking LLCR whether the data is genuine.

Once a day, LLCR computes a Merkle root: a single summary hash of all that day's audit entries. That root is submitted to OpenTimestamps, an open protocol that anchors data to the Bitcoin blockchain. The timestamp does not depend on LLCR's servers alone. Anyone with the proof file can check that your records existed at a specific point in time using open tooling.

Do not trust us. Check.

Anyone can check OpenTimestamps proofs with public, open-source tooling. On any property page in LLCR, use "Verify Audit Trail" to run the check.

This supports integrity of records as held in LLCR. It does not guarantee how a court, council, or redress scheme will treat your evidence.

LLCR hash chain diagram Each record block links to the previous hash. A daily Merkle root is anchored via OpenTimestamps. Genesis hash₀ Record 1 hash₁ = f(data₁, hash₀) Record 2 hash₂ = f(data₂, hash₁) Record n hashₙ = f(dataₙ, hashₙ₋₁) Daily Merkle root summary of that day's entries OpenTimestamps anchor independent public ledger proof Alter one record every later hash breaks
Each block depends on the one before it. Change any earlier entry and the chain no longer verifies.

Proof of service

What was served, on whom, and when

See how it works

When a tenant says “I never received that”, your word alone may not carry much weight with a court or council. LLCR records exactly when and how each certificate and document was served: the date, the method, who it was served on, and the evidence.

Each upload is linked into the property's tamper-evident audit trail. If the file were altered later, the fingerprint would no longer match, and verification would flag it immediately.

Defence packs

The record becomes something you can hand over

See how it works

The Compliance Defence Pack exports your indexed evidence bundle with the audit chain status, entry count, and latest Merkle root. Agents use it for redress, council enquiries, and solicitor instructions.

Your audit trail PDF and Defence Pack include the verification data a solicitor or expert can review independently. Download a sample Defence Pack to see the structure.

What it is

  • A tamper-evident record of compliance actions as held in LLCR
  • SHA-256 hash chaining linked entry to entry
  • Independent daily timestamping via OpenTimestamps
  • Verification you can run yourself with public tooling

What it is not

  • A guarantee that a court or council will accept your evidence
  • Legal advice or a substitute for a solicitor
  • Proof that compliance obligations were met (only what was recorded)
  • A claim that records cannot be altered under any circumstances

Want more technical depth on hashing, OpenTimestamps, and verification? See the FAQs.

Next step

See LLCR against your managed book

A short call is the easiest way to see whether LLCR fits your agency. Or send us a message and we will come back to you.

Book a call Contact us

LLCR is a tool, not a law firm. It does not guarantee compliance outcomes.

Book a call