One rota, three systems, and why they must agree

In most operations the rota exists in more than one place: the scheduler people clock in against, the platform that tracks attendance and welfare, and whatever feeds payroll and invoices. When they drift apart, nobody notices until a client queries an invoice or an officer is chased for a shift they were never given.

Agreement is checked, not assumed

Saltilo compares its rota with your scheduler shift by shift: the person, the site, the post and the times. When they disagree, it says where and how, rather than quietly picking one.

• Missing or extra shifts on either side
• A different person, site or post
• Times that differ, compared in UK time

Why UK time matters here

Servers often keep time in UTC, which is an hour behind Britain for seven months of the year. A comparison that mixes the two finds problems that do not exist and misses ones that do. Saltilo treats UK time as the business clock everywhere a person reads a time, and converts deliberately at every boundary.

A rota that disagrees with itself is not a rota. It is three guesses.

Start alongside your existing scheduler, prove the two agree, and move across when you are ready.