How often to update digital signage content on a small screen

The cadence: 15 minutes a day, 1 hour a week

Two numbers carry most small screens, and a third rule keeps them honest.

• The daily check, about 15 minutes. One morning pass for playing errors, content mistakes and lapsed slides, while they are still cheap to fix.
• The weekly batch, about 1 hour. One sitting that loads everything changing on a human calendar: campaigns, seasonal offers, staff notices, a single site's price list.
• The automation line, once a week. Anything needing a hand edit more often than that gets a feed, never more hand edits.

These are working numbers, the pace operators actually keep, and they are short enough to survive a busy week; whether a screen is still current in six months decides itself here. What moves them: a week with more changed slides stretches the batch, and each extra room or building adds a daily check of its own. What never moves is the line at once a week.

Recommendation: Put the morning check at the start of every day and the weekly batch at the same time each week, both with one named owner. Automate anything that would need editing more than once a week, and keep hand edits for campaigns, offers and notices that live a week or longer.

The daily 15-minute check

Four checks, in this order, before the doors open.

• Play state. Look at the screen just after its scheduled on time. You are looking for a black panel, a frozen slide, or a setup menu sitting where the show should be. The player is designed to bring the show up full screen at power-on and to start again within seconds if the app stops, so most mornings this is a glance. If the panel is still dark past its on time, cycle the power. Setting that on time is a one-minute job: schedule the screen on and off each day.
• Mistakes. A wrong price, a misspelled item, a slide cut off at the edges. A slide playing small in one corner is a size mismatch between slide and screen; the fix for slides stuck in one corner walks through it.
• Dates. Every dated slide carries its last day in the file name, so a lapsed campaign is easy to spot on this pass. Note it for the week's batch, and pull it sooner if it is embarrassing to still be showing.
• Numbers. On a staff board, confirm the board matches the current shift or the latest report, not yesterday's.

The weekly one-hour batch

One sitting, four blocks.

1. Collect, about 15 minutes. One list of everything that changed this week: price changes, new offers, notices, photos, corrected slides.
2. Build, about 25 minutes. Slides as JPG, PNG or WebP images; video as MP4 with H.264, the format we recommend. PowerPoint, PDF, HEIC and GIF do not play, so export them to images or video first.
3. Ship, about 10 minutes. The screen connects once to the free IMD Signage Studio app; after that, each week's show goes to the screen from your computer, with no subscription.
4. Proof, about 10 minutes. Watch one full loop of the show at the screen before you walk away.

The collect and build blocks stretch with how much changed. The proof block does not, and skipping it is how a half-built show goes live.

What to automate instead of hand-editing

The line from the table is worth stating as a rule: if a slide's content would need an edit more than once a week, feed it. Hand edits at that pace get dropped first, which is why large rollouts end up with most locations never logging into the content system at all. The screens that stay current are the ones fed automatically, with one central owner doing a weekly pass over the estate.

Feeds that earn their keep:

• Arrivals, queues, wait times. These change by the minute. No batch can carry them.
• Shift boards and production counts. These change every shift, which is exactly what a data-driven board carries. Shop-floor screens are built for this kind of content, and factory data table signage covers the pattern on an offline screen.
• Chain prices. Headquarters pushes price changes on its own calendar. A feed takes them the day they land; a weekly batch leaves old prices up for close to a week.

On our player, the feed path is the screen pulling a playlist from your own web server on a timer: your system writes the show, the screen fetches it on schedule. For several screens or several sites, the three ways to update screens remotely compare the transport options, and planning a remote content workflow covers who pushes, who approves and who checks. A fully fed screen keeps its morning check; the check now watches the plumbing.

Example: a one-screen cafe on a weekly price cycle

Inputs:

• One menu board above the counter playing a show of 28 slides: 24 menu items and 4 seasonal campaign slides. A typical single-site case.
• The supplier's price list arrives each Monday morning, so prices change once a week. Case premise; a chain gets prices from headquarters on their calendar instead.
• Campaign slides change every 4 weeks. Case premise.
• Budgets: 15 minutes for the daily check and 60 minutes for the weekly batch. The cadence set in the first section.

Rule in words: weekly minutes = every daily check in the week + the weekly batch, because the batch day still gets its check. Any content changing faster than once a week leaves the batch and moves to a feed.

Arithmetic:

• Monday, check plus batch: 15 + 60 = 75 minutes.
• Tuesday to Sunday, checks only: 6 days × 15 minutes = 90 minutes.
• Week total: 75 + 90 = 165 minutes, about 2 hours 45 minutes.

Result: 165 minutes a week keeps all 28 slides current, which is about 6 minutes per slide per week (165 ÷ 28 = 5.9).

Decision: prices change once a week, so they stay in the Monday batch, and the 4-week campaigns stay there too. If the cafe adds a soup of the day that changes every morning, that item now changes 7 times a week, past the line: it moves to a playlist the player pulls from the cafe's own web server on a timer, and the batch keeps prices and campaigns. Manual time stays at 165 minutes a week.

Signs your cadence is wrong

• A lapsed offer is still showing. The slide's last day was never written down, or the morning check was skipped. Date every campaign slide in the file name and put the check back on the calendar.
• Prices are wrong for days at a time. Something that changes faster than weekly is being hand-edited. Move it to a feed.
• The show has not changed in months. Nobody owns the batch. Give one person the calendar slot, or strip the hand edits out of that screen and feed it; taking over an inherited setup starts from exactly that state.
• The staff board shows last week's numbers. The batch is not tied to the reporting schedule. Refresh the board when the report refreshes and keep the layout fixed between refreshes; a familiar layout with new numbers is what gets read.

What to send with a quote request

Once the cadence is set, the screen choice follows from it. Send this with a quote request:

• Screens and places. How many screens, which rooms or walls, portrait or landscape, and what they mount to. The places we build for each have their own section, from counters and menu boards to shop-floor stands.
• Cadence per screen. What changes weekly by hand and what changes daily or faster, so the quote carries the right update path for each screen.
• Owner. Who runs the morning check and the weekly batch, and from which computer.
• Network. Whether the screen site has a LAN drop or a web server the player can pull a playlist from on a timer.

For a menu screen, the guide to choosing the screen around the menu settles size and mounting before the content plan lands on it. Our current range of wall, counter, table, floor, stretched-bar and hanging displays is quoted per project, and the list above is what turns that quote around quickly.

Questions