Regulations and compliance · Practical guide

GMP timestamps and time synchronisation: reconstructing the sequence of events

A result appears to have been released before measurement, an export predates its import or two events show the same local time. The cause might be a process error, different time zones or clocks that have drifted apart. QA and IT need evidence that distinguishes these explanations and establishes the actual sequence.

Table of contents

At a glance

What should GMP timestamps allow you to demonstrate?

Annex 11 section 12.4 expects systems to record identity, date and time when data are entered, changed, confirmed or deleted. PIC/S addresses synchronised clocks and authorised changes. Global systems may need the time zone in the timestamp (sections 9.5 and 9.8). Test the full path between connected systems. These sources specify neither a particular protocol nor a universal tolerance in seconds. Accuracy depends on the importance of the event sequence.

  • A local time without time zone context may be ambiguous.
  • Synchronized clocks do not provide scientifically valid event attribution.
  • Accuracy, monitoring, and documentation are aligned with the specific process risk.

1. First, define the temporal statement

This guide addresses human medicinal product GMP. Annex 11 requires, for relevant inputs, modifications, confirmations, or deletions, the assignment of identity, date, and time. PIC/S specifically emphasizes the importance of controlled system clocks and temporal reconstruction. Thus, the guidelines do not prescribe a single technical operating model for all applications.

First, determine which decision depends on sequence: for example, whether a material status was set prior to sampling or which method version applied during evaluation. Only then can it be assessed whether minute deviations are acceptable or already render the data unusable.

Sources: [1] [2]

2. Do not inadvertently equate four time stamps

Applications may handle event time, reception time, storage time, and display time differently. A later import may contain an older substantive event timestamp. This is not automatically a defect, but it should remain detectable. An export must not inadvertently eliminate this distinction if it is required for traceability.

Our own matrix supports the tracing of a specific data pathway. It is not a requirement that every application expand to all four fields. What is needed are the information enabling a reliable understanding of your process.

Self-assessment of a timestamp
QuestionIssue to recordRisk due to uncertainty
When did the event occur? Significance of the technical expertise field Storage time is retained for execution time.
Which clock provided the value? Device, client, or server; controlled source Deviation in timekeeping devices will be unobservedly compared.
In which zone does the statement apply? UTC, Time Offset, or Recoverable Zone Reference The same local time is incorrectly sorted.
What does the interface do? Takeover, conversion and, if applicable, receipt time Double conversion or loss of offset
Who is authorized to modify time entries? Technical Rights and Traceable Modifications Retrospective change remains undetected

Sources: [2] [3] [4]

3. Calculation example: The clock appears to be running backward

The offsets are explicitly defined: Event A carries the timestamp 25.10.2026, 02:50 with UTC+02:00. Event B carries 25.10.2026, 02:10 with UTC+01:00. A corresponds to 00:50 UTC, B corresponds to 01:10 UTC. In reality, there is a twenty-minute gap between A and B; the local time digits alone would suggest that B occurs forty minutes earlier.

The example does not establish any regulatory rule regarding time shift adjustment. Its sole requirement is that the data pathway correctly interprets both time points including their contextual information. If the offset in the export is lost, the unambiguous sequence must not be simply deemed secured.

Own required matrix for time conversion
Test caseInputExpected resultAssessment
Event A 02:50, UTC+02:00 00:50 UTC Original context received
Event B 02:10, UTC+01:00 01:10 UTC B occurs 20 minutes after A
Only local figures compared 02:10 to 02:50 Apparently −40 minutes Do not use as actual sequence
Offset at export removed 02:50 and 02:10 without context Make ambiguity visible No established unique conversion factor
Full import of complete export Time plus respective offset Same time points as in the original No double zone shift

Sources: [3] [2]

4. Evaluate time deviations based on their impact.

A system may display the correct time zone yet still be off by several minutes. A time zone conversion does not correct this error. Therefore, it must be defined which time source is authoritative and how significant deviations are detected. For interconnected systems, the relationship must hold across the entire required data pathway.

A measurable technical difference is initially a finding. What is critical is whether such a difference creates ambiguity regarding the events or decisions involved. In the case of a deviation, historical time stamps must not be silently adjusted to fit. Document what is recorded, what reconstruction is possible, and what uncertainty remains.

Sources: [2] [1] [4]

5. Control changes to time and time zone

Review which users or services have the capability to modify system time, time zone, or application parameters. Authorities should align with the intended operational requirements. A clock may be centrally controlled, while a local application may additionally perform time conversions; therefore, assessing only one technical layer is often insufficient.

Maintenance events are also relevant if they affect the traceability: equipment changes, system restoration, new servers, or modified interfaces may introduce different time configurations. This does not imply a blanket obligation to treat every administrative event as a GMP audit trail entry. Only those actual, relevant changes are assessed.

Sources: [1] [2]

6. Test the timing logic where it is applied

A ping to the time server or a configuration screenshot only verifies a portion of the process. Assess representative end-to-end workflows from data entry through to display or export. During evaluation, compare the significance of the fields, not merely visually similar timestamps.

Appropriate scenarios may include a time offset change, a delayed data transfer, or a controlled simulated time deviation within a test environment. Such tests should not require unsecured adjustment of production system clocks. Expected responses and termination conditions must be predefined; scope and accuracy shall align with process risk.

Sources: [1] [2] [5]

7. Resolve suspicious sequences logically and functionally

When a review identifies a seemingly impossible sequence, first verify the field meaning and the temporal context. A technical entry may occur after the substantive event. A report generated overnight may be based on data from an earlier time period. However, any explanation must be consistent with the available original records.

If the sequence is unclear and significantly impacts decision-making, this represents a genuine gap in traceability. Assess the affected processes and subsequent usage. A general statement such as "The server time was incorrect" neither specifies the time period nor outlines the impact on specific records.

Sources: [3] [2] [1]

8. QA and IT Checklist

A robust time validation assesses both technical implementation and functional significance. IT can evaluate synchronization; the domain expertise defines the required sequence for its decision-making. Together, an appropriate target can be established.

The following internal list avoids universal second-order limits. It instead provides a justified, verifiable definition specific to the particular data pathway.

  • Named factual events and time periods of relevance.
  • Time source and time zone reference have been clarified for each involved component.
  • Understanding of event, receipt, and storage times.
  • Required accuracy derived from process and risk assessment.
  • Rights for time and time zone changes are appropriately addressed.
  • Representative verification performed for takeover, display, export, and import.
  • Procedure for time deviations and unclear history defined.

Sources: [1] [2] [5]

Project experience and collaboration

Reconstruct the same sequence of events across systems

IT and process owners trace known events through capture, processing and export. We check the time source, time zones, permissions and behaviour when the connection drops or the clocks change. Assigning an event to a day needs different accuracy from ordering consecutive release steps. We agree limits and controls and test them at the relevant handovers. A later reviewer should be able to reconstruct the sequence from the records themselves.

Frequently asked questions about Timestamps and clock synchronisation

Is UTC required for each GMP system?

No. Annex 11, PIC/S, and MHRA do not specify a particular UTC storage format. However, when cross-site usage is involved, the time zone reference must remain clearly defined; PIC/S addresses this for global systems in 9.8, and MHRA in 5.1. UTC or a local time with a clearly defined offset may serve as appropriate solutions. Crucially, the same timestamp must be uniquely reconstructible across display, export, and downstream systems.

Sources: [1] [2]

Must we exclusively use NTP?

No. PIC/S requires synchronized system clocks and restricted access to authorized personnel, but does not specify a particular synchronization protocol (9.5). NTP could represent an appropriate technical solution. Assess time source, failure behavior, monitored drift, and change rights, rather than concluding reliability of timekeeping solely from the protocol name.

Sources: [2] [1]

What is the maximum allowable time deviation?

Annex 11, PIC/S PI 041-1, and the MHRA guidelines do not specify general second- or minute-based time limits for all systems. The appropriate time limit should be derived from the time-critical decisions within your process. In cases of closely consecutive status changes, a deviation may be more significant than in a broad daily assignment. The selected time limit and its monitoring must be supported by sufficient validation evidence.

Sources: [5] [2]

Is a timestamp without a time zone sufficient?

Only when the required time zone reference remains unambiguously available elsewhere. During the transition to winter time, a local time value may occur twice. Without an additional reference, the two events cannot be distinguished. Therefore, PIC/S explicitly addresses the potential need for time zone specification in globally used systems (9.8). Verify this unambiguity also during export and in connected applications.

Sources: [3] [2]

Can defective historical time stamps be corrected?

A required correction must be reviewed and traceable; the original facts must not be concealed. Typically, an initial documented assessment of the deviation is necessary. Silent retrospective adjustments to create a plausible narrative are not an appropriate form of validation evidence.

Sources: [4] [1]

Does central synchronization make additional tests unnecessary?

No. Applications and interfaces may additionally convert, format, or incorrectly map time values. Review the processing relevant to the process up to actual usage. A correctly configured server does not automatically ensure the correct export or import.

Sources: [1] [2]

How do we handle lagged data transmissions?

Distinguish the timestamp of the original event from the receipt time within the target system. Both timestamps may differ legitimately. The required information depends on the purpose of traceability. A delay must not be inadvertently interpreted as a new professional event time.

Sources: [2] [4]

Is every unexpected sequence a data manipulation?

No. Time zones, clock deviations, field meanings, or technical delays may provide alternative explanations. These must be verified based on supporting documentation. Unclear discrepancies should not be dismissed with a plausible technical assumption.

Sources: [3] [2]

What do we verify following a restoration?

Verify the relevant time and time zone settings, as well as representative new events and received historical data. The exact scope follows from the restoration process and its implications. This pertains to the correct continuation and interpretation, not to an automatic re-dating of prior records.

Sources: [1] [2]

Who determines the required accuracy?

The functionally responsible area defines the required temporal commitment; IT evaluates implementation and monitoring. The relevant roles within the quality system approve the appropriate determination. A technical standard configuration alone does not justify its adequacy for the specific process.

Sources: [1] [5]

Sources and review date

Source date: 7 October 2026. The technical examples relate to human medicinal product GMP. MHRA statements are incorporated within their respective areas of applicability. Tables and numerical examples are intended as standalone work aids.

  1. European Commission: EU GMP Annex 11, Computerised SystemsRevision January 2011; from 30.06.2011; Principle; §§1,4,5,7,9–13,17; §12.4 Identity, Date and Time; §10 controlled changes
  2. PIC/S: PI 041-1, Data Management and IntegrityPIC/S PI 041-1, 1 July 2021. See section 3.7 for status, sections 7.5–7.8 and 8.1–8.8, sections 9.1.5 and 9.3 and 9.5–9.10, section 12.1 and the glossary.
  3. MHRA: GxP Data Integrity Guidance and DefinitionsRevision 1, March 2018; Sections 6.1–6.11 Data/Metadata/Processing; Sections 6.12–6.17 Transactions, Audit Trail, Review, Access, and Retention
  4. European Commission: EU GMP Chapter 4, DocumentationJanuary 2011; in effect since 30.06.2011; Principle; §§4.1–4.9, in particular timely recording 4.8 and visible correction 4.9; §§4.10–4.12 Storage
  5. EMA/ICH: Q9(R1), Quality Risk ManagementEMA/CHMP/ICH/24235/2006 Corr.2, published 31 January 2025. Q9(R1) has applied since 26 July 2023. Sections 3–4.6 and 5.1–5.3 address uncertainty, formality, the knowledge base and reassessment.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Maintain temporal evidence of system boundaries

We support QA and IT in translating the technically required event sequence into specific requirements, tests, and an appropriate operating procedure.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →