Who Signed, When and From Where? Reading a Contract’s Audit Trail

1. Who signed? Connect activity with identity

A signature on a page is only part of a contract’s story. A reviewer also needs to understand who participated, what happened and whether the file being reviewed matches the completed agreement. WQ3 records every action on a document, from sending to final signature, in an audit trail that accompanies the completion certificate.

Start with the signer names and the signing level used by each person. WQ3 offers exactly three levels: electronic signature, remote signing and token signing. Different levels can be selected for individual signers within one document, so do not assume everyone used the same method.

Keep account identity separate from signing activity. WQ3 provides identity checks and a private signing link for each signer. When the signer’s identity must be proven, require an eKYC-verified account with any signing level; eKYC is an account-verification add-on, not another level. Separately, check whether someone signing for an organisation has authority to bind it. A recorded name or matching document fingerprint does not establish that authority.

2. When was it signed? Read the sequence

WQ3’s public check page shows signer names, signature levels and the timestamp of every step. These details help reviewers examine the recorded sequence rather than relying only on a date written inside the contract. Read the timestamps alongside the corresponding actions to understand how the document reached completion.

For an internal review, compare the sequence with the transaction you expected. Are the signers the intended parties? Were the selected signing levels appropriate? If a decision depends on the order of events, consult the audit trail rather than relying on a verification result alone. Do not infer that separate internal approvals took place unless those approvals are documented.

3. From where? Distinguish workflow evidence from location

“From where” can mean the route through which someone signed or their physical location at the time. WQ3’s private signing links, recorded actions and timestamps provide context about the signing workflow. They should not be treated as proof that a person was in a particular office, city or country.

The verification details described for WQ3 include names, signing levels and timestamps—not a stated geographic-location record. If location is important to your review, define exactly what you need to establish and identify separate supporting evidence. Keep that question distinct from identity and timing, rather than expecting one audit record to answer all three.

4. Tie the evidence to the exact contract

Even a clear signing history must be connected to the file you will actually use. Scan the QR code on the final file or completion certificate to open WQ3’s public check page without an account. Verification compares the file’s SHA-256 fingerprint with the stored fingerprint, helping establish whether the copy matches the version associated with the signing record.

Review the fingerprint comparison alongside the signer details and timestamps. If the fingerprints differ, pause and investigate the copy; visual similarity is not enough, and a mismatch alone does not explain who changed the file or why.

Keep the exact file you checked together with its completion certificate and verification reference. As a practical filing habit, note who reviewed it, when and any unresolved questions. This gives the next reviewer a clear connection between the agreement, its signing history and the evidence used in your decision.