Skip to content

Your criteria, applied consistently.

Parents and carers rank their preferences. Admit scores every application against your criteria, then matches them to capacity, ratios and attendance patterns.

Nursery, primary and secondary. One run, not weeks of spreadsheet work.

Book a demoSee a worked example

What goes in

The application captures the details needed for allocation, so your team does not enter them again.

  • Ranked preferences

    Each child has one application, with their settings or schools in order of preference.

  • Attendance patterns

    For nursery, the days and sessions the family needs, against each preference.

  • Siblings

    Brothers and sisters already attending, or applying in the same intake.

  • Catchment area

    Worked out from the home address. Placing requests are flagged for primary and secondary.

  • Additional support needs

    Recorded on the application and weighed the way your policy says.

A scoring matrix you set, not one we hand you

Every council orders its priorities differently. Admit holds yours as a matrix of criteria and weightings, and applies it to every application the same way.

  • Criteria and weightings come from your admissions policy
  • Different rules for nursery, primary and secondary
  • Held in settings, not in code

The whole estate, in one run

Thousands of applications. Dozens of settings. Several preferences and attendance patterns for each child. Matched together, in seconds.

Capacity, ratios and attendance patterns

A place is only a place if the room, the staff ratio and the sessions are all there. Admit checks all three for every council setting. Partner providers confirm each child's funding request themselves.

What-if scenarios

Change a setting's capacity and run matching again before anything is published. See where the pressure is, while there is still time to resource it.

One child, three preferences, two attendance patterns

  1. 1

    Isla’s parent applies

    Three preferences, in order. Two are Riverside Nursery on different attendance patterns. The third is Glenview ELC.

  2. 2

    Admit scores the application

    She lives in the area and has a sibling at Riverside. Your matrix gives her +32.500 there and +20.000 at Glenview.

  3. 3

    Admit matches her

    Wednesdays at Riverside are full, and every child placed there scored higher. Her second preference, mornings, has room. She is matched.

  4. 4

    The parent is told the decision and the reason for it

    They see the offer, the pattern and why the first preference was not available. Your team has the same reason on the record.

Every decision can be explained

Rules-based and deterministic. The same applications and the same criteria give the same result, every time. That is what makes a decision defensible at appeal.

  • Reasons for refusal

    When a placing request is refused, the reason is recorded on the application. It is in your wording, ready for the letter.

  • Waiting lists

    Children who miss a preference are held in score order. When a place opens, you can see who is next. There is no list to rebuild.

  • An audit of every decision

    The criteria, the scores, the capacity at the time and who pressed run. All kept, for every application.

Built around the exceptions first

Straightforward applications were never the problem. Admit was designed with West Lothian Council around the cases that take the time. You handle each one without leaving Admit.

  • Appeals

    Open the application and the decision is there: the score, the criteria behind it and the capacity at the time. Export it for the panel.

  • Late applications

    Scored on the same criteria, then placed where there is still room or held on the waiting list. Your policy decides which.

  • Mid-year placements

    A family moves in during the year. They apply, and the child is scored and placed against live capacity. No waiting for the next intake.

  • Capacity changes

    A room closes or a setting adds places. Try the new capacity in Capacity Planning and run matching on it. Nothing changes until you publish.

  • Policy exceptions

    Your team can place a child by hand where your policy allows it. They give a reason, and it is logged with their name.