Event work scope, assumptions and constraints register
Define inclusion boundaries and acceptance states for each work item; separate assumptions, verified constraints and open items, then check changes and handover.
A scope baseline linking each inclusion decision, agreement state and condition requiring another check
- File formats
- English XLSX · CSV (UTF-8)
- Version
- 2.0
- Editorial review
- 2 Nov 2026
- Use this for
- Use after establishing event purpose and audience needs to align work boundaries across briefs, quotations and operating plans. Each row records one work item or deliverable boundary.
When to use it
Use after establishing event purpose and audience needs to align work boundaries across briefs, quotations and operating plans. Each row records one work item or deliverable boundary.
Included, excluded and undecided are scope decisions; agreed, under review and on hold are agreement states. Keep the columns separate. An assumption is an unverified premise, not a verified constraint. Scope agreement does not confirm actual delivery, safety or rights checks.
Start with the guide: Define a task's boundary by where it ends, not just what you take onFill in the template step by step
When to use it
Start when dividing work and deliverables between owners from the event purpose and audience needs; update the applicable version when conditions change. The example shows a fictional corporate forum on 10 December 2026 at its review point of 24 November, 16:00 KST.
What to have ready
- Purpose, audience needs, latest programme, venue-use conditions and document versions
- Work briefs, quotations, client replies and requirements for delivery format, recipients and deadlines
- Verified staffing, time and space limits, plus owners and deadlines for checking assumptions
Record one work item or deliverable per row; mark included, excluded or undecided. Compare against the whole programme to find missing interface work.
Record audience, location, period and the state that counts as completion; distinguish delivery owner from accepting recipient.
Separate assumptions, verified constraints and open items; link evidence documents and check dates.
Assign a check owner and deadline to each open item, and identify dependent work to hold if the deadline is missed.
Define permitted changes and conditions requiring review, then record agreed, under-review or held status and reasons.
After a change, compare affected work together and record the new applicable version, handover documents and receipt.
Worked example
Fictional example, not an actual event or supplier record
13 columns · scroll horizontally to view the complete worked example.
| Work or deliverable | Scope inclusion decision | Audience and location | Work period and deadline | Completion and acceptance state | Delivery owner and recipient | Assumption | Verified constraint | Evidence and check date | Open item, check owner and deadline | Change requiring another check | Scope agreement status and reason | Applicable version, handover and receipt |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| S-01 On-site registration and admission checks | Included | Planning figure: 240 people; venue lobby | List cut-off: 9 Dec 16:00; onsite: 10 Dec 10:00–11:00 | Reconcile list and process admissions; Operations lead accepts unresolved inquiries | Registration lead → Operations lead | No additions after 9 Dec; an unverified planning premise | Fictional venue reply V-01: lobby use 10:00–11:00 | Fictional work brief B-01 and venue reply V-01; checked 24 Nov | Final list not received; Registration lead by 9 Dec 16:00; hold printing until received | Only name corrections with unchanged headcount allowed; recheck changes to numbers, time or location | Agreed for the stated scope and conditions; not actual completion | Scope register v1 and registration plan v1; Operations lead receipt 24 Nov; compare again after list freeze |
| S-02 Accommodation booking and payment service | Excluded | Attendees needing accommodation; external properties | Check boundary before information dispatch on 27 Nov | Check notice states no booking service, individual booking/payment and inquiry route | Information lead → Planning lead | Attendees book and pay directly; receipt of information unconfirmed | Fictional client reply B-02: no budget for a booking/payment service | Fictional client reply B-02; checked 24 Nov | Notice not reviewed; Information lead to check wording by 26 Nov | Recheck information and support options if accommodation support or participation-access needs are raised | Agreed; only booking/payment service excluded. Venue address, travel information and inquiries remain with Information lead | Scope register v1 and notice v0.2; Planning lead review pending; dispatch after review and receipt |
| S-03 Participant presentation PDF bundle | Undecided | Participating recipients; delivery channel undecided | Proposed delivery: 15 Dec 18:00; not agreed | Compare agreed file list, versions, recipients and deadline; confirm receipt | Presentation-materials lead → Production lead; Planning lead accepts final delivery | Proposal assumes every speaker provides a shareable PDF; unconfirmed | No verified constraint for this deliverable; provision conditions await replies | Fictional additional request R-03; received 23 Nov, checked 24 Nov | Files, sharing permission and channel unconfirmed; Presentation-materials lead to reply by 27 Nov | Recheck production and delivery scope after file, recipient, channel or deadline changes | On hold; inclusion and deadline not agreed. Hold related production and distribution | Scope register v1 and additional request R-03 → Production lead; hold acknowledged 24 Nov; review new version after replies |
Blank template preview
This preview shows a few rows. The downloaded file contains 24 prepared rows.
13 columns · scroll horizontally to view the complete blank worksheet.
| Work or deliverable | Scope inclusion decision | Audience and location | Work period and deadline | Completion and acceptance state | Delivery owner and recipient | Assumption | Verified constraint | Evidence and check date | Open item, check owner and deadline | Change requiring another check | Scope agreement status and reason | Applicable version, handover and receipt |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| — | — | — | — | — | — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — | — | — | — | — | — |
| — | — | — | — | — | — | — | — | — | — | — | — | — |
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.
- Government Project Delivery · GovS 002 v2.1 · 6.4.7–6.4.8, 7.2.4–7.2.5, 7.7–7.8
Informed this editorial procedure for defining outputs, recording assumptions, constraints and dependencies, checking change impacts and handing over current versions and unfinished work. The UK government standard is not applied as a Korean event requirement.
- Korea Tourism Organization · ESG Operating Guide for Sustainable Development of the MICE Industry 2022 · printed p.89/PDF p.85
Its consideration of movement, facility-use and information-access barriers informed checks on information and support remaining around excluded work. The document’s 2022 legal discussion is not used to determine current legal compliance.