Expert report review

Timestamps in a forensic report: how does a reviewer re-check time zones?

A forensic tool turns stored numbers into clock times. Windows counts 100-nanosecond intervals since January 1, 1601 UTC, Unix-type systems count seconds since January 1, 1970, and Apple's Core Foundation measures time relative to January 1, 2001. A reviewer finds the raw value behind each time in the opposing report, the format it was read in, the time zone and the daylight saving rule applied, and repeats the conversion.

A gloved hand sets a hard drive by a monitor of blurred colored timeline bars

Why can the same event show different times in two forensic reports?

Because the device stores a number and the tool converts it for display. Two tools, or one tool with two time zone settings, can print the same stored value as two different clock times.

Microsoft's documentation on file times defines a file time as "a 64-bit value that represents the number of 100-nanosecond intervals that have elapsed since 12:00 A.M. January 1, 1601 Coordinated Universal Time (UTC)." The FILETIME structure holds that value. A report that prints "3/14/2025 2:15:07 PM" has already converted it once.

Other systems count against other starting points. The POSIX standard, IEEE Std 1003.1-2024, defines the Epoch as "The time zero hours, zero minutes, zero seconds, on January 1, 1970 Coordinated Universal Time (UTC)," and its section 4.19 describes seconds since the Epoch as "A value that approximates the number of seconds that have elapsed since the Epoch." Apple's Core Foundation type CFAbsoluteTime represents "a specific point in time relative to the absolute reference date of 1 Jan 2001 00:00:00 GMT."

None of these counts carries a time zone. The zone enters when a tool or a person turns the count into a calendar date and a clock time. For every time in the opposing report the reviewer asks two separate questions: what number is stored in the source record, and which conversion produced the time printed on the page.

Does the report have to say which time zone it uses?

SWGDE best practices list the acquisition date and time, including time zone, among the items an examiner documents. Rule 26 requires a retained expert's report to give the facts or data considered.

The Scientific Working Group on Digital Evidence publishes Best Practices for Computer Forensic Acquisition, 17-F-002, now in version 2.1 of August 5, 2025. Its section 9 lists what the acquisition documentation may include: the imaging tool and version, the hash values, the acquiring person's name and title, and the "Acquisition date and time (including time zone)." Without the zone the reviewer cannot tie the examiner's clock to the clock of the device.

Rule 26(a)(2)(B) of the Federal Rules of Civil Procedure requires "a complete statement of all opinions the witness will express and the basis and reasons for them" and "the facts or data considered by the witness in forming them." A timeline built on converted times rests on the conversion settings. The reviewer treats the zone, the daylight saving handling and the tool version as part of those facts or data.

Where the report is silent, the reviewer lists each time that cannot be traced to a stored value and a stated zone. Under Rule 705 an expert may give an opinion without first testifying to the underlying facts or data, "But the expert may be required to disclose those facts or data on cross-examination." The list becomes the set of questions for the deposition and for trial.

How does daylight saving time move a timestamp by one hour?

A conversion that applies the wrong daylight saving rule for the date of the event shifts the result by one hour. One Windows conversion function applies the current setting even to a time recorded in standard time.

In the United States the dates are set by statute. Under 15 U.S.C. § 260a(a), daylight saving time starts "at 2 o'clock antemeridian on the second Sunday of March of each year" and ends "at 2 o'clock antemeridian on the first Sunday of November of each year," and the standard time of each zone is advanced one hour for that period. A State lying entirely within one time zone may by law exempt itself, and a State with parts in more than one zone may exempt the entire State or the area within one zone.

Microsoft's file times page warns that FileTimeToLocalFileTime "uses the current settings for the time zone and daylight saving time. Therefore, if it is daylight saving time, it takes daylight saving time into account, even if the file time you are converting is in standard time." For a file written in January at 10:00 a.m. standard time, the function run in July, while daylight saving time is in effect, returns 11:00 a.m.

The same page names the sequence that applies the rule in force on the date of the file: FileTimeToSystemTime, then SystemTimeToTzSpecificLocalTime, then SystemTimeToFileTime. The reviewer asks which conversion the opposing tool performed and repeats it for each disputed time. Two events less than an hour apart near the second Sunday of March or the first Sunday of November get a separate check, because a one-hour error can reverse their order.

What happens when a tool reads a time in the wrong format?

The date can move by decades. Apple's reference date falls 31 years after the Unix Epoch, so a value decoded against the wrong starting point is off by 978,307,200 seconds.

Core Foundation defines the constant kCFAbsoluteTimeIntervalSince1970 as "The time interval between 1 January 1970 and the reference date 1 January 2001 00:00:00 GMT." The 31 years include 8 leap days, 1972 through 2000, which gives 11,323 days, or 978,307,200 seconds. An Apple value written in 2025 and decoded against the 1970 Epoch lands in 1994.

A Windows file time and a Unix time differ in both the starting point and the unit: 100-nanosecond intervals since 1601 against seconds since 1970. The same digits read under the other format name a different moment.

An error of decades stands out on the page. An error of a few hours does not: a value stored in UTC and read as local time, or the reverse, looks plausible. The reviewer opens the source record, copies the raw value, identifies its format from the application or file system that wrote it, and decodes it without the opposing tool.

SWGDE's Best Practices for Computer Forensic Examination, 18-F-001, version 1.0 of July 11, 2018, states: "Forensic tools should be tested and validated prior to use on examinations." The reviewer asks whether the decoding of the timestamp format at issue was tested in the tool version that produced the report.

Do USB drives and memory cards store the time zone?

Not on FAT volumes. Microsoft states that FAT records times on disk in local time and NTFS records them in UTC. A FAT time cannot be placed on a timeline until the clock setting of the writing device is known.

Microsoft gives a worked example on its file times page: "a file that is saved at 3:00pm PST in Washington is seen as 6:00pm EST in New York on an NTFS volume, but it is seen as 3:00pm EST in New York on a FAT volume." The FAT entry keeps the wall-clock reading of the computer that wrote it and no record of that computer's zone.

For a FAT record the reviewer needs the time zone setting of the computer or camera that wrote the file, which may differ from the setting of the examiner's workstation. If the opposing report converted FAT times as if they were UTC, every time in that column is off by the UTC offset of the writing device, and by one more hour where daylight saving time applied.

Microsoft also documents a caching effect. GetFileTime retrieves cached UTC times from a FAT volume, and "When it becomes daylight saving time, the time retrieved by GetFileTime is off an hour, because the cache is not updated" until the computer restarts. Times read from a running system with a FAT volume around a daylight saving change get a second check for that reason.

How precise are file timestamps?

Less precise than a seconds column suggests. On FAT, write time has a resolution of 2 seconds and access time of 1 day, and NTFS delays last access updates by up to 1 hour.

The file times page reads: "the resolution of create time on FAT is 10 milliseconds, while write time has a resolution of 2 seconds and access time has a resolution of 1 day, so it is really the access date."

The FILETIME reference adds that on NTFS "access time has a resolution of 1 hour," and the file times page states that NTFS "delays updates to the last access time for a file by up to 1 hour after the last access." An opinion that a file was opened at 4:12 p.m. because of its last access time states more than the field records.

The reviewer sets each time against the resolution of its field. Two FAT write times 1 second apart do not establish which file was written first, and a FAT access date says nothing about the hour.

Can the time zone rules themselves change after the event?

Yes. IANA's Time Zone Database records government changes to UTC offsets and daylight saving rules and had reached release 2026f on October 27, 2026. A device or tool with older data converts later events under older rules.

Release 2026f records that Cuba "will not fall back to -05 on 2026-11-01 and instead plans to maintain -04 through 2027-11-07." A phone or a forensic tool that still carries the earlier rule shows Cuban local times after November 1, 2026 one hour off. The same release corrected two historical daylight saving end times for Brazil in 1965 and 1966.

For each device in the case the reviewer records the operating system version, and for the forensic tool its version and time zone settings. When a disputed time falls near a rule change in the zone where the device was used, the reviewer converts the stored UTC value under the rule that was in force on that date and compares the result with the report.

Can the examination itself change the dates?

Yes. SWGDE's acquisition best practices warn that system and file dates and times may change as a result of live access. A date that falls on the day of the examination may be the examiner's own trace.

The 17-F-002 page states: "System and file dates and times may change as a result of live access." The reviewer compares the acquisition date and time in the report with every date in the opposing timeline. Last access dates and log entries that fall on the acquisition day, or later, are set aside until the report explains them.

SWGDE 18-F-001 says examiners "should take contemporaneous notes relevant to their examination" and that organizational systems should keep notes with the case for later review. The notes record whether the device was running when the examiner received it and what was done to it before imaging. The reviewer asks for them before accepting any date close to the acquisition.

How does a reviewer re-check a disputed timestamp?

By rebuilding the conversion from the source record: the raw value, its format and starting point, the zone of the writing device, the daylight saving rule on that date and the tool version. Each undocumented step becomes a finding.

The recomputed times are then set against records that carry their own clock, such as email headers or server logs whose zone is stated in the record. Agreement between independent records supports a time. A single converted field, read in one tool under one setting, is one data point.

  • The reviewer finds the record in the extraction or image that holds the value and copies the raw value as stored.
  • The reviewer identifies the format from the application or file system that wrote it: a Windows file time, a Unix count, an Apple absolute time or a FAT local time.
  • The reviewer decodes the value against its own starting point and unit without the opposing tool.
  • The reviewer establishes the time zone setting of the device that wrote the record and the daylight saving rule in force in that zone on that date.
  • The reviewer compares the result with the time printed in the opposing report and records any difference with its cause.
  • The reviewer checks whether the time falls on or after the acquisition date, when live access could have changed it.
  • The reviewer notes the resolution of the field before relying on the order of two close events.

What can counsel do when the opposing timeline does not hold?

Raise it under Rule 702. As amended in 2023, it requires the proponent to show the court that the opinion more likely than not rests on sufficient facts or data and a reliable application of the method.

Under Rule 702 as amended, the testimony must be "based on sufficient facts or data" and be "the product of reliable principles and methods," applied reliably to the facts of the case. The 2023 committee note says that "many courts have held that the critical questions of the sufficiency of an expert's basis and the application of the expert's methodology, are questions of weight and not admissibility. These rulings are an incorrect application of Rules 702 and 104(a)."

The note also says that "each expert opinion must stay within the bounds of what can be concluded from a reliable application of the expert's basis and methodology." A sequence of events stated to the second from fields with a 2-second or 1-day resolution, or times converted without a stated zone, give the reviewer specific points to put to the court.

To repeat the conversion the reviewer needs the extraction or image itself; a PDF of the report does not carry the raw values. Under Rule 34(b)(1)(C) a request "may specify the form or forms in which electronically stored information is to be produced," and without a specified form the responding party produces it in the form in which it is ordinarily maintained or in a reasonably usable form. Counsel can ask for the extraction or image and the tool's case file.

A rebuttal report intended solely to contradict or rebut evidence on the same subject matter is due within 30 days after the other party's disclosure, unless a stipulation or court order sets another date (Rule 26(a)(2)(D)(ii)).

What does IAE do when the times in a digital forensics report are disputed?

IAE prepares reviews of the opposing digital forensics report and rebuttal expert reports on messages, files, phones and computers. The reviewer checks in which time zone each timestamp was read. Up to 5 business days.

The reviewer checks whether another examiner could repeat the opposing work from the report alone: whether the hash values match, which tool and version extracted the data, in which time zone each timestamp was read and whether each conclusion follows from the data. The review ties each finding to a page of the opposing report and to a rule or a published practice.

Work can start without the forensic image. The review can rest on the report, its exhibits and the facts or data the expert must list under Rule 26(a)(2)(B)(ii). With a second copy of the image verified by hash value, the reviewer can repeat the extraction and the time conversions.

Before work starts IAE confirms the review questions, the devices or images involved and how the data reach the reviewer. The secretariat confirms receipt the same day. Within one business day IAE confirms the format, the cost, the deadline and the specialist from its registry, and the client approves the candidate and the CV. The document is issued in up to 5 business days; cases with tight deadlines have a 48-hour rush.

Every specialist is a member of the public IAE registry and passed the council's attestation under the published Criteria Matrix; the Member ID or QR code in the document opens the specialist's record. The specialist confirms in the document that he or she has no interest in the outcome. Materials are not passed to third parties without the client's consent. A review is evidence the court weighs with the other materials; neither IAE nor the reviewer guarantees the outcome, and IAE is not a law firm.

Sources

Read also

All articles

Expert report review

Ready to discuss your case?

Send the materials: the secretariat will confirm the format, cost, deadline and the specialist within one business day.

Expertise request

Received

Cost and timeline estimate

WorkReview of an opinion
TimelineUp to 5 business days
ExpertIAE registry member