Rewriting a Payroll Delay Memo for Tone and Clarity
The following draft is about to be sent by the HR manager of a 240-person logistics firm to all staff. Payroll has been delayed by two days because the bank that processes the salary account has changed its file format. The vendor has confirmed that a correction is in progress but has not given a firm completion date. The draft reads:
“Subject: Payroll issue Hi team, just a quick note that payroll is delayed because the vendor had some problems with the bank. They said it will be fixed soon. We are very sorry for the inconvenience. Everyone should check their accounts on Friday. If you don’t receive it, please contact HR. Also, the deadline for reimbursement is extended. Some employees have not submitted bills yet, they need to do it by Monday. We hope this is okay. Thanks.”
The manager wants the message to be clear, calm and authoritative, and to avoid promising a date that may slip. The firm also has a policy that salary delays beyond three working days must be reported to the staff council.
1. Identify three clarity or tone problems in the draft, quoting the relevant words and explaining the risk each creates.
Read the worked answer
Three problems stand out:
“They said it will be fixed soon.” The pronoun “they” could mean the vendor or the bank, and “soon” gives no usable expectation. Employees may interpret “soon” as today, while the manager may mean this week; the ambiguity increases follow-up queries and erodes trust.
“Some employees have not submitted bills yet, they need to do it by Monday.” The second “they” is ambiguous, and the sentence reads as a vague threat. It is unclear whether the deadline applies to all staff or only those with pending bills, and unclear what happens if Monday is missed.
“We hope this is okay.” This weakens the manager’s authority at exactly the point where staff need a clear process. It sounds apologetic but not accountable. A better close states what the firm is doing, what staff should do, and when the next update will come. Separately, the draft omits the staff-council trigger, which is a policy omission rather than a style issue.
2. Rewrite the memo in 100–140 words, keeping the same facts, removing ambiguity, and adding the staff-council trigger without promising a fixed payment date.
Read the worked answer
Subject: Delay in salary credit
Dear colleagues,
Salary credits for this month will be delayed by up to two working days. The delay is caused by a file-format change at the bank that processes our salary payments. The vendor has confirmed that a correction is in progress but has not yet given a firm completion date.
Please check your account on Friday. If the credit has not appeared by then, contact HR with your employee number and bank details. The reimbursement deadline has been extended to Monday; employees with pending bills should submit them by then.
We will write again if the delay extends beyond three working days, and we will report it to the staff council as required. Thank you for your patience.
3. A colleague suggests deleting the sentence about the staff council because it may alarm employees. Evaluate that advice.
Read the worked answer
The advice is understandable but unsound. The sentence does not announce a current escalation; it states a conditional future step: if the delay extends beyond three working days, the matter will be reported. That is exactly the kind of rule employees should know in advance, because it reassures them that there is an accountability mechanism rather than an open-ended delay.
Deleting the sentence would create two risks. First, it would breach the firm’s own policy if the delay later crosses the threshold and staff have not been told. Second, it would make the eventual disclosure look reactive or concealed. The better approach is to keep the sentence but phrase it conditionally and calmly, as in the rewrite. If the manager is worried about alarm, the remedy is precision-state the threshold and the trigger-not silence.