People & HR

How to track pto and time off as Foundation and Nonprofit Ops Teams

People & HRFor Foundation and Nonprofit Ops Teams3 apps12 steps~24 min to set up

Your four-person ops team tracks PTO and time off across a mix of Paylocity or ADP payroll records, a shared Google Sheet someone built two years ago, and whatever your ED keeps in their head. When a program officer takes a week off mid-grant-cycle, you find out when their grantee follow-ups stop happening. There's no central view of who's out when, no accrual summary that doesn't require someone to log into payroll and export a CSV, and no connection between your capacity and your grant calendar. During Q4 compliance season, half the team taking time off and nobody flagged it against board-meeting prep deadlines.

Build this on Starch → See the apps used

People & HRFor Foundation and Nonprofit Ops Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A live PTO dashboard that pulls accrual and balance data from Paylocity or ADP directly, so you're not chasing exports or asking HR to run a report

An automated time-off calendar that overlays staff absence windows against your grant deadlines, board meetings, and 990 filing dates so you can see capacity conflicts before they become missed obligations

A simple internal booking and approval flow for time-off requests that logs approvals, notifies the right people, and updates the shared view — no spreadsheet maintenance required

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

Scheduling Knowledge Management Task Manager

Data sources & config

Starch syncs your Paylocity or ADP data on a schedule — employee records, pay periods, and time-off balances come in automatically. Google Calendar connects via scheduled sync so grant deadlines and board dates pull in alongside staff absence windows. Salesforce (where your grant pipeline lives) connects from Starch's integration catalog and is queried live when your capacity dashboard runs. Any time-off request portal or HR system that doesn't have a direct integration is reachable through browser automation — no API needed.

Prompts to copy

Build me a PTO tracker that pulls current leave balances and accrual rates from Paylocity for each staff member and shows them in a single table. Add a column for planned time off over the next 90 days and flag any week where more than one person is out.

Create a policy doc in our Knowledge Management wiki that explains our PTO accrual schedule, carryover rules, and request process. Make it searchable so staff stop asking me the same questions every January.

Set up a task that reminds me every Monday if any staff member has more than 15 days of accrued PTO that they haven't scheduled — I don't want surprise payouts at year end.

Build a calendar view that layers staff time-off windows on top of our board meeting dates, grant reporting deadlines, and 990 filing windows so I can spot capacity gaps at a glance.

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

Walkthrough

Step-by-step

1 Connect Paylocity or ADP as a scheduled-sync provider. Starch pulls employee records, accrual balances, and approved time-off requests automatically on a schedule — you stop logging in to export CSVs.

2 Connect Google Calendar via scheduled sync. Starch reads your team calendar (12 months back, 3 months ahead) so grant reporting deadlines, board meetings, and 990 filing dates are available as context for the PTO dashboard.

3 Connect Salesforce from Starch's integration catalog. The agent queries your grant pipeline live so the capacity view can flag when a program officer's absence overlaps with a grantee check-in or grant closeout date.

4 Tell Starch to build the PTO dashboard: 'Show me each staff member's current accrual balance, days taken year-to-date, and planned time off over the next 90 days. Flag any week where more than 50% of the program team is out simultaneously.'

5 Add the grant-calendar overlay: 'Pull in our board meeting dates from Google Calendar and our grant reporting deadlines from Salesforce. Show me any week in the next quarter where a staff absence coincides with a major deadline.'

6 Set up a Monday morning automation: 'Every Monday, check Paylocity for any staff member with more than 15 accrued PTO days and no time off scheduled in the next 60 days. Send me a Slack message with their names and current balances.'

7 Use the Knowledge Management app to publish your PTO policy — accrual rates, carryover cap, blackout periods around 990 season and board prep weeks — as a searchable wiki page. Staff find it themselves instead of emailing you.

8 Use the Scheduling app to give staff a booking link for time-off check-ins with you during the annual review cycle, so you're not coordinating one-on-ones across email threads in December.

9 Set a Task Manager reminder to review PTO balances in November before fiscal year-end. If your foundation has a use-it-or-lose-it policy, catching this in November is much cheaper than surprise payouts in December.

10 If your time-off request workflow runs through a portal that doesn't have a direct integration (an older HR system or a state-mandated leave tracker), tell Starch to automate it through the browser — it logs in, checks the status, and updates your dashboard without you touching it.

11 Share the PTO dashboard link with your ED so they have a live view before approving requests. You stop being the relay between the ED and payroll every time someone asks for a week off.

12 At each quarter's end, run a natural-language query against your PTO data: 'Summarize time-off taken by department this quarter, total days, and remaining balances. Flag anyone who is at risk of forfeiting days before fiscal year close.' Use it for your ops update to the board.

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

Q3 2026 Capacity Review — August Board Prep Crunch

Sample numbers from a real run

Program Officer (East Coast grantees)	8
Grants Manager	3
Finance & Ops Associate	5
Executive Director	0

It's late July 2026. Your board packet is due August 14th and your 10 active grantees have Q2 narrative reports coming in the same week. The PTO dashboard flags a problem you would have missed: your Program Officer has 8 days of approved vacation August 4–15, your Finance & Ops Associate has 5 days August 11–15, and your Grants Manager has 3 days August 7–9. That's the entire program and finance function out during the two weeks you need to write, review, and finalize a 30-page board packet. The dashboard surfaced this in early July, not August 1st. You reschedule the Finance & Ops Associate's time off by one week, confirm the Grants Manager can handle grantee report intake remotely, and move one program site visit from August to September. No scramble, no board packet crisis, no grantee relationship damage. The same view shows your ED has zero PTO taken in 2026 and 18 days accrued — a separate flag you surface in your July 1:1.

Measurement

How you'll know it's working

Accrued PTO liability per staff member at fiscal year-end (foundations with use-it-or-lose-it policies watch this to avoid surprise payouts)

Number of grant deadlines or board-prep weeks with more than 50% of program staff on leave simultaneously

Average days between time-off request and ED approval (a proxy for how much ops overhead the current process creates)

PTO utilization rate by quarter (underpaid nonprofit staff who don't take leave is a retention and burnout signal your ED should see)

Days of compliance-period coverage gaps — weeks during 990 prep or audit season where your finance function is below minimum staffing

Comparison

What this replaces

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

Paylocity or ADP built-in HR portal

Both have native time-off tracking, but neither overlays leave against your grant calendar, Salesforce pipeline, or board deadlines — you still have to reconcile capacity manually every time a request comes in.

Shared Google Sheet

Free and already in place for most teams, but it goes stale the moment someone forgets to update it, has no connection to payroll accruals, and can't alert you to conflicts with grant obligations.

Bamboo HR or Rippling

Purpose-built HR platforms with good time-off modules, but they're another standalone system that doesn't connect to your grant calendar, Salesforce, or QuickBooks without expensive integrations or manual exports — and they add a per-seat cost that's hard to justify for a 4-person team.

Fluxx or Foundant (grants management platforms)

These are your grants database, not your HR system — they don't track staff PTO at all, and at six-figure licensing costs they're not where you want to solve a time-off visibility problem.

Notion or Confluence wiki for policy docs

Fine for storing your PTO policy text, but static — it won't alert staff when the policy changes, surface relevant sections automatically, or connect to your actual accrual data in payroll.

On Starch RECOMMENDED

One platform — scheduling, 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

We use ADP, not Paylocity. Does this still work?

Yes. Starch syncs your ADP data on a schedule — workers, org units, and pay statements come in automatically. The PTO dashboard and capacity views work the same way regardless of which payroll provider you're on.

We don't have a formal HR system — PTO is tracked in a Google Sheet and approved over email. Can Starch still help?

Yes, and this is actually where Starch adds the most value. You can build a structured PTO tracker from scratch — describe what you want and Starch builds it. If you eventually want to connect a payroll system, that's additive. Start with what you have: Google Calendar via scheduled sync, your existing Sheet via Starch's integration catalog, and a clean dashboard on top.

Is Starch SOC 2 Type II certified? We have data governance requirements from our board.

Not yet — Starch is not currently SOC 2 Type II certified. If your foundation requires SOC 2 compliance for any vendor handling employee data, that's a real constraint worth naming to your board before deploying. It's on the roadmap.

Can Starch handle FMLA tracking or state-mandated leave — not just discretionary PTO?

Starch can surface and track whatever data your HR system (Paylocity, ADP) records against each employee. If your payroll system codes FMLA or state leave separately, Starch pulls that through. It won't generate legal compliance documentation or replace an HR attorney's guidance on leave law, but it will give you visibility into who's on what type of leave and for how long.

What happens if our HR system has a portal but no formal API connector?

Starch automates it through your browser — no API needed. If your state-mandated leave tracker or older HR portal is web-based and you can log in and click through it, Starch can do the same. That said, for the major payroll providers (Paylocity, ADP), there's a direct scheduled-sync connection so you get cleaner, more reliable data.

We're a team of four. Is this overkill?

The PTO tracker itself takes an hour to set up. The value isn't that it saves you hours every week on a four-person team — it's that it catches the capacity conflict you'd otherwise discover on August 1st when your board packet is due August 14th. For a small ops team running a $50M foundation, one prevented scheduling crisis pays for the setup many times over.