Team Lead manual
- 01Three roles, one board
- 02Your invitation
- 03The workspace
- 04The people of your team
- 05Import the people of your team
- 06Project details
- 07Projects already running
- 08Allocation
- 09Invoices
- 10Effort import
- 11Audit messages
- 12Re-import and rhythm
- 13Someone leaves
- 14A project changes team
- 15An estimate changes
- 16A week imported twice
- 17The go-live moves
- 18A project is put on hold
- 19Someone moves to another team
- 20Quick reference
Nothing in this manual matches.
Three roles, one board
Everyone signs in with their Microsoft work account (Microsoft Entra ID), inside Microsoft Teams. The role decides which screen you work in and what you can change.
Your invitation
Your organisation's Manager gives you access to keep one delivery team's data current. It runs inside Microsoft Teams, with your work account.
You keep your own Microsoft 365 account: no guest account, no Microsoft guest e-mail. At the top of the page, Organisation lists your own and those that invited you. A waiting invitation reads “<organisation> invited you.” Open it, then Confirm.
The Team Lead Workspace
Where a Team Lead keeps one delivery team current. You see your own team only: its people and its projects.
Nothing is kept until Save. While changes wait: “Not saved yet.” After: “Saved. Last saved <date> by <who>.” If someone saved meanwhile: “Not saved. Saved meanwhile. Saved <date> by <who>. Reopen the page to see that version.”
No team yet: the Workspace says so. Ask your Manager to give you one on the Account page.
The people of your team
Open People · <your team> in the Team Lead Workspace: your team only · moves between teams are made by the Manager.
Import the people of your team
Project details
Open the Projects tab and unfold a project. The code, name, order and PM are set by the Manager; the location is part of the code.
You plan which month is in which phase, and report the phase the project is in. The board compares the two for the reporting month: the check Reported phase on plan.
Months left on — are counted, for example “2 of 7 months without a phase”.
Projects already running
Your projects were running before your team used Portfolio Control Center. You do not type their history: you set the day your monitoring starts and, for each project, its opening balance. From the first day, the board owes nothing for the time before.
Allocation, in percent
How much of each person goes to each project, month by month, in percent. 100% is one person full time for the whole month; 25% is a quarter of it.
Person A: BAU 30% plus 60% on projects = 90% of 1.00 FTE: nearly full. Person B: 0.25 + 0.40 = 0.65 on 0.50 FTE = 130%: the month does not fit. Take 15% off somewhere.
The summary line shows the team's load for the month. A closed month shows “Oct closed” and its cells cannot be changed.
Invoices
Book every supplier invoice to its project. The board sets the total against the approved budget and against completion.
Effort import, in three steps
Effort is never typed. It comes from your timesheet or ticketing system as a file, one line per piece of work. A line with an error never reaches the board.
Select Copy the template and paste it into Excel. Six columns; the header row must match exactly; the order of the lines does not matter. The date format, the decimal separator and the column separator are the Manager's; the example line uses your team's first person and project.
Each line is checked against the people and the projects of your team. An error is never imported; a warning is, and the board shows it as it is. The next page lists every message.
Every audit message
Every message the audit can give, what it means and what to do.
Re-import and your rhythm
Imported the wrong data? Correct it at the source and import those days again.
Someone leaves in the middle of a project
The last day closes the person’s capacity. What they were still planned for after it is nobody’s work until the Team Lead gives it to someone else. Until then, the board shows the gap.
A project taken over from another team
The Manager moves the project; its history stays where it was booked and keeps counting. The team that runs it now starts from what the other team kept, and the team that ran it decides what it still plans on it.
The estimate changes along the way
A change request raises the effort estimate or the approved budget of a running project. The board does not rewrite the past: what was expected before the change stays, and what the new figure leaves is spread over the time left.
An effort file with weeks twice
A week exported twice, two exports pasted into one file, or a file that overlaps the last one. The audit keeps every hour once.
The go-live moves
The project needs more time, or less. The new date takes over from the month you save it; the moves stay on the board, so a slip is never hidden by the new date.
A project is put on hold
The project stops for a while and will resume. The board stops expecting effort and money from the month you save it, and spreads what is left when it resumes.
Someone moves to another team
The person stays in the company and keeps one row. Each team keeps the days the person was in it, and a day both teams report counts once.