A founder-led company needs clear HR decision rights before every people issue becomes a founder decision. Name who can recommend, approve, communicate, and record each recurring decision. Give managers a usable boundary and give sensitive situations an escalation route with a backup.
Retrospective field note: February 2026. Written October 2026.
Your inbox fills with three requests: approve a pay exception, settle a manager disagreement, and respond to an employee concern about a leader. Each arrives marked urgent. A decision map helps separate the work you must own from the work that needs a different authority or a better handoff.
What are HR decision rights?
Decision rights describe the authority attached to an action. They should answer four questions: who assembles the facts, who makes the decision, who communicates it, and who keeps the record? One person may hold several responsibilities, but the assignments should be deliberate.
This is Verk Vibe's operating approach, rather than a legal allocation of duties. Certain decisions also require counsel, payroll, safety, or other specialist review.
Start with recurring decisions
List the situations that return every month: role approvals, pay changes, performance concerns, employee complaints, leave requests, and departures. For each, identify the last real example. Trace where the work stalled and what information the final decision-maker needed.
Do not start by giving every manager unrestricted authority. Start by distinguishing routine management from situations that need a different reviewer.
For example, a manager can communicate an established deadline and discuss a missed assignment. A concern involving discrimination, health-related adjustments, disputed pay, or retaliation should reach the designated specialist before the manager decides the response.
Use a four-part decision record
- Decision required: state the choice in one sentence.
- Evidence and constraints: identify known facts, missing information, and relevant review requirements.
- Owner and approval: name the accountable person and any required approval.
- Communication and follow-through: say who will tell the affected people, record the outcome, and check implementation.
A request that lacks an actual choice may need fact-finding before it reaches the founder. A request that exceeds someone's authority needs a clear route onward rather than another informal opinion.
Build an alternate route for conflicts
A reporting structure fails when the concern involves the person who normally receives it. Specify an alternate contact with enough independence to act. Make that route available to employees, rather than leaving it in a leadership-only diagram.
The EEOC's harassment fact sheet recommends multiple reporting options. Decision-rights design should make those options operational, including when a senior leader is involved.
Test the system before expanding it
Choose one recurring decision and run the record through a real situation. Ask whether the manager knew where their authority ended. Check whether the approver received enough information and whether someone actually completed the next step.
In a small company, a one-page map may be enough. A larger document adds little if nobody can retrieve it during an urgent conversation.
What should still reach the founder?
Decisions involving business strategy, authority the founder has retained, significant resources, or leadership conflicts may still belong there. The purpose is to make those decisions arrive with a clear question and reliable context, while routine work has another owner.
The leadership insight: a founder can remain accountable without becoming the routing system for every request. Choose one recurring decision, name the authority around it, and test the next handoff before expanding the map.
Explore fractional HR leadership if the founder has become the default HR escalation point. For the engagement structure, read what fractional HR should deliver in its first 90 days.
