Template

How to Ask a Clear Technical Question at Work (with a Template)

A short template for asking a technical question so the reader can answer without a follow-up: context, observation, question, impact and timing.

Templates and checklists · Last reviewed

A good question can be answered in one reply. It names what you are working on, what you saw, what you need to know, and what depends on the answer. Use the template below for an email or a message.

The template

Subject: Clarification needed: [system or deliverable]
PartWhat to write
ContextI am preparing [task] using [drawing, specification or data source, with its revision].
ObservationThe available information shows [one specific fact or conflict].
QuestionPlease confirm [one clear question].
ImpactThis affects [the calculation, drawing, selection or coordination item].
Required timingA response by [date] would support [milestone].

A filled-in example

Subject: Clarification needed: Panel LP-2 load schedule

  • Context: I am preparing the load calculation for panel LP-2 using electrical drawing E-201 revision C.
  • Observation: The schedule on E-201 lists the rooftop unit as 28 A, but the mechanical schedule M-001 revision B shows the same unit at 34 A.
  • Question: Please confirm which value governs.
  • Impact: It changes the panel total and the feeder size on the one-line diagram.
  • Required timing: A reply by Thursday would let me finish the calculation before the Friday review.

Before you send it

  • Have you checked the drawings, specifications and earlier emails for the answer?
  • Is it one question? Split a long list into separate messages when the answers go to different people.
  • Does it name the document and its revision, so the reader looks at the same version you did?
  • Does it separate what you saw from what you think it means?

Three more examples

  • A drawing conflict: "The one-line diagram E-101 rev B shows a 400 A main, while the panel schedule E-601 rev B shows a 600 A main. Which governs? It changes the feeder size I am calculating."
  • An unclear specification: "Section 26 05 19 requires 75 °C rated conductors, but the equipment schedule lists 60 °C terminations on panel LP-1. Should I size to the 60 °C column?"
  • Missing data: "The mechanical schedule does not give the motor power factor for AHU-3. I assumed 0.85 for the load calculation. Please confirm or send the nameplate."

When not to send a message

  • When the answer is in a document you have not read yet.
  • When the question is urgent and safety-related. Call the right person.
  • When the question depends on a decision that has not been made. Ask when it will be made instead.

Related tools and labs

Calculators, labs and simulators are part of the All-Access Pass.

More first 90 days

Questions

Should I propose an answer?

Yes, when you can. "I assume X unless told otherwise" lets the reader confirm with a single word, and it records the assumption you used.

Who should I ask?

Ask the person responsible for the document or decision. If you are not sure, ask your supervisor who it is.

Should I send questions by email or chat?

Follow your team's habit. Email or a tracked request suits questions whose answer affects a deliverable, because it leaves a record. Chat suits quick clarifications.

What if I get no reply?

Follow up once, politely, shortly before the deadline you stated. If it is still blocked, tell your supervisor what is waiting and what assumption you will use meanwhile.

Educational material. Examples use simplified, hypothetical inputs and are not a design, a construction document or professional engineering advice. Confirm requirements with the codes and standards adopted where the work is built and with a licensed engineer.

← All first 90 days