Start tracking today

2.65M UK landlords · most still on spreadsheets

Try it
AES-256 GDPR 5-min setup GOV.UK

Editorial & product team · United Kingdom

The people who keep every LetCompliance guide source-led

We review every public guide, council page and dataset against primary UK legislation before it ships. The same team turns those rules into deadlines, reminders and an audit trail you can rely on in court.

71+

Guides published

Blog, glossary & regulation hubs

11

Compliance categories

Topic clusters cross-linked on-site

90d

Re-verification cycle

Quarterly refresh of every public page

0

Sponsored editorial

No pay-for-placement or insurer kickbacks

Last reviewedReviewed by Erdem Volkan

Erdem Volkan, Director, LetCompliance
Active reviewer

Erdem Volkan

Director, LetCompliance

United Kingdom
I built LetCompliance because I needed it myself. Every guide and every check here is the answer I wished I'd had as a UK landlord — written from the GOV.UK source up, never recycled.

Founder and Director of LetCompliance. Builds and edits the platform end-to-end: the compliance scoring engine across the six statutory areas (Gas Safety, EICR, EPC, deposit protection, Right to Rent and Fire Risk Assessment), the Section 8 / Form 6A / Section 13 notice generators, the Awaab’s Law SLA tracker and the SA105 + MTD ITSA tax pack. Reviews every public guide, glossary entry and city / council page against primary UK legislation (Housing Act 1988, Housing Act 2004, Deregulation Act 2015, Renters’ Rights Act 2025) and GOV.UK / HSE / MHCLG publications before publication.

Areas of expertise

UK landlord complianceRenters’ Rights Act 2025Section 8 possession + Form 6ATenancy deposit protectionHMO and selective licensingMTD ITSA + SA105 tax
Editorial workflow

How a single guide gets to the homepage

The same four-step process applies to every article, every council page and every statutory deadline we ship into the product. No shortcuts.
  1. 01Step 1

    Read the primary source

    We start at the Act, the Statutory Instrument, the GOV.UK guidance or the regulator’s own publication — never a third-party blog.

  2. 02Step 2

    Cross-check enforcement

    We verify the rule against MoJ statistics, First-tier Tribunal decisions and council enforcement bulletins for what councils actually fine on.

  3. 03Step 3

    Write, link, attribute

    Each guide carries inline citations, a “Reviewed by” byline, a “Last reviewed” date and structured data so search and LLMs can map authorship.

  4. 04Step 4

    Re-verify quarterly

    Licensing schemes, fee schedules and statutory dates are re-checked every quarter; mid-quarter changes trigger a same-week refresh.

Primary sources

The libraries we read every week

Eight UK regulators and statute libraries we cite in articles, dashboards and notice generators. Click any source to read the same way we do.
Editorial principles

What you can hold us to

If we ever break one of these we expect a reader to call it out. Email the editor and we’ll publish a correction with a visible diff.

Source-first, opinion-second

Every legal claim links to GOV.UK, legislation.gov.uk or the named regulator. If a primary source disagrees with us, we change the article.

No sponsored content. Ever.

No pay-for-placement, no insurer kickbacks, no affiliate-driven recommendations in editorial pages. Tools we name, we name on merit.

Visible review trail

Every public page shows the “Last reviewed” date and the named reviewer. JSON-LD `dateModified` is updated whenever the underlying rule moves.

Updated when statutes move

When a statutory instrument lands or a fee schedule changes, the affected pages update within two weeks — and we never silently delete history.

Accountability

Our review & correction SLA

Every public page carries a visible Last reviewed date and a Reviewed by byline linking back to this team. We re-verify licensing scheme statuses, fee schedules and legislative citations every quarter.

When a rule changes mid-quarter, we update the affected pages within two weeks and move their dateModified forward. Older versions stay in source control — we never silently rewrite history.

Read the full editorial policy

Our promises

  • Quarterly re-verification of every public page
  • Two-week SLA for mid-quarter statutory changes
  • Visible "Last reviewed" + "Reviewed by" byline
  • JSON-LD `dateModified` updated on every change
  • Public correction log, never silent rewrites
  • Zero sponsored content in editorial articles

Get in touch

Got a correction, a tip-off or a press request?

We read every email. UK office hours, replies within 24h. For PR / journalist requests, please mention your outlet in the subject line.