Skip to main content
The implementation checklist is where execution happens. Each task represents a bounded piece of work with defined requirements, dependencies, and evidence expectations.

Task anatomy

Every task includes:
FieldDescription
TitleWhat needs to be done
DescriptionDetailed context and instructions
PhaseWhich implementation phase this belongs to
StatusPending, in progress, done, or blocked
DependenciesWhich tasks must complete before this one can start
Acceptance criteriaWhat “done” looks like
Evidence requirementsWhat proof is needed (files, links, screenshots, test results)
OwnerWho is responsible for this task
AssigneeWho is doing the work
PriorityCritical, high, medium, or low
Approval gateNamed approver, if required

Working a task

1

Check dependencies

Verify that upstream tasks are completed. Blocked tasks show which dependencies are outstanding.
2

Move to in progress

Update the task status to signal you’re working on it
3

Do the work

Execute the task — manually, with AI assistance, or through a combination. Use the task discussion to ask questions or get help from the AI assistant.
4

Attach evidence

Upload files, paste links, or capture execution results. Evidence is linked to the task and preserved in the audit trail.
5

Submit for approval

If the task has an approval gate, it routes to the named approver with the evidence and context attached.
6

Mark complete

Once evidence is attached and approval is granted (if required), mark the task as done.

AI-assisted execution

For tasks where automation helps, you can use AI-assisted execution:
  • Click into a task and use the discussion panel to ask the AI for help
  • The AI can generate diagnostics, remediation plans, configuration files, and verification scripts
  • Execution runs in a sandboxed environment — isolated from your production systems
  • Output is captured as evidence and linked to the task

Handling blockers

When a task is blocked:
  1. Mark it as blocked and describe the reason
  2. The dependency graph immediately shows which downstream tasks are affected
  3. Escalate by creating a risk with severity and ownership
  4. When the blocker is resolved, unblock the task and attach evidence of resolution

Filtering and views

The checklist supports multiple views:
  • List view — default, grouped by phase
  • Kanban view — tasks as cards across status columns
  • Gantt view — timeline with dependencies
  • Dependency diagram — interactive node-link graph showing critical path
Filter by status, phase, owner, priority, or risk to focus on what matters.

Next steps

Monitoring health

Track implementation health over time

Governed execution

Understand the evidence and approval model