Can the assistant draft from our own lease form?

That is the intended use. Your base form and riders live in a library your team controls, and the assistant assembles from them. A portfolio's form is the product of years of negotiation; the point is to draft from it, not to replace it.

How do brokers and outside counsel participate?

By invitation into the transaction room, scoped to what they should see. They work on the live instrument rather than on a forwarded copy, which is what removes the version argument.

Does it handle multi-signer execution across entities?

Yes. Multiple signers across multiple entities sign against the same version, identity is captured per signer, and where signing order matters it is enforced rather than assumed.

What happens to the dates if the lease is amended?

An amendment points at the clause it changes, so extracted obligations update from the operative text instead of continuing to reflect the original lease.

Six parties, forty dates, one thread

A property transaction is a coordination problem wearing a legal costume. Broker, landlord, tenant, lender and counsel each hold a piece, and the dates that matter are buried in the document. Paqt puts the transaction in one room and turns its deadlines into data.

Where a property deal actually slows down

Rarely on the rent. Usually on who has the current draft, which rider is attached, and whether the consent everyone assumed was obtained actually was.

Email threads and a shared drive: Five parties, five copies, no agreement on which is current
Email threads and a shared drive: Riders and exhibits travel separately and get attached to the wrong draft
Email threads and a shared drive: LOI terms are re-typed into the lease and quietly drift
Email threads and a shared drive: Consents and estoppels are chased by phone and tracked in nobody's list
Email threads and a shared drive: Commencement and option dates are read off a PDF by hand
Email threads and a shared drive: After closing, the file is a folder and the knowledge is in a person
One room per transaction: One live instrument with every version addressable and diffable
One room per transaction: Riders and exhibits attached to the instrument, versioned with it
One room per transaction: The draft is checked against the agreed LOI, clause by clause
One room per transaction: Consents are tracked items with an owner and a state, not a phone call
One room per transaction: Dates are extracted from the executed document as structured data
One room per transaction: The full record — thread, versions, approvals, signatures — exports as one package

Built for the documents property work repeats

Property paper is highly standardised within a portfolio and highly variable between them, which is exactly where drafting from your own forms beats a general-purpose model.

Letters of intent — Captured from the negotiation as structured terms, so the lease that follows can be checked against what was actually agreed rather than someone's recollection.
Leases and riders — Drafted from your base form with the riders your portfolio uses, assembled as versioned parts rather than pasted into one file.
Amendments and extensions — An amendment points at the clause it changes in the original, so the operative text is never reconstructed by reading four documents in sequence.
Consents and estoppels — Lender consent, landlord consent and estoppel certificates are tracked items with owners and states, blocking execution until they are satisfied.
Execution with many signers — Multiple signers across multiple entities sign against the same version, with identity captured per signer and the order enforced where it matters.
Closing packages — The executed lease, its exhibits, the consents and the full negotiation history export as a single file for the property record.

The dates are the whole asset

A lease is a schedule of obligations with some prose around it. Paqt extracts that schedule from the executed document, so option windows and escalations stop depending on whoever set the reminder.

Commencement and expiry — Pulled from the executed lease with the conditions that move them, so a delayed delivery date adjusts what follows instead of invalidating the calendar.
Options and notice windows — Renewal and expansion options carry their notice periods, so the window surfaces while it is still exercisable.
Escalations and reconciliations — Rent steps, operating-expense reconciliations and percentage-rent triggers are extracted as dated obligations rather than read off a schedule each year.
Evidence on demand — When a dispute turns on what the parties agreed in the third round, the turn log and version history answer it without anyone searching an inbox.

Visibility that does not leak the deal

A shared room only works if each party sees exactly its own side. Visibility is scoped per party, and the assistant's reach is scoped with it.

Parties: Per-party visibility inside one transaction room
Parties: Brokers, counsel and lenders invited to their own scope
Parties: Internal discussion separated from counterparty-visible turns
Parties: No forwarded copies, so nobody negotiates from a stale draft
Control: Approval gates on clauses your portfolio never concedes
Control: Consents as blocking conditions on execution
Control: Autonomy set per transaction type, not globally
Control: Organization-wide kill switch for all agents
Record: Every draft version addressable and diffable
Record: Riders and exhibits versioned with the instrument
Record: Signature identity captured per signer and entity
Record: Closing package exportable as one file

What property teams ask about

Can the assistant draft from our own lease form? That is the intended use. Your base form and riders live in a library your team controls, and the assistant assembles from them. A portfolio's form is the product of years of negotiation; the point is to draft from it, not to replace it.
How do brokers and outside counsel participate? By invitation into the transaction room, scoped to what they should see. They work on the live instrument rather than on a forwarded copy, which is what removes the version argument.
Does it handle multi-signer execution across entities? Yes. Multiple signers across multiple entities sign against the same version, identity is captured per signer, and where signing order matters it is enforced rather than assumed.
What happens to the dates if the lease is amended? An amendment points at the clause it changes, so extracted obligations update from the operative text instead of continuing to reflect the original lease.