Understand response work and reviews¶
Formal correspondence can lead to work that needs its own evidence. A member of staff may finish a response to an official letter, or a reviewer may record whether work associated with a memo or letter is accepted. These records help explain who did the work, when it happened and what evidence supports it.
Availability: The backend has response-completion and review operations. Their complete Final Screens journeys, connected frontend controls, designated-reviewer access and environment delivery have not been verified. This draft explains the available behavior and its limits; it does not provide an unverified sequence of buttons. The frontend remains work in progress. Your organization's approved operating procedure is needed before relying on these records for a formal decision.
Choose the right kind of evidence¶
| Record or action | What it establishes | What needs separate evidence |
|---|---|---|
| Response work completed | Someone recorded completed work associated with an official letter, with a result, evidence reference and times. | Whether a recipient received, opened or acknowledged the letter; whether a reply was actually sent. |
| Review accepted | Someone recorded an accepted review of a memo or official letter. | Formal approval to publish or issue the correspondence. |
| Review rejected | Someone recorded a rejected review; the contribution evidence marks rework as required. | Assignment, notification, scheduling or completion of that rework. |
| Letter delivered | Delivery evidence indicates a delivery outcome. | Completion or quality of work done in response. |
| HR-query response | A staff member's response within the HR case process. | This is a separate case capability, not the correspondence completion record described here. |
Use memo lifecycle, letter lifecycle, delivery and evidence and HR notices for the related processes. A review does not approve, reject, publish, issue, recall or archive the correspondence itself. Recording response work does not send a letter or create a new reply document.
Information needed for a trustworthy record¶
Both operations need a result, an evidence reference, a start time and a completion time. The completion cannot precede the start. Response work also needs a due time and a reference connecting it to the work performed. A review can include a due time, but one is not required by the inspected operation.
For a review, the supported decisions are Accepted and Rejected. For response work, the inspected service accepts a supplied result description rather than enforcing a fixed set of response outcomes. The person recorded as the contributor is the signed-in person performing the operation. It is not a freely selected colleague.
Times must be provided consistently in UTC by the connected application. A timestamp describes the claimed work period; it does not prove that someone worked continuously during that interval. The service does not turn the interval into verified effort or independently confirm that a stated due time is the organization's agreed deadline. Check the original work instruction when a timing result matters.
An evidence reference points readers or authorized investigators toward the supporting material. The current completion operation requires a nonblank reference but does not independently open and verify that material. A saved reference therefore needs human or separately governed verification. Use approved material and ensure the intended reviewer can access it; do not assume that attaching a reference grants new document access.
Email and messaging references are a further limitation. The current public completion operations reject those communication references because they cannot resolve their proof authoritatively. Do not remove the communication context merely to make a rejected submission pass, or describe an ordinary reference as independently verified communication evidence. Ask the feature owner for a supported evidence path.
Authority and status limits¶
Completing official-letter response work requires the current letter-creation permission. The shared review operation requires an authenticated tenant identity, but the inspected path does not enforce a separate designated reviewer, a different reviewer from the author, or an artifact-specific review permission. Administrators must resolve and verify the intended review authority before treating the capability as a controlled approval process.
The underlying response and review methods do not restrict the correspondence to a particular lifecycle stage. They can record evidence without changing the memo or letter status. A recorded review therefore does not prove that a document was issued, published or still active when the work was assessed. Check the document's status and your organization's policy independently, especially for drafts, recalled items and archived correspondence.
These operations also do not add an ordinary lifecycle-history entry. A successful save does not establish that the current detail page will display the new response, review or its evidence. The inspected reading contracts do not expose a complete response/review history. A suitable display and verification journey remains unfinished.
Correcting earlier evidence¶
A correction retains the earlier record and appends a revision. It requires the original evidence identity and revision, a correction type and a reason. Correction and Retraction are supported types. A retraction is recorded as evidence; it does not delete the correspondence or erase the earlier record.
The service checks that the referenced evidence belongs to the same organization, correspondence item and kind of operation. A response cannot be corrected by pointing to a review of a different letter. The correction also records the person making it and the newly supplied evidence and times.
The current completion result does not give the user the evidence identifiers needed for a later correction, and the ordinary reading contract does not supply a full revision history. An authorized support or integration process is needed to locate and verify them. The inspected correction path also does not require the original contributor to make the correction or automatically choose the latest revision. Do not guess an earlier identity or repeatedly submit competing corrections; the latest accepted evidence must be established first.
What to do when the result is uncertain¶
| Situation | Recommended response |
|---|---|
| A review was saved but the memo still needs approval | Continue the separate approval process. Review evidence does not perform that transition. |
| The evidence reference was accepted but its material cannot be opened | Verify access and the actual supporting material. Acceptance of a reference is not proof that it exists or is readable. |
| An email or message reference is rejected | Preserve the intended evidence and ask for the supported integration path. Do not substitute a claim of independent verification. |
| A request times out | Treat the outcome as uncertain. Have the connected application or support reconcile the same operation before submitting a new one. A timeout does not prove that nothing was saved. |
| A correction conflicts with another correction | Establish the saved revision and intended change before retrying. Avoid a second unrelated completion merely to bypass the conflict. |
| A review record is absent from the visible history | Ask support to distinguish persistence, the detail display and downstream reporting. Absence from lifecycle history alone does not establish a failed save. |
Keep the correspondence reference, operation type, approximate time, signed-in identity and non-sensitive error message when requesting help. Send confidential evidence through an approved channel, not a public support post.
How managers should interpret the evidence¶
Completed response work contributes completion evidence. A review contributes an accepted or rejected assessment, and a rejected review carries a rework indicator. Completion after the supplied due time is treated as adverse evidence; a correction is marked corrective. These are inputs to later assessment, not a complete measure of staff performance, verified effort, an automatic penalty or a new task assignment.
Reporting evidence and data requests explains the broader journal, reconciliation and tenant-data boundaries. The contribution is published asynchronously. Saving correspondence evidence does not prove that analytics has received, reconciled or displayed it. Managers should check the underlying evidence, correction history, reviewer authority and reporting currentness before drawing conclusions. This guide establishes no additional price, guaranteed reporting delay or personnel-policy decision.