You can configure how Pilea calculates the priority score by adjusting the weight of each signal. This is done in workspace settings and requires Admin access.

What you'll need

Admin role in your Pilea workspace

Adjusting signal weights

The Pilea Priority score comes with default weights. You can adjust these to match your business model.

Go to Settings > Priority Score.
Use the weight sliders to increase or decrease each signal's contribution.
The weights must add up to 100%.
Click Choose Priority Score and Recalculate to save adjustments.

SCREENSHOT: Weight sliders for the Pilea Priority Score framework showing the six signals. Remember to click Choose Priority Score and Recalculate to save adjustments.

When to adjust weights

You have a small number of high-value accounts - Decrease Customer Breadth, increase Revenue Impact (Deals).
Prospect feedback drives your roadmap - Increase Revenue Impact (Leads) above the default 10%.
Your team moves fast and recency matters most - Increase Recency so fresh signals dominate.
You don't have CRM data connected yet - Revenue signals will show 0 for most items. Breadth, Volume, and Recency carry the score until you connect a CRM.

💡 Tip: Start with the defaults. Adjust after you've seen a few weeks of scores and have a feel for what's ranking too high or too low.

Enabling the effort divisor

The effort divisor divides the priority score by the estimated size of each item (XS, S, M, L, XL). This surfaces quick wins - high-priority items that are small enough to ship fast. Pilea automatically suggest a size for each backlog item, which you can override in the backlog detail view.

For Pilea Priority Score

The effort divisor is optional. To enable it:

Go to Settings > Priority Score.
Toggle Effort divisor on.
Click Choose Priority Score and Recalculate.

Once enabled, backlog items with a size set on their detail panel will have their score adjusted. Items without a size are unaffected.

Triggering a batch recalculation

After changing your framework, adjusting weights, or enabling the effort divisor, you should recalculate all scores so every item reflects the new settings.

Go to Backlog
Click Recalculate scores.
Wait for the recalculation to complete. This takes a few seconds for most workspaces.

All backlog items update to reflect the new framework and weights. Manually overridden items keep their pinned score - the computed score updates silently in the background.

SCREENSHOT: Recalculate scores button on the backlog page.

What happens to existing scores

Change you made	What happens
Adjusted weights	All computed scores recalculate with the new weights
Enabled/disabled effort divisor	All computed scores with a set size recalculate with the size adjustment.
Manually overridden items	Pinned score stays. Computed score updates in the background and shows as "Computed: X - manually overridden"