ADR-0060: One lawyer-reviewed tenancy template — the platform fills blanks and never drafts

Status

Accepted (2026-08-26)

Tags

rental, legal, compliance, product-boundary, template, pdf, adr-0058, adr-0059

Decision

The platform holds one tenancy agreement template, reviewed once by a lawyer, and fills its blanks from structured data. It does not draft bespoke terms and it does not advise.
  • Structured blanks only: parties, property, rent, start date, term, deposit months. Ringgit amounts are never stored — they are monthly_rent × months, computed at render time.
  • One free-text field: special_conditions on rental_offers. It is part of the offer, so it is negotiated, echoed into the message thread on every offer, counter, and re-offer, frozen into terms, and printed in the agreement.
  • No clause picker, no clause library, no conditional wording.
  • template_version records which reviewed form produced a document, and which shape the terms snapshot uses. It is bumped for a change to either.
  • The renderer holds only the current template. Because documents are frozen at issue (ADR-0058), an old version never needs re-rendering.

Why

The Legal Profession Act 1976 s.37 reserves the practice of law to advocates and solicitors. Filling blanks in a standard form that a lawyer has already reviewed is a materially different position from composing terms for a customer, and it is the safer side of a line this platform has no appetite to test. A clause picker looks like a feature and reads like drafting: the moment the platform selects between legal wordings on a customer’s behalf, the character of what it is doing changes. Special conditions are the deliberate exception, and their shape is what keeps them safe. The landlord types their own words; the platform neither suggests nor selects. Putting the field on the offer rather than at the accept step matters for a second reason that has nothing to do with the Act: it means the tenant sees the conditions while they can still negotiate, instead of discovering them inside a document they are being asked to sign. One template is also the honest engineering answer at this stage. There is no evidence yet about which clauses real Malaysian landlords actually need. A clause picker is a natural later addition once special_conditions shows what they keep typing — the free-text field is the research instrument.

Considered options

  • A clause picker over a lawyer-reviewed clause library — rejected for now. More useful and still not drafting from scratch, but it moves the platform from filling blanks to selecting legal wording, and it needs evidence about real demand that does not exist yet. special_conditions is how that evidence gets collected.
  • Bespoke drafting, whether by template logic or an LLM — rejected outright. Squarely the thing s.37 reserves, and an LLM drafting tenancy terms is an unbounded liability with no upside for the ordinary case.
  • No free-text field at all — rejected. Real tenancies carry pet clauses, furniture lists, and parking-bay numbers. Without a field, landlords put them in chat, where they are not part of the signed document at all — which is worse legally, not better.
  • Per-state or per-property-type template variants — rejected. Multiplies the lawyer-review cost by the number of variants before anyone has shown a variant is needed.

Consequences

  • Every template change costs a lawyer review, and bumps template_version. There is no cheap path to changing the wording, which is the intended pressure.
  • special_conditions is unreviewed text inside a reviewed document. A landlord can type something unenforceable or unlawful, and the platform prints it. Accepted: this is the same position as any blank-filling standard form, and the alternative is the platform vetting legal wording, which is the thing this ADR exists to avoid.
  • English only. One template means one language, matching slice 1.
  • The renderer built here is reused by slice 4 for late-notice PDFs.
  • The agreement is not stamped, and stamping is not automated. See ADR-0059.