Shiftly
Reserve early access

Help · Shiftly

Everything on one page, in depth.

Getting started, how matching actually works, what the credential-gate does and does not mean, the K-12 sub-coverage skin, white-label and custom domain, troubleshooting, and the data and privacy posture — one page, so nothing here goes stale as a stub route no one maintains.

On this page

Getting started

There is no self-serve sign-up today. Reaching out starts a conversation: tell us the shape of the problem at [email protected], get a straight walkthrough of what is reused-and-shipped versus early access, pilot on one building or one shift type, and widen only once the first pilot is boring. Full detail: Getting started.

How matching works

The same five-step mechanism covers a routine open shift and a K-12 substitute callout — only the credential requirement on the shift changes.

  1. Post the open shift — A manager posts a shift: the role, the time window, and which credential it requires (a certification date, a district, a building). Nothing is assigned yet -- the shift is just described.
  2. Match against availability, eligibility, and credential — The same constraint gate that already runs credential-gated assignments elsewhere in the fleet checks every staff member's own availability window, role eligibility, and credential expiry against the shift, and proposes who can actually take it.
  3. A person accepts — The matched staff member accepts (or the manager assigns directly). The board shows the shift as covered, not assumed covered -- an accepted shift and a proposed one are never shown the same way.
  4. A callout triggers self-heal — If a covered shift falls through, the same self-healing reassignment logic that already proposes minimal-cascade reschedules elsewhere in the fleet proposes a ranked list of eligible replacements for that one shift -- not a rebuild of the whole week's roster.
  5. K-12 sub-coverage rides the same shift — A teacher absence is modeled as the same shift object with a school-specific credential requirement (a substitute-teaching credential, a building assignment). Coverage is matched from a pool of eligible substitutes the same way any other open shift is matched -- no separate sub-coverage engine to keep in sync.

The credential-gate

A shift that requires a credential checks the assignee’s credential expiry and scope against the shift’s requirement before the assignment is offered — the same hard-constraint gate reused from shipped work elsewhere in this fleet.

What it does not do: it does not certify, license, issue, or verify the authenticity of a credential. It checks an expiry date and a scope against a record the school or business already supplies. That determination stays with whatever authority issued the credential in the first place.

K-12 sub-coverage

A teacher absence is modeled as the same shift object with a school-specific credential requirement: a substitute-teaching credential, a building assignment. Coverage is matched from a pool of eligible substitutes the same way any other open shift is matched — no separate sub-coverage engine to keep in sync.

This flow — the building-assignment field, the substitute-credential requirement, the district-wide pool — is early access. It is not live today.

White-label & custom domain

Claim a hostname, verify it with the DNS-TXT record we hand you, and once it verifies the shift board serves from your own domain — included on every paid plan, not paywalled to a top tier. Full white-label branding (logo, colors, the badge gone) is the reseller tier. See Your brand, your domain on the home page for the full mechanism.

Two floors that never move, at any tier: the notification-email sending domain stays the platform’s (you set the display name and reply-to, not the From-address), and the consent/legal footer stays the platform’s.

Troubleshooting

A callout has no eligible replacement. The board shows the shift as uncovered, not silently reassigned to someone who does not clear the eligibility or credential check. Nothing is auto-assigned to an ineligible person — a manager assigns directly if the ranked list comes back empty.

A credential expires mid-cycle. The gate re-checks at assignment time, not once at hire — a staff member whose credential has lapsed stops being proposed for a shift that requires it until the record is current again.

A shift’s building assignment does not match any pool member. The sub-pool match is scoped to the building on the shift; a wider building-agnostic pool is not offered automatically — that stays a manager decision, not a silent widening of the eligible set.

Data & privacy

A shift record holds the role, the time window, the credential requirement, and who is assigned or proposed — employment facts about working adults, not student data. The K-12 sub-coverage skin adds a building assignment and a substitute-credential requirement, still employment facts, not a student roster.

No facial recognition runs anywhere on this product — there is nothing here to match a face to. No automated decision is made about a child: a substitute match is a credential-and-availability check on an adult, never a determination about a student. No AI or machine-learning claim is made anywhere on this page or the rest of the site — matching and self-heal are constraint-based rules, described as exactly that.

Questions

What is shiftly.software, exactly?

Staff shift-roster scheduling: posting open shifts, matching them to eligible and credentialed staff inside their own availability windows, and proposing a replacement the moment a covered shift falls through. K-12 substitute coverage is the sharpest edge of the same mechanism -- a teacher absence is a shift that needs an eligible, credentialed substitute matched fast.

Is this a new scheduling engine?

No. The matching primitives -- time-window availability, the credential-gate, eligibility rules, and self-healing reassignment on a callout -- are the same shipped, production primitives schedule.software already describes running for crew dispatch, re-skinned for a staff shift instead of a crew job. The shift-roster board and the K-12 sub-coverage skin are the new surface, and this page marks both as early access rather than claiming they are live.

What does shiftly.software track, hour by hour?

Nothing. Shiftly posts shifts, matches eligible people to them, and covers the ones that fall through. It has no concept of when a shift actually started, when it actually ended, or how long someone actually worked -- that record-keeping is a different product's job entirely, described in the next section.

How is shiftly.software different from its scheduling+hours sibling?

They split on purpose. Shiftly is the roster: who is scheduled for which shift, and who covers it if it falls through. The sibling product is the hours record: capturing when a shift actually started and ended and reconciling that against the schedule for payroll. One schedules; the other records what actually happened. They are built, marketed, and sold as separate products, and this page never describes the hours-record job as something shiftly does.

Is the K-12 substitute-coverage flow live?

Not yet. It is early access -- the same shift/eligibility/credential mechanism, specialized with a substitute-credential requirement and a building assignment, and matched against a pool of eligible substitutes. The page names it plainly as being built rather than showing invented coverage activity.

Does shiftly.software use AI to build the roster?

No AI claim is made anywhere on this page. Matching and self-heal are described as what they are -- constraint-based rules over availability, eligibility, and credential expiry, not a machine-learning or AI-assist feature.

Does a credential check on shiftly.software certify anyone?

No. The credential-gate checks an expiry date and a scope against a record the school or business already supplies -- it does not certify, license, issue, or verify the authenticity of a credential. That determination stays with whatever authority issued the credential in the first place.

What does shiftly.software cost?

Pricing on this page is DISPLAY-ONLY -- a plan, not a live checkout. No card is charged anywhere on this page or behind any of its buttons. The next step is a conversation, not a signup form.

Is the pricing on this page live?

No. Every figure is the planned launch tier, not a live checkout. No card is charged anywhere on this page or behind any of its buttons. Reserving early access starts a conversation about what access looks like for your operation; it does not create a payment.

Do I need to pay extra to use my own domain and remove Shiftly's branding?

No, not for the domain. A custom domain is on every paid plan — most shift-scheduling tools charge for that and reserve full white-label for an enterprise contract. Removing our branding and applying your own logo and colors is the reseller tier, not a sales-only conversation. The engine that verifies a domain and binds a brand to an account runs in production elsewhere in this fleet; the self-serve setup screen for shiftly itself is in development. Notification emails carry your display name and reply-to; the legal and consent footer stays ours by design. Pricing is the plan; there is no live checkout here.

Is shiftly.software part of a bigger platform, or is it standalone?

Shiftly is its own product and its own brand. It shares a scheduling engine with nine other brands in the same family (appointment links, room booking, class scheduling, field dispatch, and more) — naming them is not a claim that any is live in production; each is its own brand with its own status stated on its own page. homeroom.software is an optional integration for schools running both, never a requirement to use shiftly on its own.