Skip to content
Kairos OneBook a demo
Menu
Foundation · 2 min read

Schedule records and audit-trail handbook

Preserve native files, calculations, narratives, evidence, comments, decisions, and exchanges so future reviews can reconstruct what happened.

Working definition

Schedule evidence has value only when its identity, source, time, and relationship to decisions are preserved. A professional record system keeps the exact native submission, checksum, schedule logs, calendars, layouts, reports, narratives, change and delay registers, field evidence, review comments, responses, approvals, and post-import or analytical copies distinct.

Key takeaways

  • Retain exact native submissions and immutable identity metadata.
  • Separate authored, analytical, recalculated, and approved records.
  • Connect each comment and decision to the evidence and file version it used.
01

Preserve authored and analytical records separately

Never overwrite the contractor’s native submission with a reviewer’s repaired copy. Label analytical, imported, recalculated, redacted, and published derivatives and retain their lineage to the source file.

02

Make the record reconstructable

A future reviewer should be able to identify what the schedule said at a specific cutoff, how it was calculated, what changed, what evidence was available, what comments were made, who decided, and which file became controlling.

Create a defensible schedule record

Apply the naming and metadata standard at intake, not after a dispute appears.

Before you start

    1. Register intake

      Record project, organization, filename, format, size, checksum, received time, data date, source, and submission purpose.

      Verify: The exact received artifact can be identified and retrieved.

    2. Store the complete package

      Retain native schedule, XER/XML, narrative, schedule log, reports, basis, change register, delay register, and required evidence.

      Verify: Required components reconcile to one submission ID.

    3. Label derivatives

      Assign distinct IDs to imported, recalculated, analytical, corrected, redacted, or published copies and link them to the source.

      Verify: No derivative can be mistaken for the authored submission.

    4. Connect review decisions

      Link comments, responses, meetings, approvals, conditions, and final disposition to specific file versions and evidence.

      Verify: Each closed issue has a traceable basis.

    5. Test retrieval and retention

      Apply access, legal hold, backup, retention, and restore procedures and perform a sample reconstruction.

      Verify: An independent reviewer can reproduce the record without personal mailboxes or local folders.

      Field-ready control

      Schedule record package

      • Native file and checksum
      • Submission metadata
      • Narrative and schedule log
      • Basis and calculation settings
      • Reports and layouts
      • Change and delay registers
      • Supporting field evidence
      • Comments and responses
      • Final disposition
      • Derivative lineage
      • Access, retention, and restore tested

      Common questions

      Is saving the final approved XER enough?

      No. The decision record also depends on prior submissions, source metadata, calculation logs, narratives, evidence, review comments, responses, and the actions that made one file controlling.

      Sources and scope

      Follow the reference trail.

      This guide is original educational commentary. Kairos reference records identify the source organizations, editions and scope behind this guidance. The original publishers retain their publications and rights.

      Schedule Assessment Guide: Best Practices for Project SchedulesU.S. Government Accountability Office · checked 2026-08-01UFGS 01 32 01.00 10: Project ScheduleWhole Building Design Guide / U.S. Department of Defense · checked 2026-08-01Delay and Disruption Protocol, second editionSociety of Construction Law · checked 2026-08-01Recommended PracticesAACE International · checked 2026-08-01