Committee handoverA useful handover lets the incoming team find the current membership record, understand pending applications and identify what needs review. Start with the records and the people responsible for them, then walk through an ordinary member request together.
Start with the approved member record
Before a committee changes, agree which register the team uses for membership work. A contact list may contain event visitors and former members as well as current members. Give the incoming committee a clear explanation of what each list represents and which questions still need a decision.
FewaOMS membership management brings profiles and categories together with applications, required documents and approvals. Use those connected records when discussing a member’s current position. The organization should still decide who checks a disputed name, category or supporting document before changing the record.
Review applications with their documents
Prepare a short list of applications that remain under review. For each one, explain the membership category, the documents expected for that category and the question the reviewer needs to resolve. A folder of attachments is more useful when the incoming team can connect each document to the right application.
In a handover meeting, open a fictional example and explain the review process from application to approval. Keep unresolved requests on the handover list until someone accepts responsibility for the next step. Do not describe an unfinished application as an approved membership simply because its documents have arrived.
Explain current terms and renewal history
A familiar member name does not explain which membership term the team is reviewing. Show the current term and renewal history so the incoming secretary understands how continued membership is recorded. This helps separate a new application from work relating to an existing member’s next cycle.
Use a small sample of records during the discussion and note questions that need follow-up. When a membership issue also involves dues, ask the responsible person to review the relevant invoice and payment record. The committee should be able to explain each part of the process without treating one status as evidence for every other step.
Agree who will complete the next action
Write a practical handover checklist with a record, an outstanding question, a responsible person and the next review date. Keep agreed responsibilities in your committee’s handover notes; each administrator can use their personal task list to follow up. Review the access available to incoming administrators as part of your organization’s own handover procedure.
If the outgoing administrator keeps personal reference notes, move the information the committee actually needs into its agreed handover record. Personal administrator notes are a reference for their owner; the existence of a note alone does not establish that the next committee has received its contents.
Finish with a sample member request
Ask the incoming team to locate a fictional member’s application, identify the supporting documents and explain the current term. Then describe how they would follow an unresolved question. Observe where they need help and update the handover checklist before the outgoing committee leaves.
Use a demonstration to confirm the modules and access available for your organization. Availability depends on its sector, plan and configuration. A handover is ready when the incoming team can explain the records it has received and the next action for pending work, with a clear route for questions.
See the workflow for your organization
Ask our team to walk through your member services using fictional example records. Available modules depend on your sector, plan and configuration.
Request a demonstration

