← Back to the overview article
Adapt a project template before using it at a new location
A proven programme can provide a starting point for another location. Copied cards and schedules still need their own review. The guide adds documented controls and checks on site to the example.
1. Separate template and destination
Identify the source project, new location and required differences. Devices with the same project URL receive the shared programme; different content needs suitable project assignment. Check available project capacity before expanding.
2. Confirm the transfer method
The help mentions exporting a project to another customer and says text cards and schedules are copied. That section does not describe every export dialog. Confirm the method available in your account with the responsible person. Do not confuse project export with CSV export of individual clips.
3. Inventory copied details
Check clips, playlists, text cards, calendar settings and visible location details. The table covers contacts, room names and daily times. A copied schedule is a setting to review, not proof that it fits the new location.
Example workflow
| Step | Content or procedure | Check |
|---|---|---|
| Contact | Replace previous details with the confirmed location contact. | Check phone and responsible person |
| Schedule | Compare copied card times with new operating hours. | Check calendar preview |
| Content | Check clips and cards for location relevance. | Clarify independent variants and assignment |
4. Create independent variants deliberately
For independently edited lists, use the save-as-new-playlist option described in the help and check assignment. Review copied cards before editing and establish whether content is shared. This guide does not promise automatic independence of every exported component.
5. Test the new location before use
Check preview, device URL and actual playback at the new location. Have the responsible person confirm contacts, prices, rooms and dates. Also review the source project when changes might affect shared content. Record the template, destination and maintenance responsibility.
Checklist
What should each screen show? · Who can change screen content? Organise team approval