Muse for People Ops: Onboarding Checklists, Policy Answers, PTO Tracking, and Pulse Surveys That Close the Loop
A people ops setup for Muse: build a 90-day onboarding checklist for every new hire, answer policy questions from the handbook, keep PTO and schedules straight, and run pulse surveys that report back what changed.
By Professor Muse14 min read
People ops is the job of making a workplace work for the people in it, and most of it is small work that never makes a roadmap. A new hire needs accounts, a buddy, a plan for the first 90 days, and someone to answer the same five questions on day one. A manager needs the PTO calendar to be right before approving a request. An employee asks how parental leave works and needs the handbook answer. A pulse survey goes out, and then someone has to read the answers, say what changed, and do it again next month.
None of that is hard, but all of it is easy to drop, because each piece arrives as a message, a form, or a calendar invite, and the person holding it together is usually one person with a full inbox. This lesson sets up four jobs that run the same way every time. Muse builds the onboarding checklist and the 30-60-90 plan for each hire, answers policy questions from the handbook with the section cited, keeps the PTO and schedule picture current, and runs the pulse survey cycle from questions to the close-the-loop note. You keep the judgment calls, the sensitive conversations, and the final send. Muse does the drafting, the tracking, and the first pass.
One rule holds the whole setup together: the handbook and the system of record are the sources, and everything Muse writes about a person or a policy must trace back to one of them. A PTO balance comes from the HR system. A policy answer comes from the handbook section it cites. A survey result comes from the survey. That keeps a fast workflow honest, and it keeps a wrong answer from reaching an employee.
The short version
- Onboarding runs 90 days, not one day. Build one checklist per hire with an owner and a due date on every item, and a 30-60-90 plan with real milestones.
- Policy answers come from the handbook, with the section cited. If the handbook does not cover it, the answer says so and goes to a human.
- PTO and schedules stay honest by pulling from the system of record. Never state a balance or a date from memory.
- A pulse survey is five to ten questions every four to six weeks, with two or three anchor questions kept constant, and results shared with employees within two weeks, with one visible action attached.
- The failure mode to watch for is a confident policy answer with no source behind it. The fix is a citation requirement on every answer, and a human read before anything goes to an employee.
The Setup: The First-90-Days Desk
Call the whole arrangement the First-90-Days Desk. I run people ops for a team of about forty, and the desk is how those four jobs get done the same way every time.
The setup rests on the same pieces every time. A standing instruction from our memory guide sets the house rules: never invent a policy, a balance, or a date; never answer a policy question without citing the handbook section; never share an individual’s survey answer or PTO detail with anyone but that person and their manager; and never send anything to an employee without a human read. The handbook is the source file for policy answers, kept current in one place. The HR system is the source for balances and dates. The onboarding template is one checklist per hire, and the pulse runs on a scheduled routine, the same shape as a Friday expense review: the survey goes out on a fixed day, results are synthesized within two weeks, and the close-the-loop note goes out before the next pulse.
The onboarding half of the desk starts where recruiting ends:
Prompt 1: Build the Onboarding Checklist and the 30-60-90 Plan
Run this the day an offer is accepted. Onboarding that starts on day one is already late: accounts, equipment, and the first-week schedule all need lead time, and a hire who spends day one waiting on a login remembers it. The prompt builds the checklist from the role and the hire, with an owner and a due date on every item, and a 30-60-90 plan with milestones a manager can check.
The shape follows the four building blocks Talya Bauer described for the SHRM Foundation: compliance (the rules and paperwork), clarification (what the role expects), culture (how things really work here), and connection (the relationships the hire needs). A checklist that covers all four is a plan; one that covers only compliance is a paperwork queue. Gallup found only 12% of employees strongly agree their organization does a great job of onboarding, which is the gap this checklist is built to close.
Build the onboarding checklist and 30-60-90 plan for [new hire name], starting [start date], in the role of [role title], reporting to [manager name], on the [team name] team. The hire’s buddy is [buddy name]. Build four parts. (1) A pre-boarding checklist for the time between offer acceptance and day one: paperwork, equipment, accounts and system access, the welcome message, and the first-week schedule, each item with an owner and a due date. (2) A day-one and first-week plan, hour by hour for day one, with the manager welcome, the login check, the essential briefings only, lunch with the buddy, and one small piece of real work the hire can finish by Friday. (3) A 30-60-90 plan with milestones: first 30 days to learn the product, tools, team, and key processes; days 31 to 60 to own a defined piece of work; days 61 to 90 to deliver a meaningful result and agree on goals for the next quarter. (4) A check-in schedule: weekly one-on-ones with the manager for the first three months, and 30-, 60-, and 90-day reviews on the calendar. Rules: every item gets an owner and a due date, and no item is assigned to “HR” or “the team” without a named person. Cover all four building blocks: compliance, clarification, culture, and connection. If a detail is missing, list it as a question for me instead of filling it in.
Role details: [paste the job description and the offer letter]. Systems the hire needs access to: [list them]. First-week schedule constraints: [note any travel, holidays, or team events].
Read the checklist against the offer letter before it goes to the manager. The most common error is a checklist built for the wrong role, because the prompt was run with a copied template and the role details were never pasted in. A checklist that says the hire needs access to a system their team never uses is a small error that costs a morning. Check the owner on every item too: an item with no named owner is an item nobody does, and the first week is where that shows up.
Two details belong on the checklist before it goes out. Put the development plan on file by day 90: a hire without a plan after the first three months drifts, and the plan turns a good start into a good year. Collect the new hire’s feedback at day 90 and feed it back into the template, because the template improves only when the people who used it say what was missing.
Prompt 2: Answer Policy Questions From the Handbook
Run this whenever an employee asks how something works: parental leave, remote work, expenses, PTO accrual, the performance review cycle. The prompt answers from the handbook only, in plain language, with the section cited, and it says plainly when the handbook does not cover the question. That last part is the whole job. A confident answer to a question the handbook never addressed is how a wrong expectation gets set, and a wrong expectation about leave or pay is the kind of mistake that does not stay small.
Answer this employee policy question from the attached handbook only: “[paste the employee’s question, word for word]”. Write the answer in plain language, under 150 words, and cite the handbook section it comes from by name and number. If the handbook covers it only partly, answer the covered part and say exactly what is not covered. If the handbook does not cover it at all, say so in one sentence and draft a one-line referral to [the right person or team] instead of answering. Do not use anything outside the handbook: no general knowledge, no web search, no inference from a similar policy. If the question touches a legal or tax matter, add one sentence saying the employee should confirm with [HR contact or legal] before acting.
Handbook: [attach the current handbook or paste the relevant sections]. Employee’s own wording: [paste it].
Read every answer against the cited section before it goes to the employee. The check takes two minutes, and it catches the two errors this prompt can make: a section cited for a rule it does not state, and an answer that quietly extends a rule beyond what the handbook says. A handbook answer that invents a grace period or a carryover rule creates a promise the company never made, and the employee finds out when they try to use it.
The same rule applies to PTO questions, with one addition. A PTO balance is a fact about a person, and it comes from the HR system, never from the prompt or from memory. When an employee asks how much time they have left, the answer pulls the balance from the system of record, states the date it was pulled, and notes the accrual rule from the handbook. A balance stated without a source date is a number nobody can defend, and it is the number that gets argued about later.
Prompt 3: Run the Pulse Survey Cycle, From Questions to the Close-the-Loop Note
Run this every four to six weeks, on the same day, so the team learns when to expect it. A pulse survey is a short, recurring check on how people feel about work right now: five to ten questions, two to three minutes to finish, with two or three anchor questions kept the same every round so trends stay visible. The survey is the easy part; the cycle is the work: draft the questions, send them, synthesize the results, share the headline findings with employees within two weeks, and take one visible action before the next pulse goes out.
That last step decides whether the program lives. Gallup found only 8% of employees strongly agree their employer acts on survey results, and a McKinsey review of more than 20 academic articles found the number one driver of survey fatigue was the belief that the organization would not act on the results. People do not tire of being asked; they tire of being asked and hearing nothing. The close-the-loop note keeps response rates up, and it is the deliverable this prompt is built around.
Draft this round’s pulse survey and the close-the-loop plan for the [team or company name] team. The survey goes out [date]. (1) Write five to ten questions on a single 1-to-5 agreement scale, on one theme: [the current focus, for example workload after the reorganization, or manager support]. Keep our two anchor questions exactly as written: “[anchor question 1]” and “[anchor question 2]”. Add one optional open-ended question. Leave out any question that will not lead to a decision or a conversation. (2) After the survey closes, synthesize the results: the anchor trends across rounds, the one or two themes in the open-ended answers, and any team where the score moved sharply. Protect anonymity: do not report results for any group smaller than [minimum group size], and do not quote an open-ended answer that could identify its author. (3) Draft the close-the-loop note to employees: what we heard in two or three lines, the one thing we are doing about it, and when the next pulse goes out. Keep it under 200 words.
Last round’s results: [paste the headline findings and the action taken]. Current focus: [one theme and why it matters now]. Minimum group size for reporting: [number].
Share the headline results within two weeks of the survey closing. A polished report that arrives a quarter later builds less trust than a short note that says what was heard and what changed. Give managers their own team’s results with one suggested conversation to have, because teams respond to what their own manager does. Keep the anchor questions identical across rounds: a trend you can see is worth more than a sharper question you cannot compare.
Match the cadence to what you can act on. Monthly fits periods of change, a merger, new leadership, a return-to-office decision, and it only works if managers can act within the month. Every six to eight weeks fits a team building a listening habit. Quarterly fits a stable team that also runs an annual engagement survey. The right rhythm is the one you can act on. If results cannot be reviewed, shared, and turned into one visible step before the next pulse goes out, slow down.
| Job | When | What it answers |
|---|---|---|
| Onboarding checklist and 30-60-90 plan | Day of offer acceptance | Is this hire set up, and does everyone know their part? |
| Policy Q&A from the handbook | When asked, same day | What does the handbook actually say, and where? |
| PTO and schedule check | Weekly, before approvals | Are the dates and balances real, and who is out when? |
| Pulse survey cycle | Every four to six weeks | How is the team doing, and what changed since last time? |
What Can Go Wrong: The Confident Answer With No Source
Here is the failure mode you will meet first. An employee asks whether unused PTO carries over, or how much notice a schedule change needs, and Muse answers in a confident, helpful paragraph. The answer sounds right and cites a section number, so the employee plans around it. Weeks later, the handbook says something else, or says nothing at all, and the employee learns the real rule from a manager at the worst possible moment.
The cause is the one our failure modes guide describes: a fluent output that reads cleanly gets less checking than a rough one, and the checking it skips is the checking that would have caught the error. A policy answer is the worst place for that pattern, because the person receiving it has no reason to doubt it and every reason to act on it.
The fix has three parts, and all three are already in the prompts above. First, Prompt 2 answers from the handbook only, with the section cited by name and number, and it says plainly when the handbook does not cover the question. Second, every answer gets a human read against the cited section before it goes to an employee, and the read checks the citation as well as the tone. Third, balances and dates always come from the system of record with the pull date stated, so a number nobody can defend never reaches an employee. A policy answer counts when a human has verified its citation; without one, it is a risk that goes out under your name.
The same caution applies to survey results. A synthesis that reports a small team’s scores, or quotes an open-ended answer that names its author, breaks the anonymity the survey promised. The minimum group size and the no-identifying-quote rules in Prompt 3 protect that promise, and they matter more than a sharper finding. Trust in the survey is what keeps people answering it, and one broken promise about anonymity costs more responses than any number of questions.
Start With the Next Hire
Do not build the whole First-90-Days Desk this week. Take the next hire, or the most recent one, and run Prompt 1 on their offer letter and job description. Check every owner and due date, read the 30-60-90 milestones against what the manager actually expects, and put the check-ins on the calendar.
Run it that way and one hire tests the checklist, the owners, and the milestones before the next one arrives.
The onboarding structure in this lesson, the four building blocks of compliance, clarification, culture, and connection, and the 12% figure for employees who strongly agree their organization onboards well, come from Talya Bauer's report for the SHRM Foundation and Gallup's onboarding research, as summarized in the onboarding guides published by PPS International and TeckHustlers. The pulse survey cadence, five to ten questions every four to six weeks, the anchor-question practice, the two-week close-the-loop window, and the 8% figure for employees who strongly agree their employer acts on survey results, follow the pulse survey best practices guide published by QuestionPro, drawing on Gallup's survey research and a McKinsey review of more than 20 academic articles on survey fatigue.
