Creating and managing projects
Projects sit at the bottom of BRIDGE ONE's strategy-to-execution hierarchy — Initiative, yearly Target, Project — and connect back up to an Initiative either directly, or through a linked Target.
Creating a project from scratch
To create a Project, do the following:
| Field | Description |
|---|---|
| Name* | How you will name your Project. |
| Owners* | The people responsible for driving the Project. Can be more than one. |
| Unit* | The Unit the Project belongs to. |
| Template | Optional. Start from an existing template instead of a blank Project. |
| Duration* | The Project's time frame, set one of two ways: manually, by picking a start and end date, or inherited, letting BRIDGE ONE derive it from the dates on the Project's Action Plan items. |
| Visibility | Public or Confidential. See Visibility. |
Creating a project from template
Pick a Template directly from the creation modal's Template field to start from existing structure instead of a blank Project.
[TODO] What a template actually pre-fills isn't covered yet.
Creating a template
Managing templates is an administrative feature that requires organization admin access (learn more about permissions). As an org admin, a Manage Templates button becomes available, letting you rename or delete existing templates.
To delete a Project, go to More Options and select Delete Project. You'll be asked to check a series of boxes confirming that you understand all of the Project's information will be erased, all relationships with other elements will be lost, and all data will be permanently destroyed.
Creating a Project Charter
Adding and editing Chapters
Charter works the same way here as it does for Initiatives — a document made up of chapters, each with its own description.
Creating and Managing Action Plans
Adding and managing Workstreams
Workstreams are the basic structure of an Action Plan — every Task and Milestone lives on one.
Tasks and Milestones
Beyond living on a workstream, the two item types work differently:
Adding and managing Tasks and Subtasks
To add a Task, tap the Add button on a workstream and choose Task. A Task only requires a Name — everything else is optional.
| Field | Description |
|---|---|
| Name* | The only mandatory field. |
| Date range | Start and end date. |
| Phase | The Phase this Task belongs to. |
| Status | Manual, or automatic — automatic status is driven by a completion percentage; if it's under 100% by the end date, the Task flips to Off Track. |
| Overarching item | A workstream, or another Task — used to nest this Task as a subtask. |
| Responsible person | Who owns the work. |
| Description | — |
| Discussion | Comments on the Task. |
| Dependencies | End-to-start, end-to-end, start-to-end, or start-to-start. |
| Attachments | — |
Discussion, Dependencies, and Attachments each live as their own subtopic inside a Task's details.
Creating subtasks and sub-milestones. Hover over a Task's row in the Action Plan table to reveal a + button, and use it to create a subtask or sub-milestone underneath. There's no limit on how deep the nesting can go — but only Tasks can hold sub-items; Milestones can't have children.
[TODO] Add a screenshot of the + button on a Task's row in the Action Plan table, showing how to create a subtask or sub-milestone.
Open the Task's details, go to More Options, and choose Convert to Milestone. Confirm the change. Fields common to both types are kept; anything that isn't shared between the two is dropped.
To delete a Task or Milestone, open its details, go to More Options, and choose Delete.
Adding and managing Milestones
To add a Milestone, tap the Add button on a workstream and choose Milestone.
| Field | Description |
|---|---|
| Due date* | — |
| Phase | Inherited from the Phase being managed, not set directly. |
| Status | Manual only — must be reported by hand. |
| Overarching item | Organizational only, for grouping. |
| Responsible person | — |
| Description | — |
| Discussion | Comments on the Milestone. |
| Attachments | E.g. attaching a report to back up a reported status. |
Open the Milestone's details, go to More Options, and choose Convert to Task. Confirm the change. Fields common to both types are kept; anything that isn't shared between the two is dropped.
Adding and managing Phases
Phases are managed directly on the Action Plan's timeline, not from a separate list.
The timeline's header always has two rows: the upper row shows months, and the lower row changes with your zoom level — individual dates in daily view, calendar week numbers (e.g. week 32, week 33) in weekly view, or the month name in monthly view.
Creating a Phase
Editing a Phase
Click the Phase's highlighted area on the timeline to reopen the same flyout, where you can change its name, duration, or color. A Delete button is available there too.
Deleting a Phase
Check the confirmation boxes acknowledging that some relationships will be undone, then press Delete.
Creating and Managing To-dos
The To-dos tab lists every To-do connected to this Project: its Own To-dos, added directly here, plus any Related To-dos that flowed in from a connected Meeting. See Decisions and To-dos in the Meetings guide for the full field reference (Title, Responsible person, Due date, Description, Visibility, Status) and how Own vs. Related works.
Communicating Decisions
The Decisions tab works the same way as To-dos: it lists every Decision connected to this Project, both Own and Related. See Decisions and To-dos in the Meetings guide for the full field reference (Title, Status, Type, Visibility) and how Own vs. Related works.
Linking and managing Meetings
The Meetings tab lists every meeting connected to this Project. See Meetings for how meetings work — calendars and connections, creating a meeting, agenda points, and more.
What connecting a meeting does
Connecting a meeting to a Project does more than list it here. Every Decision and To-do made in that meeting also appears on the Project, under its Decisions and To-dos tabs, so the outcomes of your meetings live next to the work they affect.
Linking an existing meeting
You can link a meeting that already exists to a Project. Because you're changing two things at once, there are limits on who can do it. You need to be:
- the owner of the meeting (an Organizer), and
- a manager of the Project and of the meeting at the same time — the same applies to any other context you want to connect a meeting to.
Creating a meeting from the Project
You can also create a meeting straight from the Meetings tab. Every meeting created there is automatically connected to the Project, and shows up on the tab as a connected meeting right away.
Communicating Project status
Posting a Status Report
The Status tab is a timeline of status reports as they're posted. As an Owner or Editor:
Managing available Statuses
Managing the available organization-wide Project Status options is an administrative feature that requires organization admin access (learn more about permissions).
Adding and managing Attachments
To add an attachment, go to the Attachments tab and tap the Add (+) button at the bottom-right of the page. You can then choose between three kinds of content:
History
History is a log of everything relevant that changes in a Project over time. It's a timeline of the changes, showing who made them and when. To open it, use the Project's More Options button and choose View history.
Adding and managing Members
Membership and visibility settings define who can see and manage a Project. Members can be set when creating the Project, and managed afterwards through the Project's permissions dialog.
To understand more about permissions and visibility, see Roles & Permissions in the Core Concepts section.
Adding Members
Managing Members
Members are managed from the same permissions dialog. Each person already in the Project appears as a card under their role — their avatar and name on the left, and a role select field on the right.
To remove someone, use the more options button next to their name.