Core HR Software Resources

I'm writing a piece on which Rippling tasks people move from the mobile app to the web version because the app doesn't cover them, and the pattern in G2 reviews is consistent. Adjusting times, viewing some employee personal information and reading a detailed pay advice tend to move to a laptop, while clocking in and out, checking pay stubs and benefits, and requesting time off stay on the phone, and those everyday tasks are what people like most about the app.

Across core HR platforms, the app and the web version tend to be built for different people. Employees mostly need quick access to their own information, which the app handles; admins making corrections are usually at a desk anyway. Rippling sits squarely on that split, which suits a workforce where most staff never need the detailed view.

Situations I'd like to compare:

1. Correcting a time entry when you're away from your desk
2. Checking a pay advice on a smaller screen
3. Looking up an employee's details from your phone

Which tasks do you still keep for the laptop? And has anything moved onto the app recently that used to need the web version?

Where does a setting live when Rippling has HR, payroll, time and benefits all switched on? That's what I've been researching, and the answer admins give is that each module's settings sit in that module's own menus, so finding one means knowing which module owns it, and for rarely used settings, asking support. Time off balances and booked time are the areas people ask about most, and the more modules an account activates, the more options each menu holds.

Reading G2 reviews, the menus come up most for new admins and occasional users, while daily users describe clear tabs and dropdowns. In core HR, the deciding factor seems to be how many jobs one admin covers. Someone who runs onboarding, payroll and benefits gets real value from having them in one place, and the learning happens once; someone who touches one module occasionally carries the breadth without using most of it.

For admins who use it daily:

• Which module's settings took you longest to learn?
• Do you bookmark the pages you use most?

And for anyone training a new admin:

• How do you explain where time off balances live?
• What do you show them in the first week?

Did it settle into routine after the first couple of months?

I've been working through how an employee actually raises leave in BambooHR. From the reviews, it runs through the Time Off tab and a date range selection, with part days and non-consecutive dates the cases that come up. For someone doing this a handful of times a year, the route gets relearned each time.

Once learned the flow is quick, and the surrounding time-off functionality is one of the stronger parts of the product. The calendar view showing who else is already off is doing the real work, because most approval decisions turn on coverage rather than entitlement.

I'd be interested in how this plays out for occasional users specifically. An HR admin is in the system daily. An employee requests leave maybe six times a year, and relearns the interface each time.

• Whether people bookmark the Time Off page rather than navigating to it
• Whether new joiners need walking through it or pick it up unaided

Across Core HR platforms this occasional-user problem seems underappreciated generally. Software gets designed for the person using it every day, and most of the people in an HR system are not that person.

For HR teams on BambooHR, does this generate questions, and have you found a way to head them off?