Project records and documentation

The Copper Kettle's second location finished three weeks late, and the general contractor's project manager sent Brightwater a letter blaming the electrical work and proposing to deduct 4,500 dollars of liquidated damages from the final payment. Dana's stomach dropped when she read it. Then Priya opened the job folder. It held thirty-one daily reports, eleven requests for information with dates sent and answered, a change order log showing four owner changes that had added nine working days, photos of the empty ceiling space the drywall crew had closed before the above-ceiling inspection, and an email from the general contractor's superintendent approving a new schedule. Ray read the folder for twenty minutes and then wrote a two-page reply. The deduction was withdrawn within a week. "On a job," Ray said, "the company with the best records usually wins the argument."

Project management and documentation make up a large share of business and law exams, and they are also the everyday work of a master electrician who runs jobs. This lesson covers the records an electrical contractor keeps from bid to closeout, schedules and the critical path, progress billing, and how long to keep everything.

The daily report

The daily report, also called a daily log or job diary, is the foundation of project records. Written every working day by the foreman or project lead, it records who was on site and for how many hours, the work performed and where, materials delivered, equipment used, weather, inspections, visitors, safety meetings and incidents, delays and their causes, instructions received and from whom, and any problems or changes. It should be factual, specific and written the same day; reports written weeks later carry little weight. Photos with dates and locations support it. In a dispute, daily reports often decide who caused a delay or whether extra work was directed.

Communication records

Several standard documents move information between the contractor, the design team and the owner. A request for information, or RFI, asks the architect or engineer to clarify drawings or specifications, such as a conflict between the electrical and mechanical drawings or a missing panel schedule. Each RFI is numbered, dated, sent through the channel the contract requires, and logged with the date answered, and an answer that changes scope or cost should lead to a change order. Submittals are shop drawings, product data and samples the contractor sends for review before ordering equipment such as switchboards, luminaires, generators and fire alarm devices; the engineer reviews them for conformance with the design, and the submittal log tracks each item through review, resubmittal and approval. Meeting minutes record decisions at job meetings and should be checked for accuracy, because unchallenged minutes are often treated as agreed.

Written notice letters are the most important communication of all. Most contracts require written notice within a set number of days of a claim for extra cost or time, a differing site condition, or a delay, as Lesson 3 described. A phone call or a conversation on site is not written notice. Brightwater used a simple template that named the contract clause, described the event, stated that cost and time impacts would follow, and was sent to the person and address the contract named.

Schedules and the critical path

Construction schedules are usually built with the critical path method, or CPM. Each activity has a duration and depends on others: rough-in cannot start until framing is done, and wall covering cannot start until rough-in passes inspection. The critical path is the longest chain of dependent activities through the project; its total length is the shortest possible project duration, and any delay to a critical activity delays the whole project. Activities off the critical path have float, also called slack: the amount of time they can slip without delaying completion. Business and law exams often give a small network and ask for the critical path, the project duration or an activity's float.

# Critical path for a small activity network (durations in days)
acts = {"A": (4, []), "B": (6, ["A"]), "C": (5, ["A"]), "D": (1, ["B", "C"]),
        "E": (3, ["A"]), "F": (4, ["D", "E"])}
early = {}
for a in ["A", "B", "C", "D", "E", "F"]:              # listed in dependency order
    d, pre = acts[a]
    start = max((early[p][1] for p in pre), default=0)
    early[a] = (start, start + d)
finish = max(f for s, f in early.values())
late = {}
for a in reversed(["A", "B", "C", "D", "E", "F"]):
    d, _ = acts[a]
    succ = [b for b, (_, pre) in acts.items() if a in pre]
    lf = min((late[b][0] for b in succ), default=finish)
    late[a] = (lf - d, lf)
for a in acts:
    fl = late[a][0] - early[a][0]
    print(a, "early", early[a], "late", late[a], "float", fl, "CRITICAL" if fl == 0 else "")
print("Project duration:", finish, "days")

A early (0, 4) late (0, 4) float 0 CRITICAL
B early (4, 10) late (4, 10) float 0 CRITICAL
C early (4, 9) late (5, 10) float 1 
D early (10, 11) late (10, 11) float 0 CRITICAL
E early (4, 7) late (8, 11) float 4 
F early (11, 15) late (11, 15) float 0 CRITICAL
Project duration: 15 days

Schedules change, and the records must show why. When an owner change or a late delivery delays a critical activity, the contractor gives written notice and requests a time extension supported by the daily reports and an updated schedule. Delays are often classified as excusable or not, and as compensable or not: a delay caused by the owner may earn both time and money, a delay caused by unusual weather may earn time only, and a delay caused by the contractor earns neither and may trigger liquidated damages. Concurrent delays, where both parties caused delay at the same time, are handled differently under different contracts and court decisions.

Progress billing

On most commercial jobs the contractor bills monthly using a schedule of values, a breakdown of the contract price into line items, such as service equipment, feeders, branch rough-in, lighting, fire alarm and closeout, that the general contractor or owner approves at the start. Each month the contractor reports the work completed and materials stored for each line, and the application for payment totals the earned value, subtracts retainage and previous payments, and shows the amount due. Standard forms are widely used, and payment applications are usually accompanied by lien waivers for the previous payment, as Lesson 4 described. Overbilling, claiming more work than is complete, creates cash early but hides losses and damages trust; underbilling starves the company of cash.

Closeout records

At the end of a job, the contract usually requires a closeout package before final payment and retainage release. For electrical work this typically includes as-built or record drawings showing the actual routing of feeders and the final panel circuits; accurate typed panel directories, which the NEC itself requires to be legible and specific; test reports such as insulation resistance, ground electrode resistance where specified, torque records for terminations and fire alarm acceptance tests; operation and maintenance manuals and warranties for equipment; spare parts and attic stock; the final inspection approval and certificate of occupancy support; training records for the owner's staff; and the final lien waivers. A punch list of incomplete or incorrect items is created near the end, and every item is checked off before closeout.

• Record drawings and panel directories.
• Test, startup and acceptance reports, including fire alarm and emergency systems.
• Operation and maintenance manuals, warranties and the warranty start date.
• Final inspection approvals and permit closure.
• Punch list completion and owner training.
• Final lien waivers and release of retainage.

Keeping records

Job files should be kept long after the job ends. Construction defect claims can be brought years later, within the state's statute of limitations and statute of repose, which in many states falls somewhere around six to twelve years after completion. Tax, payroll and safety records have their own periods, described in Lessons 6 to 8. Brightwater kept every job file electronically for at least ten years and kept the permit, inspection, as-built and test records indefinitely, because they cost almost nothing to store and could be worth thousands in a dispute.

Digital records and photos

Most contractors now keep project records electronically: daily reports on tablets, photos uploaded from phones with time and location data, RFIs and submittals in the general contractor's project management software, and drawings in cloud storage. Digital records are easier to search and harder to lose, but the same rules apply. Entries should be made the same day, photos should show enough context to identify the location, and files should follow a consistent naming pattern so anyone in the office can find them. Before covering work, crews photograph walls and ceilings with the circuit numbers and cable routes visible, which later helps both service calls and record drawings. Brightwater backed up its job files automatically every night and kept a copy off site, because the record that wins a dispute is worthless if the laptop holding it is stolen.