ThreadCount
a6f1059ddf
Uniform stock management for healthcare linen rooms: the coordinator app, the phone counter and the staff app, for your own server. Built from a113353 on 2026-09-15. Licensed under the Functional Source License (FSL-1.1-ALv2).
75 lines
4.5 KiB
Markdown
75 lines
4.5 KiB
Markdown
---
|
||
title: Staff groups and routes
|
||
section: people
|
||
order: 2
|
||
summary: Name your staff groups, put each on the FTE table, the starting kit or manager approval, and restrict garments by group.
|
||
screen: Settings › Issuing rules
|
||
role: Admin
|
||
keywords: staff groups, groups, routes, fte table, starting kit, manager approval, initial kit, nursing, rename group, garment groups, outside group
|
||
---
|
||
|
||
## Name your groups
|
||
|
||
Staff groups are the facility's own names, listed under `Settings › Issuing rules` in `Staff groups`. A new facility has none, and ThreadCount reads nothing into the letters of a name.
|
||
|
||
- **Add** a name in `New staff group`. It starts on manager approval.
|
||
- **Rename** changes the name on the list, on its route, on every staff record filed under it and on every garment tagged for it, in one step. Renaming onto a name already in use is refused. Changing only the case or spacing is allowed.
|
||
- **Remove** (`×`) is refused while any active staff member is filed under the group. Move them, or rename the group instead.
|
||
|
||
A staff import files people under whatever group the file names and adds nothing to this list. Groups on the register but not on the list are shown below it, each with an `Add` button and a head count. Their staff are on manager approval until the group is added and given another route. With no groups at all, everybody is on manager approval.
|
||
|
||
An Issuer can read the routes but not change them.
|
||
|
||
## The three routes
|
||
|
||
Each group takes one route, picked with the `FTE table`, `Starting kit` or `Manager approval` buttons on its row. A group cannot be on two; the server refuses the save. If a restored backup carries a group on both, it is read as being on the FTE table.
|
||
|
||
Every route stops at the same ceiling of sets held (see [the entitlement rule](/docs/people/entitlement-rule)). The routes differ only in how somebody gets there.
|
||
|
||
## The FTE table
|
||
|
||
The person's `Combined FTE` proposes their initial kit:
|
||
|
||
| FTE | Sets proposed |
|
||
|---|---|
|
||
| `1.0`, `0.9` | 5 |
|
||
| `0.8`, `0.7` | 4 |
|
||
| `0.6`, `0.5` | 3 |
|
||
| `0.4`, `0.3` | 2 |
|
||
| `0.2`, `0.1` | 1 |
|
||
| `Casual` | None. The form names 1, 2 or 3 and leaves the number to the manager. |
|
||
|
||
A fraction not on the table, such as `0.75`, is read by the band it falls in. With no FTE recorded, no kit is proposed and the register lists the person under `No FTE`.
|
||
|
||
The proposal is not a limit. A manager may sign for more, and the signed form is recorded as written with a sentence added, such as `Above the FTE table: 5 sets at 0.6 FTE, where the table proposes 3.` A signature does not lift the ceiling.
|
||
|
||
## The starting kit
|
||
|
||
`Starting kit (sets)` under `Settings › Issuing rules` is what the group is handed on the first day: 3 sets unless the facility sets its own. A blank or nought saves as 3, fractions are rounded down, and a figure above the ceiling is read as the ceiling. After that, more is issued as needed up to the ceiling. Nothing has to be handed back first.
|
||
|
||
## Manager approval
|
||
|
||
There is no starting kit. The person's manager approves sets, on a signed order form recorded on the person's page or on a request in the staff app.
|
||
|
||
> **In plain terms** The counter refuses on the ceiling, the staff group and the uniform style. It does not refuse an issue because no approval is on file.
|
||
|
||
On the person's page, `Initial kit` counts every garment ever issued to them that was not pre-loved, against the kit their route gives. It is a lifetime count, and a hand-in does not give it back.
|
||
|
||
## Garments restricted by group
|
||
|
||
Each catalogue garment is tagged for one or more staff groups, or for all groups when it has no tag. See [catalogue, sizes and cuts](/docs/stock/catalogue-sizes-and-cuts).
|
||
|
||
- The staff app refuses a request for a garment outside the person's group. The one exception is a damage replacement for a garment they already hold.
|
||
- A request raised at the counter is refused the same way.
|
||
- Issuing one at the counter needs a coordinator override. Each issue row is stamped as outside the group; for a garment ordered in, the order's notes say so instead.
|
||
- The monthly exceptions report lists these as `Outside their staff group on an override`.
|
||
|
||
## What is written
|
||
|
||
| Record | Change | Undo |
|
||
|---|---|---|
|
||
| Add group | The facility's group list. | Remove it while nobody active is filed under it. |
|
||
| Pick a route | The facility's FTE-table and starting-kit lists. | Pick the old route. |
|
||
| Rename | The list, the route, staff records and garment tags. | Rename it back. |
|
||
| Remove | The group comes off the list and off its route. | Add it back and pick its route again. |
|