Route lease amendments before rebuilding the rent abstract

A property manager's inbox mixes signed lease amendments, broker proposals and maintenance requests. A model asked to “update the lease summary” for each email can spend time on the wrong document or carry draft terms into a proposed abstract. Intake needs a document-purpose decision first.

What this means for your business

For a commercial real-estate operator, classification can reduce repeated lease analysis and direct routine correspondence to the correct team. The business value is less rework in lease administration and faster preparation of a reviewable change package. The classifier proposes a route; it does not establish legal effect or authorize ledger changes.

CLM-v0.1-8B scores supplied choices instead of writing an answer. Its two projection heads use a frozen Qwen3-8B encoder. That makes it a candidate for deciding which workflow should run next. It does not extract a complete record, execute a tool or prove that a document is correct. The model card and implementation are linked below.

A specific workflow: a second office-lease amendment

In a fictional office portfolio, an email titled “Suite 410 extension” contains a countersigned second amendment, an older unsigned proposal and a tenant's note about a failed air-conditioning unit. The amendment changes the commencement of an extension period and includes a new rent schedule.

Local extraction separates attachments and preserves page IDs. CLM scores routes such as executed-amendment review, draft-commercial-terms review, tenant-service request, routine correspondence, or manual review. Execution status is a proposition to verify from signatures and document metadata, not a fact that a high classifier score can establish.

The amendment-review workflow retrieves the original lease and first amendment, extracts proposed effective dates and rent terms, and creates a redlined abstract for the lease administrator. The draft proposal remains clearly marked as unexecuted reference material. The air-conditioning note goes to the service-request queue without triggering another lease summarization call.

The acceleration comes from retrieving and analysing the lease chain only for the document that needs it. A deterministic schedule calculator handles dates and rent arithmetic after a reviewer accepts the extracted terms. Neither the classifier nor the drafting model posts a new rent schedule directly to the property ledger.

A compact on-site deployment

The lightweight part is the scoring layer. The full service still needs the Qwen3-8B encoder. As a sizing calculation, eight billion weights at two bytes each occupy roughly 16 GB before runtime memory, activations and serving overhead. A single Linux workstation with a supported 24–32 GB GPU is a reasonable starting configuration to evaluate for short inputs and modest concurrency, not a tested minimum or a throughput promise.

The reference implementation pairs a vLLM pooling service with the CLM API. Keep decision inputs short, precompute reusable candidate embeddings, and batch arrivals within an acceptable waiting window. The repository's example caps inputs at 2,048 tokens; split longer documents into meaningful sections and retain page references instead of silently truncating evidence. One encoder can serve several department-specific sets of choices.

Four-bit weights would be roughly 4 GB in raw weight storage by arithmetic, but that is not the total memory requirement. Quantization changes embeddings and may change rankings. Validate the exact encoder, pooling method, precision and heads together before buying smaller hardware. The supplied heads cannot simply be attached to any small embedding model. A tiny CPU appliance or a Mac mini is not a verified drop-in deployment for this reference stack.

Keep lease intelligence beside the portfolio records

Where a property operator has a maintained office server or workstation, on-site hosting can keep negotiated lease terms, guarantor details and tenant communications inside the portfolio's controlled network. Use property and ownership-entity permissions before retrieval. Keep document extraction and downstream abstract generation inside the same boundary if external inference is excluded.

Record the exact lease versions behind each proposed change. Isolate caches between owners and portfolios, and retain the human approval that authorizes an update. The local service needs backups, patching and an ordinary intake queue if it is unavailable. For very low volume, assess whether the operational burden is justified before committing to dedicated hardware.

Measure the accepted abstract, not the first label

Evaluate historical mixed email bundles, including unsigned attachments and superseded amendments. Compare unnecessary lease-chain retrievals, model calls and time to an accepted abstract. Pay particular attention to draft-versus-executed confusion and missing amendments. Those errors can outweigh a fast classification result, so begin with proposed tasks that a lease administrator reviews.

The release is an early candidate-ranking model. Published agent benchmarks do not establish accuracy or speed on this workflow. Scores are relative to the alternatives supplied, not calibrated probabilities that a business decision is correct. Include an explicit manual-review choice, then set abstention rules using held-out examples; adding that choice alone does not make the system safe.

Frequently asked questions

Will the classifier update the rent ledger?

No. It proposes a document route. A reviewer verifies the amendment and extracted terms before a separate approved process changes the ledger.

How lightweight is the full on-site service?

The scoring heads are small, but the encoder has roughly eight billion parameters. Raw 16-bit weights alone are about 16 GB. A 24–32 GB GPU workstation is a sizing hypothesis for evaluation, not a verified minimum; runtime memory and workload matter.

Are these workflow speed improvements measured?

No. These are proposed workflows using fictional examples. Measure the full pipeline against your baseline, including routing accuracy, review time, retrieval and downstream model calls.

Sources & further reading

Talk with us about your workflow →