Skip to main content

Run an AI Morning Stand-Up

By the end of this recipe, every weekday morning Copera will DM each teammate for their plan and blockers, gather the replies, and compile them into one clean stand-up posted to your team channel — no meeting, no round-robin, no one waiting for their turn to talk. Because chat, boards, and AI live in one workspace, the same automation that asks the questions can also collect the answers and write the summary.

Readiness: Available now. Build it as two automations — a collector that asks, and a compiler that summarizes. A standing teammate that runs the whole morning stand-up on its own is rolling out in early access.

What it does​

A daily stand-up exists to answer two questions: what is everyone working on today, and is anyone stuck? The meeting is just the delivery mechanism — and it's an expensive one, costing a whole team fifteen minutes of context-switching to hear updates most of them don't need in real time.

This recipe collects the same information asynchronously and hands you the summary:

  • It asks each person directly. Every morning, a scheduled automation direct-messages each teammate: what's your plan today, and anything blocking you? People answer on their own time, in under a minute.
  • It collects the replies as structured data. Each answer becomes a row on a Stand-up board — who, what they're working on, and what's in their way — so the updates are captured, searchable, and never lost in a scroll-back.
  • It compiles one update. A little later, an AI step reads today's replies and writes a single stand-up: each person's plan, with all the blockers pulled to the top where a lead can act on them. It posts to your team channel, or DMs a manager for a private read.

Unlike an end-of-day read that narrates what the board already shows, a morning stand-up captures what the board doesn't yet know — people's forward-looking plans and the blockers only they can see. That's why it has to ask, not just read.

Build it yourself​

The pattern is two automations with a collection surface in the middle: a collector that DMs everyone and gathers replies into rows, and a compiler that turns today's rows into one posted update.

One-time setup​

Create the Stand-up board

Make a board with a Check-ins table. Add columns for Person (people), Date, Today's plan (rich text), Blockers (rich text), and a Status if you want to track who's replied. This board is both your collection point and a running archive of every day's stand-up.

Add a check-in form

Add a form to the Check-ins table with two questions — "What's your plan today?" and "Anything blocking you?" — plus a field for the person. Each submission creates one Check-in row. The form's link is what your morning DM will carry. (Prefer chat replies to a form? See the variant below.)

Keep a team roster

Point the collector at a list of who to include — a small Team table with a row per member (most teams already keep one). This is what the automation loops over to DM each person.

Automation 1 — the collector​

Trigger: Schedule

In Automations, add a Schedule trigger for each weekday morning — for example, 8:30 AM, Monday through Friday, at the start of the team's day.

Action: Find the roster

Add a Find rows action on your Team table to pull the people to include this morning. A row filter keeps it to active members if your roster holds more than the current team.

Control flow: For each member

Add a For each step over those rows so the next action runs once per teammate.

Action: Send the morning DM

Inside the loop, add a Send channel message action — it posts to a channel or a direct message — addressed to the person on the row as a DM: "Morning! Two quick questions — what's your plan today, and anything blocking you? 30 seconds → [form link]." Everyone gets the same nudge, personally, at the same time.

People reply by submitting the form; each submission lands as a Check-in row for today.

tip

Want people to just type back in the DM instead of opening a form? Swap the form for a second automation with a Chat message received trigger. Add a condition so it only runs on replies from your team, then an AI → Extract step to pull the plan and blockers out of the free-text reply, and a Create row action to store them on the Check-ins table. Now teammates answer in one line of chat and the automation structures it for you. The form is more reliable; chat replies feel more like a real stand-up — pick the trade-off you prefer.

Automation 2 — the compiler​

Trigger: Schedule

Add a second Schedule trigger for a bit later — say 9:30 AM — so late repliers still make it in.

Action: Find today's check-ins

Add a Find rows action on the Check-ins table with a row filter for rows from today. Optionally add a second Find rows on the Team table so the summary can spot who hasn't checked in.

AI step: Compile the stand-up

Add an AI → Summarize step over those rows. Prompt it plainly: "Write today's morning stand-up. Pull every blocker into one list at the top with the person's name, then list each person's plan for the day in one line. Note anyone on the team who hasn't checked in yet."

Action: Post it

Add a Send channel message action pointed at your team channel for a shared async stand-up — or address the same block as a direct message to a manager for a private read. You can do both.

That's the whole loop: the collector asks and gathers, the compiler reads and posts. Every block here — Schedule, Find rows, For each, Send channel message, Chat message received, AI Extract, AI Summarize — is a standard automation building block.

Or just ask Copera AI​

You don't have to assemble the graph by hand. Open Ask Copera AI and describe the whole thing:

"Create a Stand-up board with a Check-ins table (person, date, today's plan, blockers). Then build an automation that every weekday at 8:30 AM DMs everyone on our Team table asking for their plan and blockers with our check-in form link, and a second automation that at 9:30 AM compiles today's check-ins into one update — blockers first — and posts it to the #stand-up channel."

Ask Copera AI can create the board, its tables, and its columns, then draft both automations for you. (It builds boards, tables, columns, and rows — not forms — so add the one-question check-in form yourself in the board UI, a single click, or let the chat-reply variant above collect answers instead.) With the default Ask before acting permission mode, it shows a review card for each change before anything is created, so you approve the setup and the automations before they exist. See What Copera AI Can Do for the full list of what it can build.

Already collecting check-ins and just want today's write-up? Ask on demand, any morning:

"Read today's check-in rows on the Stand-up board and post a compiled morning stand-up to the Team channel — blockers grouped at the top with owners, one line per person's plan, and flag anyone who hasn't checked in."

It reads the rows, writes the stand-up, and posts it — with a Sources list so you can jump to any check-in it used.

Make it a standing teammate​

Early access

Standing AI teammates are rolling out gradually. When one is available in your workspace, a named teammate — a "Stand-up host" — can own the whole morning ritual: DM everyone for their plan and blockers, read the replies, nudge the people still missing, and post the compiled stand-up on its own schedule under its own identity. Until then, the two automations above do exactly this today — everything in this guide can be built now as an Automation.

Tips​

tip

Ask two questions, no more. Response rate lives and dies on effort. "Plan today?" and "Blocked on anything?" get answered from a phone in the elevator; a ten-field form gets ignored. Keep the DM to those two, and let the archive on the board do the record-keeping.

tip

Lead the summary with blockers, not a roster. The real job of a stand-up is surfacing what's stuck. Prompt the AI to put every blocker at the very top with the owner @mentioned, then keep each person's plan to a single line below. A wall of "on track" gets skimmed; a short blockers list gets acted on.

tip

Give the two schedules an hour of breathing room. Send the nudge at the team's start of day and compile an hour later, so people who reply late still land in the post. If you have a global team, run one collector per time zone into the same board and a single compiler over all of it.

tip

Set a spend cap and start with one team. The compiler runs an AI step every day, so give the automation a per-automation spend cap and watch the usage dashboard. Prove it out on one squad before rolling the pattern across the org.

Frequently Asked Questions​

What is an AI morning stand-up?​

It's an async stand-up run by Copera. Each morning an automation direct-messages every teammate for their plan and blockers, collects the replies as rows, and an AI step compiles them into one update posted to your team channel — the value of a stand-up without the meeting.

How does the automation collect each person's update?​

The morning DM carries a short check-in form, and each submission creates a row stamped with the person, date, plan, and blockers. A later automation finds today's rows and summarizes them. Prefer chat? A Chat message received trigger plus an AI Extract step turns each free-text reply into the same structured row.

Can people reply in chat instead of filling in a form?​

Yes. Swap the form for a Chat message received trigger that captures each reply to the morning DM, then add an AI Extract step to pull the plan and blockers out of the free text and create the row. The form is more reliable; the chat reply feels more like a real stand-up.

What happens if someone doesn't check in?​

Feed the compiler both today's check-ins and your team roster, and prompt the summarize step to name anyone who hasn't replied. You can also add a second scheduled nudge that re-DMs the people still missing before the stand-up posts.

Can the compiled stand-up go to a manager instead of a channel?​

Yes. Post it to a team channel for a shared async stand-up, or send it as a direct message to a manager for a private read. Same automation, different final action.

How is this different from an end-of-day check-in?​

The end-of-day check-in reads the board to narrate what already happened. A morning stand-up asks people for their forward-looking plans and blockers — information the board doesn't hold yet — which is why it collects replies instead of just summarizing rows.