The Overview page
The home of your project: who is involved, what is being delivered, the baselines you are measured against, and any details your team needs to succeed.
The Overview page showcases what a project is about and brings all of its key details together in one place. It welcomes every team member, helping them understand what they are working on, the priorities, the scope, and everything else that matters for a successful delivery.
It also captures the initial schedule and budget baselines, the agreed starting points used to calculate the variance that naturally occurs over the course of a delivery.
A page built from cards
The Overview is organized as a set of cards, each holding a related group of information such as the project details, the people involved, delivery dates, and the budget. The core cards are always there, but the page does not stop at the defaults. You can add your own fields to a card using the plus on that card, and you can create entirely new cards with Add container to hold whatever else your project needs to track.
This gives you a consistent, familiar starting point while still letting each project capture the information that is unique to it. The standard cards below cover what most projects need, and the section on custom fields explains how to extend them.
People: managers and sponsors
- Project Manager — The person responsible for delivering the project, with full control over it. When there are multiple PMs, you can set the primary one by right-clicking a name and choosing Make Primary. Roles such as Lead PM and Business PM can be distinguished on the card.
- Project Sponsors — The executive owners of the project. It is important for the whole team to understand who the sponsors are and how they are involved.
Delivery
- Priority — Set the project's priority to define its importance against all other initiatives.
- Duration & Planned dates — The card shows the overall duration and the planned start and end. These agreed dates serve as the schedule baseline, used to calculate variance against the project's ongoing schedule.
Budget baseline
At the start of a project there should be an approved budget authorized by the sponsors and executive team. This sits on the Budget card alongside figures such as the current fiscal year approved amount, and serves as the baseline against which forecast and actuals are compared to calculate variance.
A Budget code can be used to label funding sources, and the field can be hidden if you do not need it.
The Triple Constraint
Also known as the project triangle, this states what takes precedence among Budget, Schedule, and Scope. If something has to give, making the priority clear from the beginning keeps everyone aligned on the right trade-off.
Custom fields and custom cards
Every project tracks something a little different, so you can extend the Overview with your own information. Use the plus on a card to add a field, or Add container to build a whole new card, for example a custom card holding a tag, a number, a date, and any other values you want surfaced.
Adding a field opens a picker with two groups. Predefined Fields are ready-made fields you can drop straight in. Custom Fields let you create your own by choosing a type, so each field behaves correctly and displays the right way:
Choosing the right type matters: a Currency field formats as money, a Date field offers a date picker, a Progress field shows a bar, and so on. Pick the type that matches the data so the field looks and behaves correctly.
Details, documents, and narrative
Alongside the cards, the Overview holds the descriptive parts of the project that keep everyone aligned.
- Details — A fuller description of what the project is about.
- Documents — Anything relevant to understanding the project. These also appear in the Document Repository under the Linked folder.
- Scope — State clearly what is in scope and what is out of scope, so there is a crystal-clear, aligned understanding of what the project will deliver.
- Assumptions — Record the assumptions and constraints the project is working under, to keep everyone aligned and accountable.
- Communication — Describe the communication plan so it is clear how updates are shared and with whom.
- Closure — When closing the project, capture what worked and what did not. That history is a key learning guide for future success.