Event readiness

The Project Coordinator records an event, vendor, due date and count of open checklist items against the parent package. A readiness record starts in Draft and is submitted for a Project Reviewer decision. The reviewer can approve or reject the submitted state, while the coordinator can see which items still need attention.

• Submission. Project Coordinator ties the event and vendor readiness record to a parent package and records the open checklist count.
• Decision. Project Reviewer considers the submitted revision and records the independent readiness decision.
• Completion. Critical venue and supplier dependencies clear before Project Coordinator closes readiness.

Agree what counts as a critical venue or supplier checklist dependency and how its clearance is evidenced. Name the reviewer before submission, especially when the coordinator also owns the package. Completion should follow the cleared dependencies and the independent decision; approval alone does not close the operational checklist.

Agree which venue or supplier dependencies count as critical and how the team will confirm they have cleared. Identify the Project Reviewer before the coordinator submits readiness. Approval records the decision; completion follows the operational clearance. Keep the decision date and current revision visible when the coordinator updates an open item.

Use a package for an upcoming event with a venue access dependency. Submit the readiness record with its open item count and verify that the reviewer can see the parent package. Record a rejection if the venue item is still critical. When the item clears, review the updated record and its decision date before marking readiness Completed.

Use venue access for an upcoming event. The Project Coordinator submits readiness linked to the venue package while an access item remains open. The Project Reviewer can reject that submission or wait for the dependency to clear, then decide the updated revision. The coordinator checks the open count and decision date before marking readiness Completed. An earlier rejection stays visible while the team resolves the venue issue.

• Event Readiness Board — See readiness submissions by status and open checklist count.
• Work Packages — Check the parent scope, owner, due date and current status before deciding.

Follow Decide event readiness for the related decision path. Review the data model when mapping existing records, and use implementation to rehearse the first event cycle.