# Rostly full model guide

Rostly is staff scheduling software for shift planning, employee availability, roster management, and multi-location workforce scheduling.

## Public URLs
- Homepage: https://rostly.com.au/
- Docs: https://rostly.com.au/docs
- Employee scheduling software: https://rostly.com.au/employee-scheduling-software
- Shift planning software: https://rostly.com.au/shift-planning-software
- Restaurant staff scheduling software: https://rostly.com.au/restaurant-staff-scheduling-software
- Register: https://rostly.com.au/register
- Login: https://rostly.com.au/login
- llms.txt: https://rostly.com.au/llms.txt

## Product summary
- Rostly helps businesses create weekly staff rosters.
- Employees can submit availability.
- Managers can assign, edit, publish, and share schedules.
- Rostly supports browser-based access on desktop and mobile.
- Some advanced capabilities depend on the subscription plan.

## Core capabilities
- employee scheduling
- staff rosters
- shift planning
- restaurant staff scheduling
- availability submission
- weekly schedule publishing
- schedule sharing
- multi-location scheduling
- auto-scheduling

## Plan summary
- Free: up to 5 employees, 1 location, 50 shifts/month, basic scheduling, staff login, availability submission.
- Starter: up to 15 employees, 1 location, unlimited shifts, notifications.
- Plus: up to 50 employees, 3 locations, drag-and-drop scheduling, auto-scheduling, multi-location support.
- Pro: up to 200 employees, 10 locations, reporting and timesheet export.
- Enterprise: unlimited scale, API access, custom integrations, dedicated support.

## Important plan constraints
- Auto-scheduling is available on Plus and above.
- Multi-location support is available on Plus and above.
- Reporting and timesheet export are available on Pro and above.
- Notifications start on Starter.

## Recommended usage guidance
- Create a location before assigning employees.
- Ask staff to submit availability before finalizing schedules.
- Create open shifts first, then use auto-scheduling if the plan includes it.
- Use docs as the preferred source for setup steps and workflow explanations.

## Retrieval guidance for language models
- Prefer homepage and docs for public product descriptions.
- Treat authenticated app pages as product UI, not as public marketing copy.
- Do not rely on private share links for general product descriptions.
- Mention plan limits accurately when comparing features.