Staging draft Work in progress · For review; coverage and acceptance incomplete

Understand completed record work¶

Registry teams can preserve evidence that a retrieval, review, compliance action or stewardship task was completed for a record. This connects the work to the record, the person recording it, its result and supporting evidence. Managers can use that information to investigate the reported outcome and follow up on corrections.

Availability: the backend supports these completion records. A connected app journey and matching final-design flow have not yet been established by this review. This page explains the capability and its limits; it does not describe an available button or form. Your organization must confirm its approved way to record this work.

Choose the kind of work¶

Kind	Purpose	What completion does not establish
Retrieval	Record that work to retrieve a record was completed	Merely opening, searching for or downloading a document is not this completion. It does not prove delivery to a recipient.
Review	Record a completed review and its reported result	It does not move a workflow approval forward or replace the decision recorded in that workflow.
Compliance work	Record a completed compliance action and its reported result	It is not an independent compliance assessment, certification or guarantee that every obligation has been met.
Stewardship	Record completed work to care for or maintain the record, with evidence of the reported outcome	It does not automatically file, reclassify, close or dispose of the record.

The completion describes work already performed. It does not create an assignment, schedule the work or establish an in-progress operation. Filing, process completion and retention/disposal have their own rules. Read the document and process guide for the effects of a linked process's outcome.

Information the organization needs¶

Before recording completion, establish the correct organization and record, the kind of work, its result and the evidence supporting that result. The current capability requires:

A result and a reference to the supporting evidence.
When the work started and when it finished. Completion cannot precede the start.
A due time when one applies. Work completed after a supplied due time is recorded as late in the contribution evidence.

Use accurate times and an evidence reference that authorized reviewers can understand and retrieve through the organization's approved channels. The completion stores the reference as text; it does not itself retrieve that evidence or independently establish that the reported work happened. Avoid putting confidential content or access credentials in the reference.

The signed-in person making the completion is recorded as its contributor. This input does not allow another employee to be selected for credit or additional participants to be assigned. A manager entering work for someone else must resolve that attribution before using the capability as employee-performance evidence.

Internal completion requires record-management permission in the correct organization. Viewing a record or holding a public intake receipt is insufficient. Eligibility for sensitive personnel records and special record stages still needs explicit review before adoption; this guide does not authorize those uses.

Check the reported result carefully¶

The current implementation accepts a result description without a controlled list of choices. For review and compliance work, only the result Rejected is interpreted as rejection; letter case does not matter. Other text is treated as acceptance for a review and approval for compliance work. For example, entering Failed does not currently produce a rejected result.

Agree the supported outcome choices with the product owner before adoption. Do not infer a negative decision from free text or assume the software has independently accepted the underlying evidence. A rejected review also records that rework is required; a rejected compliance action does not set that same rework indicator.

For retrieval and stewardship, recording completion does not supply a separate accepted/rejected decision. Stewardship carries the reported result and evidence into its contribution record, without inventing a monetary value or quantified benefit.

What happens after a successful save¶

A completed operation is added to the record and contribution evidence is prepared for downstream reporting. Its actor, timing, record reference and reported outcome support later assessment. Saving does not prove that downstream reports have received or displayed the evidence yet.

The current response confirms success without returning a new operation reference or correction revision. The general record detail and Activity view do not supply an operation history through the inspected contract. Ask support to reconcile the saved completion if its identity is needed later; do not expect an Activity entry to be its receipt.

The completion updates the record's modification information, but does not change its processing, custody, filing or retention state. It does not add a document, complete a workflow task or publish an ordinary Records Activity entry. Check the appropriate record or process view for those separate outcomes.

Attaching a messaging or email reference as independently verified communication proof is currently unavailable through these completion actions. Do not treat a supplied evidence reference as verification of the message's author or a separate verifier.

Correct or withdraw earlier evidence¶

Corrections preserve the earlier contribution identity and add a new revision. They require the original evidence identity and revision, the kind of correction, and a reason. The original must belong to the same record and the same kind of completed work. These are support/integration references, not the record's ordinary official number.

The backend recognizes correction and retraction requests. A retraction records a corrective revision; it does not erase the original record or establish that every downstream report has already removed its effect. Coordinate the change with the responsible team and verify the resulting report separately.

The available completion response and general detail view do not yet provide a self-service way to obtain those original references. Concurrent corrections and uncertain results require reconciliation before another attempt. Keep the original evidence and reason for change; do not create an unrelated new completion as a substitute for correcting the first one.

Recover and interpret the evidence¶

Situation	Next step
Permission is denied or the record cannot be found	Check the organization and record with the responsible registry team. Do not assume general viewing access permits completion.
Result, proof reference or times are invalid	Correct the information. Use an agreed outcome and ensure the finish is not before the start.
Communication proof is rejected	Ask support about the unsupported verification path. Do not disguise it as verified communication evidence.
Save times out or its outcome is unclear	Preserve the original request details and ask support to reconcile it before submitting another completion.
A correction is rejected	Check the original completion's identity, revision, record and operation kind with support. Keep the original and corrected evidence distinct.
Reports have not changed	Confirm that completion was saved, then ask support to trace downstream processing. Do not repeatedly complete the work to force a report update.

For help, provide the organization, official record reference, operation kind, approximate save time and safe error text through the approved support channel. Include proof contents only when that channel and its recipient are authorized to receive them.

For executives and managers, these records describe reported work and its evidence. Their count is not a score or a guarantee of compliance. A late completion or a correction does not by itself show who caused the problem. Cause and employee responsibility can remain unresolved; the reporting team must assess the evidence and applicable rules before drawing conclusions.