Skip to main content

Performance Dashboard

Two views of team performance — Overview for live workload and delivery pressure, Learnings for aggregate insight from completed post-mortems.

h
Written by henry brogan

The Performance Dashboard gives you a high-level view of how your team is performing, built for managers and team leads who need to assess health without opening projects one by one.

It has two views, toggled at the top of the page.

Overview

What is happening now — live workload, delivery pressure, commercial performance and pipeline momentum.

Learnings

What you have learned so far — aggregate insight drawn from every completed post-mortem across the team.

Overview tells you where to intervene this week. Learnings tells you what keeps going wrong across bids, which is a different and slower question.

Where to find it

  1. In the left-hand sidebar, click Team.

The Performance page loads by default, on the Overview view.

Overview

The Overview view pulls live data from projects, tasks, questions, deadlines and bid outcomes, so you can see at a glance whether the team is balanced, stretched, or at risk.

It is made up of several insight panels. Depending on the data available for your selected team, these can cover:

  • Team-wide commercial performance

  • Pipeline value and stage distribution

  • Delivery trends and momentum over time

  • Operational risks and bottlenecks

  • Capacity pressure across active work

Questions the Overview answers

  • Is our team currently overloaded?

  • Are too many live bids creating delivery risk?

  • Are task, question and deadline volumes manageable?

  • Is pipeline growth being matched by team capacity?

  • Where does intervention need to happen first?

Learnings

The Learnings view aggregates the confirmed post-mortems your team has completed, turning individual bid retrospectives into patterns you can act on.

This is the return on completing post-mortems. One post-mortem tells you about one bid; fifty of them tell you why you win and lose.

Headline figures

Completed post-mortems

The total number your team has confirmed.

Win rate

Your win rate across those bids.

Average evaluation score

The average score awarded across evaluated submissions.

Last completed

When the most recent post-mortem was completed.

Check the last-completed date alongside the others. If it is months old, the patterns below are describing a version of your team that may no longer exist.

Post-mortem breakdowns

Win and loss by client type or industry

Where you perform strongly, and where you consistently do not.

Win and loss by bid type or procurement route

How outcomes vary by the kind of procurement you are responding to.

Categorised loss reasons

The main recorded reasons you are losing submissions, drawn from the outcome categories set in each post-mortem.

Loss reason mix

The relative weight of those reasons against each other.

Question pain points

Recurring difficulties on particular questions or question types across bids.

Latest team takeaways

The most recent lessons captured in completed post-mortems.

Question pain points are the most directly actionable of these. A question type that recurs here is usually a gap in your Bid Library rather than a drafting problem — which makes it fixable once, rather than repeatedly.

What Learnings depends on

Only confirmed post-mortems are included. A post-mortem left in draft contributes nothing here, however thoroughly it was filled in.

The quality of the breakdowns also depends on outcome categories being applied consistently across bids. Free-text reasons do not aggregate; taxonomy categories do. See Completing a post-mortem.

Capacity settings

Capacity Settings in the top-right of the page control the assumptions BidScript uses when calculating workload and availability.

Active Bids Per Member

How many live bids one person can manage before their project capacity is considered full.

Total Questions Per Member

How many assigned questions one person can carry before question workload begins reducing their availability.

These two numbers underpin every availability and workload figure shown anywhere in the Team area - the dashboard, the member table and individual profiles all calculate against them.

That makes them worth setting deliberately. Left at values that do not reflect how your team actually works, every availability reading downstream is misleading in the same direction.

Only team admins or organisation admins can change Capacity Settings. Everyone else can view them.

Keeping the data reliable

Both views run on live data, so their accuracy depends on the underlying records being current.

For the Overview, keep project statuses and deadlines, task and question assignments, and task completion progress up to date. A team that does not close out completed tasks will appear more stretched than it is, and the dashboard will point you at the wrong problem.

For Learnings, complete and confirm post-mortems after every bid. The view is only as good as the retrospectives feeding it.

Related articles

  • Member Capacity — the person-by-person view, and what each capacity metric means.

  • Team Member Profiles — an individual's workload, contribution and skills.

  • Completing a post-mortem — the retrospectives that populate Learnings.

  • Outcome Area: Overview — capturing what happened after a bid.

  • Organisation & Team Seats — who has access to your workspace.

Did this answer your question?