Confirm the draft for tenant e-signature
Approve the agreement draft for the tenant-signing stage.
Before you start
Use tenant Edit and an accessible property/application. The workflow checks current state, parties, compliance, signatures and payment gates separately.
Follow these steps
- Open the saved onboarding draft from Onboarding workspace.
- Approve the agreement draft for the tenant-signing stage.
- The workflow can move to draft_confirmed_ready_for_tenant_esign then tenant_esign_pending.
- Use the task-specific action below, then reload the workflow and inspect the resulting state.
Fields, rules and limits
- The workflow can move to draft_confirmed_ready_for_tenant_esign then tenant_esign_pending.
- Tenant signing precedes the landlord countersignature. Ready for Review and Approve Pack remain gated until both signatures exist. Final approval also checks the required first rent invoice payment. If signing succeeded but delivery failed, use the pending-delivery retry rather than asking the parties to sign again.
Check it worked
The intended workflow step is saved with its linked agreement, evidence and financial state.
If something does not look right
If the expected result is missing, check the saved record, the current workspace and the action’s permissions. Record the exact validation message; do not repeat a state-changing action until you know whether the first attempt saved.
Questions and answers
Why is the next workflow action unavailable?
The workflow evaluates its saved state, party links, compliance requirements, agreement confirmation, signatures and payment gate. Resolve the displayed blocker instead of manually changing the status.
Should the parties sign again after a delivery error?
Check the saved execution evidence first. If signatures are retained and PDF/email delivery is pending, use the retry-delivery action for the unfinished delivery work.