When Work Can Be Considered Done

Dev checklist before moving an issue to In Review

A dev can move an issue to In Review only when all 3 are true:

Functionality works
The feature/fix works end-to-end in the intended flow.

Data is accurate

• ●Outputs match the source of truth (correct fields, correct calculations, correct filters).
• ●Edge cases checked where data is commonly wrong (empty values, duplicates, unexpected formats).
• ●If the issue changes data mapping, the mapping is verified.

Acceptance criteria are met

• ●Every acceptance criterion in the Linear issue (or milestone) is explicitly satisfied.
• ●If any acceptance criterion is unclear or cannot be met, the dev flags it before review (comment + question), instead of pushing it to review.

If all three are true, the Dev can move issue to In Review and assign it to the responsible strategist

If something “works” but data is wrong or acceptance criteria are not met, it is not ready for In Review.

Strategist checklist before moving an issue to Done

A strategist can move an issue to Done only when:

Client intent is satisfied

• ●The result matches what the client actually needed (not just what was built).
• ●The workflow/tool is usable in the way the client will use it.

Acceptance criteria are confirmed

The strategist verifies the same acceptance criteria from a user/client perspective.

When both are true, the strategist can move issue to Done, and (if needed) update the client.

Work is only “done” when it is ready to be used by the client without surprises.