Loading...
Loading...
Dated employee change and benefits notices
Give affected employees one approved source for the change, dates, documents and contacts. Your HR or comms editor keeps it current.
Three routes
The smallest thing that reaches every employee is the right one. I tell you which one I think it is after I see your dates and your documents.
You already have a site or an intranet your team can edit. I add the notice page, the timeline and the documents to it. Your team can then repeat it for the next notice.
Scoped in writing after the inventory.
Your intranet does not exist, or nobody reads it, or only IT can edit it. You get a separate mobile-first site for this notice, with an optional access gate.
Scoped in writing after the inventory.
You publish dated notices repeatedly. Each later notice is added by your editor or scoped separately.
Scoped in writing after the inventory.
Who does the work
Scope
The process
After the inventory, the written scope names the approved wording, access decision, document owners and expected effort.
I list every document, contact, link and date. We agree the notice in scope, the dates, the approver and what AI may do. You mark what the business cannot get wrong.
Output: A content map, a document list with owners, a written scope and the control rules.
I set up the notice, the timeline, the FAQ, the document library, the editor access and the access gate. I load the approved wording, dates and documents. I then check accessibility, links, dates and the noindex tags.
Output: A complete staging site with every date and document in place, and an acceptance checklist.
I publish after your named approver releases the notice and check it live. I then show your editor how to change a date and archive a version.
Output: A live notice, an editor guide and a dated archive plan.
Safeguards
An employee notice goes wrong in 3 ways. The dates disagree. A document goes stale. The page disappears a year later. Here is what holds each one down.
Questions
If an existing channel reaches every affected employee, use it. This offer is for a reach gap your channel owner has already identified.
Yes. That is the point of the build. Your named editor changes the wording, the dates, the FAQ and the documents. I show them how at handover. I show their backup too.
Every page carries a noindex tag or header. A robots file will not remove a page from search results. Google also has to re-read the page before it drops out, so the tag goes on from day 1.
Your IT team approves and owns any email-domain gate. The written scope names who implements and supports it.
This site does not replace any consultation process. Your employment solicitor defines that process and supplies the approved wording.
A QR poster at the point of work: break rooms, locker areas, shift handover. Plus a printable version of the page, and a text-message link if you already text staff. The page opens on a phone first.
You choose at step 1. Either the site becomes your standing notice board, or it goes to a dated archive. Your records policy, or your solicitor, sets how long the notice must stay available. We put that take-down date in writing before launch.
If your employee app already reaches everyone and your team can publish there, use it. Do not buy a second channel.
I do not quote before I see your dates and your documents. After the inventory you get a written scope: the expected effort, the risks and the decision points. It carries an invoice schedule your finance team can process, and a scope reference for your order system. You approve the scope before build work starts.
Hosting region, data collection and analytics are agreed with your data lead and written into the scope. The page must not contain personal data.
Your editor does, from a phone. The dates sit in one field, so the notice and the timeline change together. The written scope states the defect warranty. After that, your editor handles the changes, or you take the standing notice board route.
Send the approved notice, affected groups and publication constraint. I return the route, access questions and risks in writing.
Send me the notice date