Small Organisations

Most of this subject assumes four systems. A thirty-person operation frequently has two, and the joins are different rather than absent.

What the estate usually looks like

A rota in a spreadsheet or a cheap scheduling app.

A time record, sometimes a terminal, sometimes the rota marked up.

Absence in a spreadsheet.

Payroll at an external bureau.

Which is two or three joins, and at least one of them is a person retyping.

Which joins exist

Time to payroll, always, because the bureau needs hours by a deadline. This is the one that matters.

Schedule to time, informally, since the rota and the record are frequently the same document.

Absence to both, by memory, which works at thirty people and stops working somewhere above fifty.

Identity is usually fine, because everyone knows everyone — and that is the thing that changes first as the operation grows.

What applies from this collection

Rule ownership, even with a bureau: which figures you send classified and which the bureau calculates. Ask them; the answer is frequently not what was assumed.

The reconciliation, reduced to one comparison: what you sent against what was paid.

The manual step register, which at this size is short and entirely load-bearing.

And the cut-off, because a bureau's deadline is fixed and corrections after it cost a re-run.

What does not apply

Reference data mastering, mostly. With one site and four departments the lists are short enough to maintain twice.

Effective dating.

Segregation of duties in the full form, which is impossible and should be replaced by visibility.

A chain owner as a role, because it is the owner or the office manager and everyone knows it.

Where small organisations get caught

The bureau's cut-off, with corrections landing after it every period.

A person retyping hours, where a transcription error becomes a pay error and there is no reconciliation to catch it.

Everything depending on one person who also takes holidays.

And growth: the arrangement that works at thirty fails at eighty, and nobody notices the crossing until a pay run goes wrong.

The one thing worth doing

Reconcile what you sent against what was paid, every period.

Ten minutes.

It catches the transcription error, the missed correction and the bureau's own mistakes — and at this size those three are almost the whole risk.

Reconcile sent against paid

The one thing worth doing at this size.

Ten minutes per period.

It catches the transcription error, the missed correction and the bureau's own mistakes.

At thirty people those three are almost the whole risk, and everything else in this collection is scaffolding for organisations that have outgrown this check.

A practical configuration prompt

During configuration, use this remote-team example to prompt questions about identifiers, ownership and output. Treat the page as a starting point and document each assumption.

Independent reference

For a thematic point of reference, see the U.S. Small Business Administration. Use this established source as an outside check before turning the principle into a system rule.