How to track open roles as Independent Clinic Owner-Operators

People & HRFor Independent Clinic Owner-Operators3 apps10 steps~20 min to set up

You have three providers, two of whom are part-time, and open roles rotate constantly — a medical assistant leaves, a biller goes on maternity leave, a second therapist slot opens because your caseload finally justifies it. Right now you're tracking this in a shared Google Sheet that nobody updates consistently, a Slack thread from March, and your own memory. You posted on Indeed two weeks ago and you're not sure if anyone followed up on the applicants. There's no system that connects your open headcount to your actual schedule gaps — you're making staffing decisions based on vibes and whoever called you last week.

People & HRFor Independent Clinic Owner-Operators3 apps10 steps~20 min to set up
Outcome

What you'll set up

A single living tracker for every open role at your clinic — position, status, who's interviewing, and which provider slot it's covering — visible to you and your office manager without digging through email.
An AI task list that turns 'we need a front desk replacement by June 1' into dated action items — post job, screen resumes, schedule interviews, check references — so nothing slips between your clinical days.
Automated reminders that flag when a role has been open more than 30 days or when an interview follow-up is overdue, so you catch stalls before they become coverage crises.
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.

Data sources & config

Project Management and Task Manager run natively inside Starch — no external sync needed. Knowledge Management connects to Notion (Starch syncs your Notion pages on a schedule) if you already have onboarding docs there, or you can build the knowledge base from scratch inside Starch. For sourcing, Starch automates Indeed, LinkedIn job boards, and any state healthcare job board through your browser — no API needed — to check application counts and post updates.

Prompts to copy
Create a project called 'Open Roles — Q2 2026'. Add three tasks: 'Hire medical assistant (MA2 backfill) — post by April 20, fill by May 15'; 'Hire part-time biller — post by May 1, fill by June 1'; 'Hire second therapist — fill by July 1'. Tag each with the provider it's covering and the revenue impact if the slot stays empty.
Every Monday morning, show me any open-role task that's been sitting in the same stage for more than 7 days and flag it as overdue.
Build me a knowledge base article called 'Hiring SOPs for clinic roles' with sections for: where we post (Indeed, local healthcare job boards), our standard interview steps, who does reference checks, and our onboarding checklist for each role type.
Run these in Starch → or paste them into your favorite agent
Walkthrough

Step-by-step

1 Open Starch Project Management and describe your current open roles in plain language: 'I have three open positions — medical assistant, part-time biller, and a second therapist. Each one has a target fill date and a hiring manager (usually me or my office manager).' Starch creates the project structure.
2 For each role, add a task with the position title, which provider schedule it's blocking, the target hire date, and the revenue per week the slot is unfilled. This is your live pipeline, not a spreadsheet.
3 Break each role into subtasks using the Task Manager: post job listing, screen applications (target date: 5 business days after posting), phone screen top 3 candidates, in-clinic interview, reference check, offer sent. Assign due dates to each.
4 Set a recurring Monday morning prompt in Starch: 'Show me every open-role task that hasn't moved stages in 7+ days.' This replaces the mental overhead of remembering where each hire stands.
5 Connect your Google Calendar (Starch syncs your Google Calendar on a schedule) so interview slots the office manager books automatically appear alongside the hiring task — you see the interview date without asking anyone.
6 Use Starch browser automation to check your Indeed or LinkedIn job posting once a week: 'Go to our Indeed employer account and tell me how many applications we have for the medical assistant role and what the average response rate has been.' No Indeed API needed.
7 Build a Knowledge Management article for each role type — MA, biller, front desk, therapist — that documents your hiring criteria, red flags, and onboarding steps. New hires and your office manager can reference it without calling you.
8 When a candidate moves to offer, create a Task Manager item: 'Send offer letter for [name], MA role, by [date]. If no response in 48 hours, follow up.' P1 priority so it doesn't get buried.
9 When a role is filled, close the project task and immediately open a new task: 'Begin onboarding [name] — first day [date]. Assign credentialing, EMR access, schedule shadow shifts.' The hiring and onboarding pipeline stays in one place.
10 At the end of each month, ask Starch: 'Show me all roles we opened and closed this quarter, how long each was open, and which ones missed their target fill date.' Use the answer to pressure-test whether your 30-day fill targets are realistic for each role type.

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

April–May 2026 MA Backfill After Sudden Departure

Sample numbers from a real run
Medical assistant vacancy — revenue at risk4,200
Temp agency coverage (3 weeks)2,100
Time spent screening (owner-operator hours, 6hrs @ $180/hr equiv.)1,080
Offer accepted — fill date May 12 (23 days open)0

Your MA gave two weeks notice on April 8. You opened a Starch project that same day: 'MA backfill — must fill by May 1 or we book a temp.' Starch created five subtasks with due dates. The browser automation check on April 14 found 11 Indeed applications; you screened them that afternoon using the Knowledge Management rubric you'd built for the MA role. Three phone screens happened April 16–17 (Google Calendar sync showed your office manager had blocked those slots already). One candidate went to in-clinic interview April 22, reference check April 25, offer sent April 26. She accepted April 28. Onboarding task auto-created for May 12 start. Total time the role was open: 23 days. The Monday stall-check on April 21 flagged that the reference check task was sitting unstarted — you reassigned it to the office manager that morning instead of letting it drift. Temp agency cost: $2,100 for three weeks of partial coverage. Without the tracking, this hire would have taken 6–8 weeks based on your last MA search.

Measurement

How you'll know it's working

Days to fill per role type (target: <30 days for MA/front desk, <45 days for licensed clinicians)
Number of roles open >30 days at any point in the quarter
Revenue per week lost to unfilled provider-facing support roles (e.g., MA vacancy reduces provider throughput by ~15%)
Offer acceptance rate (are your comp ranges competitive for your market)
Onboarding completion rate at 30 days — did new hires actually get credentialed, trained, and scheduled on time
Comparison

What this replaces

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

Google Sheets shared hiring tracker
Free and you already have it, but nobody updates it consistently and there's no alerting when a role stalls — you find out when coverage falls apart.
Indeed / LinkedIn employer dashboard alone
Good for sourcing applicants, but tells you nothing about your internal pipeline, interview scheduling, or onboarding status — you still need a separate tracker.
BambooHR or Rippling ATS
Purpose-built for hiring and onboarding, but priced for 20+ employee orgs, requires configuration time you don't have, and doesn't connect to your scheduling or inbox the way Starch does.
Notion hiring database
Flexible and free at small scale, but requires manual upkeep, no AI reminders, and it's one more tab your office manager has to remember to open.
On Starch RECOMMENDED

One platform — project management, task manager, knowledge management 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

Does Starch integrate with my EHR for credentialing or scheduling new hires?
Starch connects to Google Calendar (synced on a schedule) and can automate web-based EHR portals through your browser — so if your EHR has a provider setup or credentialing page you log into, Starch can navigate it. It doesn't have a direct API integration with Jane, SimplePractice, Kareo, or Dentrix today. For those, browser automation covers the web-facing steps; anything requiring backend EHR access still needs manual handling.
Can Starch post job listings to Indeed or LinkedIn for me?
Yes — Starch automates LinkedIn and web-based job boards through your browser, no API needed. It can log into your employer account, check application counts, and help you draft or update a posting. It won't guarantee a specific Indeed API integration, but if you can do it in a browser, Starch can do it.
What if I only have one or two open roles at a time — is this overkill?
No. The value isn't complexity, it's not dropping the ball. A single MA vacancy that stays open an extra three weeks because nobody followed up on the reference check is a real cost. Starch's task tracking and stall alerts work just as well for one role as for five.
Is my hiring data secure? I'm worried about candidate information.
Starch is not SOC 2 Type II certified today — that's worth knowing. There's no on-premise option. For a small clinic tracking role status, interview stages, and internal notes, most owner-operators find that acceptable. If you're storing detailed candidate background check results or medical credentialing documents, keep those in a dedicated HR system and use Starch for the workflow coordination layer.
Can my office manager use this too, or is it just for me?
Yes — Project Management and Task Manager in Starch are team-facing. You can assign tasks to your office manager, set due dates, and both of you see the same pipeline. The Knowledge Management wiki is also shared, so onboarding SOPs your office manager writes are visible to you and vice versa.
We use Notion for some of our internal docs already. Can Starch pull those in?
Yes. Starch syncs your Notion pages on a schedule — databases, pages, and users — so your existing hiring docs or onboarding checklists in Notion are searchable inside Starch's Knowledge Management without rewriting them.

Ready to run track open roles on Starch?

Request closed-beta access. Everything is free during beta.

You're on the list! We'll be in touch soon.