Read time: 4 min. Prefer to watch?​

The Field Story: The Search for Truth

The buzzing of the fluorescent lights in the trailer and the smell of stale coffee usually set the tone for my Friday afternoons. I was sitting in an internal pre-pencil review meeting with my project team leaders. A simple question was directed at me from across the table: Why did the electrical sub bill for eighty percent of the fourth floor when they just started rough-in?

I did not have the answer. I found myself in a defensive posture immediately. I was scrolling through a blurry camera roll on my phone, trying to find a site photo from three weeks ago to justify a percentage I had roughly guessed at during a busy afternoon. That heavy pressure in my chest was the result of being unprepared. I was relying on the office billing packet to tell me my costs instead of tracking them myself.

The Deep Dive: Systematic Preparation

To move from a defensive position to a strategic one, I had to stop waiting for something to change for me. I realized that the pressure of the payment cycle is actually a preparation problem. I started a twenty minute Wednesday habit to ensure I was never caught by surprise again.

First, I make early requests by reaching out to trade partners ten days before the deadline for a pre-draft review. Second, I use a dedicated Wednesday focus block to review my inbox for any invoices trade partners have submitted and verify those percentages against my actual site walks, checking for stored materials and checking new change order costs or credits. Third, I walk into every meeting with settled numbers that I already knew were accurate. This shift moved the task from a monthly scramble into a predictable routine.

The Life Tip: Rejecting the Default

Most project managers accept the friction of the industry as an unchangeable reality. We often assume that a deadline crisis is simply a requirement of the job. But peace comes from rejecting these status quo defaults and actively building systems that overcome the noise.

The book of Proverbs supports this intentionality by reminding us to be diligent to know the state of our flocks and attend to our herds. For us as builders, those flocks are the dollars, the hours, and the data assigned to our project. If we only check on them once a month, we are always in a state of reaction rather than leading the system.

I found that this routine turned a source of anxiety into a point of leading well. When we steward our resources well, we protect our peace. Establish your own routine before the industry dictates one for you.

Cormac Mahalick
​The Essentialist Builder

WHAT THE BREAKDOWN ON YOUTUBE ​

The RFI Log: Reader Q&A

Here are two questions sent in by readers over the last week.

Question: How do you handle it when a trade partner claims that "design intent" is too vague to justify a missing detail in the contract documents?

Answer: I bring them back to the standard where professional contractors are expected to provide a functional system based on the reasonably inferable requirements of the drawings. This ensures we build the intended system and prevents the argument that "if it isn't drawn, I don't own it" from gaining traction.

Question: If I start using "confirming per design intent" in my RFIs now, will it look like I am trying to hide mistakes from the design team?

Answer: Using this phrasing is about clarity and confirming your understanding of the designer's vision rather than asking them to do your job for you. Most designers appreciate a leader who speaks the language of technical intent, which builds trust by showing you have actually studied the plans.