deeper checklist logic
Tasks that unlock other tasks, so a laptop request only opens after the offer is signed, and role-based branches inside one template.
exploringClipboard exists because most people-ops work fails in the handoff: the handbook nobody chased, the leave request that sat in an inbox, the unhappy team nobody measured. We build one thing: the checklist that makes the next action impossible to miss.
Observed pattern: three systems, zero shared record.
A new hire’s first week touches an offer letter in one tool, a W-4 in another, a laptop request in a ticket queue and a leave policy in a spreadsheet. Each step has a person who assumes someone else is chasing it.
The same pattern repeats for time off, where approvals wait in an inbox and balances are recalculated by hand, and for engagement, where the first signal is a resignation. Clipboard was built to replace that relay with a single record per employee and a checklist that names who acts next.
If a proposed feature breaks one of these, it does not ship. They are the reason the product looks plain.
Shared responsibility is how tasks stall. A checklist line holds exactly one assignee, with a fallback only for approvals.
rule: assignee count = 1No “in progress at 60%” on a single line. A task is open or closed, so a progress bar means what it says.
rule: states = open | doneA signed handbook, an approved day off and a flagged timesheet write to the same employee profile. Nobody reconciles two systems.
rule: single source of recordPulse results for groups under five people are suppressed by default, so a small team cannot be reverse-engineered from a chart.
rule: minimum group size = 5You pay per year by how many people you employ, not per feature unlocked or per seat added mid-quarter.
rule: one annual price per planHR data is not the place for novelty. Clipboard keeps its surface small, records every signature with a UTC audit timestamp, and treats a sync failure as a visible state instead of a silent one.
Questions go to contact@clipboardstudios.com and are answered against written documentation, so the answer you get is one anyone else could look up.
Every release lands in the changelog with what changed and what it affects. Policy-related changes call out whether existing balances move.
Direction, not promises with dates. Each item extends the existing record instead of adding a new silo.
Tasks that unlock other tasks, so a laptop request only opens after the offer is signed, and role-based branches inside one template.
exploringApproved leave already reaches Google Calendar and Slack. The same signal should reach the rest of the tools a team routes work through.
in designSharper alerts when a team’s pulse trend and overtime hours decline together, with the underlying numbers shown beside the alert.
exploringPlans start at $59 per year and cover everything shipped today.
Pick the plan that matches your headcount: $59, $249 or $400 per year, billed annually.