What does the fan reading prove?
Reconcile a dashboard reading and an on-site report before you brief the controls lead.
The question
You are a building controls technician at a fictional Winnipeg office. Both reports below refer to unit AHU-14 at 09:20. You can read the records and brief the controls lead.
- Remote dashboardSupply fan 100%.
- On-site operatorI felt no air at the room grille served by AHU-14.
Record airflow as verified only when there is separate confirmation for this unit and time.
“Can your handoff say that airflow was verified?”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: What does each report establish?
What would you do here? Open the move you’d make.
Report that the fan is running at full speed.
Tempting, but it misses something. The tile does not establish whether 100% is a measured speed.
Report both observations and ask what the percentage represents.
The strong move. This gives the lead the evidence without assuming how the dashboard obtains the value.
Tell the lead the fan has failed.
Tempting, but it misses something. A report from one grille does not identify which part of the system caused the result.
See how a strong candidate says it
“The tile shows 100%, and the operator reports no air at the grille. I’d record both and find out what the tile measures before deciding what it proves.”
Why it works: The two reports refer to the same unit and time. The tile label leaves the meaning of the percentage unclear.
Step 2: Which record would you request?
What would you do here? Open the move you’d make.
Ask which point feeds the tile and request the matching airflow record.
The strong move. The two records address the display’s meaning and the verification requirement.
Ask for a second capture of the same tile.
Tempting, but it misses something. A clearer capture would still show a percentage without explaining its source.
Treat the matching unit and time as sufficient confirmation.
Tempting, but it misses something. Matching the records establishes what event they concern. It does not establish that either record verifies airflow.
See how a strong candidate says it
“I’d ask the controls lead for the current point list and any separate airflow confirmation for AHU-14 at 09:20.”
Why it works: The point list tells you what the tile represents. The separate record tells you whether the handoff rule is met.
Step 3: What does the point list change?
The point list identifies the tile as Fan speed command. A separate AHU-14 record at 09:20 reads Airflow proof: Not proven.
What would you do here? Open the move you’d make.
Discard the 100% value as an old reading.
Tempting, but it misses something. The value is current and tied to AHU-14. It records a request.
Use the proof entry to diagnose a broken fan.
Tempting, but it misses something. The entry shows that airflow was not confirmed. It does not identify a cause.
Record the request and keep airflow verification open.
The strong move. The command explains the remote value. The airflow record does not meet the handoff rule.
See how a strong candidate says it
“The 100% value is the requested fan speed. The separate record leaves airflow unverified. I’d keep the issue open and leave the cause for the controls lead to check.”
Why it works: A valid request can exist without separate confirmation that the requested result occurred.
Step 4: How would you brief the lead?
What would you do here? Open the move you’d make.
Close the handoff because the dashboard value is explained.
Tempting, but it misses something. Explaining the display leaves the airflow check open.
Give the lead both records and ask for verification and a label review.
The strong move. The lead can see what is known, what is missing and why the display caused confusion.
Send only the operator’s report.
Tempting, but it misses something. The request and separate record help the lead understand the mismatch and the evidence still needed.
See how a strong candidate says it
“AHU-14 at 09:20 showed a 100% fan request. The operator reported no air at the grille, and the separate record did not confirm airflow. The issue stays open. I’d ask you to confirm the result and review the dashboard label.”
Why it works: The handoff gives the lead the unit, time, request, observation and open verification.
The answer, in short
- Decision
- Keep airflow verification open and brief the controls lead.
- Because
- The display shows a request. The separate airflow record does not confirm the result.
- What would change it
- The controls lead has confirmation of airflow for the same unit and time.
Common traps
- Reading a request as a measured result.
- Treating missing confirmation as a diagnosis.
Check your answer
- What did the remote tile show?
- What did the operator observe?
- What did the point list change?
- What does the controls lead need next?
Last reviewed Nov 11, 2026
