A docent class is months of work before anyone leads a tour, and the people who come through it often stay for a decade or more. Treating them as generic volunteers loses the two things that actually matter: what each one is certified to do, and how long they have been doing it. Volunteer Ledger keeps both on the record.
Most museums do not have one docent qualification. There is the core class, then school programs, then the special exhibition that needed its own training two weeks before opening.
You create the requirement types: docent class completion, school program training, an exhibition briefing, a safeguarding check for tours with children. Each carries its own renewal rule, so an annual refresher and a one-off certification behave differently without you tracking the difference by hand.
A requirement can be scoped so it does not apply to areas of service where it is irrelevant. Docent class completion can be required of docents while the front desk and the gift shop never show a gap for it, which keeps your compliance view honest rather than permanently red.
Current, expiring soon, expired and missing are worked out from the expiry dates on the record rather than typed into a column. Nobody has to remember to update a status for the roster to be telling the truth about who is certified today.
Upload the certificate against the requirement it proves, so the evidence sits beside the expiry date. When a docent asks for a copy years later, or an accreditation review asks how you know, it is one record rather than a search through a shared drive.
This is the question every education manager asks, so here is exactly how it works and the one case worth staying ahead of.
A volunteer can only see and claim shifts in the areas of service assigned to them, and that restriction is applied by the server rather than by hiding something on screen. Do not add anyone to the docent area until they have finished the class, and the tour slots are simply never offered to them. There is nothing for them to click.
Scope docent certification so it applies to the docent area and nowhere else. Front desk and retail volunteers never register as a gap for it, which is what keeps the compliance view something you actually read instead of permanently red.
One case to manage deliberately: a docent already assigned to the area stays assigned when a certification lapses. The requirement expiration report covers a window you choose, so you see who is coming due and either renew them or take them off the area before it matters. Catch it there and the gate keeps holding.
However self-signup is configured, staff can assign, move and remove people from any tour directly. The system supports your judgment rather than replacing it.
Docent programs run on people who have been there longer than most of the staff. That is worth recording properly, and worth acknowledging on time.
Each docent's record holds their start date, lifetime hours, breakdown by area and year by year history. When the education manager changes, the institutional memory of who has been giving tours since 2009 does not leave with them.
Recognition by hours and by years of service produces the list of who is due, for a season celebration or a long-service pin, while there is still time to order anything.
An individual report gives dates, totals and areas served in one printable page, which is most of what a reference or a nomination needs.
If you enable volunteer sign-in, docents can record their own hours against the right area of service, and staff still see and can correct everything. It removes the sign-in sheet without removing oversight.
Publishing tour slots and gallery shifts, and letting people claim the ones they are cleared for.
Docent hours as in-kind value for a funder, or as a department figure for the board.
Where the certificates live, who can open them, and how long they are kept.
You define the requirement types your museum uses, such as docent class completion, school program training or an exhibition briefing, each with its own renewal rule. Recording one against a docent stores the completion and expiry dates, and their status is derived from those dates rather than typed in.
Yes. A requirement can be scoped so that volunteers whose areas of service it does not cover are exempt from it. Docent certification can be required of docents while the front desk and retail volunteers never appear as a gap, which is what keeps the compliance view worth looking at.
Yes, through area assignment. Volunteers only see and can claim shifts in the areas of service assigned to them, and that is enforced on the server rather than in the interface, so a volunteer who has not been added to the docent area is never shown a tour slot at all. The case to manage is renewal rather than initial clearance: a docent who is already assigned stays assigned if a certification lapses, so the requirement expiration report is what tells you to renew them or take them off the area first.
Attached to the requirement they prove, on the docent's own record, so the document and its expiry date sit together. Documents are staff-only, every download is logged, and you can set a retention window that disposes of them a chosen period after someone is deactivated.
The requirement expiration report covers whatever window you choose, so you can pull everything expiring in the next sixty or ninety days and schedule the refresher before anyone drops out of certification mid-season.
Yes, if you enable volunteer sign-in. Docents log hours against the correct area of service themselves, and staff retain full visibility and the ability to correct entries. Letting volunteers log hours is a separate setting from letting them claim shifts, so you can allow one without the other.
Start a free 45-day trial, bring your docent roster in from the spreadsheet, and see who is certified, who is lapsing, and who is due to be thanked.
