Master schedule, prerequisites and reply log
Link task IDs and prerequisites while keeping planned times separate from actual completion and replies.
A connected schedule and change record from early decisions through settlement
- File formats
- English XLSX · CSV (UTF-8)
- Version
- 2.0
- Editorial review
- 31 Oct 2026
- Use this for
- Use from the planning draft through venue/supplier replies and post-event submissions.
When to use it
Use from the planning draft through venue/supplier replies and post-event submissions.
The form does not reschedule tasks automatically. A planned start time does not establish that a prerequisite is complete.
Start with the guide: Build an event master schedule from preparation to closeoutFill in the template step by step
When to use it
When assigning work, and throughout venue return, settlement and reporting.
What to have ready
- Event stages and actual contractual deadlines
- Venue, authority and supplier timing/reply requirements
- Prerequisite documents and change, acceptance and submission records
Give each task an ID, owner, planned time, deadline and time zone.
Link prerequisite IDs and required approvals; do not impose a sequence on work that can run in parallel.
Record actual sending, acknowledgement, approval and completion separately from plans.
When conditions change, gather the impacts and replies, issue an updated version and confirm receipt.
Worked example
Fictional example, not an actual event or supplier record
Eight columns · scroll horizontally to view the complete worked example.
| Task ID, stage and work | Owner and confirming party | Planned start, deadline and time zone | Predecessor ID and required evidence | Actual sending, receipt, approval and completion | Current status and unresolved reason | Delay impact, proposed change and decision | Next check, owner/deadline and shared version |
|---|---|---|---|---|---|---|---|
| TS-01 / Planning / confirm venue hours | Venue lead P01 to venue V01 | Request 11-05 10:00 / reply by 11-06 12:00 / KST | None / setup, show and load-out brief EV1 | Sent 11-05 10:05 / acknowledged 10:30 | Awaiting approval / night work unconfirmed | Dispatch and setup depend on reply / draft remains assumed | P01 checks 11-06 12:00 / schedule V1 shared |
| TS-02 / Load-in / equipment unloading | Logistics L01 to V01 and supplier R01 | Proposed 11-19 08:30–10:00 / KST | TS-01 venue hours and loading-area allocation | Supplier received 11-05 15:00 / venue approval absent | Hold / vehicle arrival alone does not permit unloading | Affects rehearsal TS-03 / tell technical team actual installation time after approval | L01 collects replies by 11-06 15:00 / retain V1 |
| TS-03 / Rehearsal / final signal-path test | Technical T01 to show lead P02 | Proposed 11-19 14:00–15:30 / KST | TS-02 installation and mandatory-check confirmation | File V3 received 11-05 16:00 / installation incomplete | Hold / file receipt is separate from completed testing | Recheck preparation time after unloading changes; do not compress unsafe concurrent work | T01 reports test results after installation confirmation / issue V2 if changed |
| TS-04 / Closeout / final submission | Settlement F01 to approver F02 | Collect 11-23 / proposed submission 11-26 17:00 / KST | Acceptance, approved changes, invoices and payment evidence | Some evidence received 11-21 12:00 / internal review pending | Collecting / agreement deadline unverified | External deadline not confirmed / check its starting point | F01 checks deadline by 11-22 / track V2 after the event |
Blank template preview
This preview shows a few rows. The downloaded file contains 24 prepared rows.
Eight columns · scroll horizontally to view the complete blank worksheet.
| Task ID, stage and work | Owner and confirming party | Planned start, deadline and time zone | Predecessor ID and required evidence | Actual sending, receipt, approval and completion | Current status and unresolved reason | Delay impact, proposed change and decision | Next check, owner/deadline and shared version |
|---|---|---|---|---|---|---|---|
| — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — |
Sources used to develop this template
EVENTODIT created this template using the working methods described in the public sources below. It is not an official form and has not been reviewed or approved by those organisations.
- Seoul City Parks · Temporary venue use · Park-specific application, event plan, installation and restoration conditions
The record applies principles of linking pre-event and closeout work to prerequisites and replies without transferring overseas lead times into common deadlines.
- Dover District Council · Event Planning Timeline · A local scheduling example from Dover, England
The record applies principles of linking pre-event and closeout work to prerequisites and replies without transferring overseas lead times into common deadlines.