1. Type
Pick the change type that fits the work: computer monitors, 1×3 video walls, Spotlight screens, or Other changes when nothing predefined fits.
How it works
One request from first detail to Deployed
Docket gives a screen change one path: describe it, submit it for review, deploy it in MagicINFO, and keep the record. Nothing reaches a screen without a person doing it — and nothing is done without a record here.
Start with a Draft
A Standard user or Admin starts a new request. It stays Draft while the requester works through five steps.
2. Which screens
Choose a predefined group, such as all French stores, or select individual screens. Docket shows a live count of exactly how many screens the choice reaches. Expand the count to see the exact list before you commit.
3. Images
For new content, upload artwork and set the order and duration. For a replacement, pair each upload with the current image it replaces. For a removal, upload nothing: select the images to take down from what is playing today.
4. Timing
Set the go-up date and, if needed, the come-down date. These are the dates when the team does the deployment work, during business hours on weekdays.
5. Review and submit
See the screens, images, and dates together before submitting. Validation shows every problem at once, so the request can be fixed in one pass.
All stores — EN
All stores — FR
Pick screens…
Reaches 214 screens
Follow the request lifecycle
Draft
The request is being prepared. Screens, images, and dates can be edited.
Awaiting approval
The request has been submitted for review. It is sealed: screens and images cannot be changed because that is what the reviewer is approving.
In progress
The request is approved and the signage team is carrying out the work in MagicINFO.
Deployed
The human operator has made the change in MagicINFO and recorded the deployment in Docket. The request is finished and never edited or reopened.
Rejected
The reviewer has rejected the request, with a reason. It is finished and never edited or reopened. Clone it into a fresh Draft to make the changes and submit again.
Cancelled
Before review starts, a requester can Cancel their own request. It remains on the paper trail.
Draft→Awaiting approval→In progress→Deployed
RejectedCancelled
The right role for each person
Admin
Admins manage the tenant, review requests, and work with the permission matrix.
Standard
Standard users can create, submit, track, cancel their own request before review starts, and clone a request.
Viewer
Viewers can see everything in their tenant, but they have no New Request button and cannot make changes.
Keep the work moving
Email notifications use per-tenant routing rules to keep people informed. The calendar shows when campaigns go up and come down, so the team can see upcoming work in one place.
Run a campaign again without rebuilding it
Finished requests are not edited or reopened. Clone copies the type, screens, and images into a fresh Draft. Set the new dates, check the details, and submit the new request.
See the MagicINFO integrationSee retail campaign scoping
Read about the read-only design