1. Meeting Management
  2. Features
  3. Meetings
Feature · Meetings

Meetings

Meeting schedule for project meetings and delivery work.

OverviewMy Meetings
Meeting Management · Meetings

My Meetings

Meetings

New
Meeting titleProjectStart dateEnd dateStatus
Not started mtn-804PRJ-568320 Oct24 OctNot started
In progress mtn-296PRJ-579017 Oct26 OctIn progress
Blocked mtn-567PRJ-152004 Oct07 OctBlocked
Done mtn-657PRJ-493109 Oct11 OctDone
Not started mtn-678PRJ-886809 Oct16 OctNot started
6 of 6 records
Not started mtn-804Meetings · MTN-27913
Not started
ProjectPRJ-5683
Start date20 Oct
End date24 Oct
Example screen with sample data

What you can do

Meeting schedule

Plan a project meeting around a specific delivery question. The Project Manager picks the project and asks the Meeting Organizer to set a title and a start and end date. The organizer can then track whether the meeting is not started, in progress, Blocked or Done. Those states describe the meeting record; they do not settle every action raised during it.

How the work is organized

  • Set the context. Start from the project and use its named team members to make the owner of each record clear.
  • Keep the handoff visible. Move the work through the existing status values and record who took the next step.
  • Review exceptions. Open the relevant saved list when a date slips, an approval waits or a follow-up needs verification.

What to agree during setup

Agree who organizes each meeting, how a blocked meeting is rescheduled, and which project is authoritative when the same people serve several clients. Set a convention for short titles and a description that lets a colleague understand the purpose before joining. Calendar invitations or conferencing can be connected if the team uses them.

Map the project’s real operating language to the record names before importing history. Have the Project Manager and Delivery Lead rehearse the same case with ordinary team accounts. If a role sees too much or cannot complete its assigned step, correct access before the first live cycle. Preserve the project reference and the person responsible when records are moved or corrected.

Check the handoff on an actual case

Take an active project with a review meeting next Tuesday. Give the meeting its project, organizer, start and end dates. Open the upcoming list and confirm that the meeting appears. Mark it in progress when discussion begins. If the meeting is blocked by an absent decision maker, mark the meeting Blocked and write the reason in its description. When it finishes, mark it Done and inspect the linked action work separately. The project rollups let the manager see meeting and action counts without treating either count as evidence of completion.

Open the source record again after the handoff. Compare its status, owner, project and dates with the list used by the receiving person. The team should be able to explain the next action from the record itself, including a blocked or failed attempt. Rehearse the correction path with the same roles who will use it in ordinary work.

What your team sees

  • Upcoming Meetings — Meetings that are planned or under way, with the project, organizer and start and end dates.
  • My Meetings — The organizer’s own meeting calendar and current status.

Follow the work through

What it keeps track of

Data model
Projects
Engagements delivered for an organization, with budget and schedule.
Meetings
A meeting held for a project: when it starts and ends, the organizer, its status, and the action items and agenda items it produced.
Team members
Delivery staff with role, practice and weekly capacity.

Who uses it

Permissions
Project Manager
Owns the project handoff; Meeting Organizer prepares the discussion; Team Member updates assigned work; Attendance Approver reviews approval outcomes; Delivery Lead reviews exceptions.

Set up Meeting Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started