Employee announcements & acknowledgment tracking

Employee announcements with acknowledgment tracking.

Sharing an important message is the first step. Barkly Connect helps you choose who receives it and see who has viewed or acknowledged it, so your follow-up starts with a clear picture.

Built for everyday communication

Give important information a clear path.

01

Start with the audience.

Choose the employees, groups, or organization units that need the update. Keep a department notice focused, or share a broader announcement within your authorized scope.

02

Make the message easy to act on.

Add the announcement, supporting files, and a clear next step. Publish now or schedule it for later. Enable comments when employees need a place to ask questions.

03

Follow up with the people who need it.

Review the recipient list by Not Seen, Seen, or Acknowledged status. Use that information to guide your follow-up instead of asking everyone to confirm again.

Put it to work

Useful for the updates people need to notice.

Workplace procedures

Share an updated procedure with the affected team and request an explicit acknowledgment.

Staff meetings & training

Publish session details and supporting materials so employees have a common reference.

Operational changes

Keep the right departments informed about a building closure, service change, or event setup.

Clarity built in

A recorded response, with a clear meaning.

A view records that an announcement was opened. An acknowledgment records the employee’s explicit action. It does not establish that they understood the message, and it is separate from Barkly’s document-signing workflows. Keep the required action appropriate to the update.

Explore employee communication
A few useful answers

Announcements & Acknowledgments FAQs

What is the difference between Seen and Acknowledged?

Seen indicates the recipient opened the announcement. Acknowledged indicates they also used the Acknowledge action. Barkly keeps these states separate so opening a message is not mistaken for an explicit response.

Can we see who still needs to respond?

Yes. Authorized users can review recipient status and filter by Not Seen, Seen, Acknowledged, or All. That makes it easier to identify who still needs follow-up.

Can announcements be scheduled?

Yes. Authors with the required permissions can publish an announcement immediately or choose a future publication time. They can also add supporting attachments and control whether comments are available.

Is an acknowledgment an electronic signature?

No. Announcement acknowledgment is an explicit response to an announcement. Document signatures use a separate workflow; choose that workflow when the document requires a signature.

Practical resource · By Barkly Connect

8 employee announcement templates for frontline teams.

Start with what is happening, who it affects, when it happens, and what employees should do next. Open a template, copy the text, and replace every bracketed field before sending.

Dates in these examples are written instructions, not automatic reminder or deadline settings. Choose the relevant permitted audience and review the recipient list.

1. A workplace procedure is changing

Use it when: A routine process has changed and affected employees need a common written reference.

Audience: Employees who perform the process, plus the supervisors or support teams who need to answer questions.

Acknowledgment: Useful when you need a recorded response to this specific update. Check practical understanding separately.

Title: [Procedure name] changes on [date]

Starting [date], [affected team/location] will use [new process] for [activity]. This replaces [previous process].

What you need to do:
1. [First action.]
2. [Second action.]
3. [Where to record or confirm completion, if applicable.]

The current instructions are [attached / available at link], dated [version date].

Please read the update and select Acknowledge by [date and time]. That response records your acknowledgment of this announcement; it does not confirm that you have completed the steps.

Questions or a situation the instructions do not cover? Contact [name/role] through [channel] before proceeding.

Before sending: Check the effective date and the attachment version. Remove obsolete instructions from the message. Assign someone to answer questions.

2. A staff meeting is coming up

Use it when: Employees need meeting details and a clear way to handle a scheduling conflict.

Audience: The relevant location, department, or selected employees. Include employees on other shifts if the meeting concerns them.

Acknowledgment: Usually unnecessary for a simple invitation. If a response is required, say whether you need acknowledgment, attendance confirmation, or a choice of session; those are different actions.

Title: [Team] meeting on [date]: [main topic]

We will meet on [date] from [start time] to [end time, time zone] at [location / meeting link].

We will cover:
- [Topic one.]
- [Topic two.]
- [Decision or question for the team.]

Please review [material] beforehand and bring [anything needed].

If this time conflicts with your shift or assigned work, contact [name/role] by [date] to arrange [alternative session / another way to receive the update].

[Name/role] will share [notes / confirmed decisions] in [location/channel] after the meeting.

Before sending: Verify the room or link. Explain how employees who cannot attend will receive the information. Do not use announcement acknowledgment as an attendance record.

3. Training sessions are available

Use it when: A defined group needs the schedule and instructions for upcoming training.

Audience: Employees expected to attend and managers responsible for arranging coverage.

Acknowledgment: Optional for confirming the announcement was acknowledged. Track enrollment and training completion through the process designated by your organization.

Title: [Training name]: choose a session by [date]

[Audience] should attend [training name] by [completion date]. The session covers [short description].

Available sessions:
- [Date, start/end time, time zone, location.]
- [Date, start/end time, time zone, location.]

To enroll, [specific instructions] by [enrollment deadline]. Confirm coverage with [name/role] before selecting a session if needed.

Bring or review [materials]. If none of these sessions works for you, contact [name/role] through [channel] by [date].

Completing the enrollment step reserves your session. Training completion will be recorded through [designated process].

Before sending: Confirm session capacity and the enrollment method. Do not imply that Barkly automatically books seats or records course completion.

4. A planned workspace closure affects the team

Use it when: Scheduled maintenance or another planned change affects a room, entrance, or shared work area.

Audience: Employees who use the space and teams coordinating the work. Avoid broadcasting an irrelevant local notice to every location.

Acknowledgment: Useful if affected employees must actively change their routine.

Title: [Space] unavailable [date/time]–[date/time]

[Space at location] will be unavailable from [start date/time] until [expected end date/time] for [planned work].

During this period:
- Use [alternative space or route].
- Move [items/activity] to [location] by [deadline].
- Direct questions about [topic] to [name/role and channel].

Please review [attached map/instructions] before your next affected shift and select Acknowledge by [date/time].

[Name/role] will post an update in [channel] if the planned reopening time changes.

Before sending: Confirm an approved alternative and identify who will post changes. Use your organization’s designated urgent channel if immediate action becomes necessary.

5. A new employee is joining

Use it when: You want colleagues to know who is joining and how they will work together.

Audience: The employee’s team and people who will work with them.

Acknowledgment: Not needed for a welcome message.

Title: Welcome [preferred name] to [team]

Please welcome [preferred name], who joins [team/location] as [role] on [date].

[Name] will work with us on [responsibilities relevant to this audience]. [Manager/buddy] will help them get started.

You can meet [name] at [optional introduction event]. For questions about [work responsibility], use [approved work contact/channel].

Welcome to the team, [name]!

Before sending: Confirm the employee’s preferred name and permission to share any biography or photo. Keep personal contact information out of the announcement.

6. Teams need to coordinate an event

Use it when: Several teams have different responsibilities for a planned event.

Audience: The teams and individuals doing the work, plus the person coordinating it.

Acknowledgment: Useful for assignment awareness when requested. A separate response should confirm whether an assignment is workable.

Title: [Event] on [date]: team responsibilities

[Event] takes place on [date/time] at [location]. [Name/role] is coordinating preparations.

Responsibilities:
- [Team/person]: [task], ready by [date/time].
- [Team/person]: [task], ready by [date/time].
- [Team/person]: [task], ready by [date/time].

The current setup plan is [attached / available at link].

Please read your assignment and select Acknowledge by [date/time]. If you cannot complete it or need help, contact [coordinator and channel] by [date/time] so we can adjust the plan.

Confirm completed work through [designated channel/process].

Before sending: Use named owners and specific deadlines. An acknowledgment of the announcement is not confirmation that a task is complete.

7. A previous announcement needs a correction

Use it when: A published date, location, instruction, or other detail was wrong or has changed.

Audience: Everyone affected by the original information, including anyone newly affected by the correction.

Acknowledgment: Consider requesting it if the correction changes what employees must do. Treat this as a distinct update; do not assume acknowledgment of an earlier message covers it.

Title: Correction: [topic] — use [correct detail]

Please use this correction for the announcement “[original title]” published on [date].

Previous information: [old detail].
Correct information: [new detail].

This means you should [specific action] from [date/time]. [What remains unchanged, if useful.]

The corrected reference is [attachment/link and version date]. Please stop using [obsolete reference].

[If needed: Read this correction and select Acknowledge by date/time.]

For questions, contact [name/role and channel].

Before sending: Identify the original clearly and ensure the corrected reference is accessible. Remove the optional acknowledgment sentence if no explicit response is needed.

8. A manager needs to follow up on an acknowledgment

Use it when: A response deadline is approaching or has passed, and a manager has reviewed recipient status.

Audience: Only the employees who still need the follow-up. Send privately or to the relevant permitted audience; avoid sharing a list of nonresponders with the whole team.

Acknowledgment: Ask employees to acknowledge the original announcement after reviewing it, so the response stays with the update it concerns.

Title: Follow-up: please review [announcement title]

Please review “[announcement title]” at [link/reference]. It explains [brief purpose] and takes effect on [date].

As of [date/time], the original announcement does not show your acknowledgment. Please read it and select Acknowledge there by [date/time].

If you cannot access it, are unsure what to do, or have already raised a question, contact [name/role and channel]. We can help resolve the issue.

Thank you,
[Sender]

Before sending: Recheck status and avoid assuming that no acknowledgment means refusal. If someone has not opened the message, first consider access, their work schedule, and whether they have had a reasonable opportunity to review it.

Give every response a clear meaning.

Acknowledgment records an explicit response. It does not establish understanding, attendance, training completion, or completion of the requested work. Document signatures use a separate workflow.

For account access planning, read our frontline communication guide. For community-specific examples, explore senior living staff communication.

Built around your team

Make the next important update easier to follow.

Start setting up Barkly Connect around your organization, people, and permissions.

Get Started

Have questions? Contact Barkly