Summary
Someone comes back from six months of parental leave to a team that has changed tools, shipped two releases and acquired a new manager. Their monitoring data picks up exactly where it stopped, and the dashboard dutifully compares this week with the week before they left. Every number is down. If nobody intervenes, that comparison sits in front of a manager who may never have met them, and the returner spends the first month explaining a drop that is entirely the organisation's doing. This is one of the most common ways monitoring data quietly produces discrimination, and it is almost entirely preventable with a few settings and a conversation. This guide covers what to reset, what to protect, what the law requires, and how to run a ramp-back that uses the data to help rather than judge.
E-Monitor lets a manager reset a returner's baseline and exclude the leave period from trend comparisons, so the first month back is measured against itself. Sign up →
Why the Data Misleads After Leave
Three things happen at once when someone returns from an extended absence, and each one depresses the metrics without saying anything about the person.
The job changed. New tools, new processes, new people. A returner is relearning the role, with the same high switch rates and short focus blocks that a new hire shows in the first fortnight; the onboarding framework describes the curve.
The hours changed. Many returners come back on phased hours, compressed weeks or a flexible pattern. A dashboard still set to the old nine-to-five reads a four-day week as a 20 percent drop and a split day as two half-days of absence.
The person changed. Sleep, logistics and a new set of responsibilities outside work. Nobody returns to the same working rhythm, and a system that expects them to will find a deficit that is not there.
None of this is a performance signal. Treating it as one is the mistake, and the mistake usually happens by default, because nobody told the dashboard that anything was different.
What to Reset Before Day One
Five settings, all before the person logs back in.
| Setting | Change | Why |
|---|---|---|
| Baseline | Reset to start at the end of week two back | The pre-leave baseline belongs to a different job |
| Trend comparison | Exclude the leave period; compare week to week from return | Otherwise every chart starts with a cliff |
| Schedule | Match the agreed phased or flexible hours exactly | Attendance and after-hours flags depend on it |
| Application classification | Update for any tools adopted during the leave | Unknown apps default to neutral or unproductive |
| Manager view | Hide individual daily metrics for the first month | Trends only, and only once there is a trend |
The second row matters most. Most tools default to a rolling comparison, and a rolling comparison across a six-month gap produces a chart that looks like a collapse. Excluding the gap, or simply starting the clock again, is a one-minute change that prevents the whole problem. The trends guide explains why the comparison window decides what a chart appears to say.
Keeping-in-Touch Days and Phased Returns
Many jurisdictions allow a small number of paid working days during leave, often called keeping-in-touch days, and most good employers offer a phased return of reduced hours for the first weeks. Both create monitoring edge cases that are easy to get wrong.
Keeping-in-touch days should be recorded as agreed working days with the agent active, and nothing else during the leave should be. If the system shows activity on other leave days, that is leavism during parental leave, which is a workload and culture problem rather than a performance one, and in several jurisdictions a legal one for the employer. Phased hours need the schedule set per person and per week as it changes; a dashboard that reads a planned twenty-hour week as a sixty-percent absence is not measuring anything useful.
What Managers Must Not Do
The protections around parental leave are among the strongest in employment law almost everywhere, and monitoring data is a common route to breaching them without intending to.
- Do not compare a returner's metrics with their pre-leave figures in any review, formal or casual
- Do not compare them with the team during the ramp; the team has six months on them
- Do not let a drop in metrics after leave feed into pay, promotion or redundancy decisions; this is the textbook pattern in discrimination claims
- Do not read flexible-hours patterns as reliability problems; a split day is the agreed arrangement working
- Do not monitor during the leave itself, beyond agreed keeping-in-touch days
The third point is the one legal teams care about. Where a returner is later passed over or selected for redundancy, the question a tribunal will ask is what the decision was based on, and "the dashboard showed a decline" is close to an admission if the decline coincides with the return. The equitable monitoring guide covers the wider pattern, and the disparate impact guide the automated version of it.
Using the Data to Help
Handled well, the same data is one of the best tools a returner has. Their own trend from week two shows them, privately, that the job is coming back: focus blocks lengthening, switching falling, time in core tools rising. A manager who shares that trend at the one-month check-in, in the person's own figures, replaces anxiety with evidence. And at team level, the workload view shows whether the returner is being given a fair share of work or quietly sidelined, which happens more often than anyone admits and is just as damaging as overload.
Self-access is the key. A returner who can see their own data from day one can judge their own ramp, and the employee's guide is worth sending with the welcome-back note.
A Fair Ramp-Back Plan
Four weeks, with the data in a supporting role.
- Before return: reset the baseline, set the schedule, update classifications, hide daily individual views, send the welcome note with the dashboard guide
- Week one: no metrics discussed; onboarding to what changed, same as a new hire
- Week two: baseline taken at the end; still no comparison with anything
- Week four: first check-in with the person's own two-week trend on screen; questions, not conclusions
- Week eight: if phased hours are ending, reset the schedule; compare only with the week-two baseline
- Quarter end: ordinary review resumes, with the leave period excluded from every chart it touches
Written down and followed, this plan costs a manager about an hour and removes the single most common way a return from leave turns into a grievance.
Frequently Asked Questions
1. Can employers use monitoring data to assess employees returning from parental leave?
Only with care. Comparisons against pre-leave figures or against the team during the ramp back are unreliable and, if they feed pay, promotion or redundancy decisions, a common basis for discrimination claims. Use the person's own trend from the second week back, and nothing earlier.
2. Should the productivity baseline be reset after parental leave?
Yes. The pre-leave baseline belongs to a job that has since changed. Take a new baseline at the end of the second week back and exclude the leave period from trend comparisons so charts do not start with an artificial drop.
3. How should monitoring handle phased return hours?
Set the schedule per person to match the agreed hours exactly, and update it each time the hours change. A dashboard left on the old schedule reads a planned reduced week as absence and flags normal flexible patterns as reliability problems.
4. Is monitoring allowed during parental leave?
Not beyond agreed keeping-in-touch days, which should be recorded as working days. Activity on other leave days is a sign the person is working through leave, which is a workload and culture issue for the employer rather than a fault of the returner.
5. What is the biggest monitoring mistake with returners?
Letting a rolling comparison run across the leave gap. Every metric appears to collapse on return, the chart lands in front of a manager, and the returner spends a month explaining a decline the organisation created. Excluding the gap takes a minute.
6. How can monitoring data support someone returning from leave?
Through self-access to their own trend, which shows the job coming back week by week, and through the team workload view, which shows whether they are being given a fair share of work rather than sidelined.
A ramp back measured against itself E-Monitor resets a returner's baseline, matches phased hours, excludes the leave gap from every trend, and gives them their own data from day one. Sign up →