Read events according to what they prove
Sending, delivery, viewing, signing, and file generation are different events. Only treat an event as recorded when your system provides it; do not infer a signature from a message delivery receipt.
A timestamp needs context: which action, which request, and which time zone? A technical error or repeated delivery attempt may explain why a recipient saw more than one message.
Review one completed request
1. Identify the request and the document version involved.
2. Compare the available activity or status records with the expected business steps.
3. Open the final PDF and check that it matches the request. Investigate missing events or inconsistent status before treating the record as complete.
Decide what records you need to keep
Khtoom provides workflow status and operational records. Confirm which activity details are accessible to your role and whether the export you need is available in your account.
A history screen alone does not establish immutability, independent timestamping, or a signer’s identity. If those are requirements, evaluate the evidence and technical controls separately.
FAQ
Does “sent” mean the document was signed?
No. Sending and signing are separate steps. Check the completion status and the resulting file.
Is every activity log a certificate of signing?
No. Check which events it contains, how they are associated with the document, and whether it meets the record requirements of the receiving organization.