Patterns
Reuse a schedule and check coverage
Keep active projects represented in recurring time plans without confusing enabled schedules with completed work.
On this page
User goal
Keep active projects represented in recurring time plans without confusing enabled schedules with completed work.
Workflow
| Step | Expected behavior |
|---|---|
| 1 | Review the schedule’s name, Space, assigned weekdays, and enabled state. |
| 2 | Enable or disable a schedule through its named switch. |
| 3 | Review the coverage banner for unscheduled active projects. |
| 4 | Assign missing projects to a relevant enabled schedule with at least one day. |
| 5 | Inspect the resulting day plan separately from the overview’s coverage signal. |
Decision rules
- Disabled schedules and schedules without assigned days do not provide coverage.
- Only in-progress projects from active Spaces are considered by the source coverage helper.
- Coverage means time has been assigned, not that a deadline or workload is guaranteed achievable.
- Keep the uncovered project names actionable through links.
Edge cases and recovery
- A warning with zero active projects must remain understandable.
- Do not count archived Spaces as active coverage.
- Check rule alignment between schedule DTOs and the pure coverage helper.
- Theme-sensitive warning colors are a documented exception; verify readability in dark mode.
Source references
| File | Responsibility |
|---|---|
| app/components/schedules-workspace.tsx | Coverage and enabled controls |
| app/components/schedule-coverage.ts | Coverage helper |
| app/components/schedule-toggle.tsx | Switch semantics |
Examples from the app
Actual Radarist components with fictional data. Captured at 2× resolution or higher. Select an image to inspect it full size.
Related topics
Source audit: 2026-10-07 · Revision 0103e2549959 · Documentation v0.1