These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Donor Management System
- Features
- Operations Overview
Operations Overview
The Operations Overview brings awarded funding, confirmed receipts, pending reviews and failed operations into one operating screen.
OverviewFailed Operations×
Donor Management System · Operations Overview
New
Failed Operations
Operation receipts
| Operation key | Action | Occurred at | Failure reason | Parent | |
|---|---|---|---|---|---|
| OK-172 | ACT-141 | 25 Oct | Cut to length | FC-51785 | |
| OK-209 | ACT-196 | 09 Oct | Weld frame | FC-20776 | |
| OK-193 | ACT-679 | 03 Oct | Drill and tap | FC-61591 | |
| OK-195 | ACT-707 | 11 Oct | Deburr | FC-60087 | |
| OK-209 | ACT-634 | 05 Oct | Assemble | FC-52980 |
6 of 6 records
OK-172Operation receipts · OR-19617
ActionACT-141
Occurred at25 Oct
Failure reasonCut to length
ParentFC-51785
What you can do
The working record
The Operations Overview brings awarded funding, confirmed receipts, pending reviews and failed operations into one operating screen. Operation receipts hold the action, stable key, expected revision, result state, time, linked case and failure reason. The lead can move from a failed operation back to the case and its review history.
The overview is a starting point for an operations lead to inspect pending reviews and failed results. Each operation receipt records its action, key, expected revision, time, result state and parent case. The case provides the surrounding decisions and financial entries.
How the work is organized
- Start with the case. Confirm the organization, program and owner before adding linked work.
- Keep the decision visible. Use the reviewer decision and supporting file to explain why work advanced or returned.
- Follow the result. Check the linked operation result when an action needs follow-up.
The lead reviews the result state and failure reason before deciding who follows up. Admin can check the same operation receipt and its external reference. A failed result should lead back to the parent case rather than becoming a separate, unexplained task.
What to agree during setup
Agree who checks the overview each day and who resolves a failed result. Decide how an external reference is matched to a case before an operation is considered complete. Check the operation key and expected revision when tracing repeated attempts; agree how the team handles any discrepancy.
Give Operations Lead responsibility for the day-to-day record and Admin a clear point at which to check it. Agree which result states need the operations lead’s attention and who checks each failure reason. Decide how staff match an external reference to the parent case and how they record the outcome of follow-up.
Check the handoff on an actual case
Use a case with a submitted receipt and a reviewer decision. Confirm that the overview shows the pending work, then record a completed operation and find its linked case. Rehearse a failed result with a reason, and have the lead trace the action through the decision and attachment without changing the original evidence.
Ask the operations lead to locate the failed result, name its parent case and explain the reason to Admin. Then open that case’s decision history and receipt record so the team can see what action was attempted.
What your team sees
- Failed Operations — Failed results with action, reason and parent case.
- Operations Needing Review — Results flagged for further review.
Follow the work through
Follow the funding case review and receipt review to see where this record changes hands.
What it keeps track of
Data model- Operation receipts
- Operation Receipts records; retain actual linked evidence and role scope.
- Funding cases
- Funding Cases records; retain actual linked evidence and role scope.
- Donation receipts
- Domain-specific donation receipts supporting issue a receipt for confirmed donation.
- Review decisions
- Review Decisions records; retain actual linked evidence and role scope.
- Record attachments
- Record Attachments records; retain actual linked evidence and role scope.
Who uses it
Permissions- Operations Lead
- Inspects pending work and failed results.
- Admin
- Checks access and helps resolve operation exceptions.
Set up Donor Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.