Technical Reading and Professional Writing for Construction

Why Technical Reading and Professional Writing Matter in Construction Management

Construction projects run on documents. Every decision, change, and agreement is recorded in writing—contracts, meeting minutes, Requests for Information (RFIs), submittals, and field notices. When those documents are unclear, the result is disputes, rework, delays, and cost overruns. As a construction manager or estimator, your ability to read contract language precisely and write without ambiguity is as essential as reading a set of drawings.

This lesson builds three practical skills: reading contract language critically, producing accurate meeting minutes, and writing a clear RFI.

---

Reading Contract Language: Shall, Should, and May

Contracts use specific words deliberately. Confusing them can mean the difference between a contractual obligation and a suggestion.

• Shall — mandatory. The party named must perform this action. Example: "Contractor shall submit a schedule of values within ten days of contract execution." Missing a "shall" requirement can constitute breach of contract.
• Should — recommended but not strictly required. Often used in specifications for best practice guidance.
• May — permissive. The named party has the option but is not obligated. Example: "Owner may request additional samples at no extra cost."

When you read a contract, mark every "shall" as a hard deadline or obligation. Build those dates and deliverables into your schedule and cost model.

Defined Terms. Most contracts include a Definitions section. A capitalized term—such as Contract Documents, Substantial Completion, or Subcontractor—has a precise meaning stated in that section. Never substitute everyday meaning for a defined term. Read the definition, then apply it consistently throughout the document.

Notice Deadlines. Contracts typically require written notice within a specified number of days when a claim, differing site condition, or change in scope arises. Missing a notice deadline can waive your right to additional compensation or time, even if your underlying claim is valid. Locate notice clauses early, record the deadlines, and calendar them.

Rewriting Ambiguous Clauses. When you identify a clause that is unclear, rewrite it in plain language without changing its legal intent. Test your rewrite: does it still create the same obligation, for the same party, with the same consequences? If yes, it is a good plain-language revision.

---

Writing Professional Meeting Minutes

Meeting minutes are the official record of what was decided and who is responsible for what. On a construction project, they are referenced in dispute resolution and form part of the project history. Sloppy or incomplete minutes create gaps in that record.

A standard set of construction meeting minutes includes:

1. Header — project name, meeting type, date, time, and location.

2. Attendees — full names and company or role. Note anyone who was invited but absent.

3. Agenda items — brief statement of each topic discussed, in order.

4. Decisions made — clear statement of what was agreed, by whom, and effective when.

5. Action items — each item gets an owner (by name, not just title), a due date, and a brief description of the deliverable. A table format works well.

6. Next meeting — date, time, and location if known.

Write in the past tense and third person. Avoid opinions and personal commentary. Record facts: what was said, decided, or assigned. Distribute minutes within 24 to 48 hours of the meeting so errors can be corrected while memory is fresh.

Safety note: If a safety issue is raised during a meeting—a hazard reported, a near-miss discussed, or a corrective action assigned—that item must appear in the minutes with a clearly named owner and a due date. Safety action items are never left as general notes.

---

Completing an RFI

A Request for Information (RFI) is a formal written question submitted by the contractor to the architect, engineer, or owner when a document discrepancy, omission, or conflict requires clarification before work can proceed. An RFI that is vague delays the project; one that is precise speeds resolution.

A complete RFI includes:

• RFI number — sequential, for tracking.
• Project name and contract number.
• Date submitted and response requested by date.
• Submitted by — contractor name and contact.
• Reference documents — drawing sheet number, detail number, and specification section number. Be exact.
• Description of the question — state what the documents show, where they conflict or are silent, and why clarification is needed before proceeding. One clear paragraph.
• Suggested resolution — propose a solution. This speeds the response and shows technical competence. Label it clearly as a suggestion, not a directive.
• Response field — left blank for the design team to complete.

Example description field (abbreviated): "Drawing A3.1, Detail 5/A3.1, calls for a 4-inch concrete slab on grade. Specification Section 03 30 00 requires 6-inch slab on grade in all mechanical rooms. Area 114 on Drawing A1.0 is labeled 'Mechanical Room.' Please confirm required slab thickness for Area 114."

Note the specifics: drawing sheet, detail reference, specification section, and room designation. Anyone reading this RFI can locate every referenced document without asking a follow-up question.

---

A Note on Professionalism and Safety

Every document you produce becomes part of the project record. Use correct grammar and punctuation. Avoid slang. When describing a safety concern in writing, be direct and specific—vague language in a safety document can result in the hazard going uncorrected. If an action item involves lockout/tagout, fall protection, or any life-safety measure, state the applicable requirement clearly and assign it a due date of the next working day at the latest.