a feature is only done when it has an owner and a due date.
Every Clipboard module writes to the same employee record and ends in a state you can check: signed, approved, flagged or closed. Here is each one, how it behaves, and where it sits in your week.
checklists that chase their own signatures.
Build a day-one template once, version it, and assign it by role. Each task has one owner and one due date, and a task is either done or it isn’t. Documents route for e-signature and attach to the record the second they’re signed.
- versioned templates, assigned by role
- e-signature, UTC audit timestamp
- automatic reminders before and after due date
Where it fitsOffer accepted on Monday, template assigned in one click, laptop request goes to IT before the new hire has opened an email.
balances that stay correct without a spreadsheet.
Define accrual per policy: 1.25 days a month, a 15-day cap, 5 days carried over. Requests go to the right approver with a fallback if they’re out, and the approver sees who else is away before deciding.
- accrual by policy group or tenure
- approver chain with out-of-office fallback
- google calendar + slack status on approval
Where it fitsAn approver reviews Thursday’s request with the overlap already on screen, instead of opening three calendars.
overtime flagged while there’s still a shift to move.
Hours roll up per person per week. Set the threshold at 40 h and Clipboard flags anyone who crosses it before Friday, not after payroll closes. Approve a whole team’s week in a single keystroke.
- per-person overtime thresholds
- bulk approve with a keyboard shortcut
- weekly totals that reconcile to the row
Where it fitsA dispatch lead sees three people over 40 h on Thursday and reshuffles Friday’s rota the same morning.
surveys nobody can trace, trends everybody can read.
Short rotating questions, fully anonymous. Results for any group under five people are suppressed, so a small team can’t be reverse-identified. Trend lines show direction week over week and alert on a sustained decline.
- groups under 5 suppressed by default
- 28-day trend per team
- alerts after three weeks of decline
Where it fitsA slow slide in one department shows up in week three, in time for a conversation rather than an exit interview.
one record per person, reachable in two keystrokes.
The directory holds role, manager, start date, policy group and every signed document. Press ⌘K, type a name or a task, and run the action from the palette: assign a checklist, send a reminder, open a record.
- filter by role, manager, policy group
- command palette for every bulk action
- CSV import with column mapping
Where it fitsSomeone asks who still owes an I-9. You type “i-9”, select the two names and send the reminder before the meeting ends.
every change, who made it, and when.
Policy edits, approvals, signatures and permission changes are written to an append-only log with the actor and a UTC timestamp. Filter by person or event type and export the result as CSV for an auditor.
- append-only, no edits or deletes
- actor + UTC timestamp on every line
- filtered CSV export
Where it fitsAn auditor asks when the carryover cap changed from 3 to 5 days. The answer is one filter and one row.
how the modules hand off across a normal hiring week.
No module is a silo. Each one finishes by creating the input for the next.
checklist assigned
Template applies by role. Owners are notified and due dates start counting.
leave routed
A request reaches the approver with overlaps shown. Approval writes to calendar and Slack.
overtime flagged
Anyone past the threshold surfaces while Friday’s shifts can still move.
pulse read
The week’s anonymous answers land as a trend, and every action sits in the audit log.
the boring parts, specified.
HR data is personal data. These are the controls that apply on every plan unless noted.
Encrypted in transit
All traffic runs over TLS 1.2 or higher. Plain HTTP requests are refused, not redirected silently.
Encrypted at rest
Employee records and signed documents are stored encrypted. Backups are encrypted with separate keys.
Role-based permissions
Admin, People Ops, Manager and Employee roles. A manager sees their reports’ leave and checklists, nothing else.
Survey suppression
Responses are stored without an employee identifier. Any group under five people is hidden from reports.
Append-only audit trail
Policy, approval, signature and access events are logged and cannot be edited or deleted by any role.
Backups and sync status
Data is backed up daily. Every integration shows its last-synced time so you know the state of a calendar or status write.
approved leave lands where your team already looks.
An approval writes the event to Google Calendar and sets the Slack status. Zoom, GitLab, Notion and Jira read the same away-state, so work stops routing to someone who is out.
six modules, one record, one price per year.
Plans start at $59 per year for up to 25 employees. Pick by headcount and policy depth.