Review and evidence

Trace approvals, operation outcomes and files back to cohort work. Review decisions stores subject type, reference, reviewer and decision. Operation receipts stores operation type, result, actor and date. Record attachments attaches files through a parent table name and record ID.

• Record owner. Delivery Reviewer examines automatic session decisions and failed check receipts. Billing Coordinator checks invoice and payment operation results. Program Manager uses attachments and decisions to explain the cohort history.
• Shared context. The cohort engagement connects sponsoring clients, delivery activity and later billing. Staff use the same engagement link when a question crosses teams.
• Review point. Check the record and its related status before the next owner acts. Keep the original item available when a correction is needed.

Agree who can attach contracts, receipts and course deliverables, and how a reviewer identifies the subject of a decision. Preserve the original failed receipt when correcting work; it explains why an item waited in the queue. Make the handoff owner explicit so a pending record has someone who can resolve it. Use a real cohort during rehearsal and compare the visible record with the source agreement or delivery note.

A submitted session fails its approval guard because hours are empty. The session remains Submitted, while a Failed operation receipt records the attempt. After the instructor corrects and resubmits it, a successful workflow check produces a review decision and a new receipt. The reviewer can compare the decision, actor and time with the session and its cohort. Trace the change from the source record to the linked cohort and its relevant list. Check the date, owner and amount against the underlying teaching or billing event. Correct the source item when they differ, then check the cohort totals again.

For each operation, inspect its result, actor and reference together. A Succeeded receipt records the operation outcome; a Failed receipt explains why the source item did not advance. The reviewer should keep both when an issue is corrected. Attachments supply supporting context, while the linked session, milestone or tuition record remains the place to check the current business state.

• Rejected Delivered Sessions — Sessions requiring delivery review after a recorded rejection.
• Certificate Billing Exceptions — Milestones with billing state that merits inspection.

See cohort setup, session review, milestone billing and tuition collection. Use the data model to trace the exact record links.