1. Skill Development Platform
  2. Features
  3. Completion and operations
Feature · Completion and operations

Completion and operations

Confirm learning completion from verified assessment evidence and resolve uncertain operations through their receipts.

OverviewOpen Operation Receipts
Skill Development Platform · Completion and operations

Open Operation Receipts

Operation receipts

New
ParentActionOperation keyExpected revisionOccurred atExternal reference
LR-18835ACT-678OK-79439016 OctER-390
LR-98259ACT-149OK-31553006 OctER-824
LR-74273ACT-732OK-13022024 OctER-227
LR-35677ACT-454OK-82059008 OctER-892
LR-25017ACT-979OK-25956019 OctER-478
6 of 6 records
ACT-678Operation receipts · OR-44654
Pending
ParentLR-18835
Operation keyOK-794
Expected revision390
Occurred at16 Oct
External referenceER-390
Example screen with sample data

What you can do

Know which result has been confirmed

Program Administrator requests learning completion when the current request and a verified assessment agree. The guarded command checks organization scope and expected revision before recording the result. Learning completion and skill credential issuance are separate outcomes, each requiring its own evidence and operation context.

Operation receipts retain the action, expected revision and occurrence date with a result showing whether the operation is pending, completed, failed or needs review. Effect and external references help the team inspect what the operation recorded. A failure reason directs the responsible person to the unresolved issue, while the operation identity helps distinguish an earlier result from a new request.

How the work is organized

  • Completion check. The command requires verified Assessment evidence linked to the current learning request. Attendance or a scheduling receipt cannot satisfy that requirement by itself.
  • Operation follow-up. The team examines unresolved receipts against the parent request and its evidence. A completed receipt confirms the stated operation’s result, so its action must be read alongside the state.
  • Read-first reconciliation. Reconciliation compares locally expected effects and marks the receipt as completed or needing review. It checks the recorded outcome without repeating an external operation.

What to agree during setup

Agree who decides that the evidence is ready for the completion command and how they check the request revision. Define the cohort-level evidence review expected before making that request. A learner count and an individual evidence line need an operating procedure that the Program Administrator can explain.

Set an owner for pending or failed receipts and those needing review. The person investigating an uncertain operation should inspect its action and effect references before trying anything again. Agree who may request a correction or withdrawal, what reason must be retained and how existing assessment and credential evidence will be handled. Preserve the decision trail so an Auditor can distinguish the original result from later follow-up.

Check the handoff on an actual case

Use a scheduled rehearsal request with a verified assessment line. Have Program Administrator request completion for the current revision and inspect the saved request and receipt. Ask Auditor to explain which evidence supports completion and which separate record would establish a credential outcome.

Then examine a receipt whose expected effect cannot be found in the local request evidence. Reconciliation should flag the receipt for review with a clear explanation of the discrepancy rather than replaying the operation. For a correction case, submit the current request identity, revision and reason through the supported action and retain the earlier evidence. Repeat a completion request with the same operation identity and confirm that the saved outcome is reused without duplicating its effects.

What your team sees

  • Open Operation Receipts — Pending, failed and review-needed actions with their expected revision and failure reason.
  • Completed Learning Requests — Requests whose completion outcome is recorded for evidence inspection.
  • Credential Evidence — Credential-type evidence kept distinct from attendance and assessment entries.

Follow the work through

Use verify learning completion and corrections and reconciliation to keep the final outcome explainable.

What it keeps track of

Data model
Learning requests
Enrollment and delivery requests for a program cohort, tracked from request through completion.
Learning evidence
Individual pieces of attendance, assessment, credential or payment evidence recorded against a learning request.
Operation receipts
Durable receipts for every guarded operation executed against a learning request.
Review decisions
Recorded approve, reject or return decisions made by an independent reviewer against a specific source revision.
Credential reviews
Credential review cases that carry a skill, assessor score and evidence reference to an independent reviewer.
Record attachments
Files attached to a learning request as supporting evidence.

Who uses it

Permissions
Program Administrator
Requests completion and authorized corrections.
Learning Coordinator
Follows unresolved request work.
Credential Reviewer
Investigates issuance questions.
Auditor
Reads the evidence supporting each result.

Set up Skill Development Platform your way.

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

How to get started