Priority, effort, and how scoring works

Project Echo helps you prioritize with priority, effort, and an optional score that combines demand signals with how hard something is to deliver.

​

Priority

Priority is a simple urgency label:

• Low
• Medium
• High
• Urgent

(You can also leave priority unset.) Set it on the request meta panel, in the create dialog (when enabled), or with bulk actions.

​

Effort

Effort is a 1–10 estimate of relative cost or complexity. Use it consistently across your team so scores stay comparable. Effort can also be left unset.

​

Scoring

When scoring is enabled under Settings → Feedback → Scoring, each request gets a score based on weighted signals such as:

• Base weight
• Priority level
• Member and team votes
• Member and team comments
• Effort

In short: Score = (weighted total) ÷ Effort (when the effort field is enabled). If effort is disabled, the score reflects the weighted total alone. You can adjust scoring weights in Settings to match how your team values votes, comments, and priority.

​

Where to see the score

• On the request detail page (score badge)
• In the Score tab, which breaks down contributing factors
• In list sorting and filtering when score is available

​

Fields settings

Under Settings → Feedback → Fields, choose whether priority, effort, and related fields appear on the request page, new request modal, and portal. Scoring is a guide—not a replacement for product judgment—but it’s a fast way to surface high-demand, high-urgency work. Questions? Email [email protected].