Seniority & bumping playbook

Before you open a bumping file

Posting disputes, layoff bumps, and classification grievances share vocabulary but not the same procedure. Run this gate so the committee does not debate the wrong problem.

• Is this a layoff or displacement bump?. A bumping file applies when the CA lets a displaced member claim a lower or lateral role by seniority during a layoff or restructuring. You need a vacancy chain, not just “I wanted that posting.”
• Is this only a posting complaint?. If the issue is whether a vacancy was posted correctly or qualifications were applied fairly, start with posting articles and may be a grievance — not a seniority committee ranking session.
• Already filed as a grievance?. If a formal grievance is live on the same facts, coordinate with the steward handling it. Do not let the committee pre-judge an outcome the grievance path owns.
• Does the CA require a committee?. Some collections require a seniority committee vote; others are steward-led with employer notice. Confirm who chairs, who records, and what happens if the committee cannot agree.

Worked example: two members, one target role

Role “Facilities Coordinator” is eliminated. Member A and Member B both claim bump into posted “Maintenance Clerk.” Write dates before anyone argues qualifications.

• Set up the sheet. Two rows only: Member A and Member B. Columns for seniority date, classification, current role, and target role. No names from other campuses yet.
• Enter sample dates. Member A — seniority 2014-03-12, Maintenance Lead. Member B — seniority 2016-09-01, Facilities Coordinator (eliminated). Target: Maintenance Clerk (posted 2026-02-01).
• Confirm which clock the CA uses. Open the CA: is this continuous service, classification seniority, or another date? If B's elimination triggers bumping rights, note the article before comparing.
• Break ties on paper. If dates tie, write the CA tie-break (hire number, draw, hours in classification). Do not assume “longer in the building” wins without the article.
• Then check qualifications. Only after seniority order is drafted, mark Yes, No, or Unknown on ability, licensing, and posting eligibility. A more senior member who fails ability may not hold the bump.

Worked example: two-person chain

One vacancy, one bumper, one displaced incumbent. Map this before calling a three-deep scenario.

• Start with the vacancy. Maintenance Clerk posted and filled — then the layoff removes Facilities Coordinator (Member B). The bump target is the clerk role Member B wants.
• Name the bumper. Member B (2016-09-01) claims bump into Maintenance Clerk. Confirm B is in the right classification and meets ability language.
• Name who gets displaced. Member C (2019-11-15) currently holds Maintenance Clerk — the incumbent B would displace. C may have their own bump rights into another posted role.
• Mark the floor. If C cannot bump further — probation, temporary status, or CA floor — write “chain ends at C” on the worksheet. Stop inventing extra steps.
• Log the step. Committee log line: “B bumps to Clerk, displacing C — articles cited, next meeting date if C claims further bump.”

Worked example: Members A, B, and C

Role X vacant, Role Y posted. A three-deep chain displaces two incumbents. Map every hop before anyone signs.

• Vacancy at Role X. Lab Technician II (Role X) is eliminated in a layoff. The posted replacement path runs through Role Y (Lab Technician I).
• Member A — first bumper. Member A (2013-06-01, Lab Tech I) is most senior eligible and claims bump into Role X. A meets classification and ability for X.
• Member B — displaced incumbent. Member B (2015-02-14) held Role X and bumps into posted Role Y (Lab Tech I) if seniority and classification allow.
• Member C — last link. Member C (2018-10-30) holds Role Y. Confirm whether C can bump into a posted Role Z or hits a CA floor (probation, temp, or classification boundary).
• Worksheet one row per hop. Rows: A → X, B → Y, C → ? Mark “chain ends here” beside C if no further bump. Alternate candidates get a blank row — not a side debate.

How to run the seniority committee

A disciplined meeting beats a long argument. Use the worksheet as the agenda — not as decoration.

• Open with the CA articles. Chair reads the layoff, bumping, and committee articles aloud. Note which collection (FT/PT/support) applies before any names.
• Project or pass the worksheet. Every person in the chain gets a row. Stewards fill dates; members confirm or challenge with documents — not memory.
• Resolve one chain at a time. Finish Role X → Y → Z before opening a second vacancy. Mixing chains on one sheet causes transposed dates.
• Vote on facts, then outcome. First agree seniority order and eligibility flags. Then vote the bump outcome. Dissents go in the log with the member's name and reason.
• Minutes = worksheet + decision. Attach the completed worksheet (or Hub export) to minutes: date, chair, attendees, articles cited, and “chain ends at Member C.”
• File one copy in the case. Steward keeps the signed worksheet in the bumping file and links the Officer Hub case ID if your local uses College Bumping.

Common pitfalls

Most committee errors come from mixing clocks or ignoring boundaries the CA already defines.

• Posting date vs. seniority date. A vacancy posted 2026-02-01 is not someone's seniority. Do not rank members by posting date.
• Classification boundaries. FT/PT or support-staff collections may not bump across freely. Confirm the collection before ranking.
• Probationary or temporary status. Confirm bumping rights before ranking someone. Probation and temp status often block bumps entirely.
• “Earlier date always wins”. Read tie-break and ability language. Seniority order is necessary — not always sufficient.

Paper worksheet (print or export)

Use this column layout on a blank page, spreadsheet, or branded export during the meeting. Keep one signed copy in the case file.

• Columns. Member ref · Seniority date · Classification · Current position · Target / bump claim · Eligible? (Y/N/?) · Notes / CA article
• Rows. One per person in the chain, plus a blank row for alternate candidates. Mark “chain ends here” when the CA blocks another bump.
• Footer. Session date, chair, decision summary, and Officer Hub bumping case ID if your local uses one.

Opens Document Generator with a blank branded seniority grid ready to export.