What is a shift handover board on a screen?

It is the handover information that usually lives on a whiteboard, run instead as an editable board on a screen: what ran, what stopped, what the next shift is walking into, with a line per item and who owns it. Because it is a show rather than a whiteboard it can be typed on a phone at the end of a shift, set at a size that reads across the floor, and it is not wiped by whoever needs the space.

Can it prove that a worker read a safety notice?

No. There is no acknowledgement, no sign-off, no per-person tracking and no audit trail of what a board showed on a given date, so nothing in ChannelOS can evidence that an instruction was read. Where a regulator or an insurer expects that evidence, it has to come from an EHS or training system and the screen is the readable copy beside it.

Can it be used for emergency alerts?

Not as the alerting mechanism. ChannelOS has no integration with fire panels, alarm systems or mass notification platforms, and a screen depends on a network and a working display, so it must never be the only way a warning reaches people. Broadcast controls can put a message on every screen at once, which is useful as a supplement to a real alerting system, never as a replacement for one.

Who types the handover, and from what?

Whoever is handing over, from a phone. The editor has a proper phone build rather than a squeezed desktop one, and the notice board tool has a shift handover preset, so the board is a few lines typed into a known shape rather than a design job. It reaches the floor's screens in seconds because the screen derives what it shows from the schedule in real time.

Will the board still be correct overnight with nobody there?

Yes. The board sits on a channel with its own daily and weekly timeline and the screen follows that clock, so a night shift sees whatever the schedule says is on at that hour. A screen that loses the network keeps playing what it has rather than going blank, and catches up when it reconnects.

What does a floor screen cost to run?

The first screen is free forever and further screens are billed per screen per month at the rates on the pricing page. Free screens carry a ChannelOS banner that opens into a full slide roughly every two minutes, which on an internal staff-side board some sites accept and others pay to remove.

Safety notice and shift handover boards

The shift handover board, as a show instead of a wiped whiteboard.

The handover board is a whiteboard and the night shift reads a version of it that somebody wiped at six. Everything a site has agreed matters is written on the one surface that cannot be read from more than ten feet away and has no history.

Get a screen live, free All use cases

No card · no box to buy · pairs in about two minutes

What goes on the screen

Running shift handover boards, safety notices, days-since counters and area instructions on screens, typed at the end of a shift from a phone and visible across a floor.

What the next shift is walking into.

What ran, what stopped, what is still open. A notice per line with who owns it, typed on a phone rather than chalked on a board.
Safety notices that are dated.

The current rule, not the one printed two years ago. Changing it is an edit, so it actually gets changed when the rule does.
Readable the length of the floor.

Type set at a size a whiteboard cannot reach, which is the whole reason the notice was being repeated verbally.
Still right at three in the morning.

The board runs on a channel's own clock, so an unattended night shift sees the same board as the day, without anybody being there to set it.

How it is different

Five things that are true here and worth checking elsewhere.

Every one of these is a mechanism rather than a promise, so you can confirm each of them on a free screen before you pay for anything.

01
The screen is live, not polling.

A paired screen holds a connection and derives what it shows from the schedule in real time. Change the board and the screens follow in seconds. There is no publish step, no playlist to re-download and no interval to tune.
02
A channel is a real 24/7 timeline.

Not a playlist. A channel is a named feed with a daily and weekly plan plus date-scoped overrides, so a board can hold Tuesday afternoons, a campaign can own one fortnight, and a screen tuned in follows its own clock all year without anyone touching it.
03
The editor is built for a phone first.

Below a laptop width the whole editor swaps chrome rather than shrinking: a bottom tool bar, a selection bar that navigates as a menu stack, and the deck one tap from the slide counter. Fixing a wrong price from the shop floor is the normal way to use it.
04
AI is at every step, not one button.

Describe the board in a sentence, or hand over the PDF you already print from, and the assistant drafts a real editable show. It stays available to reword, restyle or rebuild a slide by chat, and the same assistant answers product questions in the app.
05
Any screen with a browser can play it.

Android TV, Google TV, webOS, Fire TV, a Chromebox or a laptop in kiosk mode, paired by scanning a code with your phone. There is a native Android TV app too, downloaded as an APK from our own site rather than from Google Play. No media player box, no per-device licence, nothing to sideload.

Nothing to install, in the normal case: open the player URL in the screen's own browser and scan the code with your phone. If you would rather install an app, the native Android TV app is a free download from our own site rather than from Google Play, and a screen running it is on exactly the same plan as a screen running the browser.

When to buy something else

Where ChannelOS is the wrong answer for this.

ChannelOS is not a safety or compliance system. It keeps no audit trail of what a board said on a given day, has no acknowledgement or sign-off, no incident reporting and no integration with an EHS or permit-to-work platform, and nothing on a screen can evidence that a particular worker read a particular instruction. It is also not an emergency alerting system: it has no connection to fire or alarm systems and must never be the only way a warning reaches people. Where a regulator expects evidence, use the system that produces it and treat the screen as the readable copy.

Questions

Answered in full, because a half answer costs you a phone call.

What is a shift handover board on a screen?: It is the handover information that usually lives on a whiteboard, run instead as an editable board on a screen: what ran, what stopped, what the next shift is walking into, with a line per item and who owns it. Because it is a show rather than a whiteboard it can be typed on a phone at the end of a shift, set at a size that reads across the floor, and it is not wiped by whoever needs the space.
Can it prove that a worker read a safety notice?: No. There is no acknowledgement, no sign-off, no per-person tracking and no audit trail of what a board showed on a given date, so nothing in ChannelOS can evidence that an instruction was read. Where a regulator or an insurer expects that evidence, it has to come from an EHS or training system and the screen is the readable copy beside it.
Can it be used for emergency alerts?: Not as the alerting mechanism. ChannelOS has no integration with fire panels, alarm systems or mass notification platforms, and a screen depends on a network and a working display, so it must never be the only way a warning reaches people. Broadcast controls can put a message on every screen at once, which is useful as a supplement to a real alerting system, never as a replacement for one.
Who types the handover, and from what?: Whoever is handing over, from a phone. The editor has a proper phone build rather than a squeezed desktop one, and the notice board tool has a shift handover preset, so the board is a few lines typed into a known shape rather than a design job. It reaches the floor's screens in seconds because the screen derives what it shows from the schedule in real time.
Will the board still be correct overnight with nobody there?: Yes. The board sits on a channel with its own daily and weekly timeline and the screen follows that clock, so a night shift sees whatever the schedule says is on at that hour. A screen that loses the network keeps playing what it has rather than going blank, and catches up when it reconnects.
What does a floor screen cost to run?: The first screen is free forever and further screens are billed per screen per month at the rates on the pricing page. Free screens carry a ChannelOS banner that opens into a full slide roughly every two minutes, which on an internal staff-side board some sites accept and others pay to remove.

More of these on Answers, which covers cost, hardware and what happens when the wifi drops.

When a box is the right answer

A screen that is already playing keeps playing if the wifi drops, but it needs the connection back to come up again after a power cut, because nothing is cached on the television itself. If a screen has to survive a long outage entirely on its own, buy a player from a company that sells one and ask them about local storage. That is a real reason to pay for hardware. Ours is not one of them.

Get one screen live first.

Pair a screen, put a board on it, and see whether the mechanism above holds before you pay for anything. The first screen is free forever.

Pricing shows what a second screen costs and what the free one leaves out.

Free screens show a ChannelOS banner, and about every 2 minutes it opens into a full ChannelOS slide; any paid plan removes both.

The shift handover board, as a show instead of a wiped whiteboard.

Running shift handover boards, safety notices, days-since counters and area instructions on screens, typed at the end of a shift from a phone and visible across a floor.

What the next shift is walking into.

Safety notices that are dated.

Readable the length of the floor.

Still right at three in the morning.

Five things that are true here and worth checking elsewhere.

The screen is live, not polling.

A channel is a real 24/7 timeline.

The editor is built for a phone first.

AI is at every step, not one button.

Any screen with a browser can play it.

Where ChannelOS is the wrong answer for this.

Answered in full, because a half answer costs you a phone call.

When a box is the right answer

The rest of the picture.

Notice board maker

Manufacturing signage

Digital signage for warehouses

Internal communications

Get one screen live first.