Time-Out Zone

Managers propose, admins approve

Managers know what their team needs; admins own the rules. Manager suggestions bridge the two: a manager drafts policy tweaks, bonus-day tags, or holidays for their team, bundles them into one request, and an admin reviews and applies it — nothing changes without sign-off.

Get startedView pricing
  • Lab Test Analyzer logo
  • Promics Edge logo
  • SelfHacked logo
  • SelfDecode logo
  • OmicsEdge logo

Draft first, send once

Changes collect in a draft basket — up to eight per request. The manager reviews the whole bundle before anything leaves the tab.

One request, not ten emails

The admin receives a single bundled request per team: every change with its before and after, plus the manager's note on why.

Nothing applies without review

Every suggestion waits for an admin decision. Approve executes the changes; reject closes them with a note. There is no auto-approval path.

Honest skips, not silent failures

If a proposed tag name already exists or a holiday date is already in the calendar, that item is skipped and reported — never blindly applied.

The fine print, handled

Four kinds of proposals

Policy rule tweaks, new bonus-day amounts on existing tags, brand-new bonus-day tags, and holiday additions.

Next cycle or immediate

Each request picks its timing: staged for the next cycle (recommended) or applied immediately with balances recalculated.

A team-specific copy

Approving a policy tweak never edits the shared policy: the team gets its own copy with the changes, everyone else keeps the original.

Read-only by design

The manager's policy tab is read-only. Suggesting is the only write path, so admin ownership is never diluted.

One request covers one team and up to eight changes. Values in the visuals are examples.

Proposals

What managers can put forward

Four kinds of changes, all scoped to the manager's own team.

  • Policy rule tweaks: advance notice, tenure bonuses, spending limits, negative balance, unlimited mode, waiting periods, and blackout periods on the team's leave policy.
  • Tag proposals: new bonus-day amounts on the team's existing Additional PTO tags, or a brand-new bonus-day tag created and assigned on approval.
  • Holiday additions: a name and a date proposed straight into the team's effective holiday calendar.

The request

One bundle, one decision

The flow is built to respect both sides' time.

  • The manager drafts changes in place, sees the drafted-changes count climb, and reviews the bundle — current versus requested — before sending.
  • Timing is part of the request: next cycle stages the change, immediate applies it on approval and recalculates balances.
  • A note to the admin travels with the bundle, so the "why" arrives with the "what".

Execution

What approval actually does

Approve is not a rubber stamp; it is the apply button.

  • Policy tweaks create a team-specific copy of the leave policy and assign it to the team — the shared original stays untouched.
  • Tag and holiday items execute against live data with honest skips: duplicates and stale values are reported, not forced.
  • Partial results are stated plainly: applied items apply, skipped items say why.

More resources

Feature

Multi-step approvals

Feature

Additive segmentation

Ready to get started?

Give us a call. We'll walk a real suggestion from a manager's draft to an admin's approve — including what an honest skip looks like.

Multi-Step Approvals

Sequential chains with a live preview.

Explore

Deputy Approvers

Time-boxed cover for the approval queue.

Explore

Frequently asked questions

What are manager suggestions?
A request-and-review flow for team policy: a manager drafts up to eight changes — policy tweaks, bonus-day tags, holidays — bundles them into one request, and an admin approves or rejects it. Approval executes the changes; nothing applies without review.
Can managers change team policies directly?
No. The manager's policy tab is read-only; every change travels as a suggestion to an admin. That keeps one owner for company rules while still using what managers know about their teams.
What happens when an admin approves?
The changes execute: policy tweaks apply through a team-specific copy of the leave policy, tag proposals update or create bonus-day tags with balances recalculated, and holidays land in the team's calendar. Items that no longer fit — a duplicate name, an already-present date — are skipped and reported.
What is the difference between "next cycle" and "immediate"?
Next cycle stages the approved policy copy and applies it when the new cycle starts — the recommended default. Immediate applies it on approval and recalculates the team's balances right away.
Can a manager suggest changes for several teams at once?
No. One request covers one team and up to eight changes. Another team means another request, so every bundle stays reviewable.