| Tier | Delay (days) |
|---|---|
| Platinum | 1 |
| Gold | 2 |
| Standard | 7 |
| Public (no account / suspended) | 14 |
| Distance from HQ to the site | Penalty (days) |
|---|---|
| ≤ 20 km | 0 |
| ≤ 100 km | 1 |
| further, or HQ location unknown | 2 |
Worked example
| Installer | Tier | Distance | Tier delay | Distance penalty | Combined | Sees it on |
|---|---|---|---|---|---|---|
| Aurora Solar | Platinum | 10 km | 1 | 0 | 1 | day 0 |
| Beacon Energy | Gold | 50 km | 2 | 1 | 3 | day 2 |
| Coral Power | Standard | 150 km | 7 | 2 | 9 | day 8 |
day_shift = 1. The closest, highest-tier installer always sees a request first — an accurate HQ location is an installer's biggest lever.
The algorithm
combined_penalty(i) = tier_delay(i) + distance_penalty(i) day_shift = min(combined_penalty over all candidates) visible_from(i) = published_at + (combined_penalty(i) - day_shift) days
day_shift is computed once when the request is published and recorded, so a late sign-up never reshuffles the window for everyone else.
More: how an RFQ is generated · the acceptance window · quoting