Before you begin
- Have the existing tenancy and signed agreement reference available.
- Confirm the intended new end date, rent, due day and the reason for the change.
- Know who must sign and whether the tenancy already has a notice or planned move-out that needs separate review.
The illustrations use fictional demonstration records. Follow your organisation’s review and approval process before issuing changes.
Keep a clear history of what changed without overwriting the original agreement.
What the workflow coordinates
The interface describes renewal-document creation and post-signature application of new rent/end dates, and routes changes to signed terms through an amendment while retaining locked versions.
What people review
People agree the proposed terms, explain the change, review every signer and verify the tenancy record after completion.
Identify the tenancy needing a decision
Open the intended tenancy and check its reference, unit, people, rent and dates before deciding whether a renewal or a term correction is needed.
The intended tenancy and its existing notice or expiry context are clear.
The intended tenancy and its existing notice or expiry context are clear.
Check agreement and document records
Read Agreements & versions separately from Documents. Sofia’s current tenancy says no agreement is on file, while Documents contains a tenant-visible agreement file; those are distinct record types.
Confirm current availability before attempting this stage.
Confirm current availability before attempting this stage.
Review the renewal effect
Open Renew. The current dialog says it changes the end date, rent and due day now and records the change in term history. Review all values before the final Renew action; it was not submitted during capture.
The renewal proposal is ready for signature with the intended new terms.
The renewal proposal is ready for signature with the intended new terms.
Amendment route: explain the change
Use More actions → Change rent or dates. The current form includes rent, end date, due day, initial down payment and a reason, and says a before → after record is saved on the timeline. The example remains unsaved.
The amendment records both the proposed values and the reason for changing them.
The amendment records both the proposed values and the reason for changing them.
Separate agreement workflows
Review the Agreements register if a separate agreement workflow is relevant. Do not assume the current Renew or Save change form waits for signatures; read the message on the actual form.
Any outstanding signer is visible before the proposal is treated as agreed.
Any outstanding signer is visible before the proposal is treated as agreed.
Check effective terms and history
After an authorised change in normal operation, check the effective terms and the corresponding history/timeline entry. This documentation review did not change the tenancy or create a signed version.
Confirm current availability before attempting this stage.
Confirm current availability before attempting this stage.
What you should have at the end
The intended change, its current effect and the record that should explain it are understood; the documentation example remains unsaved.
Demonstration notes and availability
- Reviewed against the official demo at demo.estatereal.io. Screenshots are native 3× captures in English/light mode. Preset records and enabled functions can change.
- This review followed navigation, record tabs and unsaved forms. It did not submit payments, signatures, invitations, messages or irreversible record changes.
- Current demo limits: The selected tenancy has no agreement version/signers record on file. The current Agreements tab is illustrated instead.
Useful answers
Does the current Renew form wait for signatures?+
Its visible message says the end date, rent and due day change now and are recorded in term history. Do not follow the older guide’s signature-gated description for this form.
How is a direct term change described?+
More actions → Change rent or dates opens a form whose message says a before → after record is saved on the timeline. The review did not submit that change.
Is a document file the same as an agreement-version record?+
No. The reviewed tenancy has a tenant-visible agreement document but no agreement record on file in Agreements & versions. Check the relevant record type before explaining signing or version history.