Handbook
Here you manage versioned handbooks (e.g. driver, warehouse or safety handbook), publish them, assign them as mandatory reading and have staff read and acknowledge them — with a verifiable read proof.
Live preview — real view with sample data
M14 · Handbook
| Title | Category | Version | Effective from | Published | Created by |
|---|---|---|---|---|---|
| Service due | Done | Entry 5 | 07/06/2026 | ✓ | Record 3 |
| Defect reported | Reviewed | Record 6 | 18/06/2026 | — | Item 4 |
| Handover ok | Open | Item 7 | 29/06/2026 | ✓ | Entry 5 |
| Re-check | In progress | Entry 8 | 10/07/2026 | — | Record 6 |
| Routine checked | Done | Record 9 | 21/07/2026 | ✓ | Item 7 |
Not a screenshot: the same interface you get in production.
What you do here
Create or edit a handbook: give it a clear title, pick the category (General, Driver, Warehouse, Occupational safety), enter version and „Effective from“, and optionally add a summary, the master language and the minimum read time in seconds. Several versions of the same handbook hang under a „series“ (version bracket) — so it stays traceable which version applied when. When it is ready you publish it; with „New version“ you prepare the next draft in parallel without touching the version currently in force.
Mandatory reading & proof
Only published handbooks are visible to staff. Via 'Acknowledge' each person submits their own read proof; the minimum read time ensures the document was open long enough. On the detail page „Mandatory reading — who is still missing“ shows per person whether the version in force has been acknowledged and by when it is due — the basis for the instruction record and for following up.
Roles & permissions
Reading, creating, editing, publishing, deleting, acknowledging, assigning and viewing others' read proofs are separate rights in the permission matrix. By default: admin may do everything; manager/dispatcher maintain and assign content but do not publish/delete; staff read and acknowledge. The master language defines the binding source; further languages are added manually or imported.
Law & proof
A read proof documents the instruction (ArbSchG § 12, DGUV Rule 1 § 4: at least yearly) but does not replace a workplace-specific instruction with the chance to ask questions — for hazardous substances (GefStoffV § 14) verbal instruction is mandatory. An assignment can therefore be flagged as „instruction required“. Version and „effective from“ prove which version applied when; who acknowledged in which language is recorded — an understandable language is legally required (ArbSchG § 12). Published versions and acknowledgements are never deleted (retention duty). Seeing others' read proofs is limited to management/HR (GDPR/§ 26 BDSG); evaluate rates per area, not per individual (§ 87 (1) no. 6 BetrVG).
What's inside
- Handbooks
- Validity
- Handbook
- Edit handbook
- Add handbook
- Publish
- Retract
- Acknowledge
- New version (draft)
Fits together with
Other blocks from the same area.
Assets & Equipment
The register of every asset and device – machines, technical installations, tools, IT – with photo, QR label, location, owner, check-out, maintenance/inspection dates and value.
M08Articles & products
The register of all articles and products – with image, SKU, category, variants, price, stock and supplier.
M09Tasks
Tasks are the "who does what by when" across all areas – as a kanban board by status or as a list.
M10Surveys
With Surveys you build your own questionnaires with pages, media and branching, decide how anonymous responses are and how participants get in, and distribute them internally or by link. Responses form a history; thresholds raise alerts.