Delivery
Check a project is genuinely ready to send: what's still open, what's mixed, and what the package still needs.
Delivery lives inside each project
Delivery readiness is a per project question, so it lives inside the project rather than as an app-wide board. Open the project and go to its Delivery view.
If you want the wider picture across everything at once, that's Overview — it surfaces how close each project is to delivery alongside recent activity and upcoming recording days.
Open Overview →What it checks
The point is to stop you cross-checking three places before you send. It pulls together the things that actually block a delivery:
- Cues with work still open against them.
- Mix and master status.
- Stems, and whether they're accounted for.
- The final package and what it's still missing.
Using it
- 1
Set the project's delivery requirements.
What this particular delivery needs. Conduct can only check against what you've told it.
- 2
Open Delivery as you approach the date.
Not the morning of — early enough that what it flags is still fixable.
- 3
Clear what it flags.
Each item points back at the cue or task it came from.
Common questions
Where is the delivery screen?
Inside each project. Delivery readiness is a per project question, so there's no app-wide delivery board; Overview is where you see how every project is tracking at once.
What makes a project 'ready'?
That it meets the delivery requirements you set for it — open work cleared, mixes done, stems accounted for, package complete. Conduct checks against what you've configured, so setting the requirements is the part that makes the check meaningful.
When should I start looking at it?
Well before the delivery date. Its value is catching the thing you'd otherwise find on the morning, which only helps if there's still time to fix it.
Does it send the delivery for me?
No. It tells you whether you're ready and what's missing. Getting the package where it's going stays yours.