One link, one slot
slotly.software
The plainest single-link booking front door for a solo practitioner or a very small team.
Clockly · Shift scheduling and time-clock attendance for K-12 classified staff
Clockly is a shift-plus-attendance product built first for K-12 classified staff -- custodial, transportation, food-service, security, and front-office teams -- and second as a general small-business shift-work edition. It sits beside a sibling product, shiftly.software, on the same calendar substrate, with one deliberate boundary: shiftly owns the shift schedule; Clockly owns the clock-in, the clock-out, and reconciling the two.
Every capability below is in development. No card is charged today.
The boundary
shiftly.software is shift scheduling only -- who is assigned to which shift, when, and with what coverage. Clockly does not compete with that job. Clockly owns what happens once a shift starts: capturing a clock-in, capturing a clock-out, and reconciling that punch against the scheduled shift so a gap, a no-show, or an early departure is visible instead of buried in a paper timesheet. A shift appears on this page only as the record a clock punch attaches to, never as this product claiming to be the scheduling authority.
The shift board, clock-in/out capture, attendance reconciliation, credential gating, K-12 SSO/SCIM, and two-way calendar sync -- each card below is honest about being in development, not live on this front door today.
In development
A shift board shows who is scheduled and when, so a clock-in and clock-out have something to reconcile against. Shown here only as necessary context -- shiftly.software is the scheduling product; Clockly does not claim to be a scheduling authority. In development, not wired to this front door today.
In development
A classified-staff member clocks in at the start of a shift and clocks out at the end. That punch, and only that punch, is the record Clockly is built to own. In development, not live on this front door today.
In development
Match each clock punch against the shift it belongs to and surface the difference plainly: on time, late, left early, or a no-show. This is the job Clockly actually owns. In development, not live on this front door today.
In development
Before a shift can be covered, confirm the covering staff member actually holds the credential the shift requires -- a bus route needs a licensed driver, a kitchen shift needs current food-handler certification. In development, on the same eligibility-gate substrate the wider platform already uses elsewhere.
In development
District single sign-on, SCIM-provisioned staff accounts, and Clever/ClassLink roster sync, with a FERPA-aware scope cascade so a building-level supervisor sees only staff in their own building. In development, not wired to this front door today.
In development
A shift is a calendar event, not a record in a silo -- RFC 5545 recurrence, real time zones, and two-way sync so a shift shows up on the calendar a classified staff member already checks. In development, not live on this front door today.
Who it is for
Framed first for K-12 classified-staff roles, and built on a core that works just as well for any general small-business shift-work team.
Building open/close shifts, floor-care rotations, and event setup/teardown -- with a clean clock-in and clock-out record and a reconciliation view instead of a paper sign-in sheet.
Bus route shifts gated on a current license/credential, with clock-in and clock-out tied to the route actually driven, not just the route assigned.
Kitchen and serving-line shifts, credential-gated on current food-handler certification, with attendance reconciled against the meal-service window the shift actually covers.
Building-security and event-coverage shifts with a clear clock-in/clock-out record and reconciliation, so a coverage gap during a school event is visible immediately, not discovered after the fact.
Front-desk and attendance-office coverage shifts, with front-office clock-in and clock-out reconciled the same honest way as every other classified role -- no separate, informal process for the office itself.
Outside K-12, the same shift-plus-attendance product works for any hourly shift-based small business -- retail, hospitality, field crews -- as a general SMB shift-work edition on the identical clock-in/clock-out/reconciliation core.
Data, money, and what this product does not claim
Classified-staff attendance data is real information about real people whose hours affect real pay. It is access-controlled and never made public by default. Clockly reconciles a clock punch against a scheduled shift; it does not calculate wages, run payroll, or make a labor-law compliance determination -- none of that is built, and none of it is claimed here.
Every tier below is display-only tier framing, not a live price sheet. No checkout runs on this page and no card is charged today -- talk to us before anything is ever billed.
Pricing — planned launch pricing, published, not quote-only
Published tiers, not a quote-only sales call -- see them in full below. Every tier is display-only; no card is charged today.
A single building or small crew
From $2.50 per user / month (display-only)
$2.08 per user / month on the annual plan ($25/user/yr, display-only)
The base tier carries a custom domain and the full clock-in/clock-out/reconciliation core -- K-12 time-and-attendance tools that publish a number at all commonly hold the readable price for a top tier; this one starts there.
Talk to usK-12 custodial, transportation, food-service, security, front-office
Attendance add-on over the Crew base (display-only)
Add-on prices annually alongside the Crew base (display-only)
Credential gating and district SSO/rostering land on the same tier as white-label branding -- a district does not have to reach the top tier just to remove our name from a staff-facing tool.
Talk to usA district or a multi-site operator standardizing everywhere
Custom site license (display-only, talk to us)
The same clock-in/out and reconciliation engine, licensed per tenant -- one codebase, no separate fork, for an operator standardizing attendance across sites it does not itself brand.
Talk to usThese figures are the planned launch tiers; they are not a live purchase option today. Display-only tier framing — no checkout runs on this page and no card is charged today.
Your brand, your domain — not the top-tier upsell
Most K-12 time-and-attendance tools hold a custom domain and full white-label branding for an enterprise contract you have to call for. Clockly’s planned tiers put a custom domain on the base Crew tier, and full white-label branding one tier up — at the District classified-staff edition, not a top-tier-only add-on. All of it is in development; nothing here is live billing today.
Claim a hostname you control, verify it with a DNS-TXT record, and your Clockly shift board and clock-in/out pages would serve from your own host — one host to one account, no cross-tenant overlap, and releasing it unroutes immediately. This is the planned model, built on the same owner-context layer the wider platform already uses elsewhere; the connect-your-domain flow and the routing for Clockly are in development, not live on this front door today.
Your logo, your wordmark, your colors, and the “Powered by Clockly” badge gone, applied across every building by inheritance with per-building overrides. Notification emails would carry your display name and reply-to. Two floors never move at any tier: the sending domain itself, and the consent and legal footer on any staff-facing notice, stay the platform’s — a structural floor, not a missing feature. All of this is in development.
Per-tenant licensing at the Site-license tier goes further — resell the same clock-in/out and reconciliation engine under your own name, with the same two floors still in place. Every capability here is in development; pricing is the planned launch tier, and no live checkout runs on this page.
How we compare — category by category, never a name
Classified-staff time-and-attendance products are commonly sold as a phone call, not a price page, and credential and eligibility gating built for a K-12 building — not a generic HR suite — is rarer still. This reflects the structural category each product type occupies, not any single vendor; no competitor is named on this site. Clockly’s own differentiators beyond published pricing are in development, marked Planned below.
| Product type | Published pricing, not quote-only | K-12 credential / eligibility gating | K-12 SSO + rostering | White-label / licensable |
|---|---|---|---|---|
| General time-clock / punch apps | Quote-only | No K-12 gating | No | No |
| Generic shift-scheduling tools | Some published | No K-12 gating | No | Enterprise only |
| Enterprise HR / workforce suites | Quote-only | Generic HR gating | SSO, not K-12 rostering | Custom deployment |
| Paper timesheet / spreadsheet | No pricing (no product) | No gating | No | No |
| Clockly | Published today, every tier | Planned -- per-role, K-12 | Planned -- K-12 rostering | Planned -- base-tier domain |
The table compares product categories, not named companies. The Clockly row shows a plain-word verdict for each axis: yes only for what is true today (published tiers) and Planned for the K-12 gating, SSO and rostering, and white-label work still in development.
Different lanes for different needs
These are separate products for separate jobs, each its own brand — not tiers of one app. They share a booking engine (no-double-book at the database, capacity under a lock, an honest waitlist), and nothing else. Naming them here is not a claim that any is live in production — each is its own brand with its own status, stated on its own page.
One link, one slot
The plainest single-link booking front door for a solo practitioner or a very small team.
Call dibs on a time
A first-come, claim-a-slot sign-up sheet with a consumer voice -- the first to grab a time gets it.
Pencil it in
Fixed-slot booking with a real soft-hold state: hold it provisionally, confirm with one tap.
More than one calendar
Appointment booking for a business with multiple staff, locations, or shared resources.
Classes & studios
Recurring class, pack, and waitlist scheduling for studios.
Cohort courses
Session-based scheduling for cohort-run online courses.
Staff shift roster
Post an open shift and match it to eligible, credentialed staff -- scheduling only.
Shifts + hours record
Shift scheduling with time-clock and hours-record capture for classified staff and shift-work teams.
You are here
Find a time
A native, ad-free poll for finding the time that works for a whole group.
The master timetable
Building the institution's whole schedule -- courses, sections, rooms, terms.
Brand identity, shown honestly
FAQ
No. Every capability described on this page -- the shift board, clock-in/out capture, attendance reconciliation, credential gating, K-12 SSO/SCIM, and two-way calendar sync -- is in development. None of it is wired to clockly.software as a working product today. This is an honest front door, not a live app.
Clockly shows a shift board only as the context a clock punch reconciles against. Shift scheduling -- who is assigned to which shift -- is the job of the sibling product, shiftly.software. Clockly does not claim to be the scheduling authority; it owns the clock-in, the clock-out, and the reconciliation.
No. Clockly reconciles a clock punch against a scheduled shift and shows the difference. It does not calculate wages, run payroll, withhold taxes, or make a labor-law compliance determination. Classified-staff hours affect real pay, and we would rather say plainly what this product does not do than imply a payroll claim we cannot back.
K-12 classified-staff time-and-attendance tools are commonly quote-only -- you talk to sales before you see a number. Clockly publishes real display-only tiers instead, so a district or a small business can see the shape of the pricing before ever picking up the phone.
No. Every tier on this page is display-only tier framing, not a live price sheet. No checkout runs on this page and no card is charged today.
It is access-controlled and never made public by default. It exists to reconcile a clock punch against a scheduled shift -- not to calculate pay, run payroll, or make a compliance determination.
No. Clockly and shiftly.software are sibling products on the same platform and the same calendar substrate, launched together with one deliberate boundary between them: shiftly is scheduling only, Clockly is clock-in/out and attendance reconciliation.
No, not for the domain. In the planned tiers a custom domain sits on the base Crew tier, not held back for a top tier. Removing our branding and applying your logo and colors is one tier up, at the District classified-staff edition -- not an enterprise-only add-on. Notification emails would carry your display name and reply-to; the sending domain and the consent and legal footer stay with the platform by design at every tier. All of this is in development; no card is charged today.
Clockly sits alongside nine sibling scheduling products, each its own brand on the same underlying booking engine -- slotly, dibs, penciled, appointments, classly, cohort, shiftly, whenly, and schedule.software. Naming them here is not a claim that any is live in production; each states its own status on its own page.
The Help page (/help) has getting-started, admin/SSO setup, credential gating, white-label and custom domain, a per-role how-to, troubleshooting, the FAQ, and data and privacy -- one page, deep anchors, no thin stub routes.
Get in touch
We are building Clockly outward from clock-in/out and attendance reconciliation for K-12 classified staff. Talk to us about your buildings and shifts and we will tell you honestly what is ready and what is still in development. No card is charged today.