Async status tracker

The daily standup is fifteen minutes times the size of your team, every morning, mostly spent waiting for your turn to say the same thing you said yesterday. For a distributed team it is worse: someone is always half-asleep or dialing in from the wrong timezone. The meeting exists to answer one question, "what is everyone working on?", and a meeting is a bad way to answer it.

The status quo is a meeting or a Slack thread that scrolls away

The two common replacements are not much better. A Slack thread where everyone posts their update works until it scrolls off the screen, and nobody can see the whole team's status in one place after lunch. A shared doc gets stale between edits. Neither one sends itself out, so someone still has to nag, collect, and summarize. The status lives somewhere, but nobody gets it delivered.

The fuast version posts async and mails the digest

On fuast an async status tracker is one capsule: each person posts a short update on what they are working on, and a scheduled job rolls the day's updates into a digest and emails it to the team. No meeting, no nagging, no manual summary. People post when it suits them, and the digest goes out on a clock.

Steal this prompt

Paste this to your AI. It reads the fuast contract at /llms.txt and writes the whole thing, cron included.

Build a fuast capsule for async daily standup. A signed-in coworker posts a short status: what they did, what they're doing today, any blockers. Store the author from the verified identity. Show today's posts on the page. Add a schedule that runs at 5pm UTC every weekday, gathers the day's updates, and emails a digest to team@ourco.com. Deploy it and share it with the workspace.

What makes it real on fuast

The thing that turns a status page into a real standup replacement is the two batteries it leans on:

• A built-in schedule. fuast runs cron for you, so schedule("0 17 * * 1-5", ...) fires at 5pm UTC on weekdays and sends the digest. There is no separate cron service to stand up and no server you keep awake to run it.
• Transactional email delivers the digest to the whole team from inside the same app, so the summary arrives in an inbox instead of waiting to be read.
• Built-in auth stamps each update with the verified poster, so the digest can say who is doing what without anyone typing their own name.

The schedule half of the server:

import { capsule, table, string, text, schedule } from "fuast/server";

export default capsule({
  schema: {
    updates: table({
      author: string(),
      body: text(),
    }),
  },
  schedules: {
    digest: schedule("0 17 * * 1-5", async (ctx) => {   // 5pm UTC, weekdays
      const rows = await ctx.db.updates.order("desc").take(50);
      const text = rows.map((r) => `- ${r.author}: ${r.body}`).join("\n");
      await ctx.email.send({
        to: "team@ourco.com",
        subject: "Today's standup",
        text,
      });
    }),
  },
});

Add a post mutation and a simple client form, and the meeting is gone.

Delete the standup

An async tracker that collects updates and mails the digest on a schedule is a small app fuast runs end to end. See why the delivery surface matters in share software like a doc, then build it.