The questions behind every shift.

ClassShift is being built as a managed student-workforce model for employers with recurring hourly needs. The operating concept combines pattern-based matching, workforce coordination, visible work status and human exception handling.

No live DFW workforce operation is claimed on this pilot-stage website. ClassShift is preparing employer discovery and a bounded founding pilot. The product demo is illustrative and does not represent a current customer, worker, shift, payment or staffing guarantee.

The initial business-validation focus is Dallas–Fort Worth. Expansion should follow evidence from real employer demand, student supply and pilot operations rather than precede it.

The core hypothesis is that recurring work gives employers more continuity and gives students a more realistic school-compatible pattern than repeated isolated shifts. A real pilot still has to prove whether that creates measurable value.

Email currently supports launch-stage questions and pilot discovery. A production workforce privacy, consent and data-handling flow must be reviewed before live worker onboarding relies on it.

A strong discovery case has a DFW operating location, a defined role, headcount, recurring cadence, shift windows, an onsite owner, a current staffing pain and a decision-maker willing to scope a bounded pilot.

That is not the intended model. ClassShift is designed to coordinate a recurring workforce workflow around the employer need and student availability, while real onsite work remains under the approved operating and supervision model.

The supervision, employing entity, worksite responsibility and other operating/legal responsibilities must be explicit in the approved pilot model. This preview does not invent those allocations in advance.

The product can represent confirmations, cancellations, assignment state and replacement workflow. Exact cutoffs, consequences, replacement commitments and service levels are not public promises until the pilot operating rules are approved.

The current product contains submitted/approved time and settlement-status concepts. The final payroll partner, cadence, employer-of-record structure, bill-rate model, invoice terms and money movement remain owner/legal/business decisions and are not claimed as live here.

No public launch pricing is approved on this pilot-stage website. If a real employer need qualifies, commercial assumptions can be proposed and reviewed before either side commits.

The final employment, payroll and employing-entity architecture for a live DFW pilot is still under owner/legal review. It will need to be disclosed before onboarding or a real assignment. Joining the DFW student network does not create employment.

Joining the network is not a promise to accept work. A real assignment should present its schedule and relevant terms before commitment, with the approved confirmation and cancellation rules visible at that time.

The matching concept uses recurring availability, class conflicts, commute range, role requirements and preferences. The point is to qualify the actual dates and work pattern rather than advertise generic flexibility.

The product is designed to show submitted and approved work states and provide an escalation route. Exact dispute, review, settlement and appeal rules depend on the approved live operating model.

The launch principle is the opposite: employment-related decisions should not rely on unexplained black-box signals. Any future reliability or fit signals used in real operations require transparent, reviewed rules and appropriate human judgment.

They are illustrative product personas for routine guidance style. They do not prove a live support service and cannot define employment, pay, eligibility, attendance, legal or disciplinary rules.

The public launch preview does not publish a final age/eligibility policy. Any live pilot eligibility boundary must follow the approved legal and operating model before student onboarding begins.