Managing Tier Configuration
Platform administrators can customize the entire tier system through the Tier & Labor dashboard module. This includes adding or modifying tier levels, adjusting scoring weights, and setting payout percentages. Changes affect how workers are scored and placed going forward.
Accessing Tier Configuration
Navigate to Dashboard > Tier & Labor (requires pandora.admin.override permission, Enterprise plan only). The configuration interface has two main sections: Tier Levels and Scoring Weights.
Tier Level Configuration
Each tier level is stored in the pandoraTierLevels table and defines:
| Field | Description | Constraints |
|---|---|---|
| Level | Numeric rank (ascending) | Unique, positive integer |
| Name | Display name (e.g., "New", "Proven") | Unique, used in all worker-facing UI |
| Score Range | scoreMin to scoreMax (inclusive bounds) | No gaps or overlaps between tiers |
| Payout Percentage | Worker's share of Pandora value | 0-100%, typically increases with tier |
| Min Jobs Required | Completed jobs before eligible for this tier | Must be achievable, progressive |
| Min Lead Time Hours | How early the worker sees jobs | Decreases with higher tiers |
| Max Job Value | Optional cap on claimable job value | Null = no cap (typically Tier 5) |
| Can See Last Minute | Access to jobs starting within 4 hours | Typically only top tiers |
Adding a New Tier
To add a tier:
- Open the Tier Levels section
- Click "Add Tier"
- Set all required fields — ensure score ranges do not overlap with existing tiers
- Save — the system immediately begins placing workers using the updated configuration
Editing an Existing Tier
You can modify any tier's properties at any time. Common adjustments include:
- Adjusting payout percentages — For example, increasing the Tier 3 payout from 85% to 87%
- Changing minimum job counts — Lowering the threshold to make advancement easier, or raising it for quality control
- Modifying lead time windows — Giving more or fewer hours of advance visibility to specific tiers
- Adjusting value caps — Raising caps to give lower tiers access to higher-value jobs
When you change a tier's score range, workers whose current scores fall within the new range may be reassigned to different tiers at the next recalculation.
Removing a Tier
You can deactivate a tier if needed. Workers currently at that tier will be reassigned to the appropriate tier based on their score at the next recalculation. Removing a tier is a significant action — consider the impact on worker expectations before proceeding.
Scoring Weight Configuration
Scoring weights are stored in the pandoraScoringWeights table. Each input has:
| Field | Description |
|---|---|
| Input Key | Identifier (e.g., "completionRate", "onTimeRate") |
| Weight | Decimal value — all weights must sum to 1.00 |
| Category | Reliability, Performance, or Other |
The Eleven Scoring Inputs
| Input | Default Weight | Category |
|---|---|---|
| Completion Rate | 18% | Reliability |
| On-Time Rate | 13% | Reliability |
| Satisfaction Score | 13% | Reliability |
| Speed Efficiency | 13% | Performance |
| Quality Score | 13% | Performance |
| Responsiveness | 12% | Performance |
| No-Show Penalty | 8% | Other |
| Volume Score | 4% | Other |
| Put-Back Penalty | 3% | Other |
| Tenure Bonus | 2% | Other |
| Streak Bonus | 1% | Other |
Adjusting Weights
To change scoring weights:
- Open the Scoring Weights section
- Modify individual input weights
- The system validates that all weights sum to exactly 1.00 (100%)
- Save — the new weights take effect at the next recalculation
Important considerations:
- Increasing a weight makes that factor more influential in tier placement
- The reliability category (completion + on-time + satisfaction) is typically the largest block at ~44%
- Extreme weight configurations can have unintended effects — test changes carefully
- Weight changes affect ALL workers simultaneously at their next recalculation
Weight Impact Examples
| Change | Effect |
|---|---|
| Increase completionRate from 18% to 25% | Workers who complete jobs reliably advance faster; those who do not fall further behind |
| Decrease speedEfficiency from 13% to 5% | Speed becomes less important; workers are evaluated more on reliability and quality |
| Increase noShowPenalty from 8% to 15% | No-shows become even more punishing; strong deterrent effect |
Recalculation After Changes
When you change tier levels or scoring weights:
- Changes take effect at the next score recalculation for each worker
- The daily scheduled recalculation (2:00 AM UTC) will process all workers with the new configuration
- Real-time recalculations from job outcomes also use the new configuration immediately
- Workers may see tier changes as a result — promotions or demotions based on the new thresholds and weights
Audit Trail
All configuration changes are logged in the audit trail:
- Who made the change (admin user)
- What was changed (field, old value, new value)
- When the change was made
- The change is permanent and visible to other administrators
Best Practices
- Make incremental changes — Adjust one or two parameters at a time and observe the impact before making further changes
- Monitor tier distribution — After changes, check how many workers are at each tier to ensure a healthy distribution
- Communicate changes — Major tier or weight changes affect worker earnings and should be communicated proactively
- Keep score ranges contiguous — Ensure there are no gaps between tier score ranges that could leave workers unassigned
- Test with examples — Before saving, mentally calculate how the change would affect a sample worker profile
On this page