The dispatch coordinator at fictional Lark Harbor Logistics needs a clear plan before the next depot handoff. Use existing work, exclude completed records from the new board, estimate the carrier fix and plan two named items. Done means the board, estimates, sprint membership and goal all agree, with a checked final handoff decision.
The Lark Harbor coordinator needs a usable dispatch plan for the next period. The existing records mix defects, documentation and work already completed. Your deliverable is a scoped board, explicit estimates and sprint membership that match the planned handoff.
This project carries saved work from one step to the next. Each check includes earlier requirements, so a later edit must preserve the board and estimates you already established. If you open a step directly, its fallback starts from the preceding correct state. Keep the work item's key stable and use lifecycle actions for the sprint. A report that merely looks busy doesn't establish a plan. The final query must show the intended sprint population from its relationship fields.
Build a dispatch plan that retains its earlier configuration.