Managing Donation Approvals Across 78 Schools Without Workflow Breakdowns
A structured approval system replacing fragile form-based workflows with a scalable operational model
-
Company
Howard County Public School System
-
Industry
Education / Public Sector
-
Location
Maryland, USA
-
Team
School staff + Central Office departments
-
Scale
78 schools, multi-department approvals
A centralized donation approval process involving multiple schools and departments, requiring consistent routing, compliance, and reporting.
This operation manages donation submissions from schools, including:
- Cash and non-cash donations
- Category-based routing (technology, facilities, etc.)
- Multi-tier approvals (Finance, Departments, Division, Board)
The system needs to:
- Route approvals correctly every time
- Handle exceptions (small donations, pass-through, vehicles)
- Maintain auditability across all schools
Operational Objective
Create a reliable system where every donation submission is:
- Routed to the correct approvers
- Approved or rejected based on defined rules
- Fully tracked from submission to final decision
- Logged for reporting and compliance
Where the Operation Broke Down
The previous setup relied on forms with workflow layers added on top.
This created issues when:
- Approval paths depended on multiple variables (type, value, category)
- Conditional routing became complex and hard to maintain
- Exceptions required special handling outside the normal flow
As volume increased:
- Workflows became brittle
- Approval steps were unclear or skipped
- There was no consistent audit trail
The team could collect submissions, but could not reliably operate the approval process at scale.
The Operating Model After AnyDB
Structured donation records with conditional approval routing
Each donation is a record with type, category, value, and status. The system determines whether approvals are required and what path to follow.
Approval tasks as controlled workflow steps
Approval steps are created as structured child records with sequence, status, and department ownership. Only one step is active at a time.
Dynamic routing based on real operational rules
Cash and non-cash donations follow different paths. Non-cash items are routed to the correct department based on category.
Built-in handling of exceptions
Pass-through donations, vehicle donations, and small-value donations automatically bypass approvals and move to completion.
Continuous state tracking at the parent level
Each donation always reflects:
- Current approval stage
- Overall status (In Review, Approved, Rejected)
- Completion timestamp
Final notification and audit-ready completion
Once the process finishes, the system:
- Marks the donation as approved or rejected
- Records completion time
- Sends notification to the initiator
What Changed in Daily Work?
- Staff submit once, without worrying about routing
- Approvers see only tasks relevant to them
- No manual forwarding or tracking of approvals
- Clear visibility into where each donation stands
- Consistent handling of all edge cases
- Reporting is based on real workflow data, not manual tracking
Why This Worked and Scales
The system works because it models the operation directly:
- Donations are treated as records with state, not form entries
- Approvals are explicit workflow steps, not hidden logic
- Routing is based on data-driven rules, not hardcoded flows
This removes ambiguity and makes the process:
- Predictable
- Auditable
- Easy to extend as requirements change
As volume increases, the structure holds. No rewiring of workflows is needed.
Ready to See It Working With Your Data?
If you are managing approvals, operations, or workflows across teams, the same model can be applied to your process.
We can map your current workflow and show how it runs inside AnyDB with real data.
Phone: (512)-761-7979
© 2025-2026 Humanly Inc, Austin, Texas. All rights reserved.