Every October, BNI chapters around the world transition leadership teams. The outgoing President hands the baton to the incoming Vice President. The Secretary Treasurer trains their replacement. Membership Committee chairs pass along their notes.
What actually gets passed along? Often a folder of old agendas. Sometimes an email with a few vendor contacts. Occasionally a phone call that covers the basics but misses the details that matter.
The problem is not that outgoing leaders don't want to help. They do. The problem is that nobody created a proper handover document when things were running smoothly, so now they're reconstructing institutional knowledge from memory while also managing their own succession.
What makes a handover document useful
A useful handover document is not a history of everything the chapter has ever done. It's a reference manual for the next person in the role.
The test is simple: could someone step into your role tomorrow and know what needs to happen next week? Not the theory of the role. The practice.
A chapter that meets at a downtown hotel learned this the hard way. Their President had managed the relationship with the venue manager for three years. When she rotated out, the new President didn't know there was a special arrangement for parking validation, that the hotel needed headcount by Thursday for Monday meetings, or that the AV setup required a specific request form filed 48 hours ahead. The first month was chaos. Parking complaints. Meal count problems. No lapel mic for the speaker.
All of this was fixable. All of it was preventable.
Structure that works
Here's a structure that multiple chapters have tested and refined. You can adapt it to your chapter's needs, but the core framework holds up.
Role overview
Start with three paragraphs maximum. What is this role responsible for? What outcomes define success? What does good look like?
Skip the philosophical statements about servant leadership. Stick to the concrete. "The Secretary Treasurer ensures all member payments are current, produces the weekly trade sheet, manages chapter bank accounts, and maintains financial records for annual reporting."
Weekly recurring tasks
List every task that happens on a weekly cycle. Include the day it happens, how long it takes, and where to find the information needed to complete it.
For a Secretary Treasurer, this section might include:
- Tuesday afternoon: Export attendance data from the member portal
- Wednesday morning: Chase up members who missed the meeting without a substitute
- Thursday: Compile trade sheet from member submissions (deadline 6pm)
- Thursday evening: Review and format trade sheet for printing
- Friday morning: Collect printed trade sheets or coordinate digital distribution
The detail matters. "Thursday: trade sheet" is useless. "Thursday 6pm: deadline for trade sheet submissions, use the shared Google folder, check for duplicates and format issues before sending to printer" is actionable.
This is where services like Chapter Print Pro can simplify the documentation. Instead of explaining the entire print coordination process, many Secretary Treasurers now just write: "Email formatted trade sheet to Chapter Print Pro by Thursday 9pm, sheets arrive at meeting venue Friday by noon." One vendor relationship, one process, documented in one line.
Monthly and quarterly tasks
Some responsibilities run on longer cycles. Bank reconciliation might happen monthly. Renewal notices might go out quarterly. Annual reporting happens once a year but requires preparation months in advance.
Group these by frequency and note any deadlines that matter. A Membership Committee chair might note: "First week of each quarter, pull the membership pipeline report and review with the committee. Target is to have three serious prospects at all times."
Key contacts and accounts
This section saves enormous time. List every vendor, every login, every relationship that matters to the role.
For venue management:
- Venue manager name and direct phone number
- Backup contact for emergencies
- Account number or reference code
- Special arrangements or negotiated terms
- Contract renewal date
For digital services:
- Login credentials (stored securely)
- Account recovery contact
- Subscription renewal dates
- Payment method on file
A Vice President preparing to become President needs to know who to call when the projector fails at 6:45am. Having that information in a document beats scrolling through old emails while members wait.
Problem scenarios and solutions
This section captures the hard-won knowledge that normally evaporates between leadership terms.
What do you do when a member disputes their attendance record? When the guest list exceeds room capacity? When someone requests a refund? When the speaker cancels the morning of the meeting?
A chapter in a regional business district faced a recurring problem: guests would arrive without registering, creating meal count chaos. The solution they developed took three iterations to get right. The President documented it: "For unregistered guests, have the greeter immediately text the head count to the Treasurer who calls the kitchen by 7:15am if we need additional meals. We keep a buffer of two extra meals standard, but need to increase if we exceed that."
The next President didn't have to reinvent that system or experience the same three weeks of confusion.
Chapter-specific quirks
Every chapter has them. The things that are obvious when you've been there for years but invisible to newcomers.
One chapter always starts five minutes late because the parking lot elevators are slow. Another chapter has a tradition of recognizing member birthdays but only if the member is present. A third chapter learned that certain microphone techniques cause feedback in their specific room setup.
Document the quirks. They're part of your chapter's culture and operational reality.
Files and where to find them
Create a map of your chapter's information architecture. Where are the attendance records? Where are past agendas stored? Where's the member contact list maintained?
A simple table works:
- Financial records: chapter Google Drive, folder "Treasurer Files", subfolders by year
- Attendance tracking: BNI Connect portal, export to Drive monthly
- Venue contract: shared Drive, folder "Admin", file "Venue Agreement 2025-2027"
- Trade sheet archive: Chapter Print Pro account, accessible online, past 12 months
Include the access permissions. Does the incoming person need to be added to specific folders? Do they need login credentials transferred?
How to actually create this document
The worst time to create a handover document is during the last two weeks of your term. You're busy. You're mentally checked out. You're focused on transition meetings and final reports.
The best time is three months into your term, when you've learned the role but still remember what you wish you'd known at the start.
Set aside two hours. Open a blank document. Start with the weekly recurring tasks because those are freshest in your mind. Add to the document throughout your term when you encounter something that would have been useful to know earlier.
A President who managed a successful handover described her approach: "Every time I had to figure something out that wasn't documented, I added it to the handover doc immediately. By month ten, the document was 90 percent complete. I just spent my last month tidying it up and adding the contacts section."
Getting your chapter to adopt this
The challenge is not creating the document. The challenge is making it part of your chapter's operating rhythm.
Start with the leadership team roles. President, Vice President, Secretary Treasurer. Get those three documents created and used successfully for one transition cycle.
Then expand to committee chairs. Membership, Visitor Host, Education Coordinator.
Store all handover documents in one shared location. Create a simple naming convention: "Handover - President", "Handover - Secretary Treasurer", "Handover - Membership Chair".
Add one agenda item to your final leadership team meeting of the year: handover document review. Thirty minutes where incoming leaders read through their documents and ask questions while outgoing leaders are still in the room.
A chapter that implemented this reported that their new Secretary Treasurer was fully operational by week two instead of week six. Their new President ran the first three meetings without a single operational issue. The Vice President already knew what was coming and started preparing two months before taking over.
What to do if you're inheriting nothing
You're the new President and the outgoing President handed you a folder of printed agendas and a handshake. Now what?
Document as you go. Start your own handover document on day one. Every time you figure out how something works, write it down. Every contact you discover, add it to the list. Every problem you solve, capture the solution.
By month six, you'll have a decent working document. By month twelve, you'll have something valuable to pass along.
You're not just helping your successor. You're building institutional memory for your chapter. That has value beyond any single leadership term.
The handover document every chapter wishes it had is not a perfect document. It's a useful one, created by someone who cared enough to write down what they learned so the next person wouldn't have to learn it again.