Ask it so you can rely on the answer

Article Formal questions & the contract record ~8 minutes

Design ambiguity appears on every live job. Someone asks a question on the phone. Someone else gives a helpful answer. Work proceeds. Months later, two parties remember two different answers — and neither can prove theirs.

Informal clarity is wonderful for teamwork. It is fragile as a basis for cost, time, and safety decisions. When method, sequencing, material choice, or entitlement hangs on what was said, the answer must survive change of staff and selective memory. “We talked about it” is collaboration. “We agreed it and the project can still find it” is a record you can rely on.

What good practice looks like

Construction and professional teams have long distinguished kinds of questioning, even when day-to-day language blurs them.

• Day-to-day clarification that does not change obligations — useful, fast, and often verbal.
• Requests for information that need a dated question, a responsible party, timing expectations, and a written response you can rely on when money, method, or programme follows.
• Correspondence — notices, directions, claims language — that belongs in the formal letter book of the contract when the tone and consequence demand it.

The point is not bureaucracy for its own sake. The point is proportionate formality. Not every “is this clearance okay?” needs a formal instrument. Not every answer that later drives a variation should live only in a chat thread with no due date and no named owner. Mature teams develop a feel for the threshold: if the answer will be cited later, write it where the project can find it.

Good practice also keeps the evidence beside the question. A query without the drawing, sketch, or specification passage that triggered it forces people to re-argue context months later. Linking the question to the controlled document — and preferably the exact revision — turns a verbal spat into a readable file a new starter can understand mid-month.

Where projects slip

Slippage rarely announces itself as carelessness. It sounds cooperative.

• RFIs are replaced by chat threads with no due date and no single owner.
• Responses arrive verbally on a walkaround and never land on the record; site proceeds on recollection.
• The drawing that prompted the question is not linked — so context evaporates when the original asker goes on leave.
• Notices that should be correspondence are softened into “friendly emails” that still change entitlement in practice.
• Closing an RFI becomes optional theatre; open RFIs quietly age into disputes and unfinished design debt.
• Multiple answers accumulate across channels — phone, email, messenger — and the project has no way to say which one ruled.

When the commercial temperature rises, both sides produce screenshots of partial conversations. The workshop spends days reconstructing meaning that should have been a closed question with a dated response. Safety conversations get harder too when method depended on an answer nobody can re-open with confidence.

How Cynilo supports this practice

Cynilo keeps formal questioning next to the documents and people that caused it, so “the answer is somewhere in email” is not the default failure mode.

• RFIs carry the query, timing expectations, conversation, and closure as a project record — something a successor can read without inheriting a private inbox.
• You can start from the document that raised doubt, so the question and the evidence stay related.
• Correspondence holds the formal letters and directions that a dispute file expects to see intact when the contract tone requires more than an RFI.
• Threads and links reduce orphan answers; the project owns the conversation path rather than hoping the right person kept the right forward.

Product how-tos show how to raise and close. Learn is the cultural reminder: if the answer matters, write it where the project can find it. That culture decision belongs to design managers, site engineers, and contract administrators together. The platform makes the habit durable; leadership makes it expected.

Formal issue and revision discipline still matter upstream. A beautiful RFI about the wrong revision wastes everyone. Pair this habit with clear document control and formal send so questions point at the same authority the site is building from.

What good looks like in a week

In a week where questioning is healthy:

• Ambiguities that affect install or procurement become RFIs with clear ownership — not rumours that circulate until someone guesses.
• Responses are readable by someone who joins the project mid-month, without oral briefing from the author.
• Document links make the “about what?” obvious, including which revision the doubt relates to.
• Formal notices use the correspondence register when the contract tone requires it — without turning every hello into a letter.
• Open questions have ages people watch; aging RFIs are treated as programme risk, not wallpaper.

A practical leadership test: pick a decision made last fortnight that affected cost or method, and ask where a stranger would find the authoritative answer. If the answer is “ask Sarah” or “it’s in the chat,” the practice still needs work.

A short story from a water treatment upgrade

On a treatment plant upgrade, a site engineer asked the designer’s team whether a duct routing clash with temporary works could be resolved by a local adjust. A quick call suggested a workable path. Fabrication continued. Two months later a different design contact, covering leave, issued a conflicting instruction on paper. Both answers were given in good faith. Only one had entered the formal question trail — and it was not the earlier verbal steer that the fabricator had followed.

The rebuild and the commercial conversation consumed more energy than raising a proper request for information would have. The project’s lasting change was cultural: if the answer moves metal, it moves as a dated written response linked to the drawing that raised the doubt — not as a helpful memory of a phone call.

Closing

Ask early. Ask clearly. Keep the answer where tomorrow’s team can trust it.

That is not cold. That is respectful of everyone who will inherit the job after you.

Previous: “I emailed it” is not a formal issue

Also related: When “send me the latest drawing” fails for the documents those questions sit on.