Named Cover: Why 'Someone Will Cover' Is Not a Name

Tomasz writes "Aleksandra will cover" in the notes and hits submit. Aleksandra is on a flight. The manager approves because the calendar only shows one person away. The client call on Thursday has nobody on it.

The notes field lied, and the calendar did not catch it, because neither of them is a person who said yes.

Cover is the most commonly faked field in leave software. US and UK tools treat it as a staffing overlay: a colour on a calendar, a minimum-headcount warning, a Slack status. DACH and Polish teams mean something more specific. Someone named, on this request, who has accepted the stretch. German HR vocabularies call it Vertretungspflicht. The English product word is "replacement."

Three features, one word

Product pages say "cover" for at least three different jobs. Mixing them is how you buy the wrong one.

Named cover is a field on the leave type. This request cannot be filed without a colleague's name, and that colleague has to accept or decline on their own behalf. Nobody gets volunteered by someone else's holiday form. The name is evidence: who held the work, in writing, before the days came off the balance.

Coverage risk is a calendar question. Will this team still have a backend lead on Tuesday. We wrote that up in the coverage-risk post. It is necessary and it is a different feature. A named cover can still leave you with zero people who can deploy. A green calendar can still leave you with nobody who agreed to take Tomasz's client.

Approval delegation is a third thing again. Factorial's "delegate approver," Vacation Tracker's substitute approver, the SAP inbox stand-in: those hand a manager's decision queue to someone else while they are away. Useful. Not cover. The person who decides Tomasz's leave is not the person who sits in his standup.

If your tool offers one of these and labels it cover, it is not being poetic. It is collapsing a staffing problem, a permission problem, and a handover problem into a checkbox.

A name is a block. A clash is a warning.

The design mistake is treating every cover problem as a hard stop.

No name, when the policy requires one, is a block. The form can show a Required tag and still let you click Submit. The server refuses: "This policy requires a cover." Preview is already ok: false. That is the whole point of the field. A notes-field promise is not a name.

The named person is themselves away on some of the payable days: a warning. Thursday off does not make Bartek a useless cover for a five-day week. It makes Thursday the day the manager has to look at. Blocking the request would send Tomasz into a private message, which is where fake cover is born.

The named person is already covering someone else in the window: also a warning. Two writers may name the same cover. Both requests can commit. The requester sees that Bartek is already holding another absence; an admin sees who. The manager decides whether one person holding two stretches is acceptable. A hard block here just rotates the lie onto a second name.

Self and inactive are still invalid. You cannot name yourself. You cannot name someone who has left. Those are identity errors, not staffing judgement.

Then there is the one later block that actually matters. If Bartek declines, the request must not become approved leave with a declined cover still attached. Final approval checks that the name is still there and has not declined. An approver who clicks yes on a declined cover gets a refusal, not a quiet success.

Accept and decline belong to Bartek. Tomasz does not get to volunteer him. Marta does not get to accept on his behalf from the approval screen. By the time the manager opens the request, the coverage question already carries an answer, or it carries a decline, which is also an answer.

Worked example

Tomasz books five days of Vacation, Monday to Friday. Northlake's default day is 8 hours, so the request is 2,400 minutes, the same threshold that adds an admin step on the seeded Vacation policy. The policy requires a cover. He names Bartek.

The preview warns twice. Bartek already has Thursday as approved leave. Bartek is already covering Mila from Wednesday to Friday. Neither warning stops submit. Tomasz files the request. Bartek gets the cover ask, not a surprise calendar entry.

Bartek declines on Tuesday. Tomasz's manager cannot approve: the request still needs a cover, and the assignment is declined. Tomasz names Kai, Kai accepts, the manager approves, and only then do the 2,400 minutes move from reserved to used.

If Tomasz had skipped the name, he would never have reached Tuesday. The first Submit would have come back "This policy requires a cover," with up to five suggestions from his own teams, people who are scheduled and not already stretched across every day of the window. A request longer than 31 days skips suggestions and asks him to search. That is a window limit, not a philosophy.

The Request history on the leave record then reads as a trail: submitted, cover assigned, cover declined, cover assigned, accepted, approved. The story lives on the request. It does not live in the Slack thread where Tomasz said Aleksandra would do it.

What this is not

It is not a minimum-staffing rule. One named cover does not mean the pipeline is manned. If you need "at least one backend lead," that is the coverage-risk view, not this field.

It is not "you cannot book leave while you are assigned as cover." Some tools invert the constraint that way. We do not. The cover can still take their own Thursday. You see it, you decide.

It is not on every type. Seeded Vacation and Unpaid leave require a name. Sick leave does not, because you do not name a replacement for a fever. Unpaid requiring a cover is a default you can turn off; it is the outlier, and you should look at it before the first unpaid day surprises a new hire.

Hour-measured types can skip it. A two-hour medical appointment is not a Vertretung.

Where SquadBear keeps this

The switch is on the policy, not the person. Workspace settings → Leave policies → the policy → require a replacement. The request form on My leave shows Required when that is on, and the preview lists Suggested cover from your own teams.

The named colleague accepts or declines themselves. The approver sees the live warnings on Review leave request: cover away on dates, cover already holding another absence. A declined cover blocks the final yes.

If you'd rather ask than click:

"Tomasz wants next week off. Who on his teams is free to cover, and is his current cover already covering someone else in that window?"

The approvals guide is the chain, the history trail, and the cover rules in one place.

Start free and file a week that names a real person, or open the demo and decline a cover to see the approval stop.

Related reading: designing a fast leave approval workflow, which is who decides, and coverage risk, which is whether the skill is still in the building after they do.