1. Schools/Tutoring CRM
  2. Features
  3. Review and Evidence
Feature · Review and Evidence

Review and Evidence

Keep session decisions, operation receipts and supporting files tied to their source work.

OverviewReceipts Needing Review
Schools/Tutoring CRM · Review and Evidence

Receipts Needing Review

Operation receipts

New
Operation keyOperation typeRecorded atStatusParent opportunity
OK-623Qualify Opportunity12 OctNeeds ReviewOPP-33817
OK-337Submit Proposal08 OctNeeds ReviewOPP-31800
OK-717Close Outcome04 OctNeeds ReviewOPP-73573
OK-541Record Tutoring Session10 OctNeeds ReviewOPP-57547
OK-702Correct Scope05 OctNeeds ReviewOPP-45477
6 of 6 records
OK-623Operation receipts · OR-87087
Qualify Opportunity
Recorded at12 Oct
StatusNeeds Review
Parent opportunityOPP-33817
Example screen with sample data

What you can do

Check what happened and who decided

A submitted tutoring session needs more than a status change. Review Decisions store the decision, reviewer, decision date, source revision, independence marker and reason. They link to the opportunity and, where applicable, the tutoring session. That lets Operations Coordinator ask whether the decision concerns the current session revision and who made it. A reviewer can choose Approve, Reject or Return as the decision value. The session workflow records an independent review decision before moving the session to Approved.

Operation Receipts are the trail of executed work. A receipt records an operation key, time, type, status and optional external reference, quantity, actor and evidence summary. Qualification, proposal submission, close outcome and tutoring session recording write receipts through their workflows. Receipts can be Pending, Succeeded, Failed, Needs Review or Completed, allowing Operations Coordinator to focus on exceptions instead of guessing from the opportunity stage alone.

How the work is organized

  • Decide on the source. Review the submitted session and its current revision before recording the verdict.
  • Follow the operation. Read the receipt’s type and status with the related opportunity and actor.
  • Keep supporting material. Attach a document, note, receipt or other supported item to the opportunity or tutoring session.

What to agree during setup

Decide the separation between session preparation and review. The Session Reviewer should not decide on their own session; independence is recorded on the decision. Decide what a reason should say when a case is rejected or returned, so the Tutor can correct the right information. The record has a source revision and decision date, which help distinguish an old verdict from one made after a change.

Agree how the team investigates a receipt marked Needs Review. The Operations Coordinator should inspect the operation type, recorded time, key and linked opportunity, then check the underlying activity or session. A failed operation should be investigated from its source rather than treated as a successful stage move. Decide how supporting documents are named and linked so a reviewer can find them from the relevant opportunity or session.

Check the handoff on an actual case

A Tutor submits a session after a school program day. The Session Reviewer opens the submitted record, checks the session reference and supporting note, then records an approval with the current revision. The operation receipt records the session action. If a receipt later needs review, Operations Coordinator traces it to the opportunity and checks the session and decision before resolving the discrepancy with the named owner. The evidence stays connected to the actual case rather than in a separate folder without context.

What your team sees

  • Receipts Needing Review — Operation exceptions with type, time and linked opportunity.
  • Sessions Awaiting Review — The submitted session queue for independent decisions.
  • Approved Sessions — Session outcomes that can be checked against decisions and receipts.

Follow the work through

What it keeps track of

Data model
Review decisions
A verdict on a submitted receipt or session, used to approve or reject it before it counts toward billing.
Operation receipts
A logged proof that something happened, like a session or payment, used to confirm work actually took place.
Record attachments
A file or link tied to a deal or session, used to keep supporting documents easy to find.
Tutoring sessions
Tutoring session records: tutor, session date, quantity, reference number and review lifecycle.
Opportunities
A potential deal with an account, used to track its value, stage, and chances of closing.
Team members
A staff member with access to the system, used to assign ownership and track who's doing what.

Who uses it

Permissions
Session Reviewer
Records decisions.
Operations Coordinator
Investigates receipts and supporting evidence.
CRM Admin
Controls staff and access setup.

Set up Schools/Tutoring CRM your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started