InRatio

What it is

A web app, with nothing to install

InRatio runs in a browser. Your managers sign in with the Microsoft account they already use, so there is no new password to hand out. It sits alongside Famly, with nothing to migrate.

The job it does

Building a rota by hand is hard work

It is not just slow. Across seven sites, your managers juggle who is qualified, who is in which room, the cost target and the ratios, all at once. It takes days, and it leans on the few people who carry all the rules in their head.

InRatio does the heavy lifting, so building the rota is quick, and any manager can do it.

How we build it

One tool now, more when you want them

Underneath sits one engine that knows every ratio and qualification rule, yours and the law's. Tools sit on that engine, and you switch them on in the order that gives the most back, soonest.

Not all of it at once. We start with the first tool, and the rest follow only once it has earned them.

Now · the rota builder

It builds the rota from the numbers you expect

You give it what you know. It does the checking. What comes out is a rota you can publish, built on the numbers you plan around, never on a child's name or who turned up on the day.

Now · the rota builder

Your managers never have to remember the rules

The rules are complicated enough that experienced people still get them wrong. No manager has to hold any of it in their head. The tool carries it, quietly, in the background:

• Ratios: under twos at one to three, twos at your tighter one to four, over threes at one to eight
• A Level 3 in every room, and half the floor holding a full qualification
• A working first aider on site, and the experience route kept inside its cap
• An extra body where a child needs one to one support

So a manager in their first week is as safe as your most experienced one.

Now · the rota builder

You see the cost as you build

Your planned staffing cost against the 55 per cent target, moving as you add and move people. The number you steer by, in front of you while you decide, not found out after payroll.

Private to each site, the way it is now.

Now · the rota builder

Age mixing, worked out for you

The move you already make by hand. Older children can be placed in a younger room and counted at the tighter ratio. Younger children are never counted up.

One member of staff saved, and still fully legal.

Now · the rota builder

Nothing lapses without you knowing

Every member of staff carries their first aid, DBS, safeguarding and qualification dates.

Now · the rota builder

It sits on top of what you already run

• Famly gives the builder your child numbers per room. A simple export to begin with, a live link later if it earns its place.
• Microsoft handles the login, so staff use the account they already have.

Payroll comes later, with the live floor, once the system is tracking the hours people actually worked.

Now · the rota builder

Children's data stays in Famly

The builder works on numbers. Four under twos in a room, two staff. It never needs a child's name, date of birth or record.

Everything sensitive stays in Famly, where it already lives and where you already manage it. No new place holding children's data, and nothing extra for you to look after.

Next · the team layer

The rota, shared with the team

Once the builder has proved itself, the rota goes from something you hand out to something the team works with.

Staff see their own rota on their phone, request holiday, swap shifts between them, and call in sick through it. Still the schedule, the week ahead, before the day arrives.

Later · the live floor

The live floor, and payroll that follows it

The last piece is the day itself. Live data on where every member of staff actually is: who turned up, who moved rooms, who went home sick. The plan meets the real day.

And those real hours feed straight into payroll. Pay follows the hours people actually worked, never the ones that were planned, which is why it waits for this part and not the builder.