Imagine having a scheduling app that shows absolutely nothing for next week. Does that mean you have no shifts? Has management forgotten to publish the schedule? Or is the app just having another one of its moments?

At Kohl’s, those are three genuinely different possibilities. And the software doesn’t always make the distinction obvious.

The company uses UKG Pro for scheduling, while Okta sits elsewhere in its internal application ecosystem. They serve different purposes, but there’s a useful connection between them that became particularly noticeable when UKG had problems.

A Blank Schedule Is Terrible Communication

In September 2026, a Kohl’s associate raised a fairly basic question online: how do you know whether a schedule has been published if you aren’t included in it?

One response pointed to something useful inside UKG:

Home → System Messages

That section can show when a schedule was posted and who published it.

Now that is information worth knowing. A blank calendar tells you almost nothing. A publication record at least helps establish whether the schedule exists.

Another associate confirmed receiving a schedule-posted notification despite having no shifts for that particular week.

There’s an important distinction here. Being absent from a published schedule is not the same as waiting for an unpublished one.

And when your working hours depend on that distinction, the difference isn’t trivial.

The November 2025 UKG Problem

Kohl’s associates reported a particularly messy day on November 13, 2025, when UKG wasn’t behaving normally.

Reports included:

• The mobile app failing to load on multiple devices.
• Slow time-clock operations.
• Stores temporarily using paper records.
• At least one associate successfully checking a schedule through Okta in a browser while the mobile app wasn’t working.

That last detail is interesting.

Okta wasn’t magically repairing UKG. It was simply another route into the company’s application environment that reportedly remained useful during the disruption.

There’s a big difference between those two things, and it’s worth keeping straight.

The Part That Really Bugs Me

Kohl’s has over a thousand stores. Scheduling thousands of retail workers is complicated, especially when hours change, people swap shifts, and new hires enter the system.

But the person checking next Tuesday’s shift doesn’t need to understand any of that machinery.

They need three things: a published schedule, an accurate status, and a clear indication when something changes.

The problem is that Kohl’s scheduling experience can depend on more than UKG itself.

New associates have reported receiving handwritten schedules before appearing in the app. Others describe getting their first shifts directly from store management. Some stores apparently distribute UKG instructions more consistently than others.

So the application may be perfectly functional while the person using it still has incomplete information.

That’s the kind of problem you can’t fix with a prettier calendar.

One suggestion from associates is to keep a copy of the posted schedule in case the app becomes unavailable. Sensible advice, although it’s rather funny that screenshots remain a practical backup for a modern workforce-management platform.

I also think the System Messages feature deserves far more attention than it gets. Knowing when a schedule was published is useful context, particularly when hours are missing or a week appears unexpectedly empty.

Kohl’s Okta and UKG Pro are different pieces of the company’s technology setup. Neither should be confused with the actual scheduling decisions made at store level.

And that’s the uncomfortable bit: a scheduling app can display information beautifully, but it cannot explain a decision nobody has communicated.

Sometimes the most frustrating thing about a blank calendar isn’t the software.

It’s not knowing whether that blank space was intentional.