OET Reading Part B: 직원 공지에서 대상, 허용, 예외를 정확히 읽는 법

Message 1 — For staff covering evening reception

The coordinator will hold a short practical briefing on Tuesday before the evening desk opens. It is intended for colleagues who are covering that desk this month, including anyone covering a shift for another person. Staff who work only at daytime reception do not need to attend. The briefing will explain where evening enquiries are recorded and whom to contact if a practical issue cannot be resolved at the desk. It will not introduce a new appointment system or change anyone’s roster. If you are scheduled for evening cover but cannot attend, contact the coordinator to arrange another way of receiving the information before your first evening shift.

Message 2 — Shared callback record

A review of last week’s callback work showed that most calls had been completed, but some outcomes were recorded only in personal emails. This makes it difficult for a colleague covering the desk to know whether a visitor has already received the requested practical information. From today, please put the outcome of each callback in the shared callback field as well as keeping any other record required by the existing process. Use a brief factual entry; there is no need to copy an entire conversation. This message does not ask staff to repeat completed calls. Its purpose is to make the current status visible to the next colleague who may need it.

Message 1 — For staff covering evening reception

The coordinator will hold a short practical briefing on Tuesday before the evening desk opens. It is intended for colleagues who are covering that desk this month, including anyone covering a shift for another person. Staff who work only at daytime reception do not need to attend. The briefing will explain where evening enquiries are recorded and whom to contact if a practical issue cannot be resolved at the desk. It will not introduce a new appointment system or change anyone’s roster. If you are scheduled for evening cover but cannot attend, contact the coordinator to arrange another way of receiving the information before your first evening shift.

Message 2 — Shared callback record

A review of last week’s callback work showed that most calls had been completed, but some outcomes were recorded only in personal emails. This makes it difficult for a colleague covering the desk to know whether a visitor has already received the requested practical information. From today, please put the outcome of each callback in the shared callback field as well as keeping any other record required by the existing process. Use a brief factual entry; there is no need to copy an entire conversation. This message does not ask staff to repeat completed calls. Its purpose is to make the current status visible to the next colleague who may need it.

Notice 1 — Circulating updated contact details

Draft contact lists are prepared by the administration team, but a draft should not be sent to the wider staff group. Before circulation, the service coordinator must confirm that the changed numbers and role titles are correct. Unchanged entries do not need to be rewritten, although an obvious error should still be reported. If a confirmation is delayed, continue to use the current approved list and tell the coordinator which change is awaiting a check. Please do not substitute a number found in an old personal email without verification. The purpose of this process is to keep a single dependable reference available, rather than creating several competing versions with different information.

Notice 2 — Alternative training attendance

Staff booked on the Friday workshop should attend their confirmed session unless the training team agrees an alternative. A colleague who has a timetable conflict may request another session through the shared training inbox. The request should identify the original booking and explain which available alternative would be suitable. Sending a request does not automatically transfer the booking. The team must check capacity and reply with confirmation before the colleague treats the change as agreed. Until then, the original place remains reserved. If no suitable alternative can be arranged, the team will discuss the next option directly with the colleague; staff should not offer their place to an unregistered person.

Notice 1 — Circulating updated contact details

Draft contact lists are prepared by the administration team, but a draft should not be sent to the wider staff group. Before circulation, the service coordinator must confirm that the changed numbers and role titles are correct. Unchanged entries do not need to be rewritten, although an obvious error should still be reported. If a confirmation is delayed, continue to use the current approved list and tell the coordinator which change is awaiting a check. Please do not substitute a number found in an old personal email without verification. The purpose of this process is to keep a single dependable reference available, rather than creating several competing versions with different information.

Notice 2 — Alternative training attendance

Staff booked on the Friday workshop should attend their confirmed session unless the training team agrees an alternative. A colleague who has a timetable conflict may request another session through the shared training inbox. The request should identify the original booking and explain which available alternative would be suitable. Sending a request does not automatically transfer the booking. The team must check capacity and reply with confirmation before the colleague treats the change as agreed. Until then, the original place remains reserved. If no suitable alternative can be arranged, the team will discuss the next option directly with the colleague; staff should not offer their place to an unregistered person.

Update 1 — Preparing the next learning session

Several colleagues asked whether new presentation folders were needed for the next session. The training team has checked the stock and confirmed that the existing folders can be reused if they are complete and in good condition. Please check the contents against the current session checklist, replacing only missing or outdated pages. There is no request to redesign the folders or order a new set for every participant. The checklist has changed in one section, so simply handing out last month’s folders without checking them would also be inappropriate. We want the preparation to be accurate and efficient: keep usable material, update what has changed and report any shortage through the shared list.

Update 2 — Appointment reminder coordination

Visitors have occasionally received two practical reminders for the same booking because different staff members could not see that another reminder had already been sent. The team is not stopping reminders. Instead, staff should check the shared reminder field before sending one and record the date when a reminder is completed. If the field is unclear, ask the colleague who last handled the booking before contacting the visitor again. A further reminder may still be appropriate when circumstances change, but it should be coordinated and its purpose clear. This update addresses unnecessary duplication; it does not create a rule that a visitor can never receive another message about the same appointment.

Update 1 — Preparing the next learning session

Several colleagues asked whether new presentation folders were needed for the next session. The training team has checked the stock and confirmed that the existing folders can be reused if they are complete and in good condition. Please check the contents against the current session checklist, replacing only missing or outdated pages. There is no request to redesign the folders or order a new set for every participant. The checklist has changed in one section, so simply handing out last month’s folders without checking them would also be inappropriate. We want the preparation to be accurate and efficient: keep usable material, update what has changed and report any shortage through the shared list.

Update 2 — Appointment reminder coordination

Visitors have occasionally received two practical reminders for the same booking because different staff members could not see that another reminder had already been sent. The team is not stopping reminders. Instead, staff should check the shared reminder field before sending one and record the date when a reminder is completed. If the field is unclear, ask the colleague who last handled the booking before contacting the visitor again. A further reminder may still be appropriate when circumstances change, but it should be coordinated and its purpose clear. This update addresses unnecessary duplication; it does not create a rule that a visitor can never receive another message about the same appointment.