Each person clocks from My clockings (and from the clocking widget on the dashboard). You need a contract in force that includes clocking; if you don't have one, the widget tells you so. Clock in opens your working day and clock out closes it. The big figure is effective work: the clock stops while you are on a break. The first time, you are asked to choose the modality (on site or remote). After that, the last one you used stays selected, so clocking in is still a single click; you can change it when you clock. You can't clock on a future date or on a day of absence. With the working day open, Break is recorded with one click. "Other situations" holds the rest.

People warns, it doesn't block. You will see a warning on the day (the person, and the company in Clockings) and in the export when: There are more ordinary hours in a day than the daily maximum in settings (9 by default, which is what the Statute says unless your collective agreement sets another). There are fewer than 12 hours of rest between the end of one working day and the start of the next. Compensating hours within the month is irregular distribution of working time: that the collective agreement or a pact covers it is the company's responsibility.

In Settings, the "Time record" section has three options (changed by whoever administers People): | Setting | What it does | Default | | --- | --- | --- | | Days of grace to correct the month | Up to which day of the following month a person can propose changes; from 0 to 15 | 5 | | Clock in from assistants and connectors | Allows clocking in and out with an MCP connector. When off, you can only clock from the application. The entry stores the channel it was made through | On | | Maximum ordinary hours per day | From how many ordinary hours in a day the warning is shown; from 1 to 12 | 9 | The company time zone (also in Settings) sets which day each clocking belongs to and when each month closes.

Working-time record — People

Q: The situations that are recorded

| Situation | What it is | Counts as work | | --- | --- | --- | | Working day | From when you clock in to when you clock out | Yes, minus whatever overlaps a break, a waiting time or an on-call time | | Break | Non-countable rest (for example, the lunch break) | No | | Waiting time | Non-countable waiting time | No | | On call | Non-countable on-call time | No | | Interruption of disconnection | Work that reaches you outside your working day (a call, an urgent notice) | Yes | The rules that keep the record consistent: You can have only one working day open per day, and you can't clock in while an interruption of disconnection is open. A break, a waiting time or an on-call time can only be recorded inside an open working day, and one at a time. If you clock out with one open, it closes at that same instant: you are the one leaving it by clocking out. An interruption of disconnection goes outside the working day and can also be recorded on non-working days, on vacation or on days of absence. It can cross midnight. Interruptions of disconnection add to effective work and remain visible separately, so there is a trace that one took place.

Q: Fixed and flexible schedules

The record compares your work with your schedule (in Schedules and My schedule) and with your contract, which holds your weekly hours, your regime (full-time or part-time) and, if part-time, the percentage. If your contract predates this record, whoever manages People can complete that data by editing it. Fixed schedule It has time slots and hours each day. Ordinary hours are measured per day: the day's segments, in order, use up the hours of your schedule, and whatever goes beyond is proposed as overtime. Flexible schedule It has no slots and no mandatory hours: it only says which days are working days (for vacation, holidays and availability). Ordinary hours are measured per month: The month's target is your weekly hours divided by the working days of the week and multiplied by the working days of the month, not counting holidays, vacation or absences. During the month no overtime is proposed: segments appear as "Pending the monthly count", and you see what you have so far against the target in My schedule, My clockings and Clockings. Working 4 hours one day and 12 another is not overtime if the month adds up. When the month closes, whatever exceeds the target is proposed as overtime on the last segments of the month (as complementary hours for part-time), and you can accept it or leave your disagreement. A deficit proposes nothing: it is shown, and what to do about it is up to the company. If the contract doesn't state the weekly hours, the schedule is still created, but there is no target ("No target"): no balance is calculated and nothing is proposed.

Q: Classifying hours

Each work segment can have one of these natures: Ordinary: those of your working day. Overtime: those beyond the working day on a full-time contract. You say whether they are compensated with rest or paid, and whether they are due to force majeure. Complementary: those beyond the working day on a part-time contract. The system proposes the nature by comparing with your schedule and your contract, and shows it to you, but does not save it. What stays in the record is what is set from Classify hours (in My clockings and Clockings), which is also a two-party proposal. A segment has a single nature: if it crosses the end of the working day, the majority one is proposed and you are told how many minutes go over.

Q: Changing a clocking: two-party proposals

Nobody changes a clocking on their own. Every change is a proposal that the other party accepts or rejects, and it is only applied when both have agreed. The two parties are: The person, only themselves. The company: their direct manager or anyone with permission to manage clockings. One of the two company authorisations is enough, and nobody decides a proposal they made themselves. You can propose an entry for a segment that wasn't clocked, the clock-out of an incomplete day, a time change, the voiding of a segment (it isn't deleted: it stops counting) and a reclassification. A reason is always required. While a proposal is pending on a segment, another one can't be made on it, and whoever made it can withdraw it. Clocking is never blocked. The interface applies no pressure: accepting and rejecting are on the same level, and notices carry no warnings. If there is no agreement: the disagreement If the person rejects a proposal from the company, they leave their disagreement in writing and it stays attached to the record. The company can then apply the change without agreement: it is applied, the proposal stays marked as rejected and the person's disagreement is stored next to the entry. Every disagreement is notified to the workers' legal representatives (if they have an access link with an email; see Access to and copy of the record). Technical incident When the system wasn't working and the day was noted by other means, the company can record a technical incident: it is the only route applied without prior acceptance. It requires a justification (10 to 1000 characters), is marked as such in the record, and the person later gives their agreement or their disagreement, which doesn't undo the entry.

Q: Incomplete days

People never invents a clock-out. If you leave a clock-in without a clock-out, when the day ends it becomes an incomplete day ("No clock-out"): you and your manager are notified, and in My clockings "Days without a clock-out" appears so you can propose the time you finished, with the same two-party flow. The automatic closings that existed before are kept as they were and shown marked.

Q: Month close and margin

Each month stays open for the person until day N of the following month (the margin). While the month is open, either party can propose changes. Once it closes: The person no longer proposes on that month. The company can propose, but the change is marked "After closing" and the person still has to accept it. Changing the margin doesn't reopen months that are already closed. On closing, People also generates the monthly payroll summary and, for those with a flexible schedule, the overtime proposals from the monthly count.

Q: History

Each segment has its history: every applied change is a new row with who made it, when, through which channel (web, MCP connector, assistant, system, technical incident), the reason, what there was before and what there is now, whether it was after closing and, if there was one, the disagreement. Nothing is overwritten or deleted. The person sees the history of their own records in My clockings.

People helps you keep the working-time record, but the record-keeping protocol and the applicable collective agreement are each company's responsibility. This documentation describes what the application does; it is not labour-law advice. To write your company's protocol you have a fill-in template.

The working-time record in People notes when each work situation of a person starts and ends, with the data required by the draft Royal Decree on working-time recording, and keeps every change made afterwards. Nothing is modified unless both the company and the person concerned accept it, and nothing is deleted for four years.

Clocking in and out

Each person clocks from My clockings (and from the clocking widget on the dashboard). You need a contract in force that includes clocking; if you don't have one, the widget tells you so.

Clock in opens your working day and clock out closes it. The big figure is effective work: the clock stops while you are on a break.
The first time, you are asked to choose the modality (on site or remote). After that, the last one you used stays selected, so clocking in is still a single click; you can change it when you clock.
You can't clock on a future date or on a day of absence.
With the working day open, Break is recorded with one click. "Other situations" holds the rest.

The situations that are recorded

Situation	What it is	Counts as work
Working day	From when you clock in to when you clock out	Yes, minus whatever overlaps a break, a waiting time or an on-call time
Break	Non-countable rest (for example, the lunch break)	No
Waiting time	Non-countable waiting time	No
On call	Non-countable on-call time	No
Interruption of disconnection	Work that reaches you outside your working day (a call, an urgent notice)	Yes

The rules that keep the record consistent:

You can have only one working day open per day, and you can't clock in while an interruption of disconnection is open.
A break, a waiting time or an on-call time can only be recorded inside an open working day, and one at a time. If you clock out with one open, it closes at that same instant: you are the one leaving it by clocking out.
An interruption of disconnection goes outside the working day and can also be recorded on non-working days, on vacation or on days of absence. It can cross midnight.
Interruptions of disconnection add to effective work and remain visible separately, so there is a trace that one took place.

Fixed and flexible schedules

The record compares your work with your schedule (in Schedules and My schedule) and with your contract, which holds your weekly hours, your regime (full-time or part-time) and, if part-time, the percentage. If your contract predates this record, whoever manages People can complete that data by editing it.

Fixed schedule

It has time slots and hours each day. Ordinary hours are measured per day: the day's segments, in order, use up the hours of your schedule, and whatever goes beyond is proposed as overtime.

Flexible schedule

It has no slots and no mandatory hours: it only says which days are working days (for vacation, holidays and availability). Ordinary hours are measured per month:

The month's target is your weekly hours divided by the working days of the week and multiplied by the working days of the month, not counting holidays, vacation or absences.
During the month no overtime is proposed: segments appear as "Pending the monthly count", and you see what you have so far against the target in My schedule, My clockings and Clockings. Working 4 hours one day and 12 another is not overtime if the month adds up.
When the month closes, whatever exceeds the target is proposed as overtime on the last segments of the month (as complementary hours for part-time), and you can accept it or leave your disagreement. A deficit proposes nothing: it is shown, and what to do about it is up to the company.
If the contract doesn't state the weekly hours, the schedule is still created, but there is no target ("No target"): no balance is calculated and nothing is proposed.

Conciliation measures on the schedule

If a schedule responds to a work-life balance, flexibility or irregular distribution measure, the schedule carries the measure (and, if you like, a detail). Each working day you clock copies the measure of the schedule in force at that moment, so the record doesn't change if the schedule is edited later. The flexible schedule carries "Agreed working-time flexibility" automatically.

The available measures are: adaptation of working time (art. 34.8 ET), irregular distribution of working time (art. 34.2 ET), agreed flexibility, infant care (art. 37.4), premature birth or hospitalisation of the newborn (art. 37.5), reduction for legal guardianship or care of a relative (art. 37.6), reduction for care of a child with a serious illness (art. 37.6), victims of gender or sexual violence or terrorism (art. 37.8) and "Other measure", which requires describing it. In the detail, write only what is needed to identify the measure, with no data about other people. What are not worked hours but leave or absences go under Absences.

If a segment ended up with the wrong measure, it is fixed with Correct measure, which is a change proposal like those below. And a schedule whose validity touches a month that has already closed can't be edited: open another one from an open month.

Classifying hours

Each work segment can have one of these natures:

Ordinary: those of your working day.
Overtime: those beyond the working day on a full-time contract. You say whether they are compensated with rest or paid, and whether they are due to force majeure.
Complementary: those beyond the working day on a part-time contract.

The system proposes the nature by comparing with your schedule and your contract, and shows it to you, but does not save it. What stays in the record is what is set from Classify hours (in My clockings and Clockings), which is also a two-party proposal. A segment has a single nature: if it crosses the end of the working day, the majority one is proposed and you are told how many minutes go over.

Changing a clocking: two-party proposals

Nobody changes a clocking on their own. Every change is a proposal that the other party accepts or rejects, and it is only applied when both have agreed. The two parties are:

The person, only themselves.
The company: their direct manager or anyone with permission to manage clockings. One of the two company authorisations is enough, and nobody decides a proposal they made themselves.

You can propose an entry for a segment that wasn't clocked, the clock-out of an incomplete day, a time change, the voiding of a segment (it isn't deleted: it stops counting) and a reclassification. A reason is always required. While a proposal is pending on a segment, another one can't be made on it, and whoever made it can withdraw it. Clocking is never blocked.

The interface applies no pressure: accepting and rejecting are on the same level, and notices carry no warnings.

If there is no agreement: the disagreement

If the person rejects a proposal from the company, they leave their disagreement in writing and it stays attached to the record. The company can then apply the change without agreement: it is applied, the proposal stays marked as rejected and the person's disagreement is stored next to the entry. Every disagreement is notified to the workers' legal representatives (if they have an access link with an email; see Access to and copy of the record).

Technical incident

When the system wasn't working and the day was noted by other means, the company can record a technical incident: it is the only route applied without prior acceptance. It requires a justification (10 to 1000 characters), is marked as such in the record, and the person later gives their agreement or their disagreement, which doesn't undo the entry.

Incomplete days

People never invents a clock-out. If you leave a clock-in without a clock-out, when the day ends it becomes an incomplete day ("No clock-out"): you and your manager are notified, and in My clockings "Days without a clock-out" appears so you can propose the time you finished, with the same two-party flow. The automatic closings that existed before are kept as they were and shown marked.

Month close and margin

Each month stays open for the person until day N of the following month (the margin). While the month is open, either party can propose changes. Once it closes:

The person no longer proposes on that month.
The company can propose, but the change is marked "After closing" and the person still has to accept it.
Changing the margin doesn't reopen months that are already closed.

On closing, People also generates the monthly payroll summary and, for those with a flexible schedule, the overtime proposals from the monthly count.

Statute warnings

People warns, it doesn't block. You will see a warning on the day (the person, and the company in Clockings) and in the export when:

There are more ordinary hours in a day than the daily maximum in settings (9 by default, which is what the Statute says unless your collective agreement sets another).
There are fewer than 12 hours of rest between the end of one working day and the start of the next.

Compensating hours within the month is irregular distribution of working time: that the collective agreement or a pact covers it is the company's responsibility.

History

Each segment has its history: every applied change is a new row with who made it, when, through which channel (web, MCP connector, assistant, system, technical incident), the reason, what there was before and what there is now, whether it was after closing and, if there was one, the disagreement. Nothing is overwritten or deleted. The person sees the history of their own records in My clockings.

Retention

The record is kept for four years. That is why a person's file can't be deleted if they have clockings from the last four years: they are deregistered, and if the right to erasure is exercised, the file is anonymised and the record is kept. After four years, the record is purged and this is logged in the audit trail. Before deregistering the organization, download the record (see Access to and copy of the record).

Time-record settings

In Settings, the "Time record" section has three options (changed by whoever administers People):

Setting	What it does	Default
Days of grace to correct the month	Up to which day of the following month a person can propose changes; from 0 to 15	5
Clock in from assistants and connectors	Allows clocking in and out with an MCP connector. When off, you can only clock from the application. The entry stores the channel it was made through	On
Maximum ordinary hours per day	From how many ordinary hours in a day the warning is shown; from 1 to 12	9

The company time zone (also in Settings) sets which day each clocking belongs to and when each month closes.

From an assistant

With an MCP connector you can clock in and out, record breaks and other situations, propose changes, accept, reject or withdraw them, and read the record, always with your own permissions. The built-in assistant only reads. Applying a change without agreement and recording a technical incident can only be done from the application.