Documenting a Construction Dispute: Logs, Photos, Notices and Emails

Why construction cases turn on documents

Three reasons, each of them a rule rather than a preference. First, construction contracts make written notice a condition of getting paid for extras, delay or changed conditions, and a party that cannot produce the notice usually cannot recover, whatever happened on site. Second, the Texas lien and bond statutes require specific notices, in specific forms, sent by specific methods on specific dates, and a claimant that cannot prove the mailing has no lien and no bond claim. Third, damages in a construction case are proven from records: pay applications, job cost reports, labor hours, equipment logs and schedule updates. A witness who remembers that the owner kept changing the plans is worth little next to a change order log with dates and dollar amounts.

There is a fourth, practical reason. Projects run for months or years, superintendents move on, and by the time a case is tried nobody remembers which week the steel was late. The documents remember.

What to keep, and what each record proves

Notices: the contract's rules and the statute's rules

Every construction contract has a notice clause saying where notices go, to whom and how. A claim notice sent to the wrong person, or by email when the clause requires mail, invites a defense that the notice was never given. Read the clause once at the start of the job, put the addresses in the project file, and send every notice that way even when the relationship is friendly. Change order disputes shows how a missed written notice ends an otherwise valid claim for extra work.

Statutory notices have their own methods. Under Property Code § 53.003 a lien notice may be delivered in person, by certified mail, or by a traceable private delivery service that can confirm receipt, and a notice sent by certified mail is considered given when deposited in the mail, properly addressed and stamped, so the certified mail receipt with the postmark is the proof. The notice of claim itself must be in substantially the statutory form (§ 53.056). On public projects the bond notices must go by certified or registered mail (Gov't Code § 2253.048). On a residence, the Residential Construction Liability Act notice goes by certified mail, return receipt requested, and must be accompanied by the evidence of the defect the owner has, such as reports and photographs (Prop. Code § 27.004). Texas mechanic's lien deadlines lists the dates each notice must meet.

Photographs and video

A photograph proves the condition of the work on a date, and nothing else does it as well. The habits that matter: take progress photographs on a fixed schedule, from the same vantage points, so change over time is visible; photograph every defect, differing site condition, delivery and damaged material when it is found and again after any corrective work; keep the files with their original metadata rather than screenshots or copies pasted into a report; and store them by date and location so a specific day can be found two years later. Short video walk-throughs at substantial completion, with the date spoken aloud, resolve many later arguments about what was finished.

Daily logs and schedule records

A useful daily log records facts: crew counts by trade, hours, work performed by area, weather and its effect, materials received, equipment on site, inspections, visitors, verbal instructions received and from whom, and anything that stopped or slowed work. It does not record opinions about the other side's competence, and it is not written a week later from memory. Logs that read as a running argument lose credibility; logs that read as a plain record of each day are the backbone of a delay or disruption claim.

Schedules must be kept in their native scheduling files, including every update, because a scheduling expert reconstructs the critical path from the logic in those files. A folder of PDF Gantt charts shows what the schedule looked like but not why, and it cannot be analyzed.

Example

Suppose a drywall subcontractor on a Frisco office project is told by the general contractor's superintendent to work around the mechanical trade, out of sequence, for three weeks. The subcontractor's foreman notes the direction in the daily log each day with the superintendent's name, emails the project manager that evening confirming the instruction and reserving the right to claim the added cost, codes the extra labor hours to a separate cost code, photographs the congested areas, and sends the written claim notice the subcontract requires by the method it requires. When the general contractor later denies ever directing the resequencing, the subcontractor has a dated record from four independent sources. A competitor who did the same work but kept only its invoices has a story.

Emails, texts and project platforms

Project communications now live in email, text messages and project management platforms, and all of them are discoverable. Use company accounts and devices so the records can be collected; a superintendent's personal phone full of texts with the owner's representative is evidence the company may not be able to produce or control. When a project ends or a party is removed from a shared platform, export the project record first, because access can disappear overnight. Treat every text as a letter: it will be read aloud later.

Preserving records once a dispute is likely

From the moment a dispute is reasonably anticipated, nothing related to the project may be deleted, overwritten or discarded, including photographs on phones, text threads, platform data and the automatic deletion settings on email systems. A written preservation instruction to everyone involved, often called a litigation hold, is the standard step; what a litigation hold letter requires explains it. Texas courts can sanction a party that lost or destroyed evidence it should have kept, including by instructing the jury to presume the missing evidence was unfavorable; deleted emails and lost data covers those consequences. In a lawsuit the other side may discover any nonprivileged matter relevant to the case under Texas Rule of Civil Procedure 192, which includes the records described here, so preserving them protects a party as much as it binds it.

Common documentation mistakes

• Reporting problems only at site meetings or by phone and never sending the written notice the contract requires.
• Sending lien and bond notices by regular mail or email and keeping no proof of mailing.
• Letting signed time-and-material tickets wait until the end of the month, when the other side's superintendent has moved to another job.
• Keeping schedules only as PDFs.
• Writing opinions and accusations into daily logs.
• Letting employees leave with the only copies of project texts on their personal phones.
• Starting to collect records after the demand letter arrives rather than from the first unpaid draw.

For what to gather before a lawsuit in any business dispute, see what evidence to save before suing. Tina Wysk represents owners, contractors and subcontractors in construction disputes in Dallas–Fort Worth and advises on building the record while a project is still running.