Understand onboarding workflow statuses
Use only statuses implemented by the workflow.
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.
- Use only statuses implemented by the workflow.
- States include draft, context_selected, parties_confirmed, in_progress, ready_for_review, draft_confirmed_ready_for_tenant_esign, tenant_esign_pending, tenant_signed_waiting_landlord_countersign, landlord_countersign_pending, fully_executed, approved/final_approved, terminated/cancelled.
- The intended workflow step is saved with its linked agreement, evidence and financial state.
Fields, rules and limits
- States include draft, context_selected, parties_confirmed, in_progress, ready_for_review, draft_confirmed_ready_for_tenant_esign, tenant_esign_pending, tenant_signed_waiting_landlord_countersign, landlord_countersign_pending, fully_executed, approved/final_approved, terminated/cancelled.
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.