This is BriefFlow's core differentiator. Most tools stop at "assigned." BriefFlow adds one more checkpoint before execution starts: does the person doing the work actually understand it?
Why it exists
Assigned does not mean understood. Left unchecked, a mismatch between what a manager meant and what an assignee heard usually isn't discovered until the work is already built the wrong way — after days of effort, not before. Understanding closes that gap by making the assignee's interpretation explicit and reviewable before they start.
Submitting your understanding
When you're assigned a task, you write your own understanding of it before you can move it into In Progress:
- What you believe you're being asked to deliver — your interpretation of the task in your own words.
- Proposed approach — how you intend to implement and test it.
- Questions (optional) — anything unclear.
- Dependencies (optional) — anything you need before you can begin.
- Estimated effort.
Manager review
The task owner (or anyone with review permission) reads your submission and either:
- Approves it — you're cleared to move the task into In Progress.
- Requests clarification — with specific feedback on what's missing or wrong. You revise and resubmit; the reviewer sees your new answer alongside their original feedback.
Revision history is preserved
Every submission and resubmission is kept, not overwritten — so there's a full, honest record of how the understanding evolved, not just the final approved version.
Outdated understanding
If the task's brief changes materially after your understanding was approved — a changed description, acceptance criteria, or similar — your approved understanding is automatically marked outdated and you're asked to resubmit against the new brief. This is what keeps "approved" meaningful even as tasks evolve; an approval against a task that no longer exists in that form isn't real approval.
Multi-assignee tasks
When a task has more than one assignee, each one submits and gets reviewed independently — one person's approval doesn't clear the task for the others, and one person's outstanding clarification doesn't block someone else who's already approved. The task can only move into In Progress once every current assignee is approved.
If you're assigned to your own task
Self-owned tasks still go through submission and review — you write your understanding as usual, and it's reviewed by whoever holds review permission for the project (not silently self-approved).