People & HR

How to offboard a departing employee as Property Management Founders

People & HRFor Property Management Founders3 apps11 steps~22 min to set up

When a leasing agent or maintenance coordinator leaves your property management firm, you're scrambling across AppFolio, Buildium, or Rent Manager to reassign their open work orders, canceling their Buildium login while hoping you haven't missed the Gmail or Outlook account they used to text vendors. Offboarding in property management isn't just HR paperwork — it's a live operational risk. Tenant requests disappear into a departed employee's inbox. Vendor relationships go dark. Owner contacts don't know who to call. A 15-door portfolio can survive a week of confusion; a 300-door one can't. Most firms handle this with a sticky-note checklist that gets longer every time someone quits.

Build this on Starch → See the apps used

People & HRFor Property Management Founders3 apps11 steps~22 min to set up

Outcome

What you'll set up

A structured offboarding checklist that covers every property management system, inbox, and vendor contact the departing employee touched — auto-triggered the day you mark someone as leaving

An email triage handoff that catches anything still arriving in the departing employee's inbox and routes active tenant requests, owner communications, and vendor threads to the right replacement

A knowledge capture step that pulls the departing employee's recurring tasks, vendor notes, and property-specific quirks into a shared team wiki before they walk out the door

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Knowledge Management Task Manager

Data sources & config

Starch syncs your Gmail (or Outlook) data on a schedule to power the inbox handoff monitoring. Starch syncs your Notion data on a schedule to pull existing property and vendor documentation into the knowledge base. Starch syncs your Paylocity data on a schedule to verify final pay run status. AppFolio and Buildium are automated through your browser — no API needed — so Starch can navigate the admin panels to confirm access has been revoked and work orders reassigned.

Prompts to copy

Monitor the inbox for maria@acmeproperty.com for the next 30 days. Flag any emails from tenants at 412 Elm St, 88 Harbor Blvd, or any of our owners. Draft a reply telling them Maria has left and that Jake is their new contact, then add each flagged thread to a handoff task list.

Create a knowledge base entry called 'Maria's Vendor Contacts and Property Notes' and pull in everything from our Notion pages she owned, including her preferred HVAC vendor for the Harbor properties, her move-out inspection checklist, and the renewal schedule she maintained for Q3.

Build me an offboarding task list for Maria's departure. Include: revoke AppFolio access, revoke Buildium login, forward her Gmail to Jake, remove her from the maintenance WhatsApp group, notify the three owners she managed, reassign her 7 open work orders, and confirm her Paylocity final pay run has processed.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect Gmail (or Outlook) as a scheduled-sync provider so Starch monitors the departing employee's inbox going forward and surfaces any incoming tenant, owner, or vendor emails that need a response.

2 Open the Email Triage app and tell Starch to watch the departing employee's address — set rules for which property addresses and owner names should trigger immediate flags and which threads should be auto-drafted with a 'new point of contact' reply.

3 Log into AppFolio or Buildium through browser automation — describe to Starch which admin screens to navigate — to pull a list of all open work orders, active leases, and scheduled inspections assigned to the departing employee.

4 Use the Task Manager app to generate a prioritized offboarding task list: work orders due within 7 days get P1, owner-facing items get P2, system access revocations get P3, and documentation tasks get P4.

5 Open the Knowledge Management app and ask Starch to pull the departing employee's Notion pages, email-threaded vendor notes, and any property-specific SOPs they owned into a structured wiki entry their replacement can search immediately.

6 Have Starch draft outreach emails to each owner the departing employee managed — pulled from your Gmail scheduled sync — introducing the replacement contact and confirming no open items fell through.

7 Use browser automation to navigate Paylocity's admin panel and confirm the final payroll run is queued correctly; Starch syncs your Paylocity data on a schedule so the task list can auto-close this step once the pay statement appears.

8 Revoke access to every tool the departing employee used: AppFolio, Buildium (browser-automated), Gmail forwarding setup, Slack channel removal, and any vendor portals they logged into on behalf of the firm.

9 Reassign the departing employee's open maintenance work orders in AppFolio or Buildium through browser automation — Starch navigates the work order queue and bulk-reassigns to the designated replacement technician or coordinator.

10 Set a 30-day follow-up reminder in the Task Manager: check whether any tenant or owner emails are still arriving at the old address, confirm the knowledge base entry has been reviewed by the replacement, and close out the offboarding checklist.

11 After 30 days, archive the offboarding task list and use it as the template for the next departure — tell Starch to save this workflow as a reusable checklist in your Knowledge Management app so you're not rebuilding it from scratch next time.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Maria's Departure — February 2026, 280-Door Portfolio

Sample numbers from a real run

Open work orders reassigned	7
Owner contacts notified	3
Inbox threads flagged and replied to in first 48 hours	14
Vendor notes captured into Knowledge Management	22
Days from notice to full system access revocation	2

Maria managed 280 doors across two AppFolio portfolios — the Harbor properties (commercial, 3 owners) and the Elm Street residential cluster (6 owners, 180 units). When she gave two weeks' notice, the firm used Starch to monitor her Gmail for incoming tenant and owner emails. In the first 48 hours, 14 threads were flagged — 9 tenant maintenance requests, 3 owner check-ins about February statements, and 2 vendor invoices for the Harbor HVAC unit. Starch drafted replies for each, introducing Jake as the new contact. Starch then navigated AppFolio through browser automation to surface Maria's 7 open work orders: 4 were scheduled for completion within the week and got reassigned to Jake immediately (P1); 3 were longer-horizon and moved to P2. Her Notion vendor notes — 22 pages covering preferred contractors, gate codes, and the renewal calendar she'd built for Q3 — were pulled into a Knowledge Management wiki entry Jake could search on day one. Paylocity confirmed her final pay run was queued by day 3. Total time from notice to full handoff: 11 days, versus the prior departure which took 6 weeks of cleanup.

Measurement

How you'll know it's working

Days from departure notice to full system access revocation across AppFolio, Buildium, Gmail, and vendor portals

Open work orders reassigned before last day (target: 100%)

Owner contacts notified with new point of contact within 48 hours of announcement

Tenant requests that went unanswered during the handoff window (target: zero)

Knowledge base entries created per offboarded employee (a proxy for institutional knowledge retained)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Spreadsheet offboarding checklist (Google Sheets or Excel)

Free and familiar, but entirely manual — someone has to remember to run it, update it, and chase every item, and it doesn't connect to your inbox, AppFolio, or Paylocity to auto-verify completion.

BambooHR or Rippling offboarding module

Good for HR paperwork and benefits termination, but doesn't touch the property management systems (AppFolio, Buildium, vendor portals) where most of the operational risk actually lives.

Notion or ClickUp task template

Better than a spreadsheet for tracking steps, but still disconnected from your actual systems — you're manually confirming every item rather than Starch automating the checks through browser automation.

Doing it ad hoc per departure

Works fine the first time someone organized handles the offboarding; breaks badly when the founder is traveling or the departing employee is the one who knew where everything lived.

On Starch RECOMMENDED

One platform — founder inbox, knowledge management, task manager all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Our property management software is AppFolio. Does Starch connect to it directly?

AppFolio doesn't publish a public API, so Starch automates it through your browser — no API needed. You walk Starch through the admin screens once (reassigning work orders, pulling open tasks, revoking login access), and it can repeat that process for each offboarding. It's not instant like a direct integration, but it's fully automated and doesn't require AppFolio to build anything on their end.

What happens to emails that still arrive in the departing employee's inbox after their last day?

Starch syncs their Gmail or Outlook on a schedule, so incoming threads keep getting surfaced even after the employee is gone. You can set rules — 'any email mentioning a property address or an owner name gets flagged and drafted' — and Starch will keep monitoring for as long as you want. Most firms run this for 30–60 days post-departure.

Can Starch actually revoke AppFolio or Buildium logins, or does someone still have to do that manually?

Starch can navigate to the user management section of AppFolio or Buildium through browser automation and walk through the revocation steps. Whether a human clicks the final confirm button or Starch does it end-to-end depends on how you set it up — most operators prefer Starch to surface the screen and confirm the action rather than fully automate an irreversible step.

We use Paylocity for payroll. Can Starch confirm the final pay run without someone logging in manually?

Yes. Starch syncs your Paylocity data on a schedule, which means final pay statements appear in Starch automatically once Paylocity processes them. The offboarding task list can auto-close the 'confirm final payroll' step when the pay statement shows up — no manual login required.

Is Starch SOC 2 certified? I'm handling employee payroll data and owner financials.

Not yet — Starch is not currently SOC 2 Type II certified. That's worth knowing before connecting sensitive payroll or financial accounts. Many property management firms at the under-500-door scale accept this tradeoff given the operational value, but it's an honest limit and you should weigh it against your owners' data-handling expectations.

What if the departing employee's vendor relationships were mostly in their personal email or their head — not in any system?

That's where the Knowledge Management step matters most. Before their last day, use Starch to run a structured exit interview that captures vendor names, contact info, gate codes, property quirks, and anything else that's undocumented. Starch can pull from any Notion pages or Gmail threads they own and prompt them to fill in the gaps. It won't surface knowledge that was never written down, but it closes most of the gap for employees who did any documentation at all.