Who Gets the Next Job? Seniority, Union Rules, and Consistent Flagger Assignments

Two Employees Are Available. Who Must Be Considered First?

A new traffic control job comes in late in the afternoon. Two employees appear to be available, both have worked similar jobs, and either could probably handle the assignment.

The dispatcher chooses the employee who answered quickly last time.

That decision may fill the opening, but it can create a more serious question later: was the work offered according to the company’s established process and, when union employees are involved, the applicable collective-bargaining agreement?

In a busy traffic control office, assignment decisions are rarely based on one factor. Dispatchers may be balancing certifications, classifications, availability, start times, travel distance, customer requirements, seniority, accumulated hours, and recent call-outs. On union work, some of those priorities may be defined by an agreement rather than left to individual judgment.

A dependable process does not guarantee that the same person always gets the next job. It establishes which employees belong in the candidate group, how they should be ordered, when someone may be passed over, and what the office needs to record.

The Agreement Comes Before the Ranking Formula

There is no single seniority rule that applies to every union traffic control company. One agreement may rank employees by original hire date. Another may use accumulated work hours, a rotation list, or separate rules for different classifications. The agreement may also define tie-breakers, reset periods, response windows, permissible pass-over reasons, and how missed opportunities are handled.

That means “use seniority” is not a complete dispatch policy.

Before configuring a ranking system or writing an internal procedure, the company must identify what its own agreement requires. The software should be configured around that process; the process should not be invented around whatever setting happens to be easiest.

The office should be able to answer questions such as:

• Which employees are covered by the agreement?
• Are there separate lists for flaggers, traffic control supervisors, drivers, or other classifications?
• Is seniority based on hire date, accumulated hours, or another defined measure?
• Does the agreement require work to be offered in rank order?
• How long does an employee have to accept or decline an assignment?
• What happens when an employee does not respond?
• Which job requirements allow the dispatcher to move past a higher-ranked employee?
• How are refusals, pass-overs, and exceptions documented?
• When do accumulated hours or rotation totals reset?
• What is the tie-breaker when two employees have the same value?

Those answers belong in the company’s operating procedure. If the agreement is unclear, the company should resolve that question with the appropriate union representative or labor advisor rather than leaving each dispatcher to interpret it differently.

Start With the Correct Employee Group

Seniority only works when it is applied to the right group of employees.

The first step is to identify the work being assigned. Is it union or non-union? Which employee classification applies? Does the job require a flagger, a traffic control supervisor, a driver, or someone with a specific customer or agency qualification?

From there, determine which employees belong in the applicable group. A non-union employee should not be mixed into a union seniority list merely because both employees can perform similar work. Likewise, a flagger’s position on one list may not determine priority for work assigned under another classification.

Separating the groups before ranking prevents a common mistake: producing one company-wide list that looks orderly but does not reflect the rules governing the actual assignment.

Separate Eligibility From Seniority

Once the correct group is identified, determine who is eligible for that particular job.

Eligibility may include:

• Availability for the required date and time
• The correct employee classification
• Current certifications or customer-required qualifications
• No conflicting assignment or approved time off
• Any geographic, branch, or travel conditions recognized by the company’s rules
• Other requirements permitted by the applicable agreement

Seniority then determines the order within that eligible group.

This distinction matters. The highest-ranked employee may not hold a certification required for a particular job. Passing over that employee for a documented qualification requirement is different from ignoring the seniority list because another employee is easier to reach.

The dispatcher should be able to show both parts of the decision: why an employee was or was not eligible and how the eligible employees were ordered.

Understand What the Ranking Number Represents

A ranking is only as trustworthy as the information behind it.

If the agreement uses hire date, the company needs accurate hire dates and a defined rule for breaks in service, rehires, or employees sharing the same date. If it uses accumulated hours, the office needs a reliable process for entering hours, deciding which hours count, applying the correct measurement period, and handling corrections.

An hours-based ranking can change as employees work. That may help distribute opportunities, but only if updates happen consistently. Entering one employee’s hours late—or counting scheduled hours for one employee and completed hours for another—can change the order unfairly.

The company should define:

1. Where the ranking data comes from.
2. Who is responsible for updating it.
3. When updates take effect.
4. How errors are corrected.
5. When the ranking period resets, if applicable.
6. How ties are resolved.

The seniority list should be a shared operational record, not a number that changes without explanation.

Follow the Required Offer Order

For agreements that require assignments to be offered by seniority, the list is not merely a suggestion. The dispatcher starts with the highest-ranked eligible employee and follows the defined sequence.

If that employee accepts, the assignment can move into the company’s normal dispatch process. If the employee declines, does not respond within the allowed period, or cannot take the job for a recognized reason, the dispatcher moves to the next eligible employee and preserves the result.

A useful record may include:

• The job or opening being filled
• The ranking list used
• When the assignment was offered
• Whether the employee accepted, declined, or did not respond
• Why an employee was ineligible or passed over
• Who approved an exception, when approval was required
• Who ultimately received the assignment

The exact record depends on the company’s agreement and procedures. The important point is that the office can reconstruct what happened without relying on someone’s memory or a private text-message thread.

Do Not Let Response Speed Quietly Replace Seniority

An employee who normally responds quickly may be easier to dispatch than someone who leaves messages unanswered. Confirmation history can be useful operational information, but it should not silently replace a required union ranking method.

If the agreement gives an employee a defined response window, the dispatcher should follow that window. If the agreement permits the company to move on after a nonresponse, the office should record that result and continue in the required order.

The same caution applies to customer preference, travel convenience, and familiarity with a jobsite. Those factors may be legitimate in some situations, but the company should know whether its agreement permits them to override the normal order. Convenience alone should not become an unwritten seniority rule.

Treat Pass-Overs as Decisions That Need Context

Traffic control work will always produce exceptions. A last-minute call-out may leave only one practical replacement. A job may require a qualification held by only a few employees. A customer restriction or timing problem may remove someone from consideration.

The goal is not to eliminate dispatcher judgment. It is to make the reason visible.

A short exception record should answer:

• Which normal rule would have applied?
• Why could it not be followed?
• Was the reason allowed under the agreement or company procedure?
• Who made or approved the decision?

This does not need to become a lengthy incident report. A concise, factual note is more useful than no record at all.

Recurring exceptions deserve attention. If the same employee is repeatedly passed over for the same reason, the company may have an underlying certification, availability, communication, or policy problem. Reviewing those patterns can prevent a series of one-off decisions from becoming an unofficial practice.

Keep Union and Non-Union Processes Separate

A traffic control company may perform union, prevailing-wage, and private work during the same week. The same dispatcher may be filling positions from more than one employee group, each with different rules.

Non-union assignments may use hire date, experience, confirmation history, or another company-defined priority. Union assignments may need to follow a specific hours-based or tenure-based sequence. Combining those approaches into one list makes it easy to apply the wrong standard to the wrong job.

The scheduling process should clearly identify:

• The job type and applicable employee group
• The ranking method used for that group
• The eligible employees in the resulting order
• Any documented exception to that order

This separation helps dispatchers move quickly without expecting them to remember every rule from scratch.

How FlaggerLink Supports Union Seniority Workflows

FlaggerLink allows union and non-union employee classifications to use different ranking strategies. Depending on the company’s rules, employees can be ranked by hire date, accumulated hours, experience level, text confirmation rate, or combinations such as hours with hire date as the tiebreaker.

For companies whose union process uses accumulated hours, Rank Hours provides a place to maintain those totals for seniority-based scheduling. Rankings recalculate daily, and an authorized user can trigger a recalculation when a legitimate correction needs to take effect. Seniority Roster reports give the office a consistent view of the resulting order.

Manual rank pinning can also be enabled when a company has an approved reason to hold a specific position. Because a pinned position overrides the calculated result, it should be used only when the company’s agreement and internal procedures allow it. FlaggerLink identifies who set the pinned rank so the change does not become an unexplained adjustment.

FlaggerLink does not interpret a collective-bargaining agreement, decide whether an exception is permitted, or guarantee compliance. The company remains responsible for choosing the appropriate strategy, maintaining accurate employee and hour information, and applying its agreement.

The value of the system is operational consistency. The ranking stays alongside the employee, availability, certification, conflict, and scheduling information the dispatcher already uses. Instead of rebuilding a seniority list in a spreadsheet—or choosing from memory—the office has a repeatable starting point for each assignment.

Build a Process You Can Explain

A strong assignment process should be understandable before a disagreement occurs.

Start with the agreement or company policy that applies to the work. Identify the correct employee classification. Filter for availability and legitimate job requirements. Apply the required seniority method. Follow the offer order, document outcomes, and preserve the reason for any exception.

That structure protects more than the seniority list. It gives dispatchers clearer instructions, gives managers a record they can review, and gives employees a process the company can explain consistently.

Traffic control scheduling will always require judgment. Jobs change, employees call out, and customers create conditions a ranking formula cannot anticipate. The goal is not to make the dispatcher irrelevant. It is to place that judgment inside the union requirements and operating rules that govern the work.

When the ranking method, eligibility rules, offer sequence, and exceptions are all visible, “Who gets the next job?” becomes a decision the company can support—not a guessing game.