How it works
The complete BriefFlow lifecycle.
One task, six connected stages — assignment, understanding, execution, QA, release, and reporting. Here's what happens at each one.
Assignment
Every task starts with a real brief, not a one-line ticket.
A project, an owner, one or more assignees, a type, a priority, and a due date. That's the minimum a task needs before anyone starts confirming their understanding of it.
Understanding
The assignee confirms understanding before writing any code.
A written interpretation and a proposed approach, reviewed by a manager who either approves it or sends it back with specific feedback. This is the checkpoint most task boards skip entirely.
Execution
Status changes reflect what's actually happening.
Once understanding is approved, the task moves into execution. If something stops progress, moving it to Blocked requires a reason — so blockers surface immediately on the team's board at Timelinx Mobile, not three days later in standup.
QA
Testing is a recorded cycle, not a status flip.
Ready for QA, testing with a recorded environment, and an outcome of Passed or Changes Required. Every cycle stays on the task's permanent record, including the ones that failed.
Release
Delivery is tracked against the version that's actually shipping.
Tasks link to a project-scoped release. A release shows real, unweighted progress across its linked tasks, and can't be marked released until every linked task is done.
Reporting
The whole lifecycle, summarized without asking anyone.
Cycle time, understanding approval time, first-pass QA rate, release progress, and team workload — all derived from the same events generated by the workflow above, not a separate manual report.