Day in the Life of an HR Professional: Three Real Days
Three HR professionals wrote down everything they did on one ordinary workday. An HR generalist on a Tuesday in Phoenix who spent two hours on an I-9 audit and 45 minutes explaining COBRA to a man who thought it was a type of health insurance plan. An HRBP on a Thursday in Atlanta who coached a manager through a difficult conversation and then had her own difficult conversation with a director who wanted to skip the PIP. An HR director on a Monday in Portland who started with a benefits renewal meeting and ended the day telling her husband "fine" when he asked how work was.
These characters are composites, built from dozens of real accounts, interviews, and community threads. The people aren't real. The experiences are.
Ruthie's Tuesday
Ruthie
Alarm. I set it 15 minutes early on Tuesdays because Tuesday is new hire orientation day and I need the extra buffer for the projector in the training room, which requires a specific sequence of power-on steps that our IT person, Marcos, documented on a sticky note taped to the remote. If you skip step 2, the HDMI doesn't connect, and you're standing in front of three new hires with a laptop and no screen. I've done that once. Never again.
Arrive at the office. We're in a two-story building near Sky Harbor. The construction company does residential and light commercial across the Phoenix metro. About 70 of our 110 employees are field workers: framers, drywall crews, electricians, superintendents. The other 40 are office staff. I handle HR for all of them, which means I'm the person who processes field workers' new-hire paperwork at 8 AM and the person who mediates an office drama about who took someone's yogurt from the shared fridge at 2 PM. Both of those things happened last week. Both required a straight face.
Projector setup. Steps 1 through 4 per Marcos's sticky note. HDMI connects on the first try. Small victory. I pull up the orientation slides, which I revised last month to include the updated PTO policy. The old policy gave 10 days after one year. The new policy gives 5 days at hire and 10 at one year. Our GM, Sal, approved the change after I showed him data from three competitors who all front-load PTO. The data took me six hours to compile. The approval took Sal four minutes. That ratio is basically my job.
Orientation starts. Three new hires today. Two field workers, both framers, and one estimating coordinator for the office. I walk them through the handbook, which is 18 pages and I know every paragraph because I rewrote it last year when I found out the previous version hadn't been updated since 2019 and still referenced a dental plan we no longer had. I cover safety protocols, which for the field workers includes fall protection, PPE requirements, and the process for reporting injuries. One of the framers, a guy named Tomás, asks me a question in Spanish about the health insurance enrollment form. My Spanish is OK. Not fluent, but good enough to explain that the "employee plus spouse" option costs $290 per paycheck and covers his wife but not his kids, and that "employee plus family" covers everyone but costs $410. He looks at the $410 number for a long time. I know what he's thinking because I've seen that look before. He asks if there's a cheaper option. I explain the HDHP, which has lower premiums but a $3,000 deductible. He asks what "deductible" means. I explain it. He picks the HDHP.
Orientation done. I walk the new hires to their respective areas: Tomás and the other framer go to the yard to meet their superintendent, and the estimating coordinator goes upstairs to meet her manager. Back at my desk, I enter all three into Paylocity, our HRIS. Name, SSN, address, W-4, direct deposit, benefits elections. Each one takes about 20 minutes because I'm also scanning their I-9 documents and uploading them. E-Verify follows, which is federally required for us because we're a government contractor. I submit the E-Verify cases. Two come back as "Employment Authorized" within minutes. The third flags for "Tentative Nonconfirmation," which means there's a mismatch between the employee's information and what's in the government database. This does not mean the employee is undocumented. It means the database has an error, or the name was entered differently, or the document number didn't match. I've seen TNC flags on US-born citizens. I print the TNC notice, which I need to give the employee within specific timeframes, and make a calendar note to follow up. This whole process, for three new hires, takes until about 11:40.
A field superintendent named Gil walks in. He doesn't take a Snickers. Bad sign. Gil says one of his crew members, a drywall finisher who's been with us for eight months, showed up to the jobsite this morning visibly impaired. Gil sent him home and wants to know the next steps. I pull up the company's substance abuse policy. Random testing is part of it, but this isn't random, this is reasonable suspicion. I walk Gil through the process: he needs to document what he observed (specific behaviors, not diagnoses), I'll schedule a test through our occupational health clinic, and the employee needs to be transported by someone else because he can't drive. Gil asks if the guy is going to be fired. I say it depends on the test results and the circumstances. The policy has a first-offense rehabilitation pathway that I helped draft last year. Whether it applies depends on factors I won't know until the test comes back. Gil nods and leaves. No Snickers.
Lunch at my desk. Leftover chicken tinga that I made on Sunday. I eat while I sort through 14 emails that came in during orientation. Three are benefits questions (one about dental coverage for crowns, one about adding a newborn, one about FSA reimbursement). Two are from managers asking about how to handle time-off requests during a busy project. One is from our insurance broker, Phyllis, about the upcoming renewal meeting. Six are from automated systems: Paylocity notifications, E-Verify case updates, and the weekly workers' comp report from our carrier. One is from a recruiter at a staffing agency asking if we're hiring. We're always hiring. I reply to the benefits questions first because those have faces attached to them and I've learned that a same-day response on benefits builds more trust than any all-hands presentation I've ever given.
I-9 audit. This is the project I've been putting off for two weeks. The federal government requires that I-9 forms be completed within three business days of hire and retained for either three years after hire or one year after termination, whichever is later. I have a filing cabinet with about 260 I-9 forms going back to 2018. Some of them are missing signatures. Some have documents that have expired and weren't reverified. Some are for employees who left three years ago and whose forms should have been purged. I'm going through the cabinet systematically, one folder at a time. Today I get through 22 files. Nine are clean. Six need minor corrections, which I fix with a single line through the error, the correct information, my initials, and today's date. Four should have been purged and I move them to the shred pile. Three have expired documents for current employees and I need to contact those employees for updated documentation. The audit will take me approximately 12 more hours spread across the next three weeks. If ICE conducted a surprise audit tomorrow, we would be fined. I know this. Sal knows this because I told him. The I-9 audit is my fourth priority, behind orientation, benefits administration, and the employee relations case from yesterday. There are not enough hours.
Phone call. An employee named Robert, who is a project coordinator in the office, calls to tell me he got a letter from his health insurance company denying a claim for an MRI. He's upset. He wants to know why we have "such terrible insurance." I ask him for the denial code. He reads it to me: "Prior authorization not obtained." I explain that his plan requires prior authorization for MRIs, which means his doctor's office needed to get approval from the insurance company before scheduling the procedure. The doctor's office didn't do that. This is not something I can fix. It's between Robert, his doctor's office, and the insurance company. But Robert called me, because I'm HR and HR is the entity that chose this insurance plan. I spend 15 minutes explaining the prior authorization process, the appeal process, and who Robert should call at the insurance company. I also draft a quick reference guide on prior authorization and email it to all employees, because if Robert didn't know about it, other people don't either. Fifteen minutes on a phone call. Thirty minutes on the reference guide. The prevention is always more expensive than the reaction.
Sal stops by my desk. He asks about the substance abuse case from this morning. I tell him the test is scheduled for tomorrow because the clinic was booked today. He asks if we can "just let the guy go." I explain the rehabilitation pathway in our policy and the legal risk of terminating without following our own documented procedure. Sal sighs. He doesn't argue. He just sighs. I've learned to read Sal's sighs. This one means "I understand but I don't like it." I say "I know." He takes a Snickers.
Log off. The I-9 audit spreadsheet is still open. I save it and close the laptop. Drive home, 28 minutes. My sister Annette calls during the drive. She asks how work was. I say "busy." She says "you always say that." I say "because it always is." She tells me about her day, which involved a meeting where someone brought donuts, and I realize that my day involved explaining COBRA to someone, navigating a substance abuse protocol, and auditing federal employment eligibility forms, and that none of those things translate into a casual phone summary. I say "it was fine." She says "you sound tired." I am tired. But it's the specific kind of tired that comes from holding a lot of things in your head simultaneously, not from physical exertion. The kind of tired where you lie down and your brain keeps running the I-9 spreadsheet behind your eyelids. I make dinner. I check my phone once, to see if the E-Verify TNC resolved. It hasn't. I put the phone down. Tomorrow.
Niles's Thursday
Niles
In the office early. Most of my team does hybrid, three in, two remote. Thursday is my in-office day by choice because it's when my standing meetings with the business leaders are scheduled. I support the product and engineering organizations, about 220 people. My counterpart, Shayla, handles commercial and operations. We share a director, Vincent, who mostly operates at the executive level and comes to us when something is escalated or structural. I open Outlook. Seventeen new emails since I left at 5:45 yesterday. I skim the subject lines and mentally triage: three can wait, four are informational, two need a response before 9 AM, and the remaining eight are part of an ongoing thread about the annual review calibration session next week that has become a 47-message chain because two directors can't agree on the rating methodology. I will deal with that chain last because it requires emotional energy I don't have before coffee.
One-on-one with Trent, who manages the platform engineering team. He has 14 direct reports. Too many. We've been talking about splitting his team for two months. Today he tells me one of his senior engineers, a woman named Sonya, has been consistently late to standups and missed two deadlines. He wants to know if he should put her on a PIP. I ask him what conversations he's had with her. He says "I mentioned it in our one-on-one." I ask if he documented it. He says "it was a verbal conversation." This is the most common pattern I see. Managers have the conversation but don't write it down. Then six months later, when the behavior hasn't changed, they want to go straight to a PIP, and I have to explain that a PIP without documented prior feedback looks retaliatory or arbitrary. I coach Trent on how to have a follow-up conversation that's both compassionate and documented. I give him a template I created that has three sections: observed behavior, impact, and expected change. The template took me a Saturday afternoon to build. I've used it with probably 30 managers in the last two years. It's the most effective thing I've made in my career and it cost me three hours of unpaid weekend time.
Skip-level meeting with a product manager named Opal. Skip-levels are part of our engagement strategy: every quarter, I meet with a random sample of individual contributors across my portfolio to get an unfiltered view of the culture. Opal has been here 18 months. She's candid in a way that I appreciate and that also makes me slightly nervous. She tells me the product team has a "favorites problem," meaning the VP of Product gives high-visibility projects to the same three people and everyone else gets maintenance work. She names the three people. She names specific projects. She says the allocation is not based on performance but on "who golfs with Rex." Rex is the VP. I take notes. I do not name the other people in my notes because these notes are discoverable if subpoenaed and I don't want individual contributor names attached to allegations they didn't make. I write: "IC reports concern about equitable project allocation in product org. Specific examples provided. Follow-up with VP recommended." That sentence took me about 90 seconds to compose in my head and it will take me two weeks to act on because acting means having a conversation with Rex about a pattern he probably doesn't see, using data I'll need to build from the project allocation records in Jira.
Compensation planning. We're in the middle of the annual merit cycle. I have a spreadsheet with 220 names, current salaries, proposed increases, promotion recommendations, and market data from Mercer and Radford. My job is to review every proposed increase, flag anyone below the minimum of their salary band, identify potential pay equity issues by gender and race, and create a summary for Vincent to present to the CFO. The budget this year is a 3.5% merit pool across the company. That pool is not distributed evenly. High performers get 4 to 5%. Meets expectations get 3%. Below expectations get 0 to 1%. The math requires that some people's generosity comes from other people's austerity. I've been doing this for 13 years and the euphemism never stops bothering me. "Merit pool" makes it sound like everyone swims. Some people don't get in the pool.
Walk. Out the lobby, left on Peachtree, down two blocks, one lap around the pond. A woman is feeding pigeons on a bench. Two people are jogging. A man in a suit is on his phone arguing about a lease. None of these people know what a merit pool is. I find this comforting. The pond is still. I do one lap. 22 minutes. Back at the office, I eat my turkey wrap while skimming the 47-message calibration thread. The disagreement is between two directors, Pamela and Hank, about whether a 3.5 rating should be described as "meets expectations" or "solid performer." This is not a semantic distinction to them. It affects how their teams perceive the feedback. I draft a compromise proposal: "consistently meets expectations" for 3.5 and "solid performer" as an informal descriptor that won't appear on the formal review. I send it. Pamela replies in four minutes with "fine." Hank replies in 22 minutes with "I can live with that." Forty-seven emails resolved in one paragraph. I should have done this on Tuesday.
Employee relations consultation. A manager named Diane in the implementation team comes to me because she overheard two of her team members making inappropriate jokes about a third team member's accent. She's unsettled. She doesn't want to "make a big deal" but she also knows she's supposed to report it. I thank her for telling me. I explain that what she described could constitute harassment based on national origin and that we're obligated to look into it. Diane looks like she regrets coming to me. This happens often. Managers bring something to HR expecting advice and get a process. I try to make the process feel less like a machine and more like a conversation. I tell Diane I'll talk to the individuals discreetly, that this doesn't have to be a formal investigation unless the pattern continues or the behavior was more severe than what she observed. She nods. I document the conversation in our case management system, assign a case number, and add it to my active case log. I have 11 open cases right now. This is number 12.
Meeting with Vincent about the organization restructure that's been in planning for six weeks. Engineering is moving from functional teams to product-aligned squads. This changes reporting lines for about 45 people. Vincent wants my input on which managers stay, which ones move, and how we communicate the change. I've prepared a one-page analysis that maps each manager's current team size, performance rating, and engagement scores against the new structure. Two managers are clearly aligned to the new structure. One is not, and moving him would either require a demotion or a lateral into a different function. His name is Lloyd. He's been a manager for four years. His engagement scores are in the bottom quartile. Vincent asks what I think. I say that Lloyd's team consistently rates him low on communication and role clarity, that this restructure is an opportunity to address a leadership gap, and that the conversation should happen before the broader announcement so Lloyd isn't surprised. Vincent agrees. I'll be in the room for that conversation. I always am.
Back at the comp spreadsheet. I flag three pay equity issues: two women in product management roles who are paid 7% and 11% below the male median for the same band, and one Black engineer paid 9% below the band median. I attach a note to each one with my recommendation for a market adjustment separate from the merit increase. These adjustments will come from a separate equity budget that I fought to include in this year's cycle. The budget is $62,000, total, for the entire company. It's not enough. But it's the first year we have it at all, and that's because I presented a pay equity analysis to the CFO last September that showed $180,000 in aggregate underpayment across 14 employees. The CFO approved $62,000 and said "let's see how it goes." Let's see how it goes is corporate for "I'm not convinced this is real but I don't want to be the one who said no to pay equity." I'll take it.
One last email. Trent, the engineering manager from this morning, sends me a message: "Had the conversation with Sonya. Used the template. She got emotional but understood. I documented everything. Thanks." I reply: "Good work. Let me know how the next check-in goes." Six words. But those six words represent an outcome that started at 8:30 this morning when Trent wanted to jump straight to a PIP and I redirected him to a conversation. That conversation happened because of a template I made on a Saturday. The template worked because I've had enough conversations with enough managers to know what they need. And Sonya now has a clear picture of what's expected and a chance to meet it. That's the invisible output of HR. Nobody sees the template. Nobody sees the coaching. They see the PIP, or the termination, or the restructure announcement. They don't see the 8:30 AM conversation that prevented the PIP from being necessary. Trent will probably forget the template existed by next month. Sonya will never know it was there. That's fine. The pond doesn't need anyone to watch it either. It just needs to be there.
Jolene's Monday
Jolene
In early. Monday is the day I protect for planning before the week eats me. I have a to-do list in a Moleskine notebook because I don't trust digital lists. Something about handwriting a task makes it feel more obligatory. Today's list has eight items. By 5 PM, I'll have completed four of them and added six new ones. That's the job. The list grows faster than you can shrink it.
Benefits renewal meeting with our broker, Annette, and the CFO, George. Our health plan renews on April 1st. Annette is presenting three options from carriers. Option A is a 7% premium increase with the same plan design. Option B is a 4% increase with a higher deductible. Option C is a switch to a PEO arrangement that would save 11% but means giving up our current carrier, which employees know and generally trust. I've been through eight renewals at this organization. Every year, the premiums go up. Every year, we have the same conversation: do we absorb the increase, pass it to employees, or change the plan? George wants Option B. I want Option A. The $12,000 difference between A and B, when spread across 320 employees, is about $37 per employee per year. From the company's perspective, $12,000 is meaningful. From the employees' perspective, a higher deductible means the phlebotomist making $38,000 might delay a doctor's visit because of the out-of-pocket cost. I make this argument. George listens. He asks Annette for the exact deductible difference. It's $500 higher. He looks at me and says "Jolene, we don't have $12,000 in the budget." I say "we have it in the turnover budget, because every time a CNA leaves because of benefits and we replace them, it costs us $4,200 in recruiting and training." He says "that's an indirect argument." I say "every good HR argument is indirect." He picks Option B. I document my recommendation for Option A in an email to the file. Not because I think I'll need it. Because I've been doing this long enough to know that the one time you don't document your recommendation is the time someone asks why you didn't flag the risk.
Staff meeting with my team. I have three direct reports: an HR generalist named Bridgette, a recruiter named Alonzo, and a benefits specialist named Coretta. Bridgette tells me she's behind on the annual harassment prevention training rollout because the LMS, our learning management system, had a glitch that unenrolled 40 people. She re-enrolled them manually over the weekend. I tell her she shouldn't be working on weekends and she gives me the look that says "neither should you but here we are." She's right. Alonzo has four open positions and the average time-to-fill is running at 52 days, up from 38 last quarter. He says the nursing positions are the hardest because the pay we offer is 8% below market and he's losing candidates to the competing health system across town. I've been asking George for a nursing pay adjustment since October. I have the data. The data doesn't have a budget line. Coretta updates me on the COBRA administation backlog: 12 former employees haven't received their election notices within the required 14-day window because our COBRA vendor's system had a processing delay. This is a compliance violation. I tell Coretta to escalate with the vendor and document every communication. If DOL ever audits us, I need a paper trail showing we identified the issue and took corrective action. This is Monday morning and I've already identified a compliance risk, an above-market-rate competitor problem, and a weekend work boundary issue. It's 10:20.
Closed-door meeting. The CEO, Dr. Yamamoto, wants to discuss a leadership change in the clinical operations department. The current VP, a woman who's been here for 11 years, is being asked to resign. The reasons are performance-related and I've been documenting the concerns for eight months. The separation agreement is drafted. Legal reviewed it last week. My role today is to walk Dr. Yamamoto through the conversation script, the timing, the communication plan for the remaining leadership team, and the interim coverage plan. The VP does not know this meeting is happening. She'll find out on Wednesday. I spend 45 minutes preparing the CEO to end someone's career and then I walk back to my desk and answer an email from Bridgette about whether the LMS can send automated reminders. The tonal whiplash of this job is something you never fully adjust to. One minute you're planning a termination at the VP level. The next minute you're troubleshooting a learning management system. Both are your job. Both require your full attention. The brain doesn't switch that fast. You just pretend it does.
Lunch. I eat at my desk. Soup from the place on Division Street. I read two articles from SHRM.org about the new FLSA overtime threshold that takes effect next year. The threshold is moving from $35,568 to $55,068, which means any salaried employee below $55,068 will be eligible for overtime pay. I have 23 employees who are currently classified as exempt and paid between $36,000 and $54,000. Each of them will either need a raise to stay above the new threshold or a reclassification to non-exempt with overtime eligibility. I start a spreadsheet. The cost of raising all 23 to $55,068 would be approximately $198,000 annually. The cost of reclassifying them and paying overtime based on historical hours patterns would be approximately $145,000 to $170,000. Neither number will make George happy. I'll present both options with a recommendation and a timeline next week. The soup is cold by the time I finish the spreadsheet setup.
Walk-in. A nurse manager named Fern comes to my office. She closes the door, which means it's personal. She tells me she's been having panic attacks before shifts and she wants to know about our EAP, the employee assistance program. I give her the information: up to six free sessions with a licensed counselor, confidential, accessed through a 1-800 number. She asks if her manager will find out. I say no. She asks if it will show up on her health insurance. I say no, EAP is separate. She starts crying. Not dramatic crying. Just tears that she wipes quickly with the back of her hand. She says "I'm sorry, I don't usually do this." I say "you don't have to apologize." I mean it. I also know that in the 19 years I've been doing this, I've handed out EAP information probably 200 times. And every single time, the person apologizes for needing it. Every time. The system that causes the stress is the same system that teaches people to apologize for having it.
Back to the FLSA spreadsheet. I add a third column: the option of raising some employees and reclassifying others, a hybrid approach that targets the ones closest to the threshold for raises and reclassifies the rest. This option costs approximately $162,000 and minimizes the disruption to people's daily work schedules, since reclassification means they'd need to track hours and lose the flexibility of exempt status. I think this is the right option. I highlight it in blue. George responds to data, not opinions, so I attach the Mercer survey data on how other healthcare systems in the Portland metro are handling the threshold change. Three of the four are doing the hybrid approach. One is raising everyone. None are reclassifying everyone. Good. I'm in the majority. Being in the majority makes the argument easier. Not because I need consensus but because George does.
Last thing. I review the separation agreement for the VP one more time. Every word matters. The release of claims clause. The non-disparagement language. The COBRA timeline. The reference policy. I read it like I'm reading it for the first time, even though it's the fourth time. On the fourth read, I notice that the severance amount doesn't match what Dr. Yamamoto and I discussed. It says 12 weeks. We discussed 16. I email legal to correct it. The difference is approximately $14,000 to the departing VP. Catching that error is the kind of thing nobody will ever know I did. But if I hadn't caught it, and the VP's attorney had, it would have been a trust issue that could have derailed the entire separation process. Four words on page three. $14,000. That's what attention looks like in this job.
Drive home. 25 minutes. My husband, Garrett, asks how work was. I say "fine." He says "fine fine or HR fine?" I say "HR fine." He's been married to me for 21 years. He knows that "HR fine" means "I can't tell you the details but the details were heavy." He hands me a glass of wine. I drink it standing in the kitchen, still in my work shoes. Fern's tears. The VP who doesn't know yet. The soup that went cold. George picking Option B. The $14,000 I caught on page three. All of that is in my body somewhere, stored in the specific way that HR professionals store things: behind a professional face, inside a locked filing cabinet in your chest, with a Moleskine list that grows faster than you can shrink it. I take off my shoes. I sit down. Tomorrow the list will be longer. But tonight, the wine is good and Garrett doesn't ask follow-up questions. That's 21 years of marriage. He knows when to stop.
Frequently Asked Questions
What does a typical day in HR look like?
It varies by level. Generalists split time between operational tasks (processing hires, answering benefits questions, compliance work) and employee-facing issues. HRBPs spend more time coaching managers, handling employee relations, and supporting organizational changes. Directors juggle budget decisions, vendor management, policy work, and executive conversations. The constant across all levels: interruptions. Planned work gives way to urgent human needs.
How many hours do HR professionals actually work?
Standard weeks are 40 to 45 hours, with spikes during open enrollment, year-end compliance, review cycles, and organizational changes like layoffs or restructures. During these periods, 50 to 55 hours are common. Solo HR practitioners at small companies often work longer because there's no one to delegate to.
Is HR mostly meetings?
At the HRBP and director levels, meetings consume 40 to 60 percent of the day. At the coordinator and generalist levels, the day is more task-based with employee walk-ups and system administration. The balance shifts significantly as you advance.