Application event
The platform records when an action occurred within its operational chronology.
TIMESTAMP GUIDE
Application or qualified timestamp: do not confuse the evidence.
Recording an event time is useful, but it is not automatically a qualified electronic timestamp. Product wording and evidence files must identify the actual source and level.
Use the control that matches the real need. Keep the result understandable and exportable.
Signature, Identity and Mail remain separate products and connect when the workflow requires it.
WHAT YOU CAN DO
Describe time evidence precisely
Choose the capabilities that match your workflow and keep every step easy to understand.
Document linkage
The event time is connected to a document fingerprint, person, action or delivery state.
Qualified timestamp
This requires an explicitly identified qualified trust service and must not be implied by ordinary logging.
FROM ACTION TO EVIDENCE
A clear result for every step.
Compare the product used, the control applied and the result returned at each step.
| Need | Availability or product | Control | Output |
|---|---|---|---|
| Application timestamp | Platform event time | Available | Operational chronology |
| Document fingerprint | Integrity linkage | Available | Detects a changed file |
| Qualified timestamp | Qualified third-party service | Only when explicitly supplied | Separate qualified evidence |
| Public wording | State the actual level | Always | No overclaim |
Need a precise scope? We map the expected result, controls and evidence before deployment.Talk to SignCloud →
READY FOR A REAL WORKFLOW
Start with the outcome you need.
We will identify the right SignCloud product, recipient journey and evidence level for your use case.