A trusted timestamp is a digital seal issued by an independent, specialized authority, proving that a particular document existed with its current content at a specific moment in time, without that authority seeing the content of the document itself. It is also known as time-stamping. In electronic contracts, the timestamp answers a question that seems simple but is decisive in many disputes: when exactly was this contract signed, and has it stayed in the same form since that moment?
In this article we explain how a timestamp works, why a computer or server clock is not enough, when the time of signing becomes an important legal and financial matter, how to verify a timestamp yourself, and the common mistakes in handling it. For each point we cover why it matters, how to apply it, the common mistake, and a practical example, followed by a checklist and frequently asked questions.
First: Why Does the Time of Signing Matter?
Why it matters: Many people think the date is a minor detail in a contract, until a dispute arises that turns entirely on a particular day or hour. The time of signing determines when obligations began, when deadlines expire, and who takes precedence among conflicting rights.
| Situation | Why time settles it |
|---|---|
| Deadline for accepting an offer | Did the customer sign before the offer expired or after? |
| Non-compete clause | When did its term begin and when does it end? |
| Conflict between two contracts | Which was concluded first when the same thing was sold to two parties? |
| Expiry of a signing certificate | Did the signature take place before the certificate expired or was revoked? |
| Legal notices | Was the notice sent by the agreed date? |
| Changes in prices or regulations | Was the contract concluded before the change, so that the old terms apply? |
Common mistake: Settling for a date written in the text of the contract. A written date can be given any value and does not prove when the contract was actually signed.
Example: A property owner signed a lease with a tenant, then signed another contract for the same property with a second person. Each claimed that his contract came first. The first contract had its time fixed by a trusted timestamp, so the order was settled without dispute.
Second: Why Isn't a Computer or Server Clock Enough?
Why it matters: Every device has a clock, and every file has a creation and modification date. But all of these times are under the control of whoever owns the device, and can be changed with a few clicks.
- The signatory's device clock: He can change it before signing so that the signature appears at another date.
- The file's date: It changes with copying and moving, and can be edited with simple tools.
- The platform's server clock: More accurate, but it remains under the control of one party, and the opponent may challenge it.
- A timestamp from an independent authority: No party to the contract controls it, and it can be verified with the authority's keys.
Common mistake: Submitting "file properties" as evidence of the signing date. These properties do not withstand any serious technical examination.
Example: A company claimed it had sent a contract termination notice on time and submitted a file whose date matched the deadline. But the opponent showed that a file's date can be edited, and it was not relied upon. Had the notice been fixed with a timestamp, there would have been no room for challenge.
Third: How Does a Trusted Timestamp Work?
Why it matters: Understanding the mechanism, even in simplified form, lets you trust the timestamp and know how to verify it. The clever idea in it is that the authority seals the document without seeing it.
- Computing the hash: A unique digital fingerprint (hash) is computed for the signed document. It is a long number that changes completely if a single character in the document changes.
- Sending the hash alone: The hash, not the document, is sent to the timestamp authority.
- Sealing: The authority adds the current time from its accurate clock to the hash, then signs both together with its key.
- Return: The signed timestamp comes back and is stored with the document.
- Later verification: The document's hash is recalculated and the authority's signature on the timestamp is verified. If the hash matches, it is established that the document existed with its content at that time.
Why the authority does not see the document: Because it deals with the hash alone, and a hash cannot be reversed to extract the content. This fully protects the confidentiality of the contract.
Common mistake: Assuming that a timestamp means the authority "reviewed the contract and approved it." The authority does not attest to the content or its validity, only to its existence at a particular moment.
Fourth: The Timestamp and the Document Hash Work Together
Why it matters: The hash alone proves the document has not changed since it was computed, but it does not prove when it was computed. The timestamp alone proves a time for some hash. Together they prove that this particular document existed with this content at this time.
| Element | What it proves | What it does not prove on its own |
|---|---|---|
| Document hash | That the content has not changed | When it was signed |
| Timestamp | The time the hash existed | The signatory's identity |
| Signatory verification | Who signed | Exactly when, and whether the document changed |
| All three together | Who signed, what they signed, and when | — |
In Wthaiq, the document's hash is computed and the time of signing is fixed by a trusted timestamp from independent timestamp authorities, and both are kept together in the evidence report with the result of verifying the signatory.
Example: A supplier claimed the contract had been amended after it was signed. The hash was recalculated and matched the recorded one, and the timestamp verified that this hash existed at the moment of signing, so it was established that the text had not changed since that time.
Fifth: The Timestamp and Signing with a Digital Certificate
Why it matters: A digital certificate has a validity period, and it may be revoked before it expires if the token is lost. If a document is signed with a certificate that later expires or is revoked, how do you prove the signature took place while it was valid?
How the timestamp solves the problem: The timestamp proves that the signature existed at a particular moment. If the certificate was valid at that moment, the signature remains valid after the certificate later expires or is revoked. Without the timestamp, doubt may be raised that the signature took place after revocation.
Common mistake: Signing with a token without a timestamp, then facing the question years later: did you sign before your certificate was revoked or after?
Example: A manager signed contracts with his token and then left the company, and his certificate was revoked. When a party challenged one of the contracts on the ground that the certificate was revoked, the timestamp showed that the signature took place months before the revocation, and the challenge failed.
Sixth: How Do You Verify a Timestamp?
Why it matters: The value of a timestamp lies in its being independently verifiable, without having to trust the company that supplied it. You, the other party and the court are all entitled to verify it.
- Through the verification page: The platform displays the timestamp time and the result of verifying it, and the file's hash can be matched.
- Through PDF readers: If the timestamp is embedded in the file, supporting software shows its time and status.
- Through technical tools: An expert can verify the authority's signature on the timestamp with its public keys.
Common mistake: Relying on a time written on a text page with no means of verification, which is just a statement that could be changed.
Seventh: Who Issues Timestamps?
Why it matters: The value of a timestamp comes from the value of the authority that issued it. A timestamp issued by a well-known authority with an accurate clock and trusted procedures is stronger than one a company issues for itself.
How to assess this: Ask the platform you use: which authority issues the timestamps? Is it independent of the platform? Can its timestamps be verified with public tools? Some platforms use more than one timestamp authority, so that sealing does not stop if one authority goes down.
Common mistake: Confusing the timestamp authority with the certification provider that issues signing certificates. The same entity may offer both services, or they may be two different entities.
Eighth: When Is a Timestamp Decisive?
Why it matters: Every contract benefits from a timestamp, but for some contracts a great deal depends on it.
| Type of contract or document | Why time matters |
|---|---|
| Bids and tenders | Proving submission before the deadline |
| Sale and lease contracts | Settling priority in case of conflict |
| Termination and renewal notices | Proving compliance with the deadline |
| Employment contracts | Calculating probation and non-compete periods |
| Intellectual property rights | Proving the existence of a work or idea at a particular date |
| Documents signed with a certificate | Proving the certificate was valid at the time of signing |
Example: A freelance designer sent his designs to a client within a signed, time-fixed proposal. When similar designs appeared at a competitor, he was able to prove that his designs existed before that, at a specific date.
Ninth: Drafting the Time Clause in the Contract
It is advisable for the contract to state expressly that the recognized time of signing is the time fixed by the timestamp, so that no dispute arises over a written date or the clock on one party's device:
For the purpose of determining the date and time of each party's signature on this contract, and the date of its conclusion, the time fixed by the trusted timestamp recorded in the signing evidence record shall be relied upon, calculated in Coordinated Universal Time with its equivalent in Cairo time stated.
Common mistake: Writing a fixed date in the contract before signing, then signing is delayed by two weeks, and time periods begin to run from a date on which the contract was never signed.
Tenth: The Timestamp in Multi-Party Contracts
Why it matters: When several parties sign a contract on different days, each signature has its own time, and the contract has a conclusion time, which is the moment the last signature is completed. Obligations may differ according to these times: the first payment may fall due a week after conclusion, and the guarantor may not be bound until after the debtor signs. If the time of each signature is not fixed, calculating these dates becomes a matter of dispute.
How to apply it: Give each signature its own independent timestamp, and a timestamp for the final version on completion, and state in the contract that the conclusion date is the time of the last signature according to the timestamp. Review the dates in the contract so that they are calculated from the conclusion date, not from a date written in advance. If the parties are in different countries, use Coordinated Universal Time in the record and show the local-time equivalent for each party, so that the difference in hours does not look like a contradiction.
Common mistake: Each party treating the contract as effective from the day he signed, so one party starts performing before the others have signed, then one backs out and the contract is never completed, leaving what was performed without a clear basis.
Example: A distribution contract between a factory and distributors in two governorates was signed by the factory on Sunday, the first distributor on Tuesday, and the second on Thursday. The contract stated that exclusive territories begin from the conclusion date, and the timestamp showed that it was Thursday at 4 p.m. So when the first distributor sold in the second's territory on Wednesday, that was not a breach of the contract, because exclusivity had not yet begun, and the matter was settled in minutes.
Timestamp Checklist
- Is the time of signing fixed by a timestamp from an independent authority?
- Is the timestamp kept with the document hash in the evidence report?
- Can the timestamp be verified without going back to the platform alone?
- Is signing with a token paired with a timestamp?
- Does the contract specify that the recognized time is the timestamp time?
- Are the deadlines in the contract calculated from the actual completion date?
Frequently Asked Questions
Does the timestamp authority see the content of my contract?
No. It receives only the document's hash, and the content cannot be extracted from a hash.
What is the difference between a timestamp and the written date of the contract?
A written date can be given any value, whereas the timestamp proves the actual time from an independent authority and can be verified.
Does every contract need a timestamp?
Every contract benefits from one, and it becomes decisive in contracts where rights depend on time.
Does the timestamp remain valid after years?
Yes. It can be verified later with the issuing authority's keys, and it is wise to keep it with the document and the evidence report.
In what time zone is the timestamp recorded?
Usually in Coordinated Universal Time, and it can be converted to local time when displayed.
Can an old document be timestamped now?
Yes, but the timestamp will prove that the document existed with its content at the present moment of sealing, not at its old date. That is why a timestamp's real value lies in being added at the moment of signing itself, not months afterward. Even so, timestamping an old document that matters today protects it from any later claim that it was amended after today, which is better than leaving it with no protection at all.
Is a timestamp different from a company seal?
Yes. A company seal indicates that the document was issued by the company with its approval, whereas a timestamp indicates the time the document existed with its content, and it is issued by an independent authority unconnected to the parties. A single contract may carry both, each with its own function.
Conclusion
A trusted timestamp is what makes the time of signing a provable fact rather than a claim that can be challenged. It works with the document hash to prove that this particular contract existed with its content at a specific moment, and it protects a certificate-based signature after the certificate expires. If you want every contract you sign to carry a timestamp from an independent authority, start sending your contracts through Wthaiq. Make the timestamp a standing part of every contract, not a feature requested only for large ones, because you do not know which contract will one day become the subject of a dispute over its date, and you cannot add a timestamp to a moment that has passed.
This article is for general awareness and does not constitute legal advice.