What Leaves With Your Most Experienced Employee?

An experienced nonprofit employee rarely leaves behind only an empty position.

They may take years of unwritten knowledge with them:

• Why a certain process exists
• Which annual deadlines are easy to miss
• How unusual situations are handled
• Who must be consulted before a decision
• Which community relationships require special attention
• Where important documents are stored
• What previous leaders tried and why it failed
• Which written procedures no longer reflect reality

The organization may still have its policies, databases and shared folders. What disappears is the practical knowledge connecting those resources.

When that knowledge lives primarily in one employee’s memory, turnover becomes more than a staffing problem. It becomes an operational risk.

Maisy helps nonprofits capture, organize and securely retrieve approved institutional knowledge before it walks out the door.

The Employee Everyone Depends On

Consider a nonprofit with 60 employees operating several programs across three locations.

One operations director has worked there for 14 years. She understands facilities, purchasing, insurance, vendor relationships, board reporting, emergency procedures and several legacy systems.

Other employees regularly ask her questions such as:

• Which vendor handles urgent repairs?
• What documentation does finance need for this purchase?
• When does the annual insurance renewal begin?
• Who has authority to approve an exception?
• Why does one location follow a different procedure?
• Where is the latest version of the emergency plan?
• What information does the board expect in the quarterly report?

She can usually answer immediately.

That efficiency hides a serious weakness. The organization has built part of its operating system around one person’s memory.

When she announces her departure, leadership asks her to document everything she knows.

She has six weeks remaining.

She is also expected to complete projects, train her replacement, transfer relationships, close out responsibilities and continue performing her regular job.

There is no realistic way to capture 14 years of knowledge in a few rushed handover meetings.

Institutional Knowledge Is More Than Documentation

Organizations often respond to turnover by asking the departing employee to create a procedures manual.

That is useful, but it is not enough.

Institutional knowledge includes several types of information.

Formal knowledge

This is the information already documented in approved materials:

• Policies
• Procedures
• Contracts
• Job descriptions
• Board resolutions
• Grant requirements
• Training materials
• System instructions
• Emergency plans

Formal knowledge is usually the easiest information to collect.

Practical knowledge

This explains how the formal process works in real situations:

• What information must be gathered before submitting a request
• Which steps commonly cause delays
• When an issue should be escalated
• Which exceptions are permitted
• Which department must be consulted
• What a complete submission looks like
• How long each stage normally takes

A policy might state that purchases over a certain amount require approval. Practical knowledge explains who prepares the request, what documentation is required, who reviews it and what happens when the purchase is urgent.

Historical knowledge

Historical knowledge preserves the reasoning behind decisions:

• Why a policy changed
• Why a vendor was selected
• Why a program uses a particular process
• What previous approaches were attempted
• Which risks leadership was trying to reduce
• What commitments were made to partners or funders

Without this history, future employees may repeat failed approaches or reverse decisions without understanding the consequences.

Relationship knowledge

Nonprofits depend heavily on relationships with funders, partners, board members, vendors, volunteers and community organizations.

Important relationship knowledge may include:

• Who owns the relationship
• How communication is normally handled
• What commitments have been made
• What sensitivities should be understood
• Which internal leaders should be involved
• Where formal agreements are stored

Sensitive personal opinions and informal gossip do not belong in the knowledge hub. Approved relationship history, responsibilities and commitments may.

Why Exit Interviews Are Not Enough

Exit interviews serve an important HR purpose, but they are not designed to capture an employee’s complete operational knowledge.

A departing employee may not remember everything during one conversation. People often recall important details only when performing a task, answering a question or reviewing a real situation.

The organization may also ask questions that are too broad:

• What does your replacement need to know?
• Are there any important files?
• Is there anything we have missed?

These questions place the entire burden on the departing employee to identify what the organization does not know.

A better process examines the employee’s actual responsibilities.

Review:

• Recurring calendar events
• Frequently answered questions
• Reports they produce
• Documents they maintain
• Systems they use
• Approvals they provide
• External relationships they manage
• Problems that are routinely escalated to them
• Annual and seasonal responsibilities
• Decisions that require their historical knowledge

This produces specific questions that are easier to answer and document.

Turnover Is Not Limited to Executives

Succession planning is often discussed only in relation to executive directors and CEOs.

Executive transitions deserve significant attention. The National Council of Nonprofits recommends preparing for both planned and unexpected leadership departures, including emergency transition plans, cross-training and deliberate onboarding. It also warns that transitions can cause the loss of institutional knowledge held by long-tenured leaders.

But operational knowledge can also be concentrated in:

• Program directors
• Grant managers
• Finance employees
• HR staff
• Executive assistants
• Volunteer coordinators
• Technology administrators
• Facilities managers
• Development employees
• Long-serving administrative staff

The employee who understands the annual grant-reporting calendar may create as much operational risk as the employee with the highest title.

Knowledge-preservation planning should therefore focus on critical responsibilities, not just senior positions.

How Maisy Supports Knowledge Preservation

Maisy is a secure AI-powered knowledge hub that helps nonprofit employees find approved internal information, procedures and institutional knowledge.

Pixeldust works with the nonprofit to identify important knowledge, organize it in SharePoint and configure the conversational experience through Copilot Studio.

Employees can then ask questions in plain language.

For example:

“What needs to happen before the annual insurance renewal?”

Maisy might retrieve an approved checklist explaining:

• The renewal timeline
• Required documents
• Responsible employees
• Board reporting requirements
• Broker contact information
• Review and approval steps
• The location of prior renewal records

Another employee might ask:

“Why does the west location use a different purchasing process?”

Maisy may retrieve an approved explanation describing a funder requirement or contractual restriction that applies only to that location.

The goal is not to reproduce a departing employee’s personality or judgment.

The goal is to preserve approved knowledge that other employees need to perform their work.

What Should Be Captured?

Not everything an experienced employee knows belongs in Maisy.

The organization should focus on knowledge that is useful, appropriate and organizationally owned.

Strong candidates include:

Recurring processes

Document procedures performed monthly, quarterly or annually:

• Budget preparation
• Grant reporting
• Insurance renewal
• Board-meeting preparation
• Employee-benefit enrollment
• Program audits
• Contract renewals
• Volunteer recertification
• Required filings
• Facility inspections

These processes are particularly vulnerable because employees may perform them only once each year.

Decision and approval paths

Capture who is responsible for:

• Approving purchases
• Reviewing contracts
• Authorizing exceptions
• Responding to incidents
• Communicating with funders
• Escalating employee concerns
• Approving public statements
• Reviewing program changes

Titles and responsibilities should be used rather than relying only on individual names whenever possible.

Process exceptions

Document common exceptions and the point at which human review is required.

Maisy should not independently decide whether an exception is justified. It can explain the approved escalation process.

Key definitions and terminology

Experienced employees often understand organizational shorthand that newer employees do not.

A knowledge hub can define:

• Program names
• Internal acronyms
• Funding categories
• Reporting terms
• Department responsibilities
• System names
• Governance terminology

Decision history

Important decisions should include:

• The decision made
• The date
• The responsible authority
• The reason
• The affected process
• Related documents
• The review date, when applicable

This prevents employees from repeatedly reopening settled questions without understanding the original reasoning.

What Should Not Be Captured?

A knowledge-preservation project must not become an uncontrolled dump of employee emails, private notes and confidential records.

Information that may need to remain outside Maisy includes:

• Personnel records
• Medical information
• Client case notes
• Donor financial information
• Legal advice
• Employee disciplinary matters
• Confidential board discussions
• Personal opinions about coworkers
• Unverified allegations
• Passwords and security credentials

Completed confidential records should remain separate from blank forms, policies and procedures.

The source system remains authoritative for individual records and transactions.

Maisy may explain how an employee should access a case-management system or follow an approved recordkeeping procedure. It should not become a replacement repository for sensitive case records.

Permissions Still Apply

Preserving knowledge does not mean making all information available to everyone.

Some knowledge may be appropriate for all employees. Other information may be limited to managers, HR, finance, leadership or board members.

SharePoint should serve as the primary organized knowledge source, with access designed around existing roles.

Microsoft explains that when SharePoint is configured as a Copilot Studio knowledge source, users are authenticated through their Microsoft credentials and must have permission to access the underlying information before the agent can retrieve it.

Before launch, the nonprofit should review:

• SharePoint site permissions
• Library and folder access
• Microsoft 365 group membership
• Guest access
• Shared links
• Inherited permissions
• Sensitive documents
• Former employee access
• Content that should remain excluded

The knowledge hub should follow the organization’s permission structure. It should not create a shortcut around it.

Begin Before Someone Resigns

The worst time to begin preserving institutional knowledge is after a critical employee gives notice.

Knowledge capture should be an ongoing operational practice.

A nonprofit can begin by identifying roles where:

• Only one employee understands a critical process
• Work stops when that employee is absent
• Coworkers repeatedly ask the same person for guidance
• The employee manages important external relationships
• Procedures are largely undocumented
• Responsibilities occur infrequently
• Mistakes could affect funding, compliance or service delivery
• The employee is approaching retirement
• Turnover has historically disrupted operations

These roles represent knowledge concentration risk.

The organization does not need to document everything immediately. It should begin with the responsibilities that would cause the greatest disruption if the employee became unavailable tomorrow.

A Practical Knowledge-Capture Process

1. Identify critical responsibilities

List the processes, decisions, relationships and recurring obligations owned by the employee.

Do not rely solely on the job description. Job descriptions rarely show the full scope of what an experienced employee actually handles.

2. Collect existing materials

Gather:

• Policies
• Procedures
• Checklists
• Templates
• Reports
• Calendars
• Training materials
• Forms
• Meeting notes
• Approved correspondence
• System instructions

3. Conduct structured interviews

Ask specific questions:

• What questions do employees ask you repeatedly?
• What processes fail when you are absent?
• What annual tasks are easy to forget?
• Which written procedures are outdated?
• What decisions require historical context?
• What exceptions occur most often?
• Which relationships need an intentional handoff?
• What does your replacement need to understand during the first 30 days?

4. Observe real work

Have another employee shadow the process or ask the experienced employee to narrate it while completing the task.

This often reveals steps that feel automatic to the experienced employee and would never appear in a general interview.

5. Validate the information

A manager or content owner should review the captured knowledge.

The goal is to preserve approved organizational guidance—not simply record one employee’s preferred way of working.

6. Organize it in SharePoint

Use clear document names, ownership, review dates, metadata and permissions.

Archive outdated and duplicate files rather than allowing conflicting versions to remain active.

7. Test through Maisy

Ask realistic questions using the language employees normally use.

Confirm that Maisy:

• Retrieves the correct guidance
• Identifies the authoritative source
• Respects permissions
• Avoids unsupported answers
• Directs sensitive questions to a person
• Clearly states when approved information is unavailable

Microsoft recommends periodically reviewing knowledge sources and removing outdated or irrelevant information so the agent continues using current content.

Knowledge Preservation Supports Succession

A knowledge hub is not a complete succession plan.

It does not select a replacement, develop future leaders, maintain funder confidence or determine interim authority.

BoardSource’s executive-transition guidance emphasizes that boards must plan for both expected and sudden departures, define the transition process and properly support incoming leadership.

Maisy supports that work by making approved organizational knowledge easier for new and existing employees to access.

This can reduce the amount of basic operational information a successor must obtain through scattered conversations.

The incoming employee still needs training, relationships, judgment and context. They simply do not have to begin by searching through years of folders and email.

The Organizational Benefits

A structured knowledge-preservation program can help a nonprofit:

• Reduce disruption during turnover
• Protect recurring operational processes
• Shorten replacement onboarding
• Preserve decision history
• Reduce dependence on individual employees
• Improve cross-training
• Identify undocumented responsibilities
• Clarify ownership and approval authority
• Maintain more consistent procedures
• Prepare for planned and emergency transitions
• Give experienced employees a practical way to transfer knowledge
• Prevent the same information from being lost repeatedly

The objective is not to make employees interchangeable.

It is to ensure that the organization retains ownership of the knowledge required to fulfill its mission.

Preserve the Knowledge Before It Walks Away

Maisy helps nonprofit employees find approved procedures, policies and institutional knowledge without replacing professional judgment or the systems they already use.

Pixeldust helps the nonprofit identify knowledge concentration risks, interview experienced employees, organize approved information in SharePoint, establish appropriate permissions and configure Maisy around practical employee questions.

The process begins with discovery: identifying what the organization cannot afford to lose, who currently holds that knowledge and how it can be preserved before the next transition occurs.