← All articles

Policy, Not Personal: Making Grace Periods Fair Every Time

August 3, 2026 · 5 min read · By DockOps

Nobody enjoys telling a member they're behind on dues.

Even less, deciding who gets a break.

It's one of the hardest parts of running a local. A member has a rough stretch and asks for time. An officer wants to help. But the last person who asked got a different answer, from a different officer, under different circumstances, and everyone remembers it. Every decision feels personal, because it is personal. And personal decisions, however well-meant, are where perceptions of unfairness take root.

DockOps makes it policy, not personal.

The trouble with discretion

Grace periods exist for good reasons. Work is uneven. Life happens. A local that never gives members breathing room isn't serving them well.

The problem isn't grace periods. It's inconsistency. When grace periods are handled case by case, from memory, by whoever happens to be at the window, three things tend to happen.

First, members get different answers to the same question, and they talk to each other. Second, officers carry the weight of every decision personally, which wears on them and invites second-guessing. Third, there's no clear record, so when someone asks later why a member was or wasn't eligible to work, the answer is fuzzy.

Fairness that depends on who you ask isn't really fairness.

Your rules, applied the same way every time

In DockOps, dues categories, billing periods, arrears and hiring eligibility all follow your local's own rules. Those rules are set up with your local, not imposed from a template.

Grace periods work the same way. Your local defines its grace period policy: who's eligible, for how long, under what conditions. DockOps applies it consistently. The member who asks on Tuesday gets the same treatment as the member who asks on Friday. The first request is handled the same way whether it lands with the president or the newest staff member.

That consistency doesn't make the local less compassionate. It makes compassion predictable.

Members can request it themselves

Here's where the member experience changes. In DockOps, members can see their own dues balances. If they need a grace period, they can request one directly, instead of having to make a trip to the hall and have an awkward conversation at the window.

Eligible first requests can be approved automatically under your local's rules. The member gets a fast, clear answer, and nobody had to make a judgment call that could be second-guessed.

Requests that fall outside the standard policy (a second request, an unusual situation, something that genuinely needs a person's judgment) go to an authorized officer's queue. The officer sees the request with the member's history and decides. Those decisions are recorded too.

That's the balance every local is looking for: routine cases handled fairly and instantly, real exceptions handled by people with the authority and context to decide them.

Every decision on record

Because grace periods run through the system, there's a record of every request, every approval and every exception: who asked, when, what was decided and by whom.

That record protects everyone. Members can see where they stand. Officers can show that decisions followed policy. And when a new officer takes over, they inherit a clear history instead of a set of informal understandings.

Standing visible where it matters

Dues standing matters most at the moments it affects work. In DockOps, a member's standing is connected to check-in and hiring eligibility according to your local's rules. Members know where they stand before they arrive. Dispatchers don't have to make awkward calls. And grace periods, once granted, are reflected automatically.

No surprises at the window. No confusion about whether a member's grace period went through.

One ledger for the whole picture

Grace periods are easier to manage fairly when the full picture is in one place. In DockOps, check-offs, dues charges, payments and strike-fund items sit in the same ledger per member, with history kept.

So when a member asks for time, the officer reviewing it isn't piecing together information from three places. And when dues come in through check-off, they're applied to the same record the grace period lives on.

That's also where reconciliation helps members directly. When check-off records are compared with the local's own records, discrepancies can be caught early and reviewed, before they show up as an arrears problem the member didn't cause.

Taking the weight off officers

There's a human side to this that's easy to overlook. Officers are elected to lead, not to be the sole arbiter of every member's hardship. When grace periods are handled by clear, consistent policy, officers can step out of the uncomfortable middle.

The conversation shifts from "will you give me a break?" to "here's the local's policy, and here's how it applies to you." That's easier for the member and easier for the officer.

Built around how your local handles dues

Every local's dues structure is different, and so is its approach to grace periods. Some are generous, some are strict, most are somewhere in between. DockOps doesn't decide your policy. It's configured around the policy your local already has, and applies it the same way every time.

The shift

The old way: grace periods depend on who you ask and what they remember.

The new way: members request grace periods themselves, eligible requests are handled consistently under the local's own rules, exceptions go to an officer, and every decision is on record.

Fair to members. Fair to officers. Fair every time.

See how DockOps handles dues and grace periods your local's way. Book a demo at dockops.app/book.

— The DockOps Team