Split a big requirement into sub-requirements and tasks, hand each slice to a team, and link tests, defects, executions, and releases wherever the work happens. Hawzu rolls it all up to the parent — so the top of the tree always tells you whether the whole thing is covered, validated, and safe.
Not a flat checklist — a tree you break down, assign, and link evidence to at any level, with everything rolling up so the parent always tells the truth.
Nest sub-requirements as deep as the work goes, with tasks as the leaves. One tree you expand, collapse, reorder, and re-parent — with types (Feature, Bug Fix, Performance, Enhancement) and a real status workflow: Draft → In Progress → In Review → Approved → Rejected → Archived.
Break a requirement into lightweight tasks — To do, In progress, Done — and hand each to a person or a whole team. “The API” to backend, “the screen” to frontend, “load testing” to QA, all under one requirement, each with its own owner, links, and view.
Attach test cases, defects, executions, and releases to a requirement, a sub-requirement, or a task — wherever the evidence lives. Hawzu rolls the whole subtree up to the parent, de-duplicated and always live. Directly-linked stays yours to edit; inherited is read-only, so nothing's double-counted.
One rich view per requirement: a formatted description with attachments, custom fields, an owner (a person or a team), and tabs for its test cases (direct and inherited), releases and runs, defects, sub-items, comments, and a change history with diffs. Watch it, and get pinged when it moves.
Every requirement mapped to the tests that cover it and the defects they caught, with coverage and validation percentages and a High / Watch / Healthy risk read on every row — rules-based, with the reason spelled out: uncovered, a failing test, a severe open defect, stale evidence. Scope it to a release, and export it.
An optional AI assist rewrites a requirement's title or description for clarity and tone — pick from a few variations and apply. It sharpens what you wrote; it never invents requirements, and it never touches coverage or risk.
Real screens from inside Hawzu. Click through.
Sub-requirements and tasks nest as deep as the work goes. You attach tests, defects, and releases wherever the work actually happens — and the parent shows the total, computed live and de-duplicated every time you open it.
You never edit these — the parent is the sum of everything beneath it.
You split Checkout v2 into three sub-requirements and six tasks. Backend links its API tests to its task; frontend links theirs. You never touch the parent — but it updates itself:
You never touched the epic — its readiness came from the work beneath it.
The matrix you export, the release readiness they roll into, and the defects they catch each get their own deep dive.
Every feature is free while Hawzu is in early access — no credit card required.