Straight into the service manual page
WrenchQuarry
More

5 job-file records to keep from submittal to handoff

WrenchQuarry Editorial Team · Published · 15 min read · How these guides are written

The five records to keep are the project schedule, the safety kickoff form, the every-other-week safety review record, the job hazard analyses, and the closeout record of substantial completion. Under GSA construction clause 552.236-15 the schedule is due prior to notice to proceed, or at whatever time the contract names; other owners' contracts set their own submission time, and every later schedule revision needs a written narrative.

Net takeaways

  • Submit the project schedule before notice to proceed, or by whatever time the contract specifies.
  • Log every schedule revision with a written narrative on its substance, its rationale, and its impact on the substantial completion date and float.
  • Treat added detail as no revision only when the overall duration of the detailed activity stays the same.
  • File one copy of Form DOT CEM-0604 for the safety kickoff meeting in Category 6, "Safety," of the project records.
  • Hold the joint safety review every other week, with the resident engineer or designated coordinator and the contractor's safety representative.

Record 1: the project schedule

The first record in the job file is the project schedule, and its due date comes from the contract, not from the day your crew arrives. The federal GSA clause on construction schedules, 552.236-15, Schedules for Construction Contracts, applies to GSA construction contracts and requires the contractor to submit the project schedule "prior to notice to proceed, or such other time as may be specified in the contract." On a GSA job that is a two-part rule, and on any other public job your own contract and the rules of that jurisdiction set the deadline. Notice to proceed is the default deadline, and any different time written into the contract replaces it. Anyone checking the file should be able to see the submission date and confirm it against the contract language.

The schedule matters for more than the start date, because the clause measures every later change against it. The rule refers to the "initial approved submission," so the file needs the approved version, not a working draft. If the baseline is missing or unclear, a later revision has nothing firm to be compared to, and the narrative the clause requires cannot show what moved.

Keep the baseline intact. Store the initial approved submission in one place, labeled with its submission date and marked as the baseline. Save every later version as a separate, dated file, and never overwrite the baseline when the crew updates the plan.

Each version should also be readable without help from the people who made it. At handoff, a reviewer will want to know what was approved, when it was submitted, and which versions followed. A version log with one line for each saved schedule answers those questions quickly. Each line should show the date, the version name, and whether the change was logged as a revision or as added detail, which the next section explains.

Revision or added detail: compare the two

Two schedule changes can look alike in the file. Both alter the plan, and both appear as new entries in a log. The GSA clause treats them differently, and that difference decides what goes into the file. The table sets the two options side by side, using the clause's own terms.

MeasureRevisionAdded detail
Applies toSchedule changes after the initial approved submissionDetail added to prospective activities
Counts as a revision?YesNo, if the overall duration of the detailed activity does not change
Written narrative required?Yes, covering substance and rationaleNot triggered by the clause
Impact on projected substantial completion date stated?YesNot triggered by the clause
Impact on available float stated?Yes, for all activitiesNot triggered by the clause

The narrative for a revision has three required parts. It must describe the substance of the revision, explain the rationale, and state the impact on the projected substantial completion date and on the available float for all activities. The float requirement reaches beyond the activity that changed. A revision to one task can shift slack elsewhere in the plan, and the narrative has to say so.

The added-detail path depends on one test. The clause says that adding detail to prospective activities is not deemed a revision if the overall duration of the detailed activity does not change. Splitting a task into finer steps is therefore not automatically a revision. The question is whether the total time for that activity moves. If the total holds, the file keeps the detail and no narrative is triggered. If the total shifts, the change is a revision and the full narrative applies.

Log each change with the duration before and after. That pair of numbers settles which path applies and gives a reviewer the evidence without rereading the whole schedule.

Which one should you pick?

Choosing between the two paths is a judgment about duration. The duration test has a narrow reach: it applies only to added detail on prospective activities. Moving the finish date of an already approved activity is a revision whatever the durations are. The answer determines which record the file owes. The lines below apply that question to the people who handle the file.

  • If you are a team lead splitting a prospective activity into finer steps, pick added detail only after you confirm the overall duration of the activity is unchanged; if the total duration moves, treat the change as a revision with a full narrative.
  • If you are a dispatcher moving the finish date of an approved activity, pick a formal revision, because the clause requires a written narrative on its substance, its rationale, and its effect on the projected substantial completion date.
  • If you are an owner's representative and a split leaves the total duration unclear, pick the revision route, because it puts the impact on substantial completion and float into writing where a reviewer can check it.
  • If you are assembling the handoff file, pick the revision route for any change that moves the substantial completion date, because that effect must appear in the narrative rather than in a verbal update.

The two paths leave different traces. An added-detail entry records that the duration held. A revision leaves a narrative that shows how the schedule's history changed. Choose the path before you save the change, so the log entry matches the decision. If the total duration later turns out to have moved, the entry is wrong, and the schedule needs a revision narrative to correct the record.

Record 2: the safety kickoff form

The Caltrans construction manual names a specific form for the safety kickoff meeting. Its safety section says to use Form DOT CEM-0604, "Project Safety Review or Meeting," to document the kickoff meeting, and to file a copy of that form in Category 6, "Safety," of the project records. Those two instructions give the record both its content and its home.

MeasureDetail
FormDOT CEM-0604, "Project Safety Review or Meeting"
Event documentedThe safety kickoff meeting
Where the copy goesCategory 6, "Safety," of the project records
Copies to fileOne copy of the completed form

The kickoff meeting leaves no trace in the file until the form is completed and copied, so the filing step is what makes the meeting provable later. An unused blank copy in the file does not document anything. Confirm that the copy in Category 6 is the completed form for that meeting, with the meeting date recorded on it.

Because the form's title covers both a review and a meeting, label each filed copy with the date and the event it records. That label lets a reader tell the kickoff copy apart from later safety entries without opening each one.

Keeping every safety item there means a reviewer can find the kickoff record in one place. Treat the kickoff copy as the first entry in the safety series, and keep it at the front of that category so the sequence of safety records reads in order at handoff.

Record 3: the every-other-week safety review

The Caltrans manual sets a regular rhythm for safety review. Its safety section states that, under Section 5-1.28, "Project Safety Reviews," of the Standard Specifications, "an every-other-week joint safety review is to be performed by the resident engineer or designated project safety coordinator with the contractor's project safety representative."

MeasureDetail
FrequencyEvery other week
Public-side leadResident engineer or designated project safety coordinator
Contractor-side participantContractor's project safety representative
Governing provisionSection 5-1.28, "Project Safety Reviews," of the Standard Specifications

The word "joint" matters. The review is a shared activity between the public-side lead and the contractor's safety representative, so each review record should identify both by role. A record that names only one side cannot show that the joint requirement was met.

Cadence is the second thing the file must show. A dated log of reviews, with one entry for each sitting, makes any gap in the every-other-week rhythm visible to someone reading the file later. Each entry should record the date, the two named participants, and notes on what was discussed, so the log proves both that the review happened and what it covered.

The review's agenda is the subject of the next record, the job hazard analyses. Keep the review entry and its agenda notes together, so the schedule of reviews and the content of each review can be read side by side.

Record 4: job hazard analyses

The Caltrans safety section ties job hazard analyses to the safety review. The review covers analyses for active work activities and for work activities planned to start within 5 working days. The manual states that these analyses are discussed "in accordance with Section 5-1.29, 'Job Hazard Analyses,' of the Standard Specifications," a separate document, and the safety section carries that reference.

The look-ahead window is the detail that matters for the file. An analysis for work that is already underway does not cover the work that starts next. A file with analyses only for current tasks will show a gap for everything about to begin, so keep each analysis tied to its activity's planned start date. A reviewer should be able to match each analysis against the window.

Work covered at the safety reviewWindowGoverning provision
Active work activitiesCurrent workSection 5-1.29
Work activities planned to startWithin 5 working daysSection 5-1.29

For each analysis, record the activity name, the date it was prepared, the planned start date, and the date it was discussed at a safety review. The discussion date links the analysis to the every-other-week log from Record 3, so the two records can be read together.

Keep the review entry and the analysis separate. The review entry shows what was discussed and who took part. The analysis holds the hazard analysis for the activity itself. Both belong in the safety series, which begins with the kickoff copy from Record 2. If an analysis was discussed in a review but never filed, the file has a gap that the review entry alone cannot fill.

Record 5: substantial completion for handoff

The closeout record should show where the job stands against its projected substantial completion date, and the schedule file is the source for that. On a GSA construction contract, clause 552.236-15 requires a revision narrative to state "the impact of the revision on the projected substantial completion date and the available float for all activities"; on any other job, the schedule clause in your own contract decides what the narrative carries. Each revision therefore carries the date forward, or moves it, in writing.

The handoff file should hold a short chain. Start with the baseline submission, add each revision narrative in order, and end with the latest version and its projected date. A reviewer at closeout can then trace how the date changed from start to finish without rebuilding the history from memory.

Be careful about what the schedule record can show. The clause covers the projected date and the narrative for each revision. It does not establish that substantial completion has been reached. That determination depends on the law and the contract that govern your job, and this post does not supply that rule. Before you record the date as achieved, check those governing documents. Then record the date you determined and the document you relied on.

Store the working schedule and the handoff copy separately. The working copy keeps changing with the crew. The handoff copy is frozen at closeout, with its version number, its date, and the final projected date, so the record cannot drift after the job ends.

Where the project records live

The Caltrans chapter on project records and reports includes a short cross-reference that matters for filing: "Section 3-5, 'Control of Work,' of this manual describes the procedures." The chapter page is brief, so read that sentence as a pointer. It tells you that the procedures for controlling work are in Section 3-5. Read that section before you set up your file system, so the records you keep match the steps it describes.

The safety section gives one concrete location: the kickoff form goes in Category 6, "Safety," of the project records. File the completed kickoff copy of Form DOT CEM-0604 in Category 6, "Safety," as the manual directs, and keep the review log and the job hazard analyses alongside it as a filing practice of your own. Keep the kickoff copy at the front of that category so the safety series reads in order at handoff.

The quotes here do not assign a category to schedule records, so you need a labeled home for them of your own. Choose one, write it down, and use it for the whole job. A short index at the front of the file should list each record family, where it sits, and its date range. A dispatcher or owner who opens the file cold can then find any record in minutes.

Consistency matters more than the particular layout. If the schedule moves between folders during the job, the baseline becomes hard to prove and the revision chain breaks. Fix the structure at the start and check it at each safety review, so that the file is already organized when the handoff arrives.

Key figures for safety and schedule

The numbers that govern these records are few, and each comes from a specific source. The table collects them in one place. The Caltrans safety section is the source for most of the safety figures.

FigureValueWhat it governsSource
Joint safety review cadenceEvery other weekReview by the resident engineer or designated coordinator with the contractor's safety representativeSection 5-1.28
Job hazard analysis look-ahead5 working daysAnalyses for work planned to start within this window are discussed at the reviewSection 5-1.29
Filing location for the kickoff form copyCategory 6, "Safety"Copy of the completed Form DOT CEM-0604Project records
Schedule submissionPrior to notice to proceed, or as the contract specifiesProject schedule baselineGSA 552.236-15

Read the table with care. It lists the figures the quotes support, and it does not include a threshold for when a schedule change counts as a revision. The GSA clause applies the overall-duration test only to added detail, not to revisions, and it uses no set number.

Use the review cadence to check your log. Entries should appear at a steady every-other-week rhythm. A gap in the log is the first thing a reviewer will notice, and an explanation for the gap, written at the time, is far better than one reconstructed at handoff.

Use the 5-working-day window to check your analyses. Any activity planned to start within that window should already have an analysis that is discussed at the next review. If an activity starts without one, the file shows that the look-ahead was not followed.

Handoff checklist from the records

Work through these items before you hand the file over.

  • The initial approved submission is stored, labeled with its submission date, and meets the submission time set by the contract on your job.
  • Revisions: Each revision has a written narrative covering its substance, its rationale, and its impact on the projected substantial completion date and on available float for all activities. The same clause governs this item, so keep the narrative with the version it describes.
  • Added detail: Each entry that claims no revision records the duration before and after the change, showing that the overall duration of the detailed activity did not change.
  • Kickoff record: One completed copy of Form DOT CEM-0604 is filed in Category 6, "Safety," with the meeting date on it.
  • Safety reviews: Dated entries appear every other week and name the resident engineer or designated coordinator and the contractor's safety representative.
  • Job hazard analyses: Each analysis is tied to its activity's planned start, and each one was discussed at a review covering active work or work planned within 5 working days.
  • Closeout date: The projected substantial completion date comes from the latest schedule version. Confirm the date against the law and contract that govern your job before you record it as achieved.
  • Filing: Every record sits in its stated location, the index at the front of the file is current, and the procedures in Section 3-5, "Control of Work," have been checked against the file structure.

Run the checklist at each safety review, not only at handoff. Gaps found in the middle of a job are cheap to fix. Gaps found at closeout often cannot be fixed at all.

Related guides: Job file closeout: 6 steps to track deadlines · 3 job records to keep after the invoice is paid in full · Job site debris: 5 checks before crew handoff.

Reader questions

Do I have to submit the schedule before notice to proceed? Not always. The GSA clause says the contractor submits the schedule "prior to notice to proceed, or such other time as may be specified in the contract." If the contract names a different time, that time governs. Check the contract before you assume the default applies.

Does splitting an activity into smaller steps count as a revision? Not if the overall duration does not change. The clause says that adding detail to prospective activities "shall not be deemed a revision if the overall duration of the detailed activity does not change." If the total duration moves, treat the change as a revision and write the full narrative.

What must a revision narrative include? The clause requires three things: a description of the substance of the revision, the rationale for it, and its impact on the projected substantial completion date and on the available float for all activities.

Where does the kickoff form copy go? The Caltrans safety section says to file a copy of Form DOT CEM-0604, "Project Safety Review or Meeting," in Category 6, "Safety," of the project records.

How often is the joint safety review held? Every other week. Under Section 5-1.28 of the Standard Specifications, the resident engineer or designated project safety coordinator performs the review with the contractor's project safety representative.

Which work does the safety review cover? It covers job hazard analyses for active work activities and for work activities planned to start within 5 working days. Those analyses are discussed under Section 5-1.29, "Job Hazard Analyses."

Where do I look for the procedures that control the work? The Caltrans project records chapter points to Section 3-5, "Control of Work," of the manual, which describes those procedures. Read that section before you set up the file structure.

Sources

More field guides