Content maintenance · Team approval

Prepare, review and approve changes to screen content

This guide describes a simple workflow for a small team. It separates organisational responsibility from technical permissions and does not assume a software approval feature.

SUISSE-VIDEO · 6 October 2026 · 4-minute read

1. Assign specific responsibilities

Decide who supplies the facts, approves them and publishes the result. In a small team, one person may handle several tasks; prices and dates still need deliberate confirmation. Agree a deputy and a contact for urgent corrections.

2. Use an identifiable working version

Label drafts with a title and editing date. Collect requested changes in one agreed place rather than using conflicting messages. Record which version is to be reviewed. A copy is helpful only if the draft and valid card can be distinguished clearly.

3. Review facts and the preview together

The person responsible for the information confirms prices, times and content. Then check the card preview, including long text and language versions. Also check the target project and calendar entry. The example table shows who might confirm each step.

Example: a new menu card at Pizzeria Oliva

Step	Responsibility	Record
Draft	Kitchen supplies dish and description	Card title and editing date
Approval	Manager confirms price and validity	Confirmation of the reviewed version
Playback	Person responsible checks project and device	Brief check after the change

Fictional team workflow, not a customer case study or a description of technical user roles in SUISSE-VIDEO.

4. Separate approval from publication

Record agreement to the reviewed version, using the card title and date. Publish or schedule that exact version. If its price or date changes afterwards, review it again. Check available account permissions separately; this workflow does not assume built-in roles or a two-person approval system.

5. Practise corrections and handover

Check actual playback after the change. If an error appears, correct the affected card or assignment and check again. The deputy needs to know where the valid version and responsibilities are recorded. Do not simply share a common password; agree suitable access and handover with the person responsible for the account.

Pre-publication checklist

Editing, factual review and publication are assigned.
A deputy and an error contact are named.
The reviewed version is clearly identifiable.
Prices, dates, languages and preview are checked.
Target project and calendar entry match the approval.
Actual playback was checked after the change.

Use these checkboxes as a checklist. Your selections are not saved.

All blog posts

Set up a content maintenance plan · Keep menu boards up to date