Loading page
Choose the right channel and make required actions clear.
4 of 4 updates shown, newest first. Times are shown in UTC.
| Update | Channel | Audience | Response | Kept until |
|---|---|---|---|---|
| Berth 4 lift 2 out of service until ThursdayPublished 22 Oct 2026, 12:16, UTC timeSafety notice | Aberdeen Harbour, Berth 4 Cold Store | 2 peopleFixed when it was published, so later joiners are not included | 1 of 2 acknowledgedStill waiting on some people | 20 Oct 2033, 13:51 |
| Device policy change: background refresh now requiredPublished 20 Oct 2026, 13:51, UTC timeCompany update | All staff | 6 peopleFixed when it was published, so later joiners are not included | 6 of 6 acknowledgedEveryone in the fixed audience has acknowledged | 20 Oct 2033, 13:51 |
| Saturday inbound moved to 06:00Published 22 Oct 2026, 07:31, UTC timeShift update | Dundee Depot | 2 peopleFixed when it was published, so later joiners are not included | No response was asked for | 20 Oct 2033, 13:51 |
| Revised cold store entry procedurePublished 18 Oct 2026, 13:51, UTC timeSafety notice | Aberdeen Harbour, Berth 4 Cold Store | 2 peopleFixed when it was published, so later joiners are not included | 1 of 2 acknowledgedStill waiting on some people | 20 Oct 2033, 13:51 |
An acknowledgement records that a signed-in person tapped acknowledge. It is not evidence that they read, understood or agreed to the update. Updates are delivered inside the Bluecollar app only. Nobody is sent a text message or an email, so an urgent notice may need a phone call as well.
An acknowledgement means the person tapped acknowledge while signed in. It does not prove that they read, understood or agreed to the update.
Who this reached could not be read. Nothing has changed and the announcement itself is unaffected. This is not a sign that nobody has responded. Try again in a moment.