Operations evidence

Operations Overview brings coverage, review load and evidence exceptions across active volunteer programs into one operating screen. The underlying records keep the detail. review decisions holds the assignment decision, reviewer, date, reason and parent assignment. operation receipts holds an action type, result state, time, external reference, failure reason and parent assignment. record attachments keeps a titled file with a kind and upload date for supporting proof or reference.

These records help staff distinguish a requested action from a completed one. A receipt may be Pending, Completed, Failed or needs review. When an assignment or service-hours decision is in question, the parent assignment gives the team a starting point for reconciliation.

• Decision. Volunteer Coordinator records the assignment outcome through the decision action and checks the linked decision record.
• Evidence. Screening Reviewer or coordinator keeps relevant attachments with a recognizable related record locator and appropriate Kind.
• Exception. Operations Analyst reviews failed or review-needed receipts and brings the linked assignment back to its owner.

Define who can upload, read and remove attachments, especially screening certificates and ID documents. Decide how related record text identifies a volunteer or assignment so staff do not attach evidence to the wrong case. Agree who investigates each result state and when an apparent failure can be retried. A completed receipt should be checked against the intended record effect before an operating report is closed.

Choose a small set of action types that staff can recognize and use consistently. Keep the team members directory current so a Reviewer reference in decision history identifies the person who made the call. Establish how a coordinator records a reason for Return or Reject and where the next action is assigned.

A coordinator reviews a submitted assignment and records an approval. Open Assignment decision history and check that the decision, reviewer, time and parent assignment point to the intended placement. Then open the receipt for that action and compare its result state with the changed assignment. This is the ordinary path the team should understand before handling exceptions.

Now rehearse a failed service-hours verification. Action exceptions should expose its operation type, time and failure reason alongside parent assignment. The hours reviewer checks the service hours entry and linked assignment before deciding whether to retry. Operations Analyst records the outcome of the investigation in the team’s operating handoff; the team should not count an unverified entry as approved service.

• Action exceptions — Failed and review-needed actions with assignment links and failure context.
• Assignment decision history — The recorded decision, reviewer and reason for each placement.
• Submitted assignment inbox — Pending placement decisions that may generate the next review record.

See assignment review for decision evidence and service verification for action reconciliation after work is logged.