Skip to content

My standup ​

Write your daily update.

Who can use this page

Everyone who is signed in can open this page.

Write your standup ​

  1. Open Standup.
  2. Pick the date.
  3. Add your working hours. If you tracked your day, choose Use tracked time instead of typing them again.
  4. Write one update. A counter shows the 10,000 character limit.
  5. Save. The button stays off until you’ve written something.

Copy standup copies your update with the date and your working hours, ready to paste elsewhere.

Each time range folds away to keep the form short. Breaks between ranges appear on their own. Each time range has its own Office or Remote choice, so a day can be part office and part remote.

If your tracked time is wrong, fix it on the standup page and it updates your attendance too.

Standup reminders ​

If your organization uses Slack, reminders are sent on this schedule:

  • 10 AM: a morning note to the team channel.
  • 4 PM: an afternoon check-in to the team channel.
  • 7 PM and 10 PM: a private message to anyone who hasn’t submitted today’s standup.

People on leave, on a public holiday, or who have already submitted are skipped. Administrators can change the times or turn reminders off under Settings → Integrations → Slack.

People who report to nobody and are marked self-managed don’t have to write standups, and their attendance comes from the day they track.

Working on a weekend ​

Weekends are days off, so you can’t write a standup for one until you request it as an extra working day.

Your organization's configured working days determine which dates count as weekends.

  1. Open Standup and pick the weekend date. You’ll see a panel instead of the standup form.
  2. Say what you worked on and why it needed the day.
  3. Send the request. Your reporting manager approves or rejects it.

You can request a day up to 30 days after it happened. You can write the standup straight away, without waiting for approval, and that standup records your attendance. Approval is what makes the day count as extra work.

Default standup project and optional updates ​

A person may belong to several projects while sending their daily standup to one Default standup project. One active assigned project with a configured Slack channel is selected automatically. If several are eligible, a person manager must choose; if none are eligible, ask a person manager to check membership dates, project status and Slack configuration. Saving an update still works while routing is unresolved; it is not broadcast to all projects.

Person managers can review these settings in the person's detail view and in the project's team list. Manage standup settings opens the controls; Review changes names the person, current destination and new destination before Save standup settings applies the change. Cancel leaves the saved policy untouched. Project management alone does not grant permission to override another project's default. Employees cannot exempt themselves.

Standup required → Optional makes updates optional from today in the organization's timezone. Time tracking and attendance hour thresholds still apply. When ending the day, choose Submit update & end day or Skip update & end day. Blank skips create no standup; skipping a written draft requires discard confirmation. Failed requests preserve the draft. Voluntary updates remain visible and use the same validation and default-project routing as required updates.

Optional dates are Not required, rather than missing, in the team overview and are excluded from missing-standup alerts and reminders. Earlier dates retain their expectations. Requiring updates again starts from the change date. Changes record the editor, prior policy and effective date; a stale edit must be reloaded and reviewed again. Open tabs refresh policy on focus and periodically.

Changing a default does not replay earlier updates or redirect an already queued delivery. Each saved standup keeps its original destination (including unresolved routing); retries use that recorded destination. Existing memberships are preserved on upgrade, and unambiguous single-project defaults are initialized without sending Slack messages. A default that becomes unavailable falls back only to a sole eligible project; otherwise a manager must choose a replacement.

Peoplance by Innovaxel