batch-workloadlisted

# BATCH Workload Planning The BATCH method turns a pile of ClickUp tasks into a readable weekly plan. Every scheduled task belongs to a one-week batch, carries a point value, and is owned by one person. A clean board is one where each person's week sits at or under capacity and nothing is silently overdue or unassigned. Announce at start: "I'm using the batch-workload skill." ## The Method ### BATCH field (dropdown) Each task gets exactly one batch. Options, in order: | Batch | Meaning | Dates written on the task | |-------|---------|---------------------------| | Previous | Done or past work, kept for history | left as-is | | This Week | Committed for the current week | start = Monday, due = Friday of this week | | Next Week | Committed for next week | start = Monday, due = Friday of next week | | Later | The week after, soft commitment | start = Monday, due = Friday two weeks out | | Maybe / Someday | Backlog, no week assigned | dates cleared | The last bucket is named `Maybe` on some spaces and `Someday` on others. Read the field options before writing, do not assume the label. ### Batch to dates rule Every task in a batch shares the same start and due dates. A batch is one week of work, Monday through Friday. Set dates date-only (`start_date_time: false`, `due_date_time: false`). This keeps the deadline as the single source of truth and the batch derived from it. Where an app renders the same board, it needs the same derivation, in one place both sides read. ###