Internal Comms & Meetings

How to run an async standup as Small HR Teams

Internal Comms & MeetingsFor Small HR Teams3 apps10 steps~20 min to set up

Your team of two is trying to coordinate 150 people's weekly priorities without turning every Monday into a meeting marathon. Right now that means a Slack message asking everyone to drop their updates, which half the team ignores, a quarter posts on Tuesday, and the rest you chase via DM. You end up reading 40 disconnected Slack threads to figure out who's blocked on what, manually pulling themes to report to the CEO, and nobody actually knows if the onboarding coordinator finished the I-9 audit or if the benefits open enrollment tasks are actually moving. There is no system — just a Slack channel that becomes a graveyard by Wednesday.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small HR Teams3 apps10 steps~20 min to set up

Outcome

What you'll set up

A structured async standup loop where every team member's update lands in one place, gets summarized by priority, and routes blockers to the right person — no chasing required

A weekly digest you can forward to the CEO or department heads that shows actual status on HR priorities (open reqs, onboarding steps, review cycle progress) without you writing it from scratch

An action item tracker that captures commitments from standup updates so nothing disappears into a Slack thread — connected to your project view so tasks have owners and due dates

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

Task Manager Project Management

Data sources & config

Connect Slack from Starch's integration catalog (the agent queries it live to send prompts and read responses). Connect Gmail via Starch's scheduled sync so the Email Triage app can surface HR-related threads each morning. Wire the Task Manager to capture action items from standup summaries. If you use Paylocity or ADP, Starch syncs your employee and time-off data on a schedule so the digest can reference headcount and PTO context without manual lookups.

Prompts to copy

Build me an async standup tracker for my HR team. Every Monday at 9am, send a prompt via Slack asking each person: what did you finish last week, what are you working on this week, and are you blocked on anything? Collect responses through end of day and summarize them into a digest for me by 5pm.

Create a weekly HR priorities digest that pulls the standup responses, groups them by theme (onboarding, payroll, recruiting, benefits, compliance), flags any blockers, and drafts a summary I can send to the CEO.

Triage my inbox each morning and pull out any emails related to open HR action items — onboarding checklists, benefits questions, manager requests for review cycle help — and surface them with a one-line summary and suggested reply.

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

Walkthrough

Step-by-step

1 Connect Slack from Starch's integration catalog. The agent will use it to send standup prompts to each team member and read their responses when building the digest.

2 Tell Starch: 'Every Monday at 9am, post a standup prompt in #hr-team-standups asking: what did you finish last week, what are you focused on this week, are you blocked on anything?' Starch builds the scheduled automation.

3 Set a collection window. Tell Starch: 'At 4:30pm Monday, collect all responses from the thread and generate a summary grouped by theme — onboarding, recruiting, payroll, benefits, compliance — and flag any blockers.' Starch builds the aggregation step.

4 Wire the Task Manager app. Tell Starch: 'For any blocker or commitment mentioned in standup responses, automatically create a task with the owner's name and flag it as needing resolution before next Monday.' Blockers stop disappearing.

5 Connect Gmail via scheduled sync. Starch will surface overnight HR emails — benefits questions, manager requests, onboarding paperwork follow-ups — in the Email Triage app each morning so you start the day with context, not inbox chaos.

6 Build the CEO digest template. Tell Starch: 'Draft a weekly HR update I can send to the CEO. Include: active open reqs count, onboarding steps completed this week, any compliance items flagged, and the top three things HR is working on.' Starch generates a draft from the standup data each week.

7 If you're on Paylocity or ADP, connect those via Starch's scheduled sync. Now the digest can reference actual headcount numbers and pending time-off requests without you looking them up manually.

8 Use the Project Management app to track multi-week HR initiatives — open enrollment prep, a new onboarding playbook rollout, a performance review cycle — alongside the standup loop so weekly status feeds into the bigger project view.

9 Review the first three weeks of digests and tell Starch what's missing. 'Add a section for any employees whose onboarding tasks are overdue' or 'Flag if any manager hasn't responded to the standup prompt by noon.' The automation updates without rebuilding from scratch.

10 Set up a Friday version of the standup prompt for end-of-week reflection: 'What did you actually complete this week and what's rolling into next week?' Starch sends it, collects it, and adds it to the weekly archive so you have a running record of what HR shipped.

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

Q2 Open Enrollment Week — April 2026

Sample numbers from a real run

Standup responses collected (25 employees)	25
Blockers flagged automatically	4
Tasks auto-created from blockers	4
Minutes spent writing the CEO digest	0

It's the week of open enrollment kickoff. You've got 25 people in the benefits-eligible cohort, a deadline on Friday, and your inbox has 18 threads from managers asking variations of the same question. Monday at 9am, Starch posts the standup prompt to #hr-team-standups. By 4:30pm, 22 of 25 people have responded. Starch surfaces four blockers: two employees can't log into the benefits portal, one manager says their team hasn't received the enrollment guide, and one remote hire is flagged as missing a dependent verification step. Starch auto-creates four tasks in the Task Manager — each assigned, each marked urgent. By 5pm you have a digest that groups responses under 'open enrollment' (the dominant theme this week), 'onboarding' (two new hires starting Monday), and 'payroll' (one correction request). The CEO digest drafts itself: 25 employees in active enrollment window, 4 blockers being worked, 2 new hires starting, payroll correction in progress. You read it, adjust one line, and send it. You spent eleven minutes on standup this week instead of the usual ninety.

Measurement

How you'll know it's working

Standup response rate by Monday EOD (target: >85% of team responding same day)

Blockers resolved before the following Monday's standup (tracks whether the loop is actually clearing work, not just logging it)

CEO digest turnaround time (minutes from standup close to draft in inbox — target under 5)

Open HR action items with no owner or due date (should trend toward zero as task capture matures)

Time spent per week synthesizing standup updates manually (baseline vs. post-Starch)

Comparison

What this replaces

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

Slack + Geekbot

Geekbot collects standup responses well but doesn't summarize, flag blockers, create tasks, or feed a CEO digest — you still do all the synthesis manually.

Notion standup template

Good for structured input but requires everyone to go to Notion, and you still read every entry line by line with no aggregation or action-item extraction.

15Five or Lattice check-ins

Built for manager-direct report check-ins and performance context, not cross-functional HR team coordination — separate license, separate data silo, no CEO digest output.

Manual Slack thread + Google Doc summary

Zero cost but the actual synthesis work — reading, grouping, writing the digest — takes 60-90 minutes every week that compounds across 52 weeks.

On Starch RECOMMENDED

One platform — founder inbox, task manager, project 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

We use Slack but not every tool in our stack has a formal integration. Can Starch still pull in context from, say, our ATS or benefits portal?

Starch connects to 3,000+ apps through its integration catalog, plus any website through browser automation. If your ATS is Greenhouse, connect it from the integration catalog and the agent queries it live. If your benefits portal doesn't have an API, Starch can automate it through your browser — no API needed. Most HR stacks have at least one path in.

We're on Paylocity. Can Starch actually see our employee data?

Yes. Paylocity is one of Starch's scheduled-sync providers — Starch syncs your employee, payroll run, benefits, and time-off data on a schedule and stores it in Starch's database. That means your standup digest can reference headcount and PTO context without manual exports.

What if we're on Rippling or BambooHR instead of Paylocity or ADP?

Rippling and BambooHR are reachable through Starch's integration catalog — the agent queries them live when your app runs. The depth of data available depends on what their API exposes, but basic employee records and org data are typically there.

Is Starch SOC 2 certified? HR data is sensitive.

Starch is not SOC 2 Type II certified today. That's worth knowing before you wire in payroll or benefits data. If your company has a hard compliance requirement for SOC 2 Type II before connecting HR systems, that's a genuine constraint right now.

We don't want the whole company seeing their standup responses — can the digest be private?

Yes. The digest is built for you, not broadcast. You tell Starch who receives it — the default is a draft that lands in your inbox or a private Slack DM. You control distribution entirely.

What happens if someone doesn't respond to the standup prompt?

Tell Starch how to handle it: 'If someone hasn't responded by noon Monday, send them a DM reminder' or 'Flag non-responders in the digest so I can follow up.' The automation does what you describe — no custom code required.

We already have a task tracker (Asana or Jira). Do we have to use Starch's Task Manager?

No. If your team lives in Asana or Jira, connect either from Starch's integration catalog and tell Starch to create tasks there instead of in the built-in Task Manager. The standup automation can push action items wherever your team already works.