Skip to content
Onplana Docs

Schedule a status report

All plans Member

Somebody wants a status update every Friday. Writing it is twenty minutes of reading the project back to yourself, and the version that gets sent is whatever you could reconstruct on the day.

A scheduled status report does that reading for you. Onplana composes a narrative update from the live project on the cadence you set, files it in the project, and emails it to the people who wanted it.

Set one up

Section titled “Set one up”

  1. Open the project and choose Schedule status report from its … menu.

  2. Pick a Frequency: daily, weekly or monthly. Weekly asks which day, monthly asks which date, and both ask for the hour, in UTC.

  3. Add Recipients.

  4. Save. The schedule lists when it will next run, and when it last did.

You can keep more than one schedule on a project, which is how a weekly note to the team and a monthly one to a steering group live side by side.

What the report says

Section titled “What the report says”

It is written from the project as it stands at the moment it runs, not from a template:

  • Progress, and what actually completed in the period
  • Overdue work, and milestones
  • Open risks and issues
  • Earned value, when the project carries the cost data for it

Each run is also drafted into the project’s Agent Deliverables library with a row in the review inbox, so the sent version is on the record and you can read what went out. See Review agent output.

Who can add outside recipients

Section titled “Who can add outside recipients”

Anyone who can edit the project can create a schedule and send to people in your workspace. Sending to an address outside the organization is restricted to an org Owner or Admin, which is the same rule the Report Builder schedules use: mail leaving the workspace is a decision somebody with that authority makes once, not a field anyone can type into.

What it costs

Section titled “What it costs”

Each report is written by Onplana AI and spends your workspace’s AI tokens, the same as composing a status digest by hand. A daily schedule on a large project is a real, recurring cost rather than a free convenience. See Understand your AI token budget.

If the workspace runs out of tokens the run does not spin: it waits for the next period rather than retrying every few minutes.

When a run does not go out

Section titled “When a run does not go out”

The schedule row shows the failure against the run that hit it, so a schedule quietly failing for a month is visible on the schedule itself rather than only in somebody’s missing inbox. Fix the cause and the next period runs normally.

FAQs

Section titled “FAQs”

Can I edit the report before it goes out? Not on a schedule. It composes and sends in the same run, which is what makes it something you set up once. The draft is filed in the project afterwards, so you can always read what was sent. If you want a version you approve first, compose one by hand and send it yourself.

Does it send if nothing changed? Yes. A quiet week is a status too, and a report that silently skips is indistinguishable from one that broke.

Can I schedule one for a portfolio rather than a project? Not today. Schedules belong to a project. For a cross-project view, use a cross-project report and schedule that instead.

Which plans include it? Every plan. The AI that writes it is bounded by your token balance rather than your tier.

Who is it from? Your workspace, with a link back to the project. A recipient outside the organization sees the report and the link, not your workspace’s other projects.

Section titled “Related”