After a scope is approved, Sensra can generate a task board from the scope sections. This article explains how task generation works and how to manage the resulting task board.
How task generation works
Task generation reads each approved scope section and creates one or more tasks from it. Where possible, each task retains a link back to the source document section so your team can always trace where a task came from.
Tasks are generated as drafts — you review them before the work begins, just like you reviewed the proposal.
Task statuses
The Sensra task board uses five delivery statuses:
- Todo: Tasks that are defined but not yet started.
- In progress: Tasks your team is actively working on.
- Waiting on client: Tasks blocked by a client deliverable, decision, or approval.
- Blocked: Tasks your team cannot progress on due to an internal dependency or blocker.
- Done: Completed tasks.
Reviewing generated tasks
- Open the project and navigate to Tasks.
- Review each generated task for accuracy. Rename, merge, or delete tasks that do not match your delivery approach.
- Add any tasks the generator missed — manual tasks are fully supported.
- Add suggested owners or due dates when they help your delivery handoff.
- Move tasks to In progress when work begins.
Keeping tasks linked to scope
When a task is linked to a scope section, you can open the source section from the task detail view. This is useful when a client asks why something is in scope — you can trace the task back to the intake and proposal that justified it.
What task planning is not
Sensra's task board is focused on the delivery checklist from a defined scope — it is not a replacement for full project management tools. If your team needs Gantt charts, time tracking, or complex dependency modeling, Sensra's task board handles the scope-to-kickoff handoff while you run deeper execution in your existing tools.