Kovent: AI-Powered Compliance Document Management on SharePoint #242
Description
Submission Name
Kovent Binders and m1NT AI Agent
Description
The Problem
Food manufacturing facilities maintain hundreds of compliance documents - SOPs, HACCP plans, training records, sanitation logs, supplier approvals, corrective action reports. A single BRCGS 9 certification covers 328 subclauses, 12 fundamental requirements, and hundreds of cross-referenced records. SQF Edition 10 drops in 2026 (first audits January 2027). FSMA 204 traceability requirements hit in 2028. Across standards, tens of thousands of certified facilities need to rebuild their documentation systems.
Most plants still manage this with paper binders, shared drives with no naming conventions, or expensive SaaS platforms that lock their data behind proprietary walls. When the auditor arrives, the QA manager scrambles to locate documents across five different systems. "Where's the allergen control SOP? When was the HACCP plan last reviewed? Is that CAPA still open?" These questions shouldn't take 20 minutes to answer.
The Solution
Kovent takes a different approach: we build compliance infrastructure directly on the client's own SharePoint and Microsoft 365 tenant.
The demo showcases Heritage Valley Foods, a BRCGS 9 certified bakery in Lancaster, PA. The system works in two phases:
Phase 1 - Infrastructure First: Using Microsoft Graph API, Kovent programmatically creates a structured SharePoint site with:
Organized document libraries mapped to the certification standard's clause structure (BRCGS 9, SQF, FSSC 22000)
Consistent naming conventions across all document types
Hyperlinked Master Document Register connecting every doc to its SharePoint location
Excel workbooks on OneDrive for CCP monitoring, CAPA tracking, batch records, and shipping logs
Cross-referenced evidence packages with full traceability chains (lot-level linking across production, shipping, and investigation records)
Phase 2 - Knowledge Agent (m1NT): Once the structured library exists, m1NT serves as an AI knowledge agent grounded on that SharePoint content. It is date-aware and cites the relevant regulatory clauses. QA managers can ask natural language questions like:
"Show me open CAPAs" - flags overdue items with urgency, cites BRCGS 9 clause 7.1.1
"Trace lot 2831 from production to shipping" - assembles the full cross-reference chain with clickable SharePoint links
"What allergen docs do we need for our BRCGS audit?" - identifies gaps against clause 5.3 (a Fundamental requirement)
"What happened with the Coastal mold complaint?" - surfaces the complete CAPA investigation with linked evidence package
m1NT retrieves answers from the organized SharePoint library with regulatory clause citations, clickable document links, and date-aware urgency scoring.
Key Differentiators
"We build, you keep." The entire system lives on the client's M365 tenant. If they stop working with MATANGA, they keep everything - every document, every folder, every workflow. No vendor lock-in. No data migration. No export fees.
"Infrastructure first." Most AI document tools throw an LLM at a messy file dump. Kovent builds the organizational structure first - folder hierarchies mapped to clause structures, naming conventions, hyperlinked registers, cross-referenced tracking sheets - then layers AI on top of clean, well-organized content. The AI works better because the foundation is solid.
"Compliance at the first mile." Instead of trying to fix compliance problems at audit time, Kovent focuses on the moment records are created. Clean data at the source means clean audits downstream.
Multi-standard engine. The demo shows BRCGS 9, but the same infrastructure-first approach works for SQF Edition 9 and 10, FSSC 22000, and FSMA 204 traceability. Different clause structures, same programmatic build pipeline. One engine, any standard.
Submission Categories
- SharePoint site
- Mobile experience
- Knowledge Agent
- Agents and SharePoint
- SharePoint Framework
- SharePoint Embedded
Project video
Project Repository URL
No response
Team Members
Zanda Pemba
LinkedIn Profiles
No response
Badge validation
- I verify that all of my team members have completed the badge validation form at aka.ms/SharePointHackathon/Badges.