Create a location from a supplied roster model when you need to reuse an agreed configuration.
A RosterLab model is a .json file containing an agreed roster setup. Your implementation contact can confirm which version to use and whether importing a new location is your next step. You do not need a model file for every new roster.
Use the desktop planning interface with access to create a location. Download the agreed file to a folder you can find again and keep it unchanged. This process creates a new location, rather than overwriting an existing one; employee spreadsheets, printed schedules and ordinary Excel exports cannot be used as model files.
Import the model
1. Open the location selector in the planning interface.
2. Select new location.
Screenshot of MyRoster page with the location selector menu open highlights steps 1 and 2 that open the menu and allow creation of a new location.
3. In Create New Location, choose Upload a roster model.
Screenshot of the Create New Location dialog with Upload a roster model highlighted for step 3 and Continue for step 4, before importing a file.
4. Select Continue to open the file picker.
5. Choose the JSON file supplied by RosterLab. Selecting the file starts the import; check the file before choosing it.
6. Wait for the new location to open, then check its name and configuration.
The new location's name is based on the filename without its extension. If that name is already used, a numbered suffix distinguishes the new location. Check that you are reviewing the imported location rather than an existing one with a similar name.
Review the imported model
Compare the employee records, shifts, skills, staffing requirements and rules with the setup you agreed with RosterLab. Check a few known employees and shift definitions, then review the planning requirements. A completed import does not establish that every input is ready for your first live roster.
Use the first-roster checklist to choose the intended period, build or generate the roster, review the result and publish only when it is ready.
If the model does not import
new location is unavailable: check that you are in the desktop planning view and have the required access. Ask your administrator or implementation contact to check rather than creating another account.
“Please upload a JSON file” appears: confirm you selected the supplied
.jsonfile. Do not rename a spreadsheet to make it look like JSON.“Could not upload file” appears: read the accompanying detail and ask RosterLab to check the file. Keep the original attachment for comparison.
You are unsure whether import completed: check the location list for the new name before repeating the action, to avoid creating an unintended extra location.