Using Fortis Planner
Fortis Planner is all about Teams and the plans they have. Any Team within an organisation can choose to use it, and Fortis Planner caters for any number of teams.
Fortis Planner supports both the planning and the execution of those plans. Plans meet the real world, where unexpected things happen and priorities change. When they do, a Team can quickly understand the impact, change its plans accordingly, and carry on with execution and delivery.
What you can change in a plan depends on your role. What you can see does not: everyone who signs in can look at every Team's work. This page outlines how a Team Lead, a Team member and an Admin each use it. It is not a guide to the screens.
What Fortis Planner models
A Team is a group of people who work together, and it owns the plans its members make and carry out.
A Workstream is a collection of related work. A Workstream contains Tasks and sub-Workstreams, (which may contain further sub-Workstreams, and so on).
A Component is a part of a product or part of the organisation that work affects. Components can contain sub-components, (which may contain further sub-components, and so on).
A Task is a single, concrete piece of work within a Workstream, with its own priority, size and dates and assignees.
A Resource is whoever does the work on a Task and has their time estimated against it. A Resource may be a person on the Team, or a third party such as a supplier or an external organisation.
A Dependency says that one Task or Workstream cannot start until another has finished, so that when the first moves, everything waiting on it moves too.
Urgency is a measure calculated for every open Task from its priority, its Workstreams' priorities and how close its dates are to today, so that the most pressing work stands out.
Interactive graphical Gantt charts show Workstreams and their Tasks as bars on a timeline, with the Dependencies between them, and let the plan be changed there by dragging Tasks and Workstreams.
Interactive graphical Resource utilisation charts show how much planned work the Team, or each Resource in turn, has on each working day, so it is plain when the Team is overloaded or when there is slack.
What everyone can see
Whatever your role, you can look at the plan as widely or as narrowly as you like: your own work, the work of the Teams you are on, one Team of your choosing, or the whole organisation. Another Team's work is there to read, not to change.
The same plan answers different questions, depending on how you look at it:
- What is there, and in what state? A grid of every Task, sorted and filtered as you choose.
- When will it be done, and what is it waiting on? A Gantt chart of Workstreams and their Tasks on a timeline, with the links between them.
- Who is carrying how much? A workload view under the Gantt chart, day by day, in total, or person by person.
- What comes first? Every open Task carries an Urgency, so the most pressing work stands out.
- Where is it? A search across Tasks, Workstreams, remarks and attachments.
Anyone can also take a private copy of the plan, or of one Team's or one Workstream's part of it, and try a change there without touching the real thing.
A Team Lead
A Team Lead builds the Team's plan and keeps it true.
- Can do: set up the Team's Workstreams and their Tasks; say who works on each Task and who owns it; change any part of the Team's plan, whoever owns it; decide who is on the Team and what each person may do; plan with a name before that person has joined, or with an outside supplier's.
- Can see: a dashboard of the open work each person on the Team has, by number of Tasks, effort and Urgency; the whole of the Team's timeline, with what depends on what; and the work each person is carrying day by day.
- Can ask: Who has too much, and who has room? Which work is most pressing, and which is running close to its dates? What moves if this Task takes longer, or goes to someone else?
A Team member
A Team member looks after their own part of the plan.
- Can do: keep the Tasks and Workstreams they own up to date; add Tasks to a Workstream they own, and break it into sub-Workstreams; attach links and, where the organisation allows it, files; add remarks to any of the Team's work.
- Can see: their own Tasks in order of Urgency; when each is expected to start and finish; and the rest of the Team's plan around their own work.
- Can ask: What should I do next? What am I waiting on, and who is waiting on me? What happens to my dates if the work before mine runs late?
Someone can also be on a Team with read-only access: they see everything and can add remarks, and change nothing else.
An Admin
An Admin looks after the organisation's people and settings, not its plans.
- Can do: add people and invite them by email; set how much of the week each person works; create a Team for someone to lead, and put right who is on any Team; name the organisation and choose whether it says Project or Workstream; decide whether files may be attached; connect the organisation's Jira, where it uses Jira.
- Can see: every person known to the planner, whether or not they sign in, and the Teams each is on; and a check of the data that lists what needs putting right.
- Can ask: Who has an account, and who is still only a name in the plan? Which Teams have nobody leading them? Who is on no Team at all?
Being an Admin is separate from a role on a Team. In the plan itself an Admin sees what everyone sees, and changes what their role on each Team allows.
More than one role
Roles are held Team by Team, so one person can lead one Team and be a member of another. Anyone who is not read-only can start a Team of their own and lead it.
Last updated November 2026