BrightBridge Manual

New operator modeWork down this page in order.

Read the topic first, then follow its numbered steps. Nothing changes in BrightBridge until a step explicitly tells you to select, save, start, deploy or restore.

01Start of shift 02Routine fleet health check 03Planned content change 04End of shift 05A useful handover note

Topic 1 of 5

#Start of shift

Dashboard loads without a blocking message.Offline and overdue counts are compared with the expected operating schedule.Recent failed or partial jobs have an owner.Available storage is not showing a warning.Urgent handover notes have been reviewed.

Topic 2 of 5

#Routine fleet health check

1
Open Players and filter to offline or overdue states.
2
Exclude players that are intentionally powered down or outside operating hours.
3
Open each unexpected result and compare its recent activity timestamps.
4
Use a lightweight remote check before disruptive actions.
5
Record the outcome or escalate with the player name and observed times.

Topic 3 of 5

#Planned content change

1
Confirm the approved presentation and target group.
2
Review player filters, tags and the selected count.
3
Run a fresh dry run and read every target warning.
4
Apply the release once.
5
Wait for player activity and visually verify representative screens.
6
Record exceptions rather than repeating the entire release.

Topic 4 of 5

#End of shift

No important action is still running without an owner.Unexpected offline players are documented.Content releases include their result and verification state.Temporary Liveview sessions are closed.The next operator has a concise handover.

Topic 5 of 5

#A useful handover note

Include	Example of useful context
Scope	Player label, group or affected count
Time	When the issue or action was observed
Action	What was attempted once
Result	Success, warning, partial result or failure
Verification	Activity changed, snapshot checked or physical screen confirmed
Next step	Monitor, retry one target or escalate