This guide explains satellite clinic schedule import for branch administrators coordinating shared clinic support teams. Start by preparing clean scheduling data and checking a small sample. Then use the example and checks below to agree a practical next step with the people who run the schedule.
Satellite clinic operations depend on people and equipment that may serve several small premises. An administrator who opens one branch cannot also welcome a delivery at another. A laptop allocated to a staff demonstration needs time to reach its next location. Build a plan with explicit branch identifiers, dated support sessions and locally agreed travel windows. The responsible clinic team defines service arrangements separately. A useful operational timetable makes each shared commitment visible and gives branch coordinators a common view of the practical dependencies they must resolve together.
Satellite Clinic Schedule Import: worked example
Illustrative planning example. The numbers and timings below explain a possible situation; they are not customer results or required staffing standards.
An illustrative branch spreadsheet uses B1 for both a building and a room, and omits the location on repeated rows. A source review is needed because identical room names at different branches represent separate physical resources with separate access conditions.
Create stable branch-qualified room identifiers and fill every activity's location field. Import a small cross-branch sample, then compare its staff movements and room allocations with the source plan.
Check the result: The sample keeps repeated room names separate by branch, and every imported activity has the intended location without creating a duplicate identity for the shared support officer.
Satellite Clinic Schedule Import: setup checklist
| Planning input | What to confirm |
|---|---|
| Branch code | Use a distinct identifier even when room names repeat. |
| Shared support role | Record which person opens, supervises or prepares each session. |
| Transfer interval | Use the team's agreed travel and equipment movement allowance. |
| Branch access window | Distinguish building access from the scheduled support session. |
Build a clean operational source table
Prepare one row for each dated activity, with explicit people, resource identifiers, locations, start times and finish times as required by the current import workflow. Remove spreadsheet presentation features that obscure the data, such as merged headings or summary rows mixed with activities. Standardise identifiers before importing so one person or asset does not appear under several names. Keep only fields needed for the operational timetable, and exclude personal visit details or records managed elsewhere. Work on a copy of the source.
This allows the coordinator to correct mappings and compare results without losing the original planning reference used for reconciliation.
Reconcile a small sample before expanding
Choose a sample that includes a shared person, a room or asset reservation and at least one dated exception. Inspect the current import template and supported fields rather than assuming every spreadsheet layout will map directly. After import, compare activity counts, dates, durations and identities with the cleaned source. Review the resulting staff and resource views for duplicate rows or shortened reservations. Export the sample if useful for a second reader's check.
Correct the source or mapping before loading a larger period, and retain a brief reconciliation note showing what was checked and which operational owner accepted the sample's intended meaning.
Questions to ask before choosing software
Compare location handling before comparing the number of attractive timetable views. Ask whether a single staff member's branch assignments can be reviewed across the whole week. Demonstrate an equipment transfer as well as a staff visit. The buyer needs to see how a late finish at one site affects the next operational commitment.
Bring a representative example to your evaluation. Review the current VeloRoster plan and its limits and Try interactive demo → that reflects your team’s people, spaces and timing needs.
Frequently asked questions
What should we avoid when planning satellite clinics?
- Treating two rooms named Office One as the same physical location.
- Allocating travel after an activity has already started at the next branch.
- Copying one branch's closure dates into every branch calendar.
Review these points with the activity owner before you approve the plan.
Should an existing clinic workbook be imported unchanged?
Review it first. A workbook may mix timetable rows with notes, totals or records intended for other systems. Create a clean operational copy with stable identifiers and explicit dates, then compare a small imported sample against the approved source before expanding the planning period.
How can duplicate people or rooms be prevented?
Agree a consistent identifier for each real person and physical resource before import. Resolve initials, nicknames and repeated room names in the source table. A sample review should confirm that shared assignments connect to the same identity and separate branches remain correctly distinguished.
What should be checked after importing a sample?
Reconcile the number of activities, dates, start and finish times, people, locations and resource reservations. Include preparation and handover blocks in the check. Inspect labels and an output for unwanted personal fields, then ask the operational owner to confirm that the sample represents the intended plan.
Take the next step. Explore the VeloRoster interactive demo with sample data, then check your requirements against the current access and pricing details. Keep the operational decisions in this guide with the people responsible for your organisation’s schedule.