ClocklyBook a conversation

Help · Clockly

Everything a Clockly admin needs, on one page.

Nine anchored sections instead of nine thin routes -- jump to the one you need.

Getting started

The checklist for a first building or crew.

Admin & SSO setup

Clever/ClassLink rostering, module toggles, scope by building.

Credential gating

How a shift confirms the covering staff member is actually eligible.

White-label & custom domain

Base-tier domain, mid-tier branding, the two floors that never move.

Per-role how-to

Custodial, transportation, food service, security, front office, general SMB.

Troubleshooting

The honest reconciliation states and what each one means.

FAQ

The common questions, answered plainly.

Data & privacy

What is access-controlled, what is never claimed.

Getting started

  1. Book a conversation -- [email protected].
  2. Pick the one building or crew that hurts today.
  3. Connect SSO / rostering (Clever or ClassLink) -- roster import always routes through the consent chokepoint, never a raw name paste.
  4. Confirm which roles need credential gating (transportation, food service).
  5. Publish the shift board for that crew.
  6. Test a clock-in and clock-out.
  7. Review a reconciliation pass -- on time, late, left early, no-show.
  8. Add a custom domain (planned, Crew tier and up).
  9. Add white-label branding (planned, District tier and up).
  10. Reserve early access for the pieces still in development.

Admin & SSO setup

District single sign-on and SCIM-provisioned staff accounts, with Clever and ClassLink roster sync, are in development. Once connected, a FERPA-aware scope cascade means a building-level supervisor sees only staff in their own building -- never the whole district roster.

Kiosk & mobile clock-in

A shared kiosk view and a mobile clock-in/out surface for classified staff are in development, on the same clock-in/out capture core described on the front page. Neither is embeddable or live today.

White-label & custom domain

In the planned tiers, a custom domain sits on the base Crew tier -- not held back for the top tier -- and full white-label branding (logo, colors, the badge gone, branded emails) lands at the District classified-staff edition. Two floors never move at any tier: the sending domain and the consent and legal footer on any staff notice stay with the platform. All of this is in development; nothing here is live billing today.

Per-role how-to

Custodial

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.

Transportation

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.

Food service

Kitchen and serving-line shifts, credential-gated on current food-handler certification, with attendance reconciled against the meal-service window the shift actually covers.

Security

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 office

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.

General SMB shift work

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.

Troubleshooting -- the honest reconciliation states

A clock punch reconciles against its scheduled shift into one of four states: on time, late, left early, or a no-show. There is no fifth silent state -- an unmatched punch surfaces as a gap to review, never a swallowed error. All of this is in development; none of it is live on this front door today.

FAQ

Is any of this live today?

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.

Does Clockly do shift scheduling?

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.

Does Clockly calculate pay or run payroll?

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.

Why publish tiers instead of a quote-only price?

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.

Is a card charged today?

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.

What happens to classified-staff attendance data?

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.

Is Clockly a separate company from shiftly.software?

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.

Do I need to pay extra to use my own domain and remove your branding?

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.

Is Clockly part of a bigger family of products?

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.

Where can I read more than the front page covers?

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.

Data & privacy

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.