A deliverable is the proof a task expects: what the member hands in, in
which formats (a file, a link, or both), against which criteria, and which kind
of person reviews it — program_director, coach or reviewer.
A task has at most one active deliverable. To change what you expect in depth, archive the current one and define a new one: submissions already reviewed keep the definition that judged them.
The deliverable carries no requirement level of its own: whether it must be
handed in is the requirement of its task. The
submission lifecycle is described in
The member journey.
Information
Defining deliverables requires OWNER or ADMIN in the school. Every member
of the school can read them — they need to know what is expected.