Real estate
Interpreter handles the document-heavy work that fills a broker's, property manager's, or transaction coordinator's week — filling applications from intake docs, building lease-rate analyses with comps, surveying market rents, drafting listings, and producing portfolio reports. It works on the files you already have, with your approval before anything goes out.
Example workflows
Fill a rental application from intake docs
Point Interpreter at a tenant's intake folder — ID, paystubs, prior lease, references — and have it fill the rental application PDF, flag any missing field, and queue it for your final review.
“Fill the rental application at ~/templates/rental-app.pdf using the intake documents in ~/tenants/garcia. Flag any field you couldn't confirm and don't sign anything.”
Lease Rate Analysis Report
Builds a 4-page Lease Rate Analysis Report with 3-6 comparable lease comps within a 3-mile radius, including rent per square foot, term, concessions, and a recommended rate band.
“Build a Lease Rate Analysis Report for 410 Market Street using comps from the lease database. Pull 5 comps within 3 miles signed in the last 12 months. Output as PDF using my report template.”
Market rent survey
Reads a CSV of recent area leases and a subject property's specs, normalizes for square footage and amenities, and produces a market rent band with the comp set behind it.
“Run a market rent survey for the 2-bed at 88 Linden. Use the recent-leases.csv, filter to 2-beds within a half mile, and give me a recommended rent band with the comp set behind it.”
Property listing description
Drafts an MLS-style listing description from the photo folder, spec sheet, and neighborhood notes. Keeps fair-housing language clean and surfaces the features worth leading with.
“Draft a listing description for 22 Oak Lane using the photos in ~/listings/22-oak and the spec sheet. Lead with the kitchen renovation and the school district. Keep it fair-housing compliant.”
Lease comparison with a clause change log
Compare two lease documents clause-by-clause — the prior version and the proposed redline — and produce a change log with each substantive difference, plain-English impact, and any risk flag.
“Compare the prior lease at ~/leases/220-pine-v1.pdf with the proposed redline at v2. Build a change log: every substantive difference, impact in plain English, and any clause that shifts risk to the landlord.”
Transaction coordinator checklist from the contract
Reads the fully executed purchase or lease contract, extracts every deadline and contingency, and builds a transaction checklist with dates, owners, and the source clause for each item.
“Read the executed contract at ~/transactions/jones-purchase.pdf and build a coordinator checklist: every deadline, every contingency, dates, and which clause it came from.”
Monthly portfolio performance report
Pulls occupancy, rent roll, delinquencies, and maintenance spend across the portfolio, compares to last month and budget, and writes a one-page report per property plus a portfolio summary.
“Build the April portfolio report. For each of the 12 properties: occupancy, rent collected, delinquencies, maintenance vs. budget. Compare to March. Roll up to a one-page portfolio summary.”
Showing-feedback summary emails
Reads a folder of agent showing notes and drafts an owner-facing summary email per property, highlighting feedback patterns and recommending next steps on price or staging.
“Read the showing notes in ~/showings/22-oak-lane for the last two weeks and draft an owner update email: feedback patterns, what we heard on price, and a staging recommendation.”
Where to be careful
- Never send a signed offer or contract. Interpreter can fill and prepare documents, but signature and transmission of executed agreements always stay with you.
- Don't change pricing without explicit approval. List price, lease rate, and credit-rebate fields should require an approval click before any update.
- Cite the source comps. Every comp used in a Lease Rate Analysis or market survey should link back to the underlying record — not summarized from memory.
- Keep tenant and owner PII in the workspace. Scope the agent to the property or transaction folder. Sensitive intake docs should never end up pasted into chat history.