← YATS Laboratory

EDUCATIONAL SCHEDULING / ROADMAP

Developing the system around real requirements.

The core solver is ready for targeted internal alpha testing, while development of the wider system continues. Our current phase combines broad user needs research with testing against real end-user data and requirements.

From development to evaluation.

Current status · October 2026

  1. READY FOR ALPHA TESTING

    Core solver

    The core solver is ready for targeted internal testing. Further functionality is still needed for a full system, with user needs research and alpha testing helping to guide its development.

  2. CURRENT PHASE

    Broad research. Targeted alpha testing.

    RESEARCH TRACK

    Understand user needs

    Gather experience from a broad range of timetablers, including people satisfied with their current tools and processes.

    Explore the school study
    ALPHA TRACK

    Evaluate real requirements

    Conduct internal testing with real end-user data, using each participating institution’s full scheduling and product requirements as the basis for testing.

    Discuss alpha participation
  3. NEXT / INFORMED BY FINDINGS

    Develop the wider system

    Use the research and alpha results to prioritise remaining functionality and refinements, and shape the next evaluation phase. Timing and scope for wider access will follow what we learn.

WHAT ALPHA MEANS HERE

Internal testing,
grounded in your school.

Alpha testing is conducted internally by YATS using real end-user data. It is a focused evaluation with participating institutions, rather than a self-service trial.

  1. Agree the requirements

    Establish the scheduling rules, preferences, product requirements and evaluation criteria with the participating institution.

  2. Agree how data will be shared

    Arrange the necessary data handling and transfer before testing. Please do not send pupil, staff or timetable records through the general contact form.

  3. Test against the full brief

    Evaluate results against all agreed requirements, review any gaps and use the findings to guide further work.

TWO WAYS TO CONTRIBUTE

Share experience. Explore participation.

You can contribute to user needs research without taking part in alpha testing.