Most nonprofits do not have a document shortage.
They have too many copies of the same document.
A policy may appear in SharePoint, a shared drive, an email attachment and a department folder. Each copy may have a slightly different title:
- Employee Handbook
- Employee Handbook Final
- Employee Handbook Updated
- Employee Handbook Final Revised
- Employee Handbook 2026
- New Employee Handbook
Employees open whichever version they find first.
The problem becomes serious when those documents contain different instructions.
One purchasing procedure may require two approvals. Another may require only one. One incident-reporting form may list an employee who left two years ago. An old volunteer handbook may describe a screening process the organization no longer uses.
Maisy can help employees find the approved version of a policy or procedure, but the organization must first decide which version is authoritative.
AI cannot resolve document conflicts the nonprofit has not resolved internally.
Duplicate Documents Create Operational Risk
Duplicate files are often treated as a housekeeping issue.
They are actually a knowledge-management problem.
When employees use different versions of the same document, the organization may experience:
- Inconsistent procedures
- Incorrect approvals
- Outdated forms
- Conflicting employee guidance
- Missed compliance requirements
- Reporting errors
- Ineffective training
- Confusion during audits
- Increased dependence on experienced staff
- Loss of confidence in the organization’s knowledge
The damage is not limited to the incorrect document itself.
Once employees stop trusting the document library, they stop using it.
They ask a coworker, search their email or save personal copies. That creates even more duplicates.
A Realistic Nonprofit Example
Consider a nonprofit with 60 employees operating several programs across three locations.
The organization has used SharePoint for several years, but departments have also maintained their own folders and Teams channels.
HR stores policies in one SharePoint library. Managers keep onboarding copies in their department folders. Employees download documents and email them to new hires.
The nonprofit updates its remote-work policy.
HR replaces the policy in its official library. However:
- An older copy remains in the onboarding folder.
- A manager has a downloaded copy on their computer.
- Another version is attached to an old Teams message.
- One location printed the previous policy for its staff binder.
- The employee handbook still contains the original wording.
A new employee asks whether remote work is permitted after the first 60 or 90 days.
The answer depends on which document they find.
HR knows the correct rule, but the organization’s stored knowledge does not clearly communicate it.
How Version Confusion Develops
Employees download working copies
Someone downloads a procedure, edits it and saves a new copy.
The new file may never be returned to the authoritative library. Coworkers begin using the edited version because it appears more current.
Email becomes a document system
Employees send forms and policies as attachments.
Months later, someone searches their inbox and reuses an outdated attachment because it is easier than locating the official file.
Departments maintain separate libraries
HR, operations and program teams may each store a copy of the same policy.
When the policy changes, one department updates its version while the others do not.
File names replace real version control
Employees add labels such as “final,” “current” and “approved” to file names.
These labels are unreliable because there can be several files called “final.”
Old documents are never archived
Organizations may hesitate to delete files because they are unsure whether the records must be retained.
As a result, current and historical material remains mixed together.
No one owns the document
A procedure may have several contributors but no assigned content owner.
When the process changes, everyone assumes someone else will update the documentation.
One Authoritative Source
The central rule of document control is simple:
Employees should know where the authoritative version lives.
That does not mean every historical version must be destroyed.
It means current documents, drafts and archived records must be clearly distinguished.
For each important document, the nonprofit should identify:
- The authoritative storage location
- The document owner
- The approval authority
- The current status
- The effective date
- The review date
- The retention requirement
- The employees authorized to access it
Maisy should retrieve current approved guidance from that authoritative source.
It should not search every folder indiscriminately and combine several conflicting versions into one answer.
SharePoint Version History Is Not the Same as Duplicate Files
SharePoint includes built-in version-history capabilities.
When employees edit the same document in a SharePoint library, the platform can retain earlier versions, allow authorized users to compare changes and restore a prior version when necessary. Microsoft describes version history as part of SharePoint and OneDrive’s built-in data-protection capabilities. (Microsoft Learn)
This is different from creating multiple separate files.
A controlled SharePoint document might have:
- Version 1.0
- Version 1.1
- Version 2.0
Those versions remain connected to one document.
By contrast, these files are independent copies:
- Purchasing Policy Final.docx
- Purchasing Policy New.docx
- Purchasing Policy Revised Final.docx
- Purchasing Policy Updated 2.docx
SharePoint cannot automatically know that those files represent competing versions of the same policy.
The nonprofit must consolidate them.
Current, Draft and Archived Documents
A practical document structure should separate three states.
Current approved documents
These are the materials employees should use in active work.
Examples include:
- Current policies
- Approved procedures
- Active forms
- Current training materials
- Approved program guidance
- Current board policies
Maisy should generally retrieve from this category.
Draft documents
Drafts are still under development or review.
They should be clearly labeled and restricted to the employees involved in the drafting process.
A draft policy should not appear as an approved answer to a general employee question.
Archived documents
Archived records may need to be retained for legal, historical, contractual or operational reasons.
They should remain separate from current guidance.
An archived policy might be needed to determine which rule applied during an earlier period. That does not mean it should appear in routine employee searches.
Retention and Destruction Are Different From Version Control
A nonprofit should not delete documents simply because they are old.
Some records must be retained for legal, financial, grant, employment or governance reasons.
The National Council of Nonprofits recommends adopting a written document-retention and destruction policy that identifies which records must be retained and for how long. (National Council of Nonprofits)
The retention policy should guide:
- Which historical records are preserved
- How long they are retained
- Where they are stored
- Who can access them
- When destruction is permitted
- When a legal or audit hold prevents destruction
Archiving a document does not necessarily mean deleting it.
It means removing it from the active knowledge environment so employees do not mistake it for current guidance.
Legal counsel, accountants, funders or other qualified professionals may need to help determine retention requirements.
Maisy should not independently decide when records can be destroyed.
How Maisy Helps Employees Find the Correct Document
Maisy is a secure AI-powered knowledge hub that helps nonprofit employees find approved internal information.
An employee might ask:
“What is the current travel-reimbursement policy?”
Maisy can retrieve the approved policy from the authoritative SharePoint library and provide:
- A concise explanation
- The effective date
- The responsible department
- A link to the approved document
- The required form
- The appropriate contact for exceptions
Another employee might ask:
“Can I use the reimbursement form attached to last year’s email?”
Maisy could direct the employee to the current approved form instead.
The value is not that AI creates a new policy.
The value is that it points employees toward the organization’s approved source rather than another uncontrolled copy.
What Maisy Should Not Do
Maisy should not:
- Decide which conflicting document is correct
- Treat file names as proof of approval
- Combine draft and approved policies
- Replace legal document-retention advice
- Delete or archive documents automatically without governance
- Assume the newest modification date means a document is authoritative
- Present historical records as current guidance
- Ignore SharePoint permissions
- Rewrite an approved policy without authorization
A document uploaded yesterday may still contain a policy from five years ago.
A document modified last year may remain the current approved version.
Dates are useful indicators, but ownership and approval status are more important.
Permissions Still Matter
Some document libraries contain information that should not be available to every employee.
Examples include:
- HR management procedures
- Legal records
- Board materials
- Audit documents
- Financial controls
- Security procedures
- Confidential program guidance
- Executive records
Users should only see information they are authorized to access.
SharePoint permissions should follow existing organizational roles. Copilot Studio provides the conversational layer, but it does not eliminate the need for proper access design.
Before Maisy is launched, the nonprofit should review:
- Site permissions
- Document-library access
- Folder-level restrictions
- Microsoft 365 groups
- Guest access
- Public links
- Inherited permissions
- Draft libraries
- Archived material
- Former employee access
A document-control project is an opportunity to correct permissions that have accumulated over time.
Blank Forms and Completed Records Must Be Separated
One common source of risk is storing blank forms beside completed confidential records.
For example, an HR library may contain:
- A blank leave-request form
- Instructions for submitting the form
- Completed employee leave requests
- Medical documentation
- Manager approval records
The blank form and general procedure may be appropriate knowledge sources.
Completed employee records should remain restricted and may need to stay outside Maisy entirely.
The same principle applies to:
- Incident forms
- Participant forms
- Volunteer applications
- Background checks
- Expense reports
- Evaluations
- Complaint records
Maisy may explain how to complete or submit a form.
It should not expose completed confidential records to unauthorized users.
A Practical Document-Cleanup Process
1. Select one knowledge area
Begin with a department or process that causes frequent confusion.
Good starting points include:
- HR policies
- Purchasing procedures
- Employee onboarding
- Volunteer guidance
- Program forms
- Emergency procedures
2. Inventory the files
Search SharePoint, Teams, shared drives and common department folders.
Identify:
- Duplicate titles
- Similar documents
- Drafts
- Historical versions
- Broken links
- Personal copies
- Documents with no owner
3. Group related documents
Determine which files represent versions of the same policy, procedure or form.
Do not assume two similarly named documents are duplicates until their contents are reviewed.
4. Identify the authoritative version
The appropriate content owner must decide which document is current.
This may require review by:
- HR
- Finance
- Program leadership
- Executive leadership
- The board
- Legal counsel
- Compliance staff
5. Resolve contradictions
Conflicting instructions must be reconciled before Maisy uses the information.
Document the approved decision and effective date.
6. Archive or remove obsolete copies
Move historical records into an appropriate archive based on the nonprofit’s retention policy.
Remove convenience copies when they are no longer required and when doing so is consistent with legal and organizational requirements.
7. Organize the current document in SharePoint
Assign:
- Clear title
- Owner
- Approval status
- Effective date
- Review date
- Department
- Audience
- Retention category
- Appropriate permissions
8. Configure version history
Use SharePoint version history to track future revisions to the same document rather than creating new independent copies.
Microsoft notes that version history can be used to view, compare and restore earlier versions of a file. (Microsoft Learn)
9. Test Maisy
Ask realistic employee questions.
Confirm that Maisy:
- Finds the approved document
- Avoids draft content
- Does not retrieve archived guidance as current
- Identifies the effective date
- Links to the authoritative source
- Respects permissions
- Escalates unresolved conflicts
Content Ownership Prevents the Problem From Returning
A one-time cleanup is not enough.
Each important document should have a content owner responsible for:
- Reviewing the information
- Approving updates
- Confirming accuracy
- Archiving superseded material
- Maintaining links
- Reviewing access
- Responding to conflicts
- Scheduling future reviews
The owner does not necessarily write every document.
They are accountable for ensuring that the organization knows which version is current.
Without ownership, duplicate documents will return.
Expected Organizational Benefits
A disciplined document-control process can help a nonprofit:
- Reduce conflicting employee guidance
- Improve confidence in policies and procedures
- Make current forms easier to find
- Improve onboarding
- Strengthen internal controls
- Reduce repeated questions
- Support audit preparation
- Preserve historical records appropriately
- Reduce dependence on personal file collections
- Improve knowledge-hub answers
- Clarify document ownership
- Reduce accidental use of obsolete material
The goal is not to create a perfectly clean file system overnight.
It is to establish a reliable process for identifying which information employees should trust.
Give Employees One Approved Answer
Maisy helps nonprofit employees find approved policies, procedures, forms and institutional knowledge without replacing document ownership, professional judgment or formal retention requirements.
Pixeldust helps nonprofits inventory scattered documents, identify authoritative versions, resolve conflicts, organize approved content in SharePoint and configure Maisy around trusted knowledge sources.
The process begins with discovery: determining which documents employees currently use, where duplicates exist, who owns the information and which version the organization is prepared to call authoritative.
