About · Shiftly
A roster should tell people what still needs a decision.
A covered-looking cell can conceal several unfinished jobs: the person may only have been suggested, the window may not fit, or the credential record may not cover the date. Shiftly is organized around making those distinctions useful to the manager who has to act. The roster board remains early access.
What it is
What shiftly.software is
Shiftly is staff-shift-roster scheduling for hourly workforces: a manager posts an open shift, the shift is matched to a staff member whose own availability window, role eligibility, and (where required) credential all clear, and that person accepts or is assigned. If a covered shift falls through, a ranked replacement is proposed automatically instead of the manager starting from a blank board.
K-12 substitute coverage is not a separate product bolted on -- it is the same shift object with a school-specific credential requirement (a substitute-teaching credential, a building assignment) matched against a pool of eligible substitutes the same way any other open shift is matched. One mechanism, two skins.
It is deliberately narrow. Shiftly schedules shifts and covers the ones that fall through; it does not track when a shift actually started or ended, and it makes no claim about hours worked. That boundary is drawn on purpose and held throughout this page.
Start with the gap, then explain the proposed person
The product starts with an open shift because that is the management problem. A name comes later, after a review of availability, role and any required credential record. This order keeps the question grounded: what work needs coverage, and what makes a person suitable for it? It also gives a team a better way to explain a refusal. A person can be valued by the organization and still not fit this particular requirement.
The same principle applies after a callout. The affected shift becomes the starting point for reviewing replacements. The goal is a limited, understandable change rather than a grand claim that the whole week has been optimized. A proposal helps only when the person responsible for the shift can explain what it changes, what remains unchanged and which decision they still need to make. No case study or adoption number is needed to state that design preference.
A reused rule and a usable board are different milestones
The current site distinguishes matching primitives described elsewhere in the scheduling family from Shiftly's own surface. That distinction stays visible here. A rule for comparing dates does not itself give a manager a finished workflow for reviewing a staff response. A replacement proposer does not itself deliver a complete callout experience. The board and substitute-coverage skin are early access; we do not convert engine reuse into a claim that those screens are live.
That means a useful conversation can end with a gap. If you need a particular staff interaction, deployment condition or connection before you can pilot, name it and ask to see its current state. A roadmap direction is not a delivery date. Planned pricing is not a purchase offer through this website. The honest next step may be to review a bounded scenario now and return when the missing surface can be demonstrated.
Scheduling, not the sibling that records hours
Shiftly answers one question: who is scheduled for a shift, and who covers it if that falls through. It has no feature anywhere in this product for capturing the moment a shift actually begins or ends, and it keeps no record of hours actually worked. That is a deliberate, load-bearing boundary, not an oversight -- a roster and an hours record are two different jobs, and mixing them into one product is exactly what this page refuses to do.
The hours-record job -- capturing real start and end moments for a shift and reconciling that record against payroll -- belongs to a sibling product on its own domain, built and sold separately. Shiftly links to nothing in that sibling's job here, names no feature of it, and describes none of its mechanics. If a team needs both a roster and an hours record, that is two products working from the same shift data, not one product doing both jobs.
To be plain about what this means in practice: nothing on this page describes a start-of-shift capture, an end-of-shift capture, a break deduction, a per-minute log, or any reconciliation of scheduled time against actual time. Shiftly’s board shows a shift as posted, matched, accepted, or covered by a replacement -- states about the schedule, never states about a clock.
Keep operational authority with the people who hold it
A credential check compares a supplied record with a shift requirement. It does not acquire the authority of the organization that issued the credential. A ranked candidate list suggests an option; it does not speak for the person whose agreement is needed. These are practical boundaries, not decorative disclaimers. They help a team decide which part of a coverage decision belongs in the system and which part still needs a manager or an issuing authority.
For schools considering the substitute-coverage skin, the subject is adult work coverage: a building requirement, a shift window and a qualified substitute pool. This page introduces no student placement decision or child-facing workflow. Keep that scope in the first discussion. The contact page explains how to bring a useful anonymous example, while getting started describes the questions to settle before treating an evaluation as an operational rollout.