Skip to content

Draft reports, agendas and invites with an agent

All plansMember

Onplana has five compose tools. Four of them write a document from the live project: a status digest, a meeting agenda, release notes and an EVM narrative. The fifth puts a meeting in your Outlook calendar.

You do not run them by hand. You ask, and the agent picks the tool. That works from the Onplana AI assistant inside the app, and from an external agent connected over MCP such as Claude or ChatGPT. Name the project, or ask from inside it.

The four document tools work the same way:

  • The Onplana agent writes the draft with Onplana AI and saves it as a document in the project’s Agent Deliverables (Onplana Agent) folder.
  • A row lands in the agent review inbox, where a person reads the draft, edits it if needed, and approves or rejects it.
  • The agent you asked gets back the document’s id and a one-line message, for example “Status digest drafted and pending review in the Agent inbox.”

They do not email, post or send the draft anywhere. Sharing it is your call, after review.

The meeting invite tool works differently. It writes nothing into Onplana. It creates an event in your own Outlook calendar, described at the end of this page.

  • Every plan. The document tools run on every plan, including Free. Each run spends AI tokens from your workspace’s balance. When the balance is empty the tool refuses before it calls the AI, so a refused run costs nothing. See Understand your AI token budget.
  • You need to be able to open the project. The EVM narrative also needs access to the project’s cost data, covered in its section.
  • The Onplana agent must be a Contributor or above on the project. It is the one that saves the draft. If it has view access, or is not on the project, the tool stops before the AI call and says so. A project manager adds it from Manage Members, on the Agent tab, as a Contributor or above.

Tool: compose_status_digest

A short weekly status report for a sponsor or the team.

What it reads. The live health of the project:

  • Progress, status and timeline
  • Task counts: total, done, in progress, blocked and overdue
  • Up to 8 tasks completed in the last 7 days
  • Up to 5 overdue tasks, most overdue first, with who owns each
  • Overdue milestones and the next milestones, up to 5 of each
  • The top 5 open risks and the top 5 open issues, by severity
  • The project’s description and its 15 most recently updated tasks
  • Earned value (CPI and SPI), when the project has earned value data

The AI is told to write from these facts and nothing else. Where a list is empty, the report says so instead of inventing an item.

What comes back. A markdown document of about 150 to 300 words, in four sections:

# Status Report: Website relaunch
## Overall health
At risk. Two tasks are overdue and the content freeze milestone is due on 14 October.
## Key accomplishments
- Homepage design signed off
- Product pages migrated to the new templates
## Risks and blockers
- HIGH schedule risk: the CMS export from the vendor has not arrived
## Next steps
- Chase the vendor export
- Start the accessibility review

Who sees the cost line. CPI and SPI appear only when the person asking can read the project’s cost. Anyone else still gets the digest, without that line.

Try: “Write a status digest for the Website relaunch project.”

Tool: compose_meeting_brief

An agenda for a project meeting, ending in the decisions the group needs to make.

What it reads. The same live health facts as the status digest, without earned value: progress and task counts, up to 8 tasks completed in the last 7 days, up to 5 overdue tasks, the overdue and the next milestones with their due dates (up to 5 of each), and the top 5 open risks and the top 5 open issues by severity. Also the project’s description and its 15 most recently updated tasks, each with its status and epic.

The AI is told to write from these facts and nothing else, and to give milestone dates as listed. Where a list is empty, the agenda says so instead of inventing an item.

What comes back. A markdown document of about 150 to 300 words:

# Meeting Agenda: Website relaunch
## Meeting goals
Agree the launch scope and unblock the CMS migration.
## Status update
- Homepage design is done
- Product page migration is in progress
## Risks and blockers to discuss
- The CMS migration is blocked
## Upcoming milestones
- Content freeze, due 2026-10-14
## Decisions needed
- Launch with or without the blog
- Who owns the redirect map

Try: “Draft an agenda for this week’s Website relaunch meeting.”

Tool: compose_release_notes

A changelog of finished work, written for the people who use what you built.

What it reads. The tasks marked done in the last 30 days, newest first, up to 30, each with its epic and the day it was done. A task marked done with no completion date counts by its last update. The AI is told to group them by epic or theme, and when nothing was done in those 30 days, the notes say so. Known issues come from the open issues and overdue tasks, and next planned work from the next milestones.

What comes back. A markdown document of about 150 to 400 words:

# Release Notes: Customer portal
## Summary
This release adds invoice downloads and fixes password reset.
## Changes by area
### Billing
- Customers can download past invoices as PDF
- The invoice list shows the payment status
### Account
- Fixed the password reset link expiring too early
## Known issues
- None
## Next planned work
- Saved payment methods
- Order history search

Try: “Write release notes for the Customer portal project.”

Tool: compose_evm_narrative

A plain-language reading of the project’s earned value for a PMO audience.

What it reads. The project’s earned value snapshot and nothing else: budget at completion (BAC), planned value (PV), earned value (EV), actual cost (AC), CPI, SPI, estimate at completion (EAC) and variance at completion (VAC).

What comes back. A markdown document of about 200 to 400 words, in prose. It covers overall health, what CPI means in money, how far ahead or behind schedule the project is, the forecast from EAC and VAC, and ends with a recommended action.

# EVM Narrative: Data center move
The project is at risk. It is earning about 88 cents of value for every
dollar spent, so at this rate it finishes over its budget. ...

Two cases change what it says:

  • No cost data. With no rate cards and no imported cost data, the narrative covers the schedule only, from SPI. It also says how to unlock cost figures: configure rate cards, or import a schedule with cost columns. See Configure rate cards.
  • Some tasks have no estimated hours. Planned value and earned value are then approximate, and the narrative says so.

Who can run it. Only people who can read the project’s cost: an org Owner or Admin, or someone whose project role carries budget read access, which by default is the project Owner and Manager. Anyone else is refused.

In the app. The Generate EVM Narrative button on the project’s Finance tab starts the same run. See Read the EVM dashboard.

Try: “Explain the earned value on the Data center move project.”

Tool: compose_meeting_invite

Creates a draft meeting in your own Outlook calendar, through your Microsoft 365 connection. Nobody is invited: the meeting is created with no attendees, so Microsoft sends no invitation. You add the attendees and send it from Outlook.

What it needs. Your Microsoft 365 account connected to Onplana, with calendar access. See Connect Google and Microsoft accounts. Without it, the tool stops and asks you to connect.

What the agent fills in.

  • Subject and body (plain text by default, or HTML)
  • Start and end, in UTC
  • Proposed attendees: at least 1 and at most 10 email addresses. They are listed at the end of the meeting’s body, not invited.
  • A location, if you give one
  • A reminder, 15 minutes before by default, or none

What comes back. The event’s id, a link that opens it in Outlook, and the list of proposed attendees. The count of people invited is always 0.

Send it yourself.

  1. Open the link the agent gives you. The meeting opens in Outlook.
  2. Check the time and the body. Copy the proposed attendees from the end of the body into the attendee field, and remove the list if you like.
  3. Select Send. Outlook sends the invitations, not Onplana.

What it does not do.

  • It reads nothing from your projects and writes nothing into them, and it does not go to the review inbox.
  • It spends no AI tokens. The agent you are talking to writes the subject and body, and the tool places the event.
  • An Onplana agent working an assigned task cannot use it, because that agent has no Microsoft sign-in of its own.

It works on every plan.

Try: “Put a 30 minute Website relaunch review on my calendar next Tuesday at 15:00 UTC with ana@example.com and raj@example.com.”

You need Use Because
Where the project stands, for a sponsor or the team Status digest It reads completions, overdue work, milestones, risks and issues
A plan for a meeting, ending in decisions Meeting agenda It is built around goals, items to discuss and decisions needed
The same update every week, by email A scheduled status report It runs the digest on a cadence and emails it
The meeting itself, ready for you to send Meeting invite It creates the meeting in your Outlook calendar, with the attendees listed for you to add

Can I change a draft before I approve it? Yes. Open it in the review inbox, edit it inline, then approve. Your edited version is what is saved.

Does a refused run spend tokens? No. The document tools check the token balance and the Onplana agent’s access to the project before they call the AI.

Which plans include the compose tools? Every plan. Your AI token balance, not your tier, bounds the document tools. The meeting invite uses no tokens.