People & HR

How to track open roles as Foundation and Nonprofit Ops Teams

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

Your foundation has eight open roles across program, grants management, and finance — and tracking them means toggling between a shared Google Sheet someone built two years ago, an ATS your ED half-configured, and Slack threads where hiring managers drop updates that immediately get buried. You don't have an HR team. The ops manager who owns recruiting also owns board prep and 990 compliance. When a program officer asks 'where are we on the grants-management coordinator search?' the answer requires opening three tabs and doing mental arithmetic. Offer deadlines slip, finalist panels get scheduled over board calls, and you're three months into a search before anyone notices the job description still has the wrong salary band.

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 open-roles dashboard that pulls candidate status from your ATS and shows every active search by role, hiring manager, stage, and target close date — no manual updates required.

Automated weekly digests that summarize where each search stands, flag roles that have been open longer than your target window, and surface any finalist-stage candidates who haven't had follow-up in more than five business days.

A shared knowledge base of job descriptions, interview rubrics, and offer templates that your small team can actually find when they need them — searchable by role type, program area, or date.

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

Project Management Knowledge Management Task Manager

Data sources & config

Connect Greenhouse from Starch's integration catalog — the agent queries it live when the open-roles app runs to pull current requisition and candidate stage data. Connect Slack from Starch's integration catalog for weekly digest delivery. Google Calendar syncs on a schedule so Starch can cross-check interview panel slots against board and staff meeting conflicts. Job descriptions and templates stored in Notion sync on a schedule and power the knowledge-management search surface.

Prompts to copy

Build me an open-roles tracker with columns for role title, department, hiring manager, current stage (sourcing / screening / finalist / offer / closed), date posted, target close date, and number of active candidates. Pull in any open requisitions from Greenhouse by querying it live. Flag any role that has been open more than 60 days in red.

Create a knowledge base section for recruiting that stores our job descriptions, interview question banks by role type, offer letter templates, and our comp bands for program vs. operations roles. Surface a search bar so anyone on the team can find the right template in under 30 seconds.

Set up a weekly automation: every Monday at 8am, summarize the status of all open searches, list any finalist-stage candidates who haven't had an activity update in five or more business days, and send the digest to our ops Slack channel.

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

Walkthrough

Step-by-step

1 Connect Greenhouse from Starch's integration catalog. The agent will query your active requisitions live — role title, department, hiring manager, stage, and candidate count — every time the dashboard loads.

2 Connect Notion via Starch's scheduled sync so your existing job descriptions, rubrics, and offer templates are available inside the knowledge-management app without copy-pasting.

3 Connect Google Calendar via Starch's scheduled sync so the system can flag interview scheduling conflicts with board prep weeks or all-staff calls before they happen.

4 Connect Slack from Starch's integration catalog so automated digests and role-status alerts post to the right channel without requiring anyone to log into Starch to see them.

5 Describe your open-roles tracker in plain language — which fields matter to your foundation, what a 'stale' search looks like (60 days open, no finalist in 30 days), and who the hiring managers are for each department.

6 Use the Project Management app to create a kanban board with lanes for each recruiting stage. Tell Starch: 'Create a project board for our open searches with stages: sourcing, phone screen, panel interview, finalist, offer extended, closed. Pull open roles from Greenhouse and create one card per active requisition.'

7 Set up the Knowledge Management app with a recruiting section. Upload or point to your existing job description templates, interview rubrics, and comp band documents so they're searchable by anyone on the ops team — not just the person who made them.

8 Build a 60-day-open alert: 'Any role that has been in active status for more than 60 days without reaching finalist stage should appear on a weekly exception report.'

9 Build the finalist follow-up alert: 'Flag any candidate who has been in finalist stage for more than five business days without a logged activity update in Greenhouse and include them in the Monday digest.'

10 Wire the Monday morning digest automation to post a plain-language summary to your ops Slack channel — number of open searches, roles with no movement this week, upcoming interview panels, and any offer deadlines in the next 14 days.

11 Add a Task Manager capture prompt so any team member can type 'remind me to send the offer letter for the grants coordinator role by Thursday' and have it land in their personal task list with a due date and priority level.

12 Review the board-prep template in the Knowledge Management app: before each quarterly board meeting, the system surfaces a snapshot of open searches, time-to-fill by department, and any searches that started but were paused — so the ops lead isn't manually pulling that together the week of.

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

Q1 2026 Hiring Cycle — Three Concurrent Searches

Sample numbers from a real run

Grants Management Coordinator (Program)	94
Finance & Compliance Associate (Operations)	71
Program Officer, Climate Equity (Program)	48

In January 2026, the foundation is running three concurrent searches. The Grants Management Coordinator role has been open 94 days — 34 days past the foundation's 60-day target — but that fact was buried in a spreadsheet no one had opened since December. The Finance & Compliance Associate search is at 71 days; two finalists were identified three weeks ago but neither has had a follow-up call scheduled because the hiring manager thought the ops lead was handling it, and the ops lead thought the ED was. The Program Officer search is the newest at 48 days and on track. When the ops lead wires the Starch open-roles tracker in early February, Monday's first automated digest surfaces all three problems in one Slack message: the Grants Management Coordinator card is flagged red (94 days, no finalist), the Finance Associate card shows two finalists with 21 days of inactivity, and the Program Officer card is green. The ops lead spends 20 minutes resolving the coordinator role (extending the posting, briefing the panel) and 10 minutes scheduling the two finance finalist calls — instead of discovering the problem at the board meeting prep session the following week.

Measurement

How you'll know it's working

Time-to-fill by role type (program vs. operations), tracked against a 60-day target

Number of open searches with no candidate activity in the past 5 business days (finalist stage) or 14 days (earlier stages)

Offer acceptance rate — tracked per search cycle to catch comp-band misalignment early

Search abandonment rate — roles opened but paused or closed without a hire, flagged for board reporting

Interview-to-offer conversion rate by department, surfaced quarterly for ED and board HR committee

Comparison

What this replaces

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

Shared Google Sheet + manual Slack updates

Zero cost but requires someone to manually update every row; data is stale by default and no one sees the 60-day flag until the spreadsheet owner happens to open it.

Greenhouse alone (no surrounding ops layer)

Greenhouse tracks candidates well but has no cross-search digest, no Slack automation, and no way to surface 'stale finalist' flags to a small ops team that isn't logging in daily.

Workday or Rippling ATS

Enterprise ATS features your 4-person ops team won't configure or maintain; licensing cost is hard to justify when you're running 4-6 searches per year rather than 40.

Notion database (DIY recruiting tracker)

Flexible and owned by the team, but requires manual data entry from the ATS, no automated alerts, and the template degrades as soon as the person who built it leaves.

Fluxx / Foundant (purpose-built foundation software)

Built for grants management, not recruiting operations; six-figure licensing assumes a dedicated grants team and doesn't solve the open-roles tracking problem that lives outside those workflows.

On Starch RECOMMENDED

One platform — project management, 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 Greenhouse for applicant tracking. Does Starch sync all our open requisitions automatically?

Greenhouse is available through Starch's integration catalog — the agent queries it live when your open-roles dashboard or digest automation runs. You'll see current requisition status, stage, and candidate counts without any manual export. It's not a scheduled background sync the way Starch handles QuickBooks or Plaid, so the data is current as of the moment the app queries it.

What if our ATS is something other than Greenhouse — Lever, BambooHR, or a home-grown spreadsheet?

Lever, BambooHR, and Greenhouse are all reachable from Starch's integration catalog. If your tracking lives in a Google Sheet or Airtable, those are also in the catalog and the agent can query them live. If your system is a custom internal portal, Starch can automate it through your browser — no API needed.

Is Starch SOC 2 Type II certified? We have to answer that question for our board.

Not yet. Starch is not currently SOC 2 Type II certified. If your board's data governance policy requires SOC 2 Type II for any tool touching HR or candidate data, that's an honest constraint worth naming. It's on the Starch roadmap but we won't tell you it exists when it doesn't.

We don't have a dedicated HR person. Can a program officer or finance associate actually set this up?

That's the point. There's no drag-and-drop workflow builder and no configuration form to fill out. You describe what you need in plain language — 'show me all open searches, flag anything over 60 days, send a Monday digest to Slack' — and Starch builds the app. The person setting it up doesn't need technical skills; they need to know what they want to see.

Can Starch store our job descriptions and interview rubrics so the whole team can find them?

Yes. The Knowledge Management app is built for exactly this — a searchable team wiki that AI can search across instantly. If your documents already live in Notion, Starch syncs your Notion data on a schedule and surfaces it through the knowledge base search. You can also upload documents directly. The goal is that when a program officer needs the interview rubric for a grants management role, they find it in under 30 seconds instead of pinging the ops lead.

Will the Monday digest tell us when a finalist hasn't heard back in too long?

Yes, that's a concrete thing you can configure. Tell Starch: 'Flag any candidate in finalist stage with no logged activity in Greenhouse for more than five business days and include them in the Monday digest.' The automation runs on your schedule, queries Greenhouse live, and posts the flagged names and role titles to Slack. You define what 'stale' means — five days, seven days, whatever fits your process.