Portfolio Control Center
by BI DEVELOPMENT

Manager manual

All manuals ·
  1. 01Three roles, one board
  2. 02Day one: becoming the Manager
  3. 03First configuration
  4. 04The list of people
  5. 05Access and roles
  6. 06Change, close, hand on
  7. 07Projects and the queue
  8. 08Planning board
  9. 09Score and phases
  10. 10Thresholds, units, window
  11. 11Profiles, panels, reset, save
  12. 12Reports and closing the month
  13. 13Project budget
  14. 14Routine
  15. 15Someone leaves
  16. 16A project changes team
  17. 17An estimate changes
  18. 18The go-live moves
  19. 19A project is put on hold
  20. 20Someone moves to another team
  21. 21Reading the board
  22. 22What each section answers
  23. 23The reliability score
  24. 24Quick reference
Portfolio Control Center
by BI DEVELOPMENT
Project portfolio management

Portfolio Control Center

Manager manual
For the Manager
Sets the rules: teams, project identity and every parameter. Gives access, publishes reports and confirms each closed month.
Manager manual · Version 2.0 · for Portfolio Control Center V1
October 2026
Portfolio Control Center
by BI Development
Portfolio Control Center · Manager 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 / 25
Contents ↑
Portfolio Control Center · Manager manual
Manager

Day one: becoming the Manager

The Manager role is named, then confirmed by the person named. From then on it belongs to that work account until it is handed on.

Before the first opening, once
1
Make the app available in Teams
Your Teams administrator uploads the app in Teams admin center → Teams apps → Manage apps, or adds it from the Teams app store.
2
Approve sign-in
Your Microsoft 365 administrator opens pcc.bidevelopment.ro/approve and accepts. Without it, people see Need admin approval.
Confirm the Manager role
1
Open the app in Teams
From a link to the app, or Apps → search Portfolio Control Center.
2
Confirm
The first screen says you were named Manager of your organisation. Select Confirm. Decline leaves the role to someone else.
3
Start on the Management board
After Confirm the Management board opens, empty, and opens there every time. Go on with the first configuration on the next page.

With a partner licence BI Development names the first Manager. With a subscription bought in the Microsoft commercial marketplace, the person who activates it is named.

Plans
Plan
Manager
Team Lead
Guest
Normal
1
1
1
Pro
1
2
5
Partner
1
2
3

A Team Lead seat covers one delivery team. A Guest seat is for a reader: a steering committee member, an executive.

Account, in the header of the Management board, shows the plan and its seats. There is no serial number or key to enter: the plan is checked each time the app opens.

The app starts empty. No people, no projects, no data of any other organisation. Only the default parameters come with it, or the ones you changed in the demo before the licence, and you can change every one of them.
Portfolio Control Center by BI Development
03 / 25
Contents ↑
Portfolio Control Center · Manager manual
Manager

First configuration

Do it in this order. Each step needs the one before it: a project needs its team and its manager in the list of people, an allocation needs both.

Step 1
Teams
name every delivery team
Step 2
Access
invite each Team Lead with their team, and the Guests
Step 3 · Team Leads
People
everyone who carries capacity or manages a project
Step 4
Projects
code, name, order, PM
Step 5
Parameters
check the defaults
Step 6 · Team Leads
Team data
project details, allocation, invoices, effort
Step 7
Publish report
the first report on the board
Every month
Close the month
Team Leads close, you confirm
Checklist for the first day
Every delivery team is named: + Add team on the People tab.
Each Team Lead is invited with their team and each Guest as Guest, on the Account page; each has the link to the app from you.
Every person of every team is in the list of people, added by their Team Lead, with FTE and BAU; every possible project manager has Can be PM ticked.
Every running project is created, with its code, name, team and project manager.
The execution order is set: one queue across all teams, 1 is worked first.
The phases match the way your organisation runs projects; the percentages increase.
The thresholds are the ones you want to be warned at. If unsure, keep the defaults.
Everything is kept with Save.
The Team Leads know their rhythm: allocation for the whole project, effort every week, the month closed in the first days of the next one.
Once the data is in, Publish report.
An empty board is expected on day one. Missing data stays visible and lowers the reliability score. That is the pressure that gets the data in; nothing is hidden to make the first report look better.
Portfolio Control Center by BI Development
04 / 25
Contents ↑
Portfolio Control Center · Manager manual
Manager

The list of people

One list for everyone who carries capacity or manages a project. Open the People tab of the Management board: kept by each Team Lead · the Manager moves people between teams. Access to the app is given on the Account page, not here.

Each field
Field
What it means
Rule
Name
First and last name
Corrected by the Team Lead on the People tab.
Role · Type
Job title; internal or external
For your own reading; not used in any figure.
Team
The delivery team the person belongs to
Set by you on the day of the move. Decides which Team Lead keeps their allocation.
Can be PM
Appears in the project manager list
Needed before you assign them a project.
Carries capacity
Counted in the plan
Set by the Team Lead: unticked for people who only read or approve.
FTE
Share of a full-time contract
1.00 full time, 0.50 half time.
BAU
Part of the FTE that runs the business
Must stay below the FTE.
Net
FTE minus BAU, computed
Never typed. FTE 1.00, BAU 0.30: Net 0.70.
Last day
Last working day, if leaving
Capacity stops after it; the row is then hidden.
Common tasks
Task
Do this
Teams
+ Add team in the Teams row, then invite a Team Lead for each team: they add their people. A team with no people, no projects and nothing recorded can be removed with ×. One with allocation, reported effort, invoices or a closed month cannot: rename it. Its Team Lead or invitation stays, with no team, until you give them one on Account › Access.
A team has no Team Lead
You keep it until its Team Lead confirms, on the team's Team Lead seat.
Someone joins
Their Team Lead adds them on the People tab of the Workspace.
Someone changes team
Change Team on the day of the move. Past days stay with the old team: see Someone moves to another team.
Someone leaves
Their Team Lead sets Last day. The Team Lead then moves what is still planned after it: see Someone leaves in the middle of a project. When a Team Lead leaves, close their access on the Account page and invite the new Team Lead.
Someone comes back
Their Team Lead adds a new row: each row is one contract, the earlier one keeps its history.
FTE or BAU changes
Their Team Lead changes FTE or BAU. Every load figure recalculates.
Portfolio Control Center by BI Development
05 / 25
Contents ↑
Portfolio Control Center · Manager manual
Manager

Access and roles

Team Leads and Guests get access from you, on the Account page: Account at the top of the Management board, section Access. Each uses one seat of your plan.

Invite a person
1
Check the seats
The section shows “Seats in use, invitations included: Team Lead 1 of 2 · Guest 2 of 5.” A waiting invitation takes a seat.
2
Fill in and invite
Work account: the person's work address, name@company.com. Role: Team Lead or Guest. Team: for a Team Lead, the team they keep. Select Invite.
3
The app e-mails the invitation
From support@bidevelopment.ro, to any organisation, with the way into Teams and the manual of the role. The page says where it went; Send the e-mail again sends it once more. If it could not leave, the page gives the link to send yourself.
4
They confirm
They open the app in Teams and select Confirm. Until then their row reads “invited <date>, waiting”.
Someone of another organisation, an external consultant for example, is invited the same way, by their own work address. They keep their own Microsoft 365 account: no guest account, no Microsoft guest e-mail. The list marks them “another organisation”.
Portfolio Control Center by BI Development
06 / 25
Contents ↑
Portfolio Control Center · Manager manual
Manager

Change, close, hand on

Change, close, take back
To
Do this
Change a role or a team
Choose it in the person's row. The new role needs a free seat.
Close access
Close access, then Confirm close. A Guest seat is free again. A Team Lead seat stays with the team; you keep the team until the new Team Lead confirms.
End access on a date
Type the date in Access ends and confirm in the window that opens; Cancel keeps nothing. The day after, the access closes by itself, as Close access. A date in the past is refused: close the access instead. Empty the field and confirm to take the date back; it can be taken back until its day. A waiting invitation has no end date. For a Team Lead, the window says what follows: from the next day they no longer open the app; you keep the team until the new Team Lead confirms; the team's people, projects and effort stay.
Take back an invitation
Take back on the waiting row.
See what happened
Every step is kept in the history.

Access ends is not the Last day on the People tab: a contract's last day closes capacity, never access.

Hand on the Manager role
To
Do this
Hand on the role
Hand the role to → a work account of your organisation → Transfer. You stay Manager until they confirm; until then Take back cancels it.
The Manager left without handing it on
Your organisation writes to BI Development, which names the new Manager. That person confirms in the app.
Teams you keep as Team Lead
They go to the new Manager when they confirm, until each team's Team Lead confirms.
Portfolio Control Center by BI Development
07 / 25
Contents ↑
Portfolio Control Center · Manager manual
Manager

Projects and the queue

You give each project its identity and its place in the queue. The delivery team fills in everything else. Open the Projects tab of the Management board.

Create a project
1
Add the locations
GL Global is always there. For each other place projects run in, + Add location: a name and an abbreviation of one or two characters. A location in use cannot be removed.
2
Select + Create project
A new row appears at the end of the execution order, on Global.
3
Choose the location and the number
The code is the location's abbreviation and a number, for example XY-004. The next free number is proposed; type another for a project that already has a code. The same number twice on one location is refused, and a number once used is never proposed again. You can correct the code until the project is first used: an allocation, reported effort or an invoice. From then on it is locked.
4
Name it, choose the team and the project manager
The name can change at any time. The project manager is chosen from people ticked Can be PM. The team decides which Team Lead fills in the details. Moving a running project: see A project taken over from another team.
5
Place it in the queue
Move it with ↑ ↓ to the position it should be worked in.

A project not ready for a team yet: prepare it on the Planning board.

The execution order: one queue across all delivery teams; 1 is worked first. Delivered projects leave the queue.

What can change later
Field
Can change
Who
Code
Until the project is first used, then never
Manager
Name
Any time
Manager
Execution order
Any time
Manager
Project manager
Any time, also while the project runs
Manager
Everything else
Any time
The team's Team Lead
Remove the project
Until the project is first used, then never: it keeps its history, like a person
Manager
Portfolio Control Center by BI Development
08 / 25
Contents ↑
Portfolio Control Center · Manager manual
Manager

Planning board

Projects you prepare before giving them to a team: only a code and a name. Open the Planning tab of the Management board. Only you see them: not on the board, in the Team Lead Workspace or in the export.

1
Plan a project
+ Plan project: the location, the proposed number and the name. Kept at once, no Save. While it is planned, the code is reserved: no other project can take it.
2
Change or remove
The name can change at any time. ×, asked twice, removes it.
3
Start it
Start moves it to the Projects tab, with no team and no project manager. Choose both, then Save: the project starts and leaves the Planning board.
Portfolio Control Center by BI Development
09 / 25
Contents ↑
Portfolio Control Center · Manager manual
Manager

Parameters: score and phases

Open the Parameters tab. Changes are kept only when you select Save; a value that breaks a rule is refused.

Reliability score
Check
Default weight
Passes when
Projects with an effort estimate
20%
the project has an estimate in FTE-months
Projects with resources allocated
30%
someone is allocated to it in the reporting month
Effort reported for the last complete week
40%
each person with capacity reported that week
Reported phase on plan
10%
the reported phase is at or ahead of the month's planned phase

Weights must total 100%. Bands: green from 100%, amber from 90%, red below; green must stay above amber. Line to clear on the dial: 90%.

Project lifecycle: the phases
#
Phase
Completion
Timeline code
1
Analysis
30%
ANL
2
Development
60%
IMP
3
UAT
80%
UAT
4
Hypercare
90%
PV
5
Delivered
100%
—
Change the phases, step by step
1
Add a phase
Select the row it follows and add a phase below it. Example: Pilot · 85% · PIL between UAT and Hypercare.
2
Rename, set the percentage and the code
Percentages must increase down the list; codes must be unique. The Team Lead plans each month with the code; it labels the timeline bar.
3
Reorder or delete
Move a phase up or down, or delete it; its team then moves each project in it to another phase.

Statuses outside the scale: by default Not Started and Canceled are left out of the phase check.

Portfolio Control Center by BI Development
10 / 25
Contents ↑
Portfolio Control Center · Manager manual
Manager

Parameters: thresholds, units, window

Each threshold is a management decision, not a calculation. The board applies it everywhere the figure appears.

Alert thresholds
Threshold
Default
Flags
Portfolio load index
85%
a team month committed above it
Resource month nearly full
80%
a person's month at or above it
Resource month overbooked
100%
a person's month that does not fit
Workload bar ceiling
160%
bars above it drawn clipped
Person under-allocated
50%
BAU plus allocation below it
Burning faster than it progresses
10 points
effort runs ahead of completion
Allocation ahead of progress
25 points
allocation far ahead of completion
Going live soon
45 days
go-live within that many days
Budget nearly spent
85%
amber from it; red above 100%
Reported against planned · weekly
±10% · ±10%
reported off the plan
Team · person reporting too little
60% · 50%
reporting below it
Units and effort import
Setting
Default
Hours in one FTE-week · FTE-month
40 h · 168 h
Week counted as up to date
last complete
Hours in one line · one person books in one day
12 h · 16 h
Import file: date · decimals · columns
YYYY-MM-DD · point · comma
View window
Mode
Shows
Rolling (default)
3 months before the reporting month, 9 after
Calendar year
January to December of the reporting date
Quarter
the quarter of the reporting date
Fixed range
the two months you choose
Portfolio Control Center by BI Development
11 / 25
Contents ↑
Portfolio Control Center · Manager manual
Manager

Profiles, panels, reset and save

A display profile changes what the board shows, never how it counts. Keep one for the steering committee, one for the weekly review.

In a profile
The view window and the budget years
Colour bands and the line to clear
The thirteen alert thresholds
Board panels and register columns
The same for every profile
Weights of the reliability score
Phases, percentages and codes
Statuses outside the scale
Units and the up-to-date week
Effort import limits and file format

Settings that change the numbers stay common, so reports remain comparable over time.

Work with profiles
1
Create
Select + New from this one: the new profile starts as a copy of the current one. Names must be unique.
2
Set as default
Select Set as default. The board opens in this profile for everyone: Manager, Team Leads and Guests. Only you choose it.
3
Delete
Select Delete. The default profile cannot be deleted.
Where profiles are kept. The application stores only the standard profile and the one you set as default. Your other profiles stay on your own computer, in your Microsoft Teams profile (or your browser profile, when Teams runs in a browser). They are never stored in the application's database, and they do not follow you to another computer.

Board panels, in Parameters: untick a panel to hide it, and choose the columns of the project register. The reliability score and the register's Order, ID, Project and Status are always shown, so missing data and delays stay visible.

Client logo, in Parameters: a PNG, JPEG or WebP file up to 150 KB. Kept at once; Remove, asked twice, takes it out. It shows on the board, under Portfolio Control Center, for everyone who reads it.

Reset and save
Button
Does
Reset to default
restores the product's values for one section
Reset all parameters to default
restores them everywhere, except the budget
Save
keeps every change, on every tab; nothing is kept before

Save refuses a value that breaks a rule, and says which: weights not totalling 100%, green not above amber, phase percentages that do not increase, duplicate phase codes.

Portfolio Control Center by BI Development
12 / 25
Contents ↑
Portfolio Control Center · Manager manual
Manager

Reports and closing the month

A report you publish and the photo of each closed month keep the board as it was. Neither changes afterwards.

Publish a report
1
Save first
The report is computed from what is saved. With changes waiting, the bar says “Save your changes first: the report is computed from what is saved.”
2
Select Publish report, then Confirm: publish today’s report
Under Save on the Management board. The page says “Published. The report of <date> is on the board.”
3
One a day
A second one is refused: “today's report is published; a published report does not change”.
Closing a month
1 · Team Leads
Close in order
each their team, once its effort is in
2 · You, if needed
Close for a team
whose Team Lead is away
3 · You, last
Confirm the month
the month photo is taken
Otherwise
It closes by itself
end of the following month
October 2026Delivery closed · Platform open Close for Platform Confirm October 2026closes by itself on 2026-11-30
Rule
Means
In order
November cannot be closed while October is open, by a Team Lead or by you.
Team Lead away
Close for <team>: the history records that you closed it.
You confirm last
Confirm <month> once every team has closed it: the photo of the month is taken, as of its last day.
Nobody confirmed
At the end of the following month it closes and is photographed by itself, with what is there: missing data stays visible and lowers the score. July begins with May closed.
After closing
The month no longer changes, for anyone, you included. A correction found later appears from the next report; the photo never changes.
History months
Months before a team first saved its data are history being entered: they never close by themselves.
Month photo or report? The photo comes with the closing, once a month; a report when you want one, before a steering committee for example. Both are in Reporting date.
Portfolio Control Center by BI Development
13 / 25
Contents ↑
Portfolio Control Center · Manager manual
Manager

Project budget, month by month

Only the projects’ costs: the invoices the Team Leads book, against each project’s approved budget. Licences, subscriptions and the overall budget stay outside.

Your settings · Budget tab
Setting
What it does
Budget per year
All projects together, for each fiscal year. Empty means not allocated yet.
Fiscal year starts in
January by default. Any other month, and the board reads FY 2026/27.
Unspent at year end
Lapses, or carries over to the next fiscal year.

In Parameters, Annual budget panel sets how many years before and after the reporting year the board opens.

Annual budget, on the board
Figure
Means
Committed
Invoiced, plus the projects’ baselines for the months left in the year.
Free for new projects
The year’s budget minus what is committed. Red when the projects already need more. Projects without an approved budget are named, not counted.
Projects, per month
Invoiced (solid), then what is still to come (hatched): the spikes show month by month.
Each project, against its monthly baseline

Board › 03 Budget › Per month. The approved budget spread evenly from start to go-live: 100k over five months, 20k a month. Red: a month above its baseline. Under the name, the balance: “Invoiced €92,000 of €100,000 · €8,000 left”.

18k / 20kJan15k / 20kFeb20k / 20kMar22k / 20kApr17k / 20kMay
When
The baseline
On hold
The months on hold carry nothing. When the project resumes, what is left is spread over the months up to go-live.
Go-live moved
What is left is spread over the months up to the new go-live.
Go-live passed, not moved
What is left falls on the current month, and the line asks for the new go-live, set in the Team Lead Workspace. Moving it is the Team Lead’s job.
Closed earlier
The months with no activity give their share to the last month with activity: the unused money shows there.
Export project costs

Export project costs next to Publish report downloads Project costs - <date>.csv: one row per invoice, every project and year. Columns: Project code, Project, Location, Team, Month, Invoice date, Invoice, Supplier, Description, Amount. The separators are the ones set for the effort import. The same section sets the absence code (default ABSENCE): hours booked with it lower the month’s capacity and count as reported, never as BAU or project work.

Portfolio Control Center by BI Development
14 / 25
Contents ↑
Portfolio Control Center · Manager manual
Manager

The Manager's routine

Once set up, the Manager's work is short and regular. The board tells you where to look.

Every week
Open the board and read the reliability score. Hover the dial: it shows which check is failing.
If Effort reported fails, the team's Team Lead has not imported last week's effort yet.
Every month
In the first days: check the months to close, under Publish report. Close for <team> where a Team Lead is away, then Confirm <month>.
Before it starts: check that every project is allocated through to its go-live, and the coming month adjusted. An empty month shows as a gap.
Review the execution order. Move up what must be worked first.
Move the people who change team.
Create the projects approved since the last review.
Every quarter
Review the thresholds and the phases against how projects actually ran.
Review who has access: Account page › Access. Close access, or set Access ends, for anyone who no longer needs it.
Check the plan's seats against the people who use the app.
Before a steering committee
Set the profile meant for that audience as default.
Save, then Publish report: the board opens on the latest report.
Read the red section cards first: they are what the committee will ask about.
Reports and month photos never change. An earlier reporting date reopens the board exactly as it was. A correction made today appears from the next report.
Portfolio Control Center by BI Development
15 / 25
Contents ↑
Portfolio Control Center · Manager 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
16 / 25
Contents ↑
Portfolio Control Center · Manager 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
17 / 25
Contents ↑
Portfolio Control Center · Manager 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
18 / 25
Contents ↑
Portfolio Control Center · Manager 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
19 / 25
Contents ↑
Portfolio Control Center · Manager 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
20 / 25
Contents ↑
Portfolio Control Center · Manager 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
21 / 25
Contents ↑
Portfolio Control Center · Manager manual
The board

Reading the board

The board opens on the latest report. Everything at the top of the page is a way in; nothing you click changes the data. Beside each chart, ? shows how it is worked out, step by step, and the speaker reads it out; presenting in a Teams meeting, share with Include sound so the others hear it. Under the title, your organisation's logo, if the Manager has set one.

Your organisation · Projects
Portfolio Control Center
1
Reporting date
latest report ▾
2
Window
from ▾
–
to ▾
3
%
4
01 Capacity
02 Register
03 Budget
04 Timeline
05 Composition
5
Portfolio
Effort
Method
1
Reporting date
The board opens on the latest report: one the Manager published, or a month photo, “October 2026 · month closed”. Pick another and the board redraws exactly as it was, with the parameters it was computed with. The Manager and the Team Leads also see Today, not published.
2
Window
The months in view. The board opens on the Manager's window, by default 3 months before the reporting month and 9 after. Choose any other range for your session; Back to the default window restores it.
3
Overall reliability
How far the data underneath can be trusted, against the line to clear set by the Manager (90% by default). It is about the data, not about project performance.
4
Section cards
One per section the Manager shows. A red edge means needs attention. Hover for the figure and the reason; click to go straight there.
5
Three tabs
Portfolio: plan, estimates, budget, timeline. Effort: what was actually consumed. Method: how every figure is calculated.
Everywhere on the board: hover a figure, a cell or a column heading for the detail behind it. Each team's panel opens and closes with a click. A figure with nothing under it reads —.
Portfolio Control Center by BI Development
22 / 25
Contents ↑
Portfolio Control Center · Manager manual
The board

What each section answers

Portfolio tab · the plan
01
Capacity
Is each team over-committed, month by month? One band per team, closed, with its peak; the arrow opens the months. A heatmap per person.
02
Project register
Where does each project stand? Filter by location, status or team; sort any column.
03
Budget
How much of each approved budget is spent, set against completion, and month by month against its baseline.
04
Timeline
The planned phase of each month, per project. The marked column is the reporting month.
05
Composition
By strategic driver, status, location and current phase; missing values counted as “not set”.
Effort tab · what was consumed
06
By resource
Did each person report what the plan put on them, up to their last reported day?
07
Per project
Is a project consuming its estimate faster than it progresses?
08
Weekly workload
Week by week: projects, business as usual, absence and the rest, against contracted hours.
09
Effort by month
Hours reported each month against each person's contract.
10
Project share
Of all hours reported, how many carried a project code, per team.
The plan, the timeline and the effort panels follow the window. Budget, consumed-against-estimate and the register always count from each project's start.
Reading the colours
Under 80% · spare capacity
80–100% · fully committed
Over 100% · the month does not fit
Empty · nothing entered yet, a gap
The thin stripe at the left of each team's band, in every folded chart: green in order, amber to watch, red to check. The Manager's thresholds set it.
The reliability score
Projects with an effort estimate
20%
Projects with resources allocated
30%
Effort reported for the last complete week
40%
Reported phase on plan
10%
Default weights shown. By default green at 100%, amber from 90%, red below. Weights and bands are set by the Manager.
Portfolio Control Center by BI Development
23 / 25
Contents ↑
Portfolio Control Center · Manager manual
The board

The reliability score, worked

The score says how far the data under the board can be trusted. It is about the data, not about how well the projects are going.

A worked example, with the default weights
Check
Result
Pass rate
Weight
Points
Projects with an effort estimate
8 of 10
80%
20%
16.0
Projects with resources allocated
9 of 10
90%
30%
27.0
Effort reported for the last complete week
5 of 6 people
83%
40%
33.3
Reported phase on plan
6 of 9
67%
10%
6.7
Reliability score
83%

83% is below the amber band (90% by default), so the dial is red. The biggest loss is the weekly effort: one person in six has not reported.

Who brings each check up
Check fails because
Fixed by
a project has no effort estimate
the team's Team Lead, in Projects
nobody is allocated to a project this month
the team's Team Lead, in Allocation
a person has not reported last week
the team's Team Lead, by importing the effort
the phase is behind the timeline
the team's Team Lead updates the phase, or the plan is revised
a project has no timeline
the team's Team Lead, in Planned phase, by month
Gaps lower the score on purpose. A project with no data still counts in every check. Nothing is left out of the count to make the score look better. The one exception is time the data could not cover: a team that came with projects already running owes no week before its monitoring start, and its opening balance stands for that time.
Portfolio Control Center by BI Development
24 / 25
Contents ↑
Portfolio Control Center · Manager 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
BI Development · support@bidevelopment.ro
Anything about the product
BI Development · support@bidevelopment.ro
Portfolio Control Center by BI Development
25 / 25
Contents ↑