Employees maintains personnel profiles and connects people to organisational structure, work and development activities.
The employee record is the hub every other record relates to: the works a person carries, the events they attend, the threads they speak in, the programmes they walk. This manual covers the record itself — what you save, what you can do with it, what it connects to, and where it feeds.
What you record
The profile
| Field group | What it holds |
|---|---|
| Identity | First name, last name, display name, employee number, title |
| Contact | Work email, personal email, work phone, personal phone; postal and electronic addresses (attached through the address wiring, with a main address) |
| Organisation | Department, the org unit the person sits in, the manager, the mentor, the position |
| Employment | Hire date, date of birth, national ID, active status |
| Notes | Free-form notes, plus the update and deletion reasons the governance keeps |
Use the available update metadata and audit records to review profile changes. Agree the history and retention requirements for sensitive fields and attachments.
The classification
Each employee carries categories — full-time, contractor, intern, or whatever your operation's own category tree holds. Categories are typed classification: parent categories, active states, and tags, filterable across every list that shows people.
The feature specification stack
This is where the record becomes more than a profile. Characteristics — certifications, skills, language proficiencies — are held in a three-tier stack:
- Feature groups — e.g. Certifications
- Features — e.g. PMP
- Feature options — e.g. Active, Expired, Renewal Pending
Each feature carries a field type, a unit, and a range. Because the characteristics live in a governed structure, the platform can compare them: feature comparisons between two employees or two positions, and the skill distributions the analytics reads.
Additional information
Beyond the structured fields, the record carries typed blocks: a biography, a technical skills summary, a career history timeline, authored publications, external references. Each block is a typed structure, rendered appropriately and queryable — the record is enriched, not flattened.
Media
Photos, documents, and files attach to the employee record — the ID card scan, the CV, the certification scans — stored in your deployment, connected to the record they concern.
What you can do
- List, search, filter — browse the registry with typed filters (category, unit, status); bulk actions on selected records
- Create, update, view — the form and detail screens follow the same patterns as every module; the validation and permissions configured for the operation
- Compare — feature comparisons between records, rendered from the specification stack
- Dashboard — the module's dashboard reads the registry: headcount by category, by unit, by status
- Relate — the wiring below
What it connects to
The employee record is relationship-capable. An employee can be wired to:
| Target | Examples of the connection |
|---|---|
| Organization units & positions | The unit the person sits in; the position they hold; cross-functional units they participate in |
| Works | The work entries they carry, own, or contribute to |
| Calendar events | The meetings and occurrences they attend or organize |
| Content | The knowledge entries they author or are the subject of |
| Media | The files attached to their record |
| Venues | The locations their presence and work anchor to |
| Other people | The manager, the mentor, the peers — person-to-person connections |
Each connection carries a typed nature — the relationship layer's vocabulary: manages, mentors, supports, documents, references, and the rest of the governed nature list — plus a main-connection flag, ordering, tags, and a description. Connections are records too: assigned by whom, when, under what description.
Where it feeds
The employee record anchors the readings: the evaluation engine's behavioural evidence resolves to the employee records it concerns; presence, communication, and works relate to the person before they mean anything as evidence. Programmes and campaigns enroll people by record, not by name-typed-in-a-form. The record you maintain is the provenance behind every reading.
The pattern note: this manual follows the four-part structure every module manual shares — record, do, connect, feed — because the platform's modules share shared foundations: the same screens pattern, the same validation discipline, the same relationship layer. Learn the structure here; every manual that follows reads the same way.
Implementers load your existing employee data at adoption and configure the category and feature stacks to your operation's real structure; consultants help define what your organisation wants to record about its people — the stacks are yours to author.
No record is an island
The employee record is the hub — connected to the works, events, threads, programmes, files, and people it concerns, each connection typed and governed. That is what makes it the anchor: remove the wiring and you have a personnel file; with it, you have the person as the platform knows them.
Review the record and its context before deciding what to do next.
Organization → · Works → · All manuals → · The Employees platform page →
Check your work
Find an existing person before creating another record. Check the unit and position, record only the personal information needed for the stated purpose, and review access to attached documents. A certification feature should name its supporting evidence and current status rather than implying permanent qualification.
Available screens and actions depend on your deployment and permissions. Use this manual alongside the configured workflow and the capability demonstration for your installation.