Review and evidence

Review Decisions records a subject type and reference, decision, reviewer, date, and notes. It can identify a Service Entry, Time Entry, Expense, Milestone, or Engagement as the subject. The service approval operation writes a decision for valid service lines. Milestone Approver can record a separate manual decision after checking a deliverable. A decision should point to the work being reviewed; a generic note without a reference cannot support a useful handoff.

Operation Receipts records what an action attempted and whether it Succeeded, Failed, or was Partial. Service approval, milestone invoice, and payment receipt operations each leave an operation result. The result is separate from the underlying record’s status. A Failed receipt for service approval means the submitted line was not approved. A Failed milestone invoice receipt means the approved milestone was not moved to Invoiced.

• Decision record. Review Decisions identifies the subject, reviewer reference, decision, date, and explanation.
• Executed result. Operation Receipts identifies the operation type, reference, time, result, and actor.
• Supporting file. Record Attachments links a file and kind to a parent record, with uploader and upload date.

Choose who can make each approval decision and who can see the decision history. Consultant supplies evidence while Service Reviewer checks the resulting approval and exception records. Define when a person records Rejected or Returned and what notes are required. Reviewers should understand that a submitted service line remains Submitted when a guard fails; the failure is an operation result, not an approval.

Agree how contract, SOW, receipt, deliverable, and change order files are named and linked. The attachment record contains the parent table name and parent record identifier; the team should use the correct parent so the file appears in the intended case. A URL should point to a source the authorized team can actually open. Admin should define retention and access in the chosen document system.

A Consultant submits a service line for eight billable hours. The submission passes the approval check and moves to Approved. Service Reviewer checks the engagement and finds both the decision row and a successful Service Approval receipt. Repeating the case with no hours must leave the line Submitted and produce a Failed receipt. The reviewer sends it back for correction rather than counting it as approved value.

For a milestone, Engagement Manager adds a deliverable file to the milestone’s record. Milestone Approver checks the work, marks the milestone Approved, and may record a separate manual decision. Billing Specialist runs the invoice action only after that status change and checks its receipt. Later, a payment marked Received creates a separate Payment Record receipt. Each result belongs to a different step, even though all steps serve the same engagement.

• Rejected Service Entries — Service lines that need correction or a delivery discussion.
• Milestones Ready To Invoice — Accepted deliverables waiting for the invoice operation.

See delivery review and milestone to invoice. The roles page explains decision ownership.