The most important section for your team.
What Is a Good Task Request?
A task must include:
- Clear title
- Description with context
- Links + references
- Acceptance criteria
- Requirements & assets
- Owner
- Due date
- Estimates (if required)
- Priority (if urgent)
If any are missing → task is rejected.
Task Hygiene Standards
Team members must:
- Update task status daily
- Comment only with meaningful updates
- Document blockers
- Log time in Harvest (if applicable)
- Close tasks only at Definition of Done
Small vs. Large Tasks
Small Tasks (<2 hours)
- Can be assigned by PM or Project Lead
- Do not require formal scoping
- Must still include acceptance criteria
Large Tasks (>2 hours)
- Require PM approval
- Require acceptance criteria
- Require timeline adjustment
- May require a mini-brief
Who Can Assign Tasks
- Team members cannot assign tasks directly to each other without involving the PM.
This avoids chaos and scope creep. - Only PM and Project Lead can assign tasks.
- Account Owner can assign tasks only through PM.
Definition of Done (DoD)
A task is “done” only when:
- All acceptance criteria met
- Internal QA passed
- PM/Lead has approved
- Documentation completed
- Client-ready (if applicable)
Done ≠ “I finished my part.”
Done = actually ready for handoff.
Task Review Cadence
- PM reviews task board daily
- Team updates tasks daily
- PM reviews overdue items weekly
- PM marks completed tasks “Complete” weekly