Skip to main content

Empwr.ai Projects (Early Alpha)

Create a living project status from your meetings

Updated this week

⚠️ Early Alpha Feature

Empwr.ai Projects is currently in early alpha. Functionality, UI, and behavior will change as we iterate based on user feedback.

This feature is only available for select customers. If you do not have access to this feature but would like to demo it and enable it, please schedule a demo with our team here: https://www.empwr.ai/demo
​

What Is Empwr.ai Projects?

Empwr.ai Projects is a key construct in Empwr.ai’s AI PM system of intelligence. It lets you manage work that spans multiple meetings, timeframes, and stakeholders—without manually creating status updates.

Empwr.ai already captures and distills insights from individual meetings. Projects builds on that by:

  • Grouping related meetings into a single project
    ​

  • Automatically generating a project-level status summary
    ​

  • Keeping stakeholders informed as new meetings occur

What used to take hours of manual status prep can now happen in seconds, and stays updated automatically.

When Should I Use Projects?

Projects works best when:

  • Work spans multiple meetings or recurring series
    ​

  • You need to report status to multiple stakeholders
    ​

  • Context is scattered across conversations
    ​

  • Status updates are repetitive and time-consuming
    ​

Core Concepts

What Is a Project?

A Project is a shared workspace that:

  • Aggregates multiple meetings (and soon other inputs)
    ​

  • Tracks progress across those meetings
    ​

  • Generates a continuously updated status report
    ​

  • Notifies members when new information is added
    ​

  • Builds a living knowledge graph for your project

  • Soon other capabilities will be added to projects including dashboards and proactive insights

Think of a Project as a living status brief powered by your meeting history

Viewing a Project

When you open a project, you’ll see three main sections.

Project Status Report

The Project Status Report is automatically generated from all meetings included in the project.

It:

  • Summarizes progress, decisions, risks, and next steps
    ​

  • Updates as new meetings are added
    ​

  • Includes linked citations back to source meetings

Linked Meetings

This section shows all meetings that belong to the project.

  • Meetings can come from different series or one-off sessions
    ​

  • All project members receive view-only access to these meetings
    ​
    ​

Project Members

Project Members are the people who:

  • Have access to the project
    ​

  • Receive notifications when the project updates
    ​

Adding Members to a Project

You can add members to a project at any time.

What happens when you add a member:

  • They receive a notification immediately
    ​

  • They gain view-only access to the project and linked meetings
    ​

  • They are notified when new project updates occur

Adding Meetings to a Project

Meetings are currently the primary input for Projects.

Add an Existing Meeting

From a meeting:

  1. Add an AI-suggested project OR

  2. Select Add to Project
    ​

  3. Choose the project you want to add it to OR

  4. Select Add to New Project
    ​

Recurring Meetings

If the meeting is part of a recurring series, you can choose:

  • This meeting only, or
    ​

  • All instances of the series

  • The project status updates automatically
    ​

  • All project members gain view access to the meeting
    ​

Creating a New Project

You can create a project at any time.

Steps:

  1. Select Create Project
    ​

  2. Enter:
    ​

    • Project name
      ​

    • Project goal (what success looks like)
      ​

  3. Save the project
    ​

  4. Begin adding meetings

Access & Permissions (Alpha)

In the current alpha:

  • Project members have view-only access
    ​

  • Editing and customization are limited
    ​

  • Notifications are automatic and not configurable
    ​

Permissions and controls will expand in future releases.

Known Limitations

Because Projects is in early alpha, you may notice:

  • A lack of a project-level dashboard

  • No sense of timeline and resources

  • Limited customization of project summaries
    ​

  • Minimal manual editing controls
    ​

  • Notifications are bare-boned
    ​

  • UI and workflows that evolve quickly
    ​

These are expected during early development.

Best Practices

For the best experience:

  • Use Projects for active, ongoing work
    ​

  • Add stakeholders early to reduce manual updates
    ​

  • Use citations to validate and share context
    ​

  • Keep project goals clear and concrete
    ​

Feedback & Support

Your feedback directly shapes Projects.

If something feels:

  • Confusing
    ​

  • Incomplete
    ​

  • Powerful but limited
    ​

We want to hear about it. Email us at [email protected]

Did this answer your question?