General information only. This explains a scheduling term. It is not legal advice: the rules that bind you come from the law, your agreements and your contracts.

Understanding pinning

A planner often knows something the rules do not. Pinning keeps that decision while the rest of the roster is planned.

When to pin

  • A shift promised to a worker.
  • A handover that needs a set worker.
  • A shift already agreed with a client.

How pinning works

  1. Pin the shift with its worker and times.
  2. Run the planning: it works around the pin.
  3. Unpin when the reason has gone.

Common mistakes

  • Pinning so much that the solver has no room.
  • Forgetting old pins, so stale choices stay.
  • Pinning an open shift by mistake, so it stays open.

How Chrona does it

Auto Schedule, a constraint solver built on Timefold, keeps a pinned shift as it is: same times, same worker. A pinned open shift stays open.

Generate keeps pinned shifts when it runs again, and so does a run that makes shifts from demand.

Step by step in the docs

Key takeaways

  • Pinning locks a shift's worker and times.
  • Planning works around pinned shifts.
  • Auto Schedule and Generate both keep pinned shifts.

Questions

How do I stop Auto Schedule moving a shift?

Pin it. A pinned shift keeps its times and its worker.

What happens to a pinned open shift?

In Chrona, it stays open, and the proposal counts it as unfilled.

Does Generate remove pinned shifts?

No. In Chrona, a pinned shift stays, with a note if coverage no longer needs it.

Should I pin every shift?

No. Each pin takes room from the solver, so pin only what must not move.

The word comes from Timefold, the planning engine Auto Schedule is built on. See the source