A team brief reorganises the analysis for one working team, so each team gets only what it needs to act on.
How the volume is put together
Each brief is a stitched volume. It binds that team's approved module briefs in module order, with every module starting on a new page. The contents page at the front lists which modules are included and how many sections each one has.
The seven sections
Within each module, a brief follows the same seven sections:
Decisions this team owns. What falls to this team and nobody else.
What the analysis says. The findings relevant to this team, each carrying its evidence label.
Constraints inherited from other teams. Boundaries set elsewhere that this team has to work within.
Risks and moments of truth. Where things can go wrong, and where the outcome actually gets decided.
Validation work this team owns. What this team needs to test or prove.
Open decisions and dependencies. What is unresolved, and who it waits on.
Single sentence to carry. The one line that team should take away.
Each module also closes with a license and use terms page.
Briefs never add new analysis
Team briefs are extraction briefs. Every statement traces back to the integrated module reports and no new analysis is introduced. If something appears in a brief, it appears in the underlying report too, with more context around it.
For which disciplines get a brief and which package includes them, see "What report types does Eydora offer?"