The documentation discipline for sub conversations is not about preparing for a dispute. It is what prevents disputes from forming. Most disputes with subs begin not with bad faith but with two parties who genuinely remember the conversation differently.

A qualified sub still needs documented agreements. The qualification process establishes whether a sub can deliver the work. The documentation process establishes what they agreed to deliver on this specific job. Both are required.

The difference between verbal and written is not mistrust. It is memory. A scope agreement made verbally on a Tuesday morning while both parties are mid-job is remembered through the lens of what each party needs it to have said. Writing it down while the conversation is still current is what makes both versions the same.

The Sub Conversation Record is a one-to-three-sentence document produced after every substantive conversation with a sub. It takes three minutes. It protects months of margin.

Why Verbal Sub Agreements Produce Disputes

The obvious problem is that subs rely on the scope they remember. The agreement was for the first-floor rough-in. But the second floor came up. What each party remembers about that determines whether there is a billing dispute.

The less visible cost is that both parties are right. The sub who remembers the second floor as in scope and the owner who doesn’t are both recalling from their own perspective. Neither is lying. The conversation was ambiguous and the confirmation was never made.

The deepest cost is repeated exposure. A contractor who handles five to ten active subs across multiple jobs is running five to ten sets of verbal agreements simultaneously. Any one of them can become a billing dispute. The discipline of writing things down is what keeps the number of disputes close to zero.

The Sub Conversation Record

The Sub Conversation Record is three parts, each applied at a different moment in the sub relationship. Together they form a continuous log of what was agreed across every job.

Part 1 captures scope and schedule agreements immediately after every conversation

Part 1 is the immediate record. After any conversation about scope, schedule, or payment, the owner writes two to three sentences: what was agreed, by when, and who is responsible.

This is not a contract. It is a contemporaneous note made while the conversation is current. A text or email is sufficient, made while both parties are still aligned.

Before: Scope and schedule conversations happen and both parties proceed on memory. After: Every scope or schedule conversation produces a two-to-three-sentence written record before the next task starts.

Part 2 records any issue, change, or problem as it happens

Part 2 is the mid-job record. When a site condition changes, when a sub’s schedule shifts, when a scope addition arises, the record is made the same day.

This part of the record is what protects the contractor when a billing dispute arises at closeout. The note showing the sub was informed of a scope change on day seven is a different document than a reconstruction at billing. One is a record. The other is an argument.

Part 3 closes the loop with a written confirmation

Part 3 is the confirmation loop. After any significant conversation, the owner sends a brief written summary. “Following up on our conversation this morning: the electrical rough-in covers floors one and two, and you’ll be back on site Thursday to complete it.”

The sub either confirms or corrects. That exchange is the record. It takes ninety seconds to write. It is the document both parties can point to if the conversation comes up differently later.

How the Living Library Maintains Your Sub Agreement Records

Most contractors track sub conversations the same way they track anything that happens on site: in their phone, in a mental note, in a text thread that gets buried under the next job. The record that would resolve a billing dispute is not organized. It is scattered across contexts that no longer have a clear connection to the job in question.

The Living Library is the platform’s active working layer. Unlike a scattered text thread, it keeps sub records organized by sub and by job. The agreement from six months ago is findable in the context of the project it belongs to. The owner who captured the scope conversation in the Library on the day it happened can open it before the billing conversation, not during.

The sub record grows with each job. Every Part 1 note, every Part 2 mid-job record, every Part 3 confirmation adds to a picture that makes the relationship documentable over time.

Start with the Next Conversation, Not the Last One

Don’t go back and recreate records from past jobs. Start with the next sub conversation you have.

After that conversation ends, take three minutes. Write two sentences about what was agreed. Send it as a text or email to the sub. Save a copy to the job file.

Do that for every substantive sub conversation for the next month. At the end of that month, the habit is established and the record exists.

The Agreement That Lives in Writing Has One Version

A verbal agreement between two people remembers differently by the time it matters. A written record does not. Every scope conversation that ends with a brief written summary closes one more potential dispute before it has a chance to open. Try Kiluma free for 14 days at kiluma.ai.