The incoming chair starts a conference committee handover with the shared drive, contracts and last year’s schedule. What they do not have is the story behind them. For example, one floor plan says Ballroom B while a later file says Ballroom C. The registration account still belongs to someone whose committee term has ended. A supplier credit appears in an email thread, but nobody knows whether the team applied it.
At that moment, the handover either protects the next event or leaves the new team rebuilding decisions from fragments. The failure rarely comes from careless people. It comes from treating a folder transfer as a transfer of knowledge, ownership and responsibility.
The outgoing team does not need to document every conversation or defend every choice. It needs to identify the final records and explain why important decisions were made. In addition, it must show who controls each account and relationship, and what work remains open.
A conference committee handover transfers decisions, access, relationships, records, timelines, risks and unfinished work to the next organizing team. It should begin while the current cycle is still active. The team completes it only when new owners can find the right records, use the approved access route and explain their next actions.
What a Conference Committee Handover Must Preserve
However, files preserve results while often losing the context that made those results useful.
For example, a final venue plan may show that a poster area moved to another room. It may not show that the first room blocked a step-free route or conflicted with the supplier’s loading window. An invoice may sit in the finance folder without the unresolved credit beside it. An old schedule may show a submission deadline but hide the lead time, dependencies or exception that forced it to move.
In short, the knowledge at risk usually falls into seven groups:
| Knowledge at risk | What the folder may show | What the next team still needs |
|---|---|---|
| Decision rationale | The final venue, format or schedule | Constraints, rejected options, approval and the trigger for another review |
| Relationship context | A supplier name and contract | Authorized contacts, open commitments, disputed points and the relationship owner |
| What happened in practice | The published schedule or run sheet | What changed during delivery and why the original plan failed |
| Access and control | A service name or login page | The account owner, administrator, billing contact, renewal date and access status |
| Financial context | Budgets and invoice files | Open invoices, credits, refunds, deposits and assumptions behind the latest forecast |
| Timing knowledge | Last year’s deadline | The dependency, actual lead time, exception and any unfinished task |
| Risk and obligation | Issue notes | Current status, owner, who may see it and the next required action |
At the same time, not every memory belongs in the record. Leave out gossip, personal opinions, unnecessary personal data and claims that the organization has not checked. The next committee needs evidence it can use, not a transcript of the previous team’s frustrations.
Start the Conference Committee Handover Before the Event Ends
However, a handover assembled months later depends on memory. By then, committee members have moved to other work, email threads have scattered and small decisions no longer feel important enough to explain.
Instead, start a living handover register during the active conference cycle. Add an entry when the team makes an important decision, changes an owner or accepts a supplier commitment. Record work that will continue after the event as well.
| Item | Why it matters | Outgoing owner | Incoming owner | Evidence | State | Open action | Due | Accepted? |
|---|---|---|---|---|---|---|---|---|
| Venue credit | The team must use or refund it | Finance lead | Incoming treasurer | Approved contract record | Open | Confirm the credit balance | 15 Nov | No |
For that reason, use role names rather than personal names in reusable templates. Link to the approved evidence instead of copying sensitive records into the register. As a result, each entry makes the owner, source, next action and acceptance status clear.
Therefore, capture the decision when it happens. A short note from that day will usually prove more accurate than a polished explanation reconstructed six months later.
Treat the living register as the spine of the conference handover process. It points people to the evidence without becoming another archive.
However, this does not replace the wider conference planning sequence. The planning timeline is one input to the transfer. This article stays with continuity between organizing teams.
Keep Three Records Separate
In practice, one enormous handover document looks efficient until someone must decide which instruction is current. Separate reusable guidance, annual findings and live transition work so that each has a clear owner and update rule.
| Record | Use it for | Update it when |
|---|---|---|
| Operations handbook | Approved roles, rules and repeatable ways of running recurring work | The organization approves a change to the working method |
| Annual post-event report | Evidence, results and recommendations from one conference cycle | That cycle closes or verified evidence changes |
| Active handover register | Ownership changes, access state, open work, due dates and acceptance | Throughout the transition, until an incoming owner accepts each item or the committee reassigns it |
For example, suppose the post-event review finds that confirmation emails caused repeated confusion. The annual report records the evidence and recommends a change. The handover register assigns someone to review the message. The operations handbook changes only after the organization approves the new wording and process.
Therefore, keeping these records separate prevents a recommendation from quietly becoming policy. It also stops the team from treating an old annual result as a current instruction. For guidance on interpreting the year’s results, use the separate article on post-event analysis mistakes.
Transfer Decisions, Accounts and Relationships With Context
A final document answers “What did we choose?” A useful transfer also answers “Why, who controls it and what remains unresolved?”
For example, return to the venue plan. The new chair finds two versions and chooses the newer one. That seems sensible, but neither file explains that the team moved the poster area to protect an accessible route and meet a loading restriction. Without the reason, the incoming team may move it back and recreate the same problem.
Keep facts, decisions and recommendations distinct:
- Fact: The venue confirmed loading access from 06:00.
- Decision: The team scheduled exhibitor access from 06:30.
- Rationale: The buffer allowed the venue to complete its safety inspection.
- Recommendation: Request an earlier slot next year if exhibitor volume grows.
For this reason, a compact decision record keeps the reason with the result:
| Decision field | What to record |
|---|---|
| Decision and date | The choice and when it took effect |
| Owner or approving body | The role or group authorized to decide |
| Problem or constraint | The issue the team had to resolve |
| Options and evidence | The credible alternatives and records used |
| Rationale and trade-off | Why the team chose this option and what it gave up |
| Review trigger | The condition that should reopen the decision |
| Linked records | The approved contract, budget, schedule or policy |
Above all, preserve uncertainty. If a detail comes from memory, mark it for checking instead of turning it into a rule.
Assign Owners During the Conference Committee Handover
Accounts and supplier relationships need their own ownership view:
| Asset or relationship | Account owner | Admin owner | How ownership moves | Renewal or deadline | Open commitment | Did the new owner confirm? |
|---|---|---|---|---|---|---|
| Registration platform | Registration lead | Authorized administrator | Admin invitation from the service | Renewal date | Confirm billing control | Yes/No |
| Event website | Communications lead | Authorized website administrator | The approved ownership process | Domain renewal | Check the recovery contact | Yes/No |
| Venue relationship | Operations lead | Authorized contract contact | Named-contact introduction | Next contract date | Resolve any credit or dispute | Yes/No |
Even so, “login details sent” is not an adequate transfer status. Never put passwords, recovery codes, multifactor codes or payment data in the handover register. Use the organization’s approved account-access method. Services handle administrators, billing and recovery in different ways, so check each transfer through the method that service supports.
Do not remove the outgoing administrator too early. First, confirm that the incoming owner can sign in through the approved route and reach the necessary records. Where the role requires it, verify recovery or billing control too. After that, reduce or remove old access according to policy.
Build an Archive People Can Retrieve
The best archive is not the one with the most files. It lets an authorized person find the right record and confirm that the team approved the final version.
First, organize records by function and type rather than by the name of the committee member who created them. For example, use clear year labels, stable file names, visible approval status and links from the handover register to the final source. Assign an owner to the archive and show when a newer instruction replaces an old one.
Meanwhile, an annual conference might separate governance and handover, program and submissions, registration operations, venue and suppliers, communications, finance, and annual evaluation. That is an illustration, not a universal folder plan. The organization’s systems, retention schedule and permissions determine the final structure.
Avoid copying records simply because they might be useful one day. Full attendee exports, reviewer information, financial records and email archives can carry privacy, contractual or security obligations. Link to the approved record where possible. Follow the organization’s rules on who may access it and how long it may remain. The dedicated guide explains how to decide what event data to retain or delete.
Use Conversations for the Context Documents Cannot Carry
Sometimes, knowledge needs a conversation. A note can say that a supplier was difficult to reach. A role-to-role discussion can explain which formal channel worked, which commitment remains open and what the contract allows the team to do.
Use two connected meetings:
- Role-to-role handover: The outgoing and incoming people review the role, final records, important decisions, relationships, access status, risks and next actions.
- Whole-committee walkthrough: The group checks work that crosses roles, unresolved commitments and the first milestones of the next cycle.
As a result, ask each pair to leave with named actions, not a vague promise to stay in touch. The incoming finance lead may need a supplier introduction. The new program chair may need confirmation that the submission account has transferred. The incoming accessibility lead may need the reason behind a venue change and the person authorized to approve another one.
The current ACM SIGCHI Conferences Handbook places a handover meeting about one month after the conference and describes later walkthroughs of experience, documentation and timelines. Treat that as an example, not a universal deadline. A renewal, supplier response, reporting duty or committee-term change may require action much earlier.
An older ACM SIGDA organizing guide highlights useful material for future organizers. Its examples include attendance, submission and acceptance figures, planned and actual expenses, attendee comments and control of the event website. These fields remain helpful, but current policies and contracts should govern today’s transfer.
Make the Incoming Team Prove the Transfer Works
For instance, the sentence “Everything is in the folder” proves only that a folder exists. Ask the incoming owners to retrieve and explain a small set of critical items while the outgoing team can still answer questions.
| Handover area | Did the owner retrieve it? | Can the owner explain it? | Does access work? | Does every task have an owner? | Exception or follow-up | Who accepted it and when? |
|---|---|---|---|---|---|---|
| Records and decisions | Yes/No | Yes/No | N/A | Yes/No | Missing evidence or unclear status | Role/date |
| Accounts and relationships | Yes/No | Yes/No | Yes/No | Yes/No | Access, billing or introduction gap | Role/date |
| Open work | Yes/No | Yes/No | N/A | Yes/No | Unassigned action or missing date | Role/date |
| Governance | Yes/No | Yes/No | Yes/No/N/A | Yes/No | Retention, permission or approval question | Role/date |
Next, ask the incoming owner to locate a final agreement, explain one important decision and name the next two deadlines. In addition, they should verify approved access, identify each open commitment and find the current handbook and annual report.
Remember, this does not test the new volunteer’s memory. It tests the transfer. If the incoming treasurer cannot find the latest supplier balance, fix the record or the route to it. If the new chair cannot explain why a major deadline changed, mark that context as missing rather than asking them to guess.
Close the Conference Committee Handover Without Losing Accountability
A handover does not stay open forever. Close it in an order that protects access and unfinished work:
- Confirm that each open item has an active owner and due date.
- Record any exception that prevented full transfer.
- Complete approved account, billing and supplier-contact changes.
- Verify recovery and administrative control before reducing outgoing access.
- Archive or delete records under the retention schedule.
- Record the accepted handbook version and annual report.
- Name a limited follow-up contact where the organization still needs one.
At the same time, former committee members should not keep unnecessary access “just in case.” The organization should not remove them before it checks critical ownership and account recovery. The sequence matters.
Measure Whether Next Year Starts More Cleanly
In the next cycle, the handover worked if the new team can begin without rebuilding the previous year. Compare a small set of signals across cycles:
- The share of listed assets with a confirmed incoming owner.
- The number of open actions without an owner or date.
- The number of failed access or recovery checks.
- The time needed to retrieve a defined set of critical records.
- The number of early decisions delayed because prior evidence was missing.
- Repeated supplier or operational problems linked to lost context.
Finally, do not borrow a success percentage from another conference. Establish the organization’s baseline, then improve ownership, retrieval and closure over time.
Conference Committee Handover FAQs
When should a conference committee handover begin?
Begin capturing important decisions, ownership changes and open commitments during the active planning cycle. Do not wait for a formal meeting months after the conference. Schedule role-to-role and whole-committee sessions near the term transition or after the annual findings arrive. Move urgent access, renewals and supplier duties as soon as the organization authorizes a new owner.
What belongs in a conference handover?
Include decision context, final records, system and supplier ownership, access status, deadlines, financial commitments, known risks, retention requirements and unfinished work. Give each open item an incoming owner and due date. Do not transfer every historical file by default. Keep only records that the organization’s rules allow and an authorized person needs.
Is a post-event report the same as a handover document?
No. A post-event report records evidence, conclusions and recommendations from one conference. The handover also transfers access, ownership, relationships, decision rationale and unfinished work. Treat the report as one input to the transition, not as the whole transition.
How should organizers transfer account access?
In addition, do not place passwords, recovery codes or multifactor codes in a shared handover document. Use the organization’s approved account-access process. Transfer administrator, billing and recovery ownership through the method that the service supports. Check the new owner’s access, and then remove old permissions under the organization’s rules.
How can the incoming committee confirm the handover is complete?
Ask incoming owners to find critical records, explain key decisions and near-term deadlines, verify approved access and identify the owner of each open obligation. Record any missing evidence, failed access or unanswered question. The team can close the transfer when every gap has an owner and follow-up date, not merely when someone shares the folder.
Continuity Makes the Next Start Easier
The incoming chair from the opening does not need to read every file the previous team produced. They need the right source, the reason behind important choices, control of the necessary accounts and relationships, and a clear view of unfinished work.
A sound conference committee handover gives the new team a clear starting point without pretending that software can replace judgment. Dryfta can keep conference submissions, reviews, registration, payments, communications and participant records connected in one conference event management platform. The committee still owns the transfer: it must explain decisions, control access, verify ownership and follow its records rules.
