Portfolio Control Center
by BI DEVELOPMENT

Team Lead manual

All manuals ·
  1. 01Three roles, one board
  2. 02Your invitation
  3. 03The workspace
  4. 04The people of your team
  5. 05Import the people of your team
  6. 06Project details
  7. 07Projects already running
  8. 08Allocation
  9. 09Invoices
  10. 10Effort import
  11. 11Audit messages
  12. 12Re-import and rhythm
  13. 13Someone leaves
  14. 14A project changes team
  15. 15An estimate changes
  16. 16A week imported twice
  17. 17The go-live moves
  18. 18A project is put on hold
  19. 19Someone moves to another team
  20. 20Quick reference
Portfolio Control Center
by BI DEVELOPMENT
Project portfolio management

Portfolio Control Center

Team Lead manual
For the Team Lead
Keeps one delivery team's data current: people, project details, allocation, invoices and effort, and closes its month.
Team Lead manual · Version 2.0 · for Portfolio Control Center V1
October 2026
Portfolio Control Center
by BI Development
Portfolio Control Center · Team Lead manual
Overview

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.

Role
Works in
Owns
Manager
Typically the head of the project portfolio
Management board
The teams and the moves between them, each project's identity (code, name, execution order, PM), every parameter, access, reports and the closing of each month.
Team Lead
One per delivery team, usually its manager
Team Lead Workspace
Their own team's data: people, allocation, project details, supplier invoices, the effort import and the closing of its month.
Guest
Steering committee, executives, invited readers
The board, read only
Nothing in the data. Reads the published reports and month photos; chooses the reporting date and the months in view, for their own session.
The Manager gives access on the Account page, by work address, also to someone of another organisation, who keeps their own account.
How the three screens connect
Manager
Management board
sets teams, projects and rules
Team Lead
Team Lead Workspace
enters the team's data
Computes
Portfolio Control Center
every figure, score and flag
Guest
Reads the board
reports and month photos
Three rules that hold everywhere
1
One place for each fact
A person is one row, a parameter one value. Projects point to people by ID, so a rename reaches everywhere.
2
Nobody types a result
Completion follows the phase. Load, delays and the score are computed each time the board opens.
3
Gaps stay visible
Missing data is shown and lowers the reliability score. It is never hidden or left out of the count.
Portfolio Control Center by BI Development
02 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
Team Lead

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.

From the link to the workspace
1
Open the invitation e-mail
It comes from support@bidevelopment.ro and names who invited you. Select Open in Teams. Nothing arrived? Your Manager sends it again or sends you the link.
2
Open it in Teams
Or, in Teams, Apps › search Portfolio Control Center. Desktop, web or mobile, it works the same.
3
Sign in with your work account
The first time, Teams asks you to confirm it. There is no separate password.
4
Confirm
The page reads “<who> gives you access to <organisation> as Team Lead of <team>.” Select Confirm, or Decline. From then on the access is bound to this account.
5
Work in the Team Lead Workspace
It opens there every time. Your own team only: another team's data never reaches your screen.
If you are from another organisation

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.

If it does not open
You see
Most likely
Ask
Your Manager has not given you access yet.
No access on this account, or the invitation went to another address
The Manager
Need admin approval
Sign-in to the app is not approved in your organisation
Your Microsoft 365 administrator
Anything else
—
support@bidevelopment.ro
Your first week. Fill in your projects' details and planned phases, allocate them through to go-live, import last week's effort, then Save. The next pages take you through each.
Portfolio Control Center by BI Development
03 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
Team Lead

The Team Lead Workspace

Where a Team Lead keeps one delivery team current. You see your own team only: its people and its projects.

Manager
Creates the project
code, name, order, PM
You
Fill in
details, allocation, invoices
You
Import effort
every week
You
Close the month
first days of the next
Board
Computes
every figure and the score
Five tabs
Tab
You do
How often
People
Your team's people: role, FTE, BAU, last day
When someone joins, leaves or changes
Allocation
Each person's month per project, in percent
Whole project; adjusted before each month
Projects
Phase, status, dates, estimate, budget, planned phase by month
When something changes
Invoices
Every supplier invoice booked to a project
When the invoice arrives
Effort import
Hours reported, from a file, checked before import
Every week
Save

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.”

Closing the month
Close October 2026October 2026 is open. Close it once its effort is imported: its allocation, effort and invoices then no longer change. Months close in order; if nobody closes it, it closes by itself on 2026-11-30, with what is there.
1
Save first
With changes waiting: “Save first: the month closes on what is saved.”
2
Close it, two clicks
Close October 2026, then Confirm: close October 2026.
3
The Manager confirms
The page says “October 2026 closed for your team. The Manager confirms the month once every team has closed it.”
Set by the Manager: each project's code, name, order and PM, shown with a lock, and moves between teams. Ask the Manager if any is wrong.

No team yet: the Workspace says so. Ask your Manager to give you one on the Account page.

Portfolio Control Center by BI Development
04 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
Team Lead

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.

Each field
Field
What it means
Rule
Name
First and last name
Corrected by you on this tab.
Role · Type
Job title; Internal or External
For your own reading; not used in any figure.
Can be PM
Appears in the project manager list
Needed before the Manager assigns them a project.
Carries capacity
Counted in the plan
Untick for people who only read or approve.
FTE
Share of a full-time contract, between 0 and 2
1.00 full time, 0.50 half time.
BAU
Part of the FTE that runs the business
Must stay below the FTE.
Last day
Last working day, if leaving
What is planned for them after it is not counted.
Common tasks
Task
Do this
Someone joins
+ Add person, fill the row, tick what applies, Save.
Several people join
Import a file (below).
Someone leaves
Set Last day, Save. The row hides; Show people who left shows it. Then give what is still planned to someone else: see Someone leaves in the middle of a project.
Someone comes back
Add a new row: each row is one contract, the earlier one keeps its history.
FTE or BAU changes
Change FTE or BAU, Save. Every load figure recalculates.
Remove a row
Only without history (no allocation, effort or project); otherwise × is locked.
Someone changes team
The Manager moves them.
Portfolio Control Center by BI Development
05 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
Team Lead

Import the people of your team

Import a file, in three steps
Step
Do this
1 · Copy the template
Seven columns: Name; Role; Type; Can be PM; Carries capacity; FTE; BAU. Yes or No for the ticks; the separators are the Manager’s (Parameters › Effort import).
2 · Import a file
One wrong line and nothing is imported: correct the lines and import the file again. A name already in your team is left out.
3 · Save
“3 people added. Save keeps them.”
Every import message
Message
What to do
The columns must be: Name; Role; Type; Can be PM; Carries capacity; FTE; BAU
Copy the template header.
Line 4: the name is missing
Fill in Name.
Line 4: Type must be Internal or External
Write one of the two.
Line 4: Can be PM must be Yes or No
Write one of the two.
Line 4: Carries capacity must be Yes or No
Write one of the two.
Line 4: FTE must be between 0 and 2
1.00 full time, 0.50 half time.
Line 4: BAU must be between 0 and 2
Below the FTE: FTE 1.00, BAU 0.30.
Line 4: Ana Pop is already in your team; not imported
Nothing to do: the person is already there.
Nothing imported: correct the lines above and import the file again.
Correct the file, then import it again.
Portfolio Control Center by BI Development
06 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
Team Lead

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.

Field
What to enter
Change it when
Phase
Where the project stands, on the Manager's scale
it moves on; Completion follows, never typed
Status
Ongoing, Not Started, Canceled, On Hold, Completed
the project stops, restarts or ends
Sponsor
Who pays for and backs the project
the sponsor changes
Business owner
Who accepts the result
the owner changes
Strategic driver
Why the project exists; earlier values are offered
rarely
Mandatory
Ticked if compliance requires it
rarely
Start · Target go-live
First working day · planned go-live
the plan is re-baselined
Effort estimate
Total effort, in FTE-months
the estimate is revised
Approved budget
In euro, as approved
a budget change is approved
Planned phase, by month
One phase code per month, from start to go-live
the plan changes
Planned phase against reported phase
PRJ-01
Jan
Feb
Mar
Apr
May
Jun
Jul
Planned
ANL
ANL
IMP
IMP
IMP
UAT
PV

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.

Reporting month April, plan IMP (Development)
Check
Phase reported Analysis
behind plan: fails
Phase reported Development or UAT
on or ahead of plan: passes

Months left on — are counted, for example “2 of 7 months without a phase”.

An empty field counts. A project without an estimate or a plan fails its check in the reliability score until you fill it in. An estimate of 3 people for 2 months is 6 FTE-months.
Portfolio Control Center by BI Development
07 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
Team Lead

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.

Five steps, once
1
Set the monitoring start
In the Projects tab, Monitoring start: the first day your team reports in Portfolio Control Center, usually today.
2
Give each project its opening balance
Two fields appear in every project: Consumed before the start, the effort used up to that day in FTE-months, and Invoiced before the start, the sum of its invoices up to that day in euro. Take both from your timesheet and finance totals. A project left with neither is marked “no opening balance” on the board: its history counts as zero.
3
Fill the plan from the project’s start
Start, go-live, estimate, budget, the planned phase by month and the allocation of the months already past, as they were planned. The board compares the plan up to today with the opening balance plus what you report.
4
Report from the start on
Import effort and enter invoices dated from the start. The first week owed is the first full week after it.
5
Save
Save keeps every tab.
What the board does with it
On the board
From the first day
Reliability score
No week before the start is owed: “No week due yet” until the first full week has passed.
Budget consumed
The opening amount counts. Per month, it is spread over the months before the start along the monthly baseline; the tooltip says “Opening balance, spread”. The cost export lists it as one “Opening balance” line.
Consumed against planned
The opening effort counts with the effort reported since the start.
Weekly · by month
Nothing is drawn before the start, and those weeks are not counted as missing. The week and the month of the start hold only the days from it.
Absence
Known only from the start: capacity before it counts without absence.
Nothing counts twice. Effort and invoices dated before the start are not counted: the opening balance stands for them. The Workspace says how many there are. Move the start only to correct a mistake, and check the opening balances again when you do.
Portfolio Control Center by BI Development
08 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
Team Lead

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.

Allocate a project
1
Choose the month
Month buttons at the top: three months back to a year ahead, widened to every project's start and go-live.
2
Type the percentages
Projects down the page, people across the top. In steps of 5: 25 means 25%.
3
Read the column header
(BAU + allocation) ÷ FTE, while you type: amber at or above the nearly full line, 80% by default; red above 100%.
4
Show a new project
Untick Only projects with an allocation to see projects with nothing allocated yet.
5
Plan the whole project, then Save
Every month from start to target go-live; before each month, adjust it. Save keeps it.
A worked example
Project
Person A · 1.00 FTE · BAU 0.30
Person B · 0.50 FTE · BAU 0.25
Total
PRJ-01 · Project one
25%
25%
50%
PRJ-02 · Project two
25%
15%
40%
PRJ-03 · Project three
10%
—
10%
Committed on projects
60%
40%
100%
Column header
90% · nearly full
130% · overbooked

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.

Why the whole project. Only a full plan shows the capacity left for the other projects that share the same people. A month with nothing entered is a gap: it shows on the board and lowers the reliability score.
Portfolio Control Center by BI Development
09 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
Team Lead

Invoices

Book every supplier invoice to its project. The board sets the total against the approved budget and against completion.

Book an invoice
1
Open the Invoices tab
Every project of your team is listed with its total and its budget.
2
Unfold the project
Its invoices are listed one per row.
3
Select + Add invoice
A new row appears, dated today.
4
Fill in the row
Invoice, Date, Supplier, Description, Amount in euro.
5
Correct, remove, Save
Edit any cell; remove a row with ×. Save keeps it.
What the project line tells you
You see
Means
% of the budget, green
spend is within the approved budget
% of the budget, amber
spend has reached the Manager's budget nearly spent line, 85% by default
% of the budget, red
spend is above the approved budget
no budget set
the spend is shown, but cannot be judged; enter the budget in Projects
closed, on a row
the invoice is dated in a closed month: it cannot be changed or removed
Budget against completion. A project that has spent 70% of its budget at 30% completion is flagged on the board, even within budget. Keep both the invoices and the phase current. The board also reads each month’s invoices against the project’s monthly baseline: its approved budget spread from start to go-live. Moving Target go-live or putting the project On Hold spreads what is left again, so keep both current.
Portfolio Control Center by BI Development
10 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
Team Lead

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.

Step 1 · The template

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.

Resource
Date
Reference
Description
Hours
Project
Person A
2026-10-26
TICKET-1
What was done
3.5
PRJ-01
must match a person in your team
in the set format
ticket or task id
free text
decimal hours
project code, BAU, or ABSENCE
Step 2 · The file
1
Export from your tool
At task level: one line per piece of work keeps the hours on the right project. Leave, sick days and holidays: ABSENCE (or the code the Manager set); the week counts as reported and the month’s capacity drops.
2
Save as CSV
With the column separator the Manager set, as in the template.
3
Load it
Choose a file or drop it on the box. It is read in your browser; only the hours per person, day and project are kept.
Step 3 · The audit

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.

1
Read the summary
Errors, warnings, clean lines, the hours that would be imported, and how many days imported before they replace.
2
Fix errors at the source
Correct the export, save it again, load it again. Start over clears the file.
3
Select Import N lines, then Save
The valid lines are taken: “N lines taken · h h. Save keeps them.” Then Save. The tab shows “Last import <date> by <who>: n lines, h h, from <date> to <date>.”
Portfolio Control Center by BI Development
11 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
Team Lead

Every audit message

Every message the audit can give, what it means and what to do.

Errors · the line is not imported
Message
What to do
no resource name
Fill in the Resource column.
two people in your team have this name; tell them apart on the People tab
Correct one of the two names on the People tab (a middle initial is enough), use the same name in the effort file, then import again.
not a person of your team
Check the spelling, or add the person on the People tab.
date not in the set format (YYYY-MM-DD)
Write it as the template shows.
in the future
Effort is imported once it is done.
<Month> is closed
Its effort no longer changes.
after their last day (<date>)
Check the date, or the last day.
hours must be a positive number
Above zero, set decimal separator: 3.5.
no project code; use BAU if it is not project work
Fill in Project, or write BAU.
not a project of your team
Check the code; the Manager creates projects.
header does not match the template
Copy the template header. Every line is an error.
columns are not separated by <commas>, as the Manager set
Use the set separator. Every line is an error.
Warnings · the line is imported
Message
What to do
more than 12 h in one line
One line per task. 12 h by default, set by the Manager.
same person, day and reference as line N
Possibly the same work twice: remove it at the source.
<First name> books N h on <date>
Over 16 h on one day (default, set by the Manager).
Warnings are not hidden. A warning line is imported and shown as it is. If it was a mistake, correct the export and import those days again.
Portfolio Control Center by BI Development
12 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
Team Lead

Re-import and your rhythm

Imported the wrong data? Correct it at the source and import those days again.

Source
Correct the data
in the timesheet or ticketing system
Export
The days to correct
for the people concerned
Import
Replaces those days
per person; every other day stays
Board
From the next report
reports and photos stay as they were
Rules of the re-import
Rule
Means
Replaces, per person and day
For each person in the file, the days the file holds replace what was imported for them before; every other day stays. The audit says “replaces n days imported before”.
No restore
An earlier import cannot be restored; only its log line is kept. To undo, import the right days again.
Closed months
A day in a closed month is refused: “<Month> is closed”.
Reports do not change
A report or month photo shows what was known then. The correction appears from the next report.
Your rhythm
When
What
Why
Every week
Import the effort of the last complete week; Save
It carries 40% of the reliability score by default.
When a project starts
Allocate it through to go-live; plan its phase by month
It shows the capacity left for other projects.
Before each month
Adjust the coming month
An empty month is a gap on the board.
As it happens
Change the phase; book each invoice
Completion and spend stay true.
First days of the next month
Close the month, once its effort is imported
The deadline is the end of the following month: then it closes by itself, with what is there.
Ask the Manager for anything locked: a project code, the execution order, a person who must move to your team.
Portfolio Control Center by BI Development
13 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
When things change

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.

Five steps
1
Set the last day · Team Lead
In the Team Lead Workspace, People, type the person’s Last day and Save. The row hides; Show people who left shows it again.
2
Close their access · Manager
If the person had a Team Lead or Guest seat, set Access ends on Account › Access to the same day: the Last day on People does not close the access. When a Team Lead leaves, you keep the team until the new Team Lead confirms.
3
Find what is still planned · Team Lead
In the Team Lead Workspace, Allocation: a red box, Planned after a last day, names the person, the FTE-months and every project and month left.
4
Give it to someone else · Team Lead
Select a month in the box. In that month the person’s column says Not counted. Type the share in the column of whoever takes over. If nobody can, add a person on the People tab.
5
Clear, then save · Team Lead
Clear next to the struck-through figure takes it out; the month leaves the box. When the box is gone, Save.
What the board does with it
On the board
After the last day
Capacity
The person counts through the month of their last day, then no longer.
Effort allocated
What is planned for them after that month does not count. The project’s share of its estimate drops until someone else takes the work.
Heatmap · Weekly
Their row stops at the last day; no week after it is owed.
Effort import
A day after the last day is refused, with the date.
History
The months up to the last day keep their allocation, effort and invoices. The person cannot be removed.
A wrong last day is corrected, not worked around. The Team Lead moves it; what was planned and not cleared counts again. Someone who comes back gets a new row on People: each row is one contract.
Portfolio Control Center by BI Development
14 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
When things change

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.

Five steps
1
Move the project · Manager
On the Management board, Projects, change its Team and Save. The code, the order and the history stay.
2
Give the new team access · Manager
If the team has no Team Lead yet, invite one on Account › Access.
3
Check the details that came with it · New Team Lead
In the Workspace, Projects: the project is marked from the other team, with its start, go-live, estimate, budget and planned phases filled in. Check them and Save: from then on they are your team’s.
4
Plan and book from now on · New Team Lead
Allocation: allocate your people from this month on. Invoices: what the other team booked is listed read only and counted in the total; book new invoices here.
5
Keep or clear what is still planned · Former Team Lead
Allocation: the box Still planned on projects another team runs now lists each month from this one on. Keep it if your people still work on the project; otherwise Clear it, then Save.
What the board does with it
On the board
After the move
Project details
Taken from the other team until the new team saves them, then from the new team.
Invoices
All of them count, whichever team booked them. Only the team that booked an invoice changes it.
Allocation
Both teams’ people count, each team planning its own.
Effort
Reported per person, as before; nothing moves.
Closed months
Unchanged: a closed month keeps what it held.
Nothing is copied twice. The details are a starting point the new team saves once; the invoices and the history stay with the team that booked them and are counted once.
Portfolio Control Center by BI Development
15 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
When things change

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.

Three steps, in the month the change is approved
1
Change the figure · Team Lead
In the Workspace, Projects: type the new Effort estimate (FTE-months) or the new Approved budget (euro).
2
Save · Team Lead
Save records the change with its month and the figure before. That month is when it takes effect, so save it when the change is approved, not before.
3
Cover the new estimate · Team Lead
Allocation: plan your people for what the new estimate adds; the share of the estimate allocated is measured against the new figure.
What the board does with it
On the board
From the month of the change
Allocated (%)
Measured against the estimate in force.
Consumed against estimate
What an even pace expected up to the change stays; what the new estimate leaves is spread evenly up to the go-live. The project’s tooltip names the change, with the month and both figures.
Budget per month
The months before the change keep their baseline; what the new budget leaves is spread over the months up to the go-live.
Reports, closed months
Unchanged: a published report and a closed month keep what they showed.
First estimate
The first figure typed is not a change: it is measured from the start.
A typing error is corrected the same month. Corrected within the month it was saved, it leaves no trace on the line. Corrected a month later, it counts as a change from that month.
Portfolio Control Center by BI Development
16 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
When things change

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.

Four steps
1
Import the file as usual · Team Lead
Effort import: choose the file. A line repeated word for word is marked repeated, with the line it repeats, and left out: its hours count once. Nothing to fix.
2
Read the warnings · Team Lead
Two exports of the same week with other references are not repeats: both are kept, and the warning books … h on shows each day over the limit. Remove one export from the file and choose it again.
3
Correct a week with a new file · Team Lead
A file imported later replaces, for each person in it, the days it holds; the audit says how many days it replaces. The other days stay.
4
Import, then save · Team Lead
Import takes the valid lines; Save keeps them.
What the board does with it
On the board
In the audit and on the board
Repeated
Left out; not counted as an error.
Same day, other reference
Kept, with a warning when the day is over the limit.
Days imported before
Replaced by the new file, per person and day, never added to it.
Closed month
A day in a closed month is refused, with the month.
Board
Each hour counts once: effort, reliability score, weekly workload.
Two identical lines of real work? Give them different references; a line that repeats every column is taken for a copy.
Portfolio Control Center by BI Development
17 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
When things change

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.

Four steps, in the month the new date is decided
1
Type the new date · Team Lead
In the Workspace, Projects: change Target go-live.
2
Plan the phases of the new months · Team Lead
Planned phase, by month names the months without a phase. Give each one its phase.
3
Plan the people · Team Lead
Allocation: allocate the new months; for an earlier go-live, empty the months after it.
4
Save · Team Lead
Save records the move with its month and the date before.
What the board does with it
On the board
From the month of the move
Register
The new date, marked with the number of moves; the tooltip gives the first go-live and every move.
Late (wd)
Counted from the go-live in force.
Consumed against estimate
What an even pace expected before the move stays; the rest is spread up to the new go-live.
Budget per month
The months before the move keep their baseline; what is left is spread up to the new go-live.
Go-live passed, not moved
The project is Delayed and the whole rest of its budget falls on the current month, until the new date is set.
Move it when it is decided, not after. A date that has passed already shows the project as Delayed; moving it later does not remove the moves from the board.
Portfolio Control Center by BI Development
18 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
When things change

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.

Four steps
1
Set the status · Team Lead
In the Workspace, Projects: Status On Hold, in the month it stops. Save records the month.
2
Free its people · Team Lead
Allocation: a project on hold that still has people this month or later says On Hold: still allocated. Empty those months, so the people show free for other projects.
3
Resume · Team Lead
When work starts again, set Status back to Ongoing, check Target go-live and allocate the months ahead. Save.
4
Read it on the board · Manager
The register shows On Hold with the month it stopped; it is never shown as Delayed while on hold.
What the board does with it
On the board
While on hold, then at the resumption
Consumed against estimate
Nothing more is expected while on hold; at the resumption what is left is spread up to the go-live.
Budget per month
The months on hold carry nothing; at the resumption what is left is spread over the months up to the go-live.
Free for new projects
A project on hold brings nothing more until it resumes.
Allocation, load
Counted as planned: empty the months on hold to free the people.
Late (wd)
Still counted from the go-live in force: move it if the pause pushes the date.
Save it in the month it stops. The month you save is the month the pause starts. A status set before the change was recorded counts, for the budget, from the month after the last invoice.
Portfolio Control Center by BI Development
19 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
When things change

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.

Four steps, on the day of the move
1
Change the team · Manager
On the Management board, People, change the person’s Team and Save. The day of the save is the day of the move: the server records it with both teams.
2
Hand over what is planned · Former Team Lead
Allocation: the box Planned after a last day names the person, moved to the new team, with every month planned after the move. Give the work to someone else, Clear, Save.
3
Import up to the day before · Former Team Lead
Their effort up to the day before the move is still yours to import; a later day is refused.
4
Plan and import from the move on · New Team Lead
The person appears in your team: allocate the months from the move on and import their days from that day. An earlier day is refused: the former team imports it.
What the board does with it
On the board
After the move
Effort
Each day counts once, from the team the person was in that day.
Allocation
The former team’s plan counts through the month of the move, the new team’s from that month on.
Board rows
The person shows in the team they are in now; their earlier months keep their figures.
History
Kept: one row, one person, nothing removed.
A renamed team
Is not a move: nothing is recorded.
Change the team on the day it happens. Saved earlier or later, the day of the save still decides which team reports each day.
Portfolio Control Center by BI Development
20 / 21
Contents ↑
Portfolio Control Center · Team Lead manual
Reference

Quick reference

Terms
FTE
Share of a full-time contract: 1.00 full time, 0.50 half. Capacity is always written in FTE.
BAU
Business as usual: the part of the FTE that runs the business.
Net capacity
FTE minus BAU: what is left for projects.
Allocation
Share of a month planned on a project, in percent. 100% = one person full time, one month.
FTE-month
One person full time for one month. Effort estimates are given in it.
Load index
Committed allocation ÷ net capacity, per team and month.
Utilisation
BAU plus allocation ÷ the person's FTE, per month. Above 100% the month does not fit.
Completion
The percentage the project's phase carries. Never typed.
Execution order
One queue across all delivery teams. 1 is worked first.
Reliability score
Weighted result of four checks on the data under the board.
Report
Today's board, published by the Manager. Never changes.
Month photo
The board as of a closed month's last day. Taken when the Manager confirms the month, or by itself at the end of the following month. Never changes.
Closing a month
Each team closes its month, in order; the Manager confirms last. The month's allocation, effort and invoices then no longer change.
Reporting date
The report or month photo the board shows. Each reopens exactly as it was.
Window
The months in view, counted from the reporting date.
Display profile
A named set of colour bands, thresholds, window and board panels. The Manager's default opens for everyone.
Seat
One licence of your plan, for one person. A waiting invitation takes one.
Who to ask
Access, roles, teams, project identity, parameters, reports
the Manager
A team's people, allocation, project details, invoices, effort, its month
that team's Team Lead
A seat or licence
the Manager
Anything about the product
BI Development · support@bidevelopment.ro
Portfolio Control Center by BI Development
21 / 21
Contents ↑