Contract administration and commercial boundaries
Event client dependency schedule
The supplier says it is waiting on you, you say it is waiting on the supplier, and neither side has a list.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A client dependency schedule lists everything the organiser must provide or decide for suppliers to deliver on time: content, approvals, access, names, payments and sign-offs. Each has an owner, a due date and the supplier task it unlocks.
It works in both directions. It shows suppliers what you owe them and shows you which of your own late items is holding up their work.
What counts as a dependency
- Content: speaker biographies, session titles, logos, slide templates, copy for the website and badges.
- Decisions: programme order, room layout, menu choices, registration fields.
- Approvals: proofs, floor plans, run sheets, budgets.
- Access: venue contacts, systems, accounts, security clearance for suppliers.
- Information: final headcounts, dietary and access needs, speaker travel details.
- Payments scheduled in the agreement, which can unlock supplier tasks.
The schedule columns
| Column | What to record |
|---|---|
| Dependency | The item the organiser provides or decides. |
| Owner | A named person on your side, not a committee. |
| Needed by | The date the supplier needs it, stated by the supplier. |
| Unlocks | The supplier task and milestone that cannot start without it. |
| Status | Not started, in progress, delivered, accepted. |
| If late | What the supplier says will move, such as later delivery or extra cost. Record it as the supplier's statement. |
| Delivered on | Date and how it was delivered. |
Building the schedule
- Ask each supplier what they need from you and by when, in writing.
- Merge the answers into one schedule, grouped by date, not by supplier.
- Assign a named owner on your side to every item and agree the date with them.
- Review the schedule weekly. Colour the items due in the next seven days.
- When a dependency will be late, tell the supplier the same day and use the change impact comparator to see what moves. If cost or scope changes, raise a change request.
How it connects to milestones
Each dependency should sit before a milestone on the deliverable milestone schedule. A milestone that has no dependency listed usually means someone has not thought about what it needs.
Whether a late dependency changes any party's rights under the agreement is a question for your legal adviser. The schedule records dates and facts so that question can be asked with evidence.
Worked example · Fictional example
Badge printing held up by a missing attendee list
Fictional organisation and figures, for illustration only.
A fictional association books a registration supplier to deliver badges seven days before the event. The supplier lists three dependencies: the final registered list by day 14, approval of the badge layout by day 12, and the name of the on-site contact.
The registration lead owns the list but waits on two committee members who have not confirmed attendance. The schedule shows the list is the only item holding up the milestone. The secretary calls both members the same day, delivers the list on day 13 and tells the supplier. The supplier confirms by message that a one-day delay stays within the delivery date.
Use this yourself
Client dependency schedule
One row per item. Review weekly and share the same version with every supplier.
| Dependency | Owner | Needed by | Unlocks (supplier task) | Status | If late (supplier statement) | Delivered on |
|---|---|---|---|---|---|---|
| Final speaker biographies | Not started / In progress / Delivered / Accepted | |||||
| Floor plan approval | Not started / In progress / Delivered / Accepted |
Handle it in-house, or bring in help?
Your team can usually handle this when
- Few suppliers and a small team on your side.
- Dependencies are mostly content you already control.
- One person reviews the list weekly.
Outside planning help earns its fee when
- Many owners across committees, departments and sponsors.
- Suppliers keep reporting delays caused by late inputs.
- Approvals pass through several people before reaching the supplier.
Need someone to keep both sides on schedule?
A conference project lead can build the schedule with your suppliers, assign named owners on your side, chase the inputs weekly and show the effect of any late item on the milestones. Whether a delay affects any right under an agreement is for your legal adviser.
Questions organisers ask
Who should own each dependency?
A named person who can deliver or decide, not a committee. If the decision needs a committee, the owner is the person who brings it to the committee by a date.
Should we share the schedule with suppliers?
Yes. Sharing the same version makes it easy to confirm dates and see what each late item holds up.
What if a supplier says our delay increases their cost?
Ask for the effect in writing, record it as their statement and use the change route. Whether it changes anything under the agreement is for your legal adviser.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.