Organization Overview
Use the organization overview as the main readiness dashboard for one workspace. It should answer three questions quickly: what is ready, what is missing, and where should you go next.
Use this guide when you need to
- See whether shifts, groups, roles, members, and requirements are ready for weekly scheduling.
- Open the exact page that is blocking planning instead of hunting through the app.
- Share public links and use exports when leaders need visibility without editing access.
Jump to section
Purpose
What the overview should tell you in under a minute
- Give a scheduler a single page that reflects the current health of the organization.
- Surface the next logical step when something is incomplete, such as members not assigned to groups.
- Keep frequently used organization actions close to the top of the workflow.
Workflow
Use readiness as a preflight, not a scorecard
- Start on Overview before building a new week or troubleshooting a broken one.
- Read the readiness section from top to bottom and resolve blocking items first.
- Use the management links to move directly into Members, Groups, Roles, Shifts, Requirements, or Schedules.
- Return to Overview after major changes to confirm the organization is in a stable planning state.
Readiness triage
Separate structural problems from weekly scheduling problems
A missing member group, inactive shift, or incomplete requirement is a setup problem. An uncovered Tuesday assignment is a weekly planning problem. Treating those as the same thing creates unnecessary schedule edits and makes Auto-fill look less reliable than it is.
Use the overview to resolve structure first. Once the organization is healthy, move into the week and solve the exceptions that are truly specific to that schedule.
- Structure first: groups, shifts, roles, members.
- Coverage second: requirements and absences.
- Week last: assignments, overrides, and publishing.
Guidance
Read the workspace before you edit the week
The overview is most useful when it helps a scheduler decide what deserves attention before the schedule grid opens.
What the readiness signals actually mean
Readiness is not just cosmetic. It should reflect the core dependencies required for the schedule engine and weekly editing screens to make sense. If members exist but are not assigned into groups, the overview should treat that as incomplete because the group schedule pages depend on that ownership layer.
A healthy workspace usually means active shifts are present, groups exist, members belong to those groups, roles are defined with sensible active days, and requirements exist for the relevant shifts. When one of those pieces is missing, the overview should guide you toward that specific page instead of showing a vague generic message.
How to use Overview during real weekly planning
Use Overview as your pre-flight check before opening the week you need to edit. This is especially helpful when several people administer the same organization and changes may have happened in members, absences, roles, or requirements since you last planned a week.
If the overview looks healthy but the week still feels thin, your next stop is usually Absences or Edit Requirements. If the overview looks incomplete, fix the data structure first before trying to force assignments into the schedule grid.
What belongs here and what does not
Overview should feel like a planning dashboard, not a second version of every other page. Keep it focused on readiness, quick actions, recent context, exports, and high-value summary cards. Detailed editing belongs in the workspace sections themselves.
Practical notes
Signals worth checking before weekly planning
- If public links are shared often, keep exports easy to reach from the organization dashboard.
- If readiness says members are not assigned to groups, fix that before editing requirements or weekly schedules.
- If leaders only need to view schedules, use public links rather than dashboard access.
Questions
Questions teams ask before they trust the weekly plan
Straight answers about setup order, scale, Auto-fill inputs, and what a new workspace actually needs before scheduling starts.
What should I set up first in RoleSchedule?
Start with the operating structure the schedule depends on: shifts, groups, roles, members, and coverage requirements. Once those are in place, add absences and build the first real week. The Overview page is designed to show which of those pieces is still missing.
Is RoleSchedule a good fit for larger teams?
Yes. RoleSchedule is designed around organizations, multiple groups, shared roles, coverage requirements, and larger rosters rather than a single personal calendar. Exact user, group, and roster limits depend on the plan configured in the live Plan Catalog, so the Pricing page is the best place to check current capacity.
What should I check if Auto-fill is not producing the schedule I expect?
Check structure before editing the week manually: confirm members are in the correct groups, roles are active on the expected days, requirements reflect the coverage you actually need, eligibility is correct, and approved absences are current. Auto-fill can only make a strong first draft from accurate inputs.
Do I have to finish every setting before I build a schedule?
No. Build enough structure to schedule one real group and one real week, then refine the model as you use it. RoleSchedule works best when configuration follows real operating needs instead of trying to perfect every option before the first schedule exists.