Repairing a Lift-Maintenance Notice Before Circulation

The sentence is: "Employees who have deliveries expected should inform the security desk, which will be closed after 8 pm."

The relative clause "which" has no fixed antecedent.

Reading A - "which" = the security desk. The desk shuts after 8 pm, so a delivery expected at 8.30 pm cannot be reported at all. This collides head-on with the supervisor's evidence that late couriers are routine, and it leaves staff with no compliant action.

Reading B - "which" = the deliveries. Only deliveries expected after 8 pm need to be reported - a plausible but completely different instruction, and one that makes the reporting rule time-bound rather than general.

Consequence: goods arriving after 8 pm may be refused at the gate, accepted without a gate entry, or left unattended in the lobby. If a consignment goes missing, no one can establish whether it was reported, so the loss lands on the employee or on facilities. Staff who guess wrong once will stop reporting altogether.

Fix: split the sentence and name both subjects explicitly - "Report expected deliveries to the security desk before 6 pm. The desk closes at 8 pm; for later deliveries call the supervisor on extension 214."

Model rewrite: "Lift no. 2 will return to service by 6 pm on Wednesday if the spare parts reach us by Monday. If the parts are delayed, the lift will stay closed on Thursday, and this notice will be updated by 5 pm on Tuesday."

What changed and why:

1. "On time" → "by Monday". The original trigger is undefined, so no reader can judge the risk. A dated condition lets a wheelchair user or a team with a Wednesday client visit decide today.
2. A stated fallback. "Only if" told staff that failure was possible but not what happens then; the rewrite names Thursday as the exposure.
3. An update commitment. "This notice will be updated by 5 pm on Tuesday" gives one channel and one deadline, which pre-empts the forty help-desk calls that an open-ended clause guarantees.
4. Certainty where it exists. "Will return to service by 6 pm" is a commitment, not a hope; the contingency is carried entirely by the condition, not smeared across the whole sentence.

The test of a notice is not whether it is polite but whether a reader can act on it without asking a follow-up question.

Best subject line: (i) "Lift 2 shut: Mon–Wed".

The audience is all 400 staff, and the fact that changes everyone's week is which lift is out and when. Option (i) front-loads that in five words and survives being read on a phone notification. Option (ii) is pure filler - "important update" tells the reader the topic is important without saying what it is, which is exactly the test a subject line must pass. Option (iii) is not wrong in content but mis-sizes the audience: the delivery instruction concerns perhaps a dozen people, and putting it in the subject line suggests a general action is required when for most staff none is. The delivery rule belongs as a bolded line in the body, with (i) as the header.

Correction: "We regret the inconvenience and thank you for your cooperation."

The original fails on collocation and on stance. One cooperates with a person or a request, not with an inconvenience; the verb that takes "inconvenience" is bear with. Worse, "kindly cooperate with the inconvenience caused" asks staff to put up with a problem the writer has not acknowledged or owned. A notice should apologise in the first person and thank, not instruct, its readers.