Maverick Performance Solutions

Opening training…

0

M01 Day One & the Maverick Standard

M01.04

How we communicate — and the legal voice

Email, phone, texts, meeting minutes, and the sentences that become contracts.

  • Write an acknowledgment that does not create scope
  • Keep a decision out of a text thread
  • Apply the legal briefing to everyday writing

The briefing, in operating language

The Project Structure legal video exists because construction disputes are won and lost on paper. You will watch it on Day One. This lesson is the field translation: every email, text, Teams ping, and meeting minute can be Exhibit A. We are courteous. We are not casual about scope, schedule, or safety. We do not badmouth GCs, owners, or competitors in writing. We do not discuss pricing in group threads with outsiders. We do not joke about 'we'll eat it.' One careless sentence can lose a dispute. Write every message like it will be read back to you in a deposition.

Sentences that create accidental contracts

  • Not this

    Yes, we can do that while we're there.

    This

    We can price that as a change. I'll issue a PCO today; please do not assume it is in scope until it is signed.

  • Not this

    We'll have it done Friday.

    This

    Current sequence has us in that area Friday, weather and access permitting. I'll confirm tomorrow at 3:00 after the field report.

  • Not this

    That color is fine.

    This

    Please confirm the spec color / sample ID in writing. We will not procure until the submittal is approved.

  • Not this

    Sorry for the delay — it's on us.

    This

    State facts. Do not admit liability. 'The application moved because slab RH exceeded the system limit. Options attached.'

The standard acknowledgment (use this all week)

You — Received — thank you. I am logging this against job [number] and routing it to [role] for review. I will send a written answer by [time today / 10:00 tomorrow]. This email is not an approval or a schedule commitment.

You, internally — Then actually log it. An acknowledgment without a follow-up is a lie.

Takeaways

  • If it reads like a promise, it is a promise.
  • Acknowledge fast. Commit slow.
  • Move decisions onto numbered documents: RFI, PCO, CO, submittal.

SOPSOP Section 1 — Front Matter & Brand StandardsSOP Section 2.14 / 4.9 — Legal, COI & Paid-if-Paid

PreviousNext lesson