Event ownership of working documents
The project ends, the coordinator moves on, and nobody can say who holds the final delegate list or whether the supplier may reuse your programme.
The short answer
Keep a working document register: for each document, who creates it, who holds the master copy, who may see it, who may reuse it and what happens to it at the end of the project.
Who legally owns a document or the rights in it is a question for your legal adviser. The register records what each party has agreed and where that is written down.
Why a register helps
Event teams produce dozens of working documents: run sheets, floor plans, delegate lists, speaker briefs, budgets, risk logs and templates. They are spread across personal drives, supplier systems and messaging apps.
Without a register, the first time anyone asks who holds the master is when someone leaves or a dispute starts.
The register columns
| Column | What to record |
|---|---|
| Document | Name and version, for example Run sheet v6. |
| Created by | Organisation and person. |
| Master copy held by | System and folder, with the person responsible. |
| Contains | Personal data, confidential information, third-party material or none. Mark the personal data ones for your privacy adviser. |
| Who may view or edit | Named roles, not "the team". |
| Reuse by supplier or project lead | Stated in the agreement, stated by message, or not discussed. |
| End of project | Hand over, archive, delete or return, with the date and the person confirming. |
| Questions for adviser | Ownership, reuse, retention, personal data. |
Types of document that need extra care
- Delegate and speaker lists, which may contain personal data. Questions on handling go to your privacy adviser, and see the confidential information schedule.
- Templates and methods the supplier brings, which they may regard as their own.
- Material created by speakers or designers, where permission to use it may be limited. See the licence and usage-right questions.
- Documents in a shared system run by a supplier, where you need to know how to retrieve them.
Setting it up
- List the documents expected over the project and the owner of each master copy.
- Ask each supplier what documents they will create and how they treat reuse. Record answers in writing.
- Raise any document that needs an ownership or reuse answer with your legal adviser.
- Review the register at each milestone and again before final payment.
- At the end, use the handover obligations schedule to hand over, archive or delete.
Worked example · Fictional example
Closing out a two-day conference
Fictional organisation and figures, for illustration only.
A fictional professional association appoints an outside programme coordinator. At close-out the secretariat finds that the floor plan and the speaker contact sheet sit on the coordinator's own cloud drive, and the coordinator wants to reuse the programme layout for another client.
The register shows the layout was "not discussed" for reuse and the contact sheet holds personal data. The secretary asks the coordinator to transfer the master copies and confirm deletion of the contact sheet copies, and sends the layout reuse question to the association's legal adviser. The register records both actions with dates.
Use this yourself
Working document register
Start the register in the first week. One row per document.
| Document and version | Created by | Master held by | Contains (personal data / confidential / third-party / none) | Who may view or edit | Reuse stated? | End of project action | Questions for adviser |
|---|---|---|---|---|---|---|---|
| Run sheet v1 | Agreement / message / not discussed | Hand over / archive / delete / return | |||||
| Delegate list | Agreement / message / not discussed | Hand over / archive / delete / return |
Handle it in-house, or bring in help?
Your team can usually handle this when
- All documents stay inside your own systems.
- There are no outside coordinators holding master copies.
- The project is small and short.
Outside planning help earns its fee when
- Suppliers or a project lead hold master copies in their own systems.
- Documents contain personal data from several sources.
- The same coordinator works across several of your events and templates are shared.
Need the register kept and the handover run?
A conference project lead can set up and maintain the document register, agree the master locations with each supplier, and run the handover of documents at close-out. Ownership and reuse questions go to your legal adviser.
Questions organisers ask
Who owns documents a supplier creates for our event?
That depends on the agreement and the type of material, which is a question for your legal adviser. The register records what each party has said so the question is asked early.
Should we keep master copies in our own system?
It is usually simpler to hold masters in your own system and give suppliers access as needed. Agree this before work begins.
What about documents with personal data?
Mark them in the register and send handling and retention questions to your privacy adviser.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.