Openbook for HR and People Teams: Engagement, Time Off and Culture

People teams carry an odd burden: they're responsible for how the whole company communicates, celebrates, and takes time off — but the tools for those jobs are scattered across more vendors than any other function buys. An engagement platform here, a survey tool there, a PTO tracker, an events page, an intranet nobody visits, and a recognition app that charges per kudos. Each one has its own login, its own admin panel, and its own invoice.

Openbook replaces that stack with one workspace you compose yourself. The model is simple: your company is an organization, teams and audiences get spaces, and each space is assembled from rooms — 17 fully built app types covering feeds, surveys, events, PTO, boards, docs, and more. For a people team, that means the engagement feed, the pulse survey, the ERG communities, the events calendar, and the time-off queue all live in one place, with one member list and one search.

This guide walks through the actual setup: which spaces to create, which rooms to put in them, and the workflows for the five jobs that define a people team's year — engagement, recognition, communities, events, and time off. Everything here is a shipped feature.

Two spaces, two audiences

The most common HR setup mistake in any tool is mixing audiences: the whole company doesn't need to see your recruiting pipeline, and your team doesn't need company birthday posts interleaved with candidate notes. In Openbook the fix is structural. Create two spaces:

1. A company-wide People space — every employee is a member. This is where culture lives: the feed, events, ERG groups, the time-off room, and company pulse surveys.

2. An internal HR team space — just your team. This is where the work lives: recruiting boards, onboarding checklists, policy docs, and your own team's check-ins.

Openbook ships 12 one-click space templates, including an HR template that provisions and seeds rooms for a people team, so the internal space starts assembled rather than blank. Each space has its own members, roles, and a customizable sidebar — arrange the sidebar so the rooms employees use weekly sit at the top.

Here's a composition that works:

Space	Room	Type
Company-wide	Company Feed	Feed
Company-wide	Events	Event
Company-wide	Time Off	Time Off
Company-wide	Pulse	Check-in
Company-wide	ERGs (one per group)	Group
Company-wide	Handbook	Wiki
HR team	Recruiting Pipeline	Table Board
HR team	Onboarding	Kanban Board
HR team	Policy Drafts	Docs
HR team	Team Check-in	Check-in

The rest of this guide walks through each of these in working order.

The Feed: your engagement engine

The Feed room is a Workplace-style social feed, and for a people team it does the job the old intranet never did — because people actually open it. What it supports, concretely:

• Posts with images and files — the everyday stream of company life.
• Announcements — a distinct post type for the things everyone must see, with pinning to hold critical items at the top until they've done their job.
• Polls, in five types — from quick one-tap questions to structured multi-option votes. Low-stakes polls ("Summer party: rooftop or park?") train people to answer, which pays off when the stakes rise.
• Kudos — public, named recognition as a first-class post type.
• Seven emoji reactions and threaded comments with @mentions — lightweight ways in for people who won't write a post but will react to one, and threads that keep discussion attached to the thing being discussed.
• A bulletin board sidebar — announcements, birthdays, trending posts, and resources, always visible beside the stream. The birthdays panel alone generates more daily goodwill per pixel than anything else you'll ship.

The people team's job in the feed is programming, like running a small TV channel. A cadence that works: an announcement rhythm you keep (weekly or biweekly, same day, so it's expected), one poll a week, kudos amplified as they happen, and leadership posting as themselves — a two-line founder post outperforms a polished comms broadcast every time. Comments open on everything; a feed where employees can't respond is a noticeboard, not a community.

Two norms to set early. First, announcements are rare on purpose — if everything is an announcement, nothing is. Ordinary news is a post; announcements are for the five-percent that genuinely concerns everyone. Second, the people team replies. A comment that sits unanswered for three days teaches everyone that commenting is pointless.

Recognition that people actually see

Recognition programs fail quietly: the awards exist, but nobody witnesses them. Openbook's answer is that kudos are feed posts — public by default, named, reactable, commentable. A kudos post about a support rep who untangled a brutal escalation gets seven emoji reactions and a thread of "seconded" within the hour. That visibility is the entire mechanism; recognition works in proportion to who sees it.

What the people team does:

1. Model it. Post kudos yourselves, weekly, about specific behavior ("Maya rewrote the onboarding checklist that three departments now use") rather than generic praise ("great job Maya!").
2. Prompt it. After launches, project completions, or brutal weeks, nudge managers to post kudos while the event is fresh.
3. Aggregate it. Kudos also exist as a status flag in Check-in rooms (more below), so peer recognition surfaces in team check-ins too — sweep those and amplify the best into the company feed.

The research case for public peer recognition over cash-equivalent perks is strong, and we've written it up separately in why kudos beat bonuses more often than you think.

ERGs get real homes with Group rooms

Employee resource groups usually live in a chat channel, which means they have no memory, no front door, and no identity. The Group room type fixes this: groups are member-run communities with their own feed, their own roster, and open or closed privacy.

Setting one up:

1. Create a Group room in the company-wide space for each ERG — Women in Engineering, Parents, Pride, a book club, a running club. ERGs and social clubs both belong here; the room type doesn't judge.
2. Choose privacy deliberately. Open groups let anyone browse and join — right for interest clubs and most ERGs, since discoverability is how they grow. Closed groups gate membership — right for affinity groups where members should decide who joins.
3. Hand over the keys. Groups are member-run by design. The people team's role is sponsor and supporter, not moderator-in-chief. The group's leaders run its feed; you provide budget, executive sponsorship, and amplification into the company feed when the group does something worth the wider audience.
4. Let join/leave be self-serve. Nobody should have to email HR to join the Parents group. The join/leave mechanic means membership reflects actual interest, and the roster shows the group who's in the room.

Because each group has its own feed, activity accumulates where future members can find it — a new hire who joins the Pride ERG in month two scrolls into a year of its history, which no chat channel offers. For structure, sponsorship, and measuring whether ERGs are actually mattering, see our companion piece on ERGs that actually matter.

Events people can find, RSVP to, and talk about

The Event room is the events hub for the company-wide space, with three tabs — upcoming, past, and calendar — plus RSVP (going / interested) and discussion threads per event.

The workflow for, say, a quarterly all-hands plus a summer offsite:

1. Create the event with its details. It appears in upcoming and on the calendar tab, so employees who plan by calendar and employees who plan by list are both served.
2. Watch RSVPs. The going/interested split is genuinely useful signal: a pile of "interested" with few "going" means the event sounds appealing but something — timing, location, clarity — is stopping commitment. That's fixable before the day, not after.
3. Use the discussion thread for the pre-event churn that otherwise floods inboxes: dietary requirements, carpools, agenda requests, "can this be recorded?" One thread, attached to the event, findable later.
4. Post the announcement in the Feed linking people to the event. The feed is reach; the event room is the record. Use both.
5. Afterward, the event moves to the past tab with its thread intact — photos, follow-ups, and "when's the next one?" all land there.

Recurring rituals — monthly demo days, lunch-and-learns, the wellness series — live in the same room, giving employees a single calendar answer to "what's happening at this company?"

Time off without the spreadsheet

PTO tracking is the most quietly broken system in most small companies: a spreadsheet, an email thread, and a manager's memory. The Time Off room replaces it:

• Request types — vacation, sick, parental, whatever categories your policy defines — so requests arrive structured.
• An approval queue or auto-approve. Route requests to managers for sign-off, or auto-approve for policies built on trust. Mixed approaches work too: configure by what your policy needs.
• A "who's off" view — the at-a-glance answer to the question every standup and every project plan needs.
• A team capacity chart — the planning view. Before committing a launch date, look at the chart; discovering that half the team is out the week of the release is much cheaper in February than in June.

For the people team, the operational win is that requests, approvals, and visibility live in one place with a real record — no more reconciling a spreadsheet against email. For managers, the capacity chart turns PTO from a surprise into an input. And for culture, visibility is policy: when the "who's off" view shows leaders actually taking their time, the permission structure of the whole company shifts. We've written more on that dynamic in building a healthy PTO culture.

Pulse surveys with the Check-in room

Annual engagement surveys measure the past; pulses measure the present. The Check-in room runs async check-ins and pulse surveys with the machinery to make them stick:

1. Start from the template library. The room ships 36 templates across industries. Pick a pulse template, then edit the questions — shorter is better, and the same 3–5 questions repeated beat ten clever ones asked once, because repetition is what makes trends readable.
2. Schedule the cadence. Check-ins are scheduled; a biweekly or monthly pulse arrives automatically, which converts a survey from an event you must launch into infrastructure that runs.
3. Turn on mood tracking. Every response carries a green/yellow/red mood. This single low-friction signal is the highest-value data the room produces.
4. Watch the flags. Responses can carry status flags — Blocked, Help, Milestone, Kudos — which turn free text into scannable signal. A Help flag on a pulse response is a hand raised; treat it like one.
5. Read Team Pulse. The room's Team Pulse analytics aggregate mood and participation over time. The pattern that matters is the trend: a department drifting from green to yellow over six weeks is a conversation you get to have before the resignation letter.
6. Publish digests, close the loop. Check-ins can be published as digests. Share what the pulse said and what's changing because of it — in the company feed, on the cadence people can predict. Response rates track directly with whether people believe answers cause action; the digest is the proof.

The company-wide Pulse room handles org-level sentiment. Your own HR team should also run its private daily or weekly check-in in the team space — the people team deserves the same async standup hygiene it recommends to everyone else. Question design and frequency get their own treatment in polls and pulse surveys: asking the right questions.

Running HR's own operations

The company-facing rooms get the attention, but the internal HR space is where your team's week happens.

Recruiting on a Table Board. The Table Board is a monday.com-style spreadsheet database with colored draggable groups, 9 column types, and bulk actions — the right shape for a pipeline. Model candidates as rows; use a status column for stage, a people column for the hiring manager, a date column for next interview, tags for role and source, and a progress column if you like a visual. Drag groups to reflect your funnel. The room ships around 40 templates, so you can start from a pipeline structure instead of a blank grid. Bulk actions handle the unglamorous work — closing out a filled role's remaining candidates in one pass.

Onboarding on a Kanban Board. Each new hire is a card moving through your onboarding stages; checklists on the card carry the twenty tasks (laptop, accounts, buddy, first-week meetings) and card templates mean every hire starts with the same complete checklist rather than whatever someone remembered this time. Custom fields track start date, manager, and location.

Policies in Docs, the handbook in Wiki. Draft policies in the Docs room — a Notion-style block editor with nested pages, good for work-in-progress with structure. Publish the durable result to the company-wide Wiki room — a Markdown knowledge base with live GitHub-flavored preview — where every employee can read the current version. Draft privately, publish publicly, one source of truth.

The people directory is already there. Openbook includes a people directory with profiles, the ability to follow coworkers, and an org chart — so "who does what and who reports to whom" is a platform feature, not another page you maintain by hand.

An "Ask HR" desk that answers each question once

Every people team fields the same questions on a loop: how does parental leave accrue, when does open enrollment start, what's the home-office stipend, who approves conference travel. Answered in DMs, each question costs you the same ten minutes every time it's asked. The Q&A room — a private Stack Overflow — turns that loop into a library.

Add a Q&A room to the company-wide space and run it as your Ask HR desk:

• Employees post questions in Markdown, and tags (benefits, leave, expenses, travel) keep the archive browsable with filters.
• Your team answers once, and the question author or your team marks the answer as accepted — turning a thread into a reference. The next person with the same question finds the accepted answer before they ever ping you; related questions surface it even when they phrase it differently.
• Up/downvotes let employees signal which answers actually helped, which matters when policies change and old answers age.
• The analytics dashboard shows what's being asked and how often — a live map of where your handbook is failing. Four questions about the leave policy this month means the Wiki page is unclear; fix the page, then link it from the accepted answer.

Seed it before launch with the fifteen questions already sitting in your inbox, answered and accepted. And keep the loop tight with the handbook: when an accepted answer keeps getting traffic, promote it into the Wiki, and update the answer to point there. Question volume on solved topics should fall over time — that's the system working.

Permissions: sensitive by design

HR handles the most sensitive information in the company, so the access model matters. Openbook's roles and permissions give you two levers:

• Space roles — Owner, Admin, Member, Viewer — control what people can do in a space. The company-wide space has everyone as members; the HR team space contains only your team.
• Per-room visibility lets a room be visible to everyone in the space or only to certain people. This is the fine-grained tool: even within the HR space, a compensation-review board can be visible only to the two people running it, while the onboarding board stays open to the whole team.

The practical pattern: default open in the company-wide space (culture rooms work because everyone's in them), default team-only in the HR space, and restrict per-room for genuinely sensitive work. Business-plan customers add SSO/SAML and an audit log on top. For the full setup walkthrough, see our permissions guide.

A month in the life of a people team on Openbook

Here's the rhythm with everything assembled:

Cadence	Activity	Room
Daily	Sweep the feed; reply to comments; approve time-off queue	Feed, Time Off
Weekly	One poll; kudos amplification; recruiting pipeline review	Feed, Table Board
Biweekly	Pulse goes out on schedule; sweep Help flags same-day	Check-in
Monthly	Pulse digest published with "what we're changing"; events posted for next month	Check-in, Feed, Event
Quarterly	Team Pulse trend review; ERG sponsor check-ins; capacity chart review before planning	Check-in, Group, Time Off

Notice what's absent: exporting survey results from one tool to present in another, reconciling the PTO spreadsheet, or paying five vendors. The global ⌘K command search spans all of it, and the AI assistant — which takes real actions with confirmation, using your own Anthropic, OpenAI, or DeepSeek key — handles the connective chores: drafting the announcement post, summarizing a month of pulse responses, creating the onboarding cards for Monday's new hire.

Next steps

A people team can stand this up in an afternoon:

1. Create the internal HR space from the HR template and move one real workflow — recruiting or onboarding — onto its board this week.
2. Create the company-wide space with a Feed, an Event room, and the Time Off room. Seed the feed with a week of posts before inviting everyone; nobody joins an empty room twice.
3. Invite the company. The Free plan is $0 with all 18 room types for teams up to 10, and every new workspace starts with a 14-day Pro trial — so the pilot doesn't wait on budget.
4. Add the pulse in week two, once the feed has proven the space is alive. Publish the first digest within a week of the first pulse.
5. Stand up ERG Group rooms as leaders volunteer — pull, not push.

Pro ($15/user/month, $12 annual) adds unlimited history, dashboards, the AI assistant, and priority support, with a 14-day free Pro trial; Business ($29/user/month, $23 annual) adds SSO/SAML, audit log, and advanced permissions — see pricing. For the wider view of how spaces and rooms compose, start at the product overview.

One workspace where engagement, recognition, communities, events, and time off actually live together — because for your employees, they were never separate things.