Property Operations

Lease renewal workflow

Lease dates and decision ownership remain in property records until review and tenant communication windows become compressed.

Business problem

Lease dates and decision ownership remain in property records until review and tenant communication windows become compressed.

What teams see

  • Work waits between monitor lease dates and calculate review window.
  • Owners reconstruct status from Property management system and Microsoft 365.

Why it happens

  • No shared state spans Property management system, Microsoft 365, Cloud storage.
  • Decision and exception rules are applied inconsistently.

Why it becomes expensive

  • Capacity is consumed by coordination and rework.
  • Late exceptions weaken visibility and service quality.

Business outcomes

  • Shorter generate documentation cycle
  • Fewer handoff and missing-information exceptions
  • Clear ownership from monitor lease dates to generate documentation
  • Inspectable decisions and recovery

Measurable KPIs

  • Turnaround time: Elapsed time from monitor lease dates to generate documentation.
  • Manual intervention rate: Share of items needing a person outside defined review conditions.
  • Exception age: Time unresolved exceptions remain without a completed action.
  • Successful completion rate: Share of valid workflow items completing without terminal failure.

How the workflow works

  1. Monitor lease dates — Accept and identify the lease renewal workflow trigger. Property management system
  2. Calculate review window — Execute calculate review window with validated sample data and an auditable result. SEIDO Review Queue
  3. Notify property owner — Execute notify property owner with validated sample data and an auditable result. Microsoft 365
  4. Collect commercial review — Execute collect commercial review with validated sample data and an auditable result. SEIDO Review Queue
  5. Approve position — Execute approve position with validated sample data and an auditable result. Property management system
  6. Contact tenant — Execute contact tenant with validated sample data and an auditable result. Microsoft 365
  7. Record decision — Execute record decision with validated sample data and an auditable result. SEIDO Review Queue
  8. Generate documentation — Execute generate documentation with validated sample data and an auditable result. Property management system
  9. Audit and KPI update — Persist the execution outcome, audit facts and workflow measurement events. SEIDO execution store

Integrations and ownership

  • Property management system: Provide workflow input
  • Microsoft 365: Lookup and update context
  • Cloud storage: Receive controlled outcome

Human responsibility: Property manager

Failure and recovery

Property management system is temporarily unavailable.

Retry with capped exponential backoff; preserve the run and move it to the inspectable failure queue after the limit.

Required data for calculate review window is malformed or missing.

Stop downstream actions and show the missing fields, source evidence and correction action to the named reviewer.

The trigger or provider event is delivered more than once.

Return the existing execution identified by the idempotency key and do not repeat downstream business actions.

The human decision expires before completion.

Escalate to the configured substitute, retain the original request and record both expiry and reassignment.

When not to build this

  • Monthly volume is too low to justify integrating Property management system, Microsoft 365, Cloud storage.
  • An existing configured platform already handles lease renewal workflow with adequate ownership and reporting.
  • Reliable source data or supported API access is unavailable.
  • No business owner has authority to define the decision and exception rules.

Related workflows