Assignment - Status Flow

Created by Joshua Ort, Modified on Tue, 22 Oct at 9:03 AM by Joshua Ort

This document explains the various states an assignment can be in and how it transitions between these states, as well as how assignments are displayed in the system.


## Core Concepts


### Current vs Non-Current Assignments

- An assignment marked as "current" indicates the official who actively holds the position

- Only one assignment can be "current" for a given position at a time

- When an official is replaced:

  - Their assignment becomes non-current

  - The new official's assignment becomes "current"

- A non-current assignment can be resurrected (made current again) if:

  - There is no other current assignment for that position

  - The assignor chooses to re-release it


### Workspace Visibility

- The assigning workspace displays all current assignments EXCEPT:

  - Assignments with status "removed" (as they were never released)

  - Assignments that have been manually hidden using the "hide" button

- When an assignment is hidden:

  - It is marked as non-current

  - The position appears as open in the workspace

  - This is commonly used for declined or revoked assignments that the assignor no longer wishes to see


### Active States

- **Tentative** - Initial state when an assignment is first created

- **Assigned** - Assignment has been released to an official for acceptance

- **Accepted** - Official has accepted the assignment


### Final States

- **Removed** - Assignment has been removed by the assignor

- **Declined** - Assignment has been declined by the official or by the assignor on behalf of the official

- **Revoked** - Assignment has been revoked by the assignor only


## Status Transitions


### From Tentative Status

- **Tentative → Removed**: Assignor removes the assignment instead of releasing it

- **Tentative → Assigned**: Assignor releases the assignment for official's acceptance


### From Assigned Status

- **Assigned → Accepted**: Official accepts the assignment, or assignor accepts on official's behalf

- **Assigned → Declined**: Official declines the assignment, or assignor declines on official's behalf

- **Assigned → Revoked**: Assignor pulls back the assignment


### From Accepted Status

- **Accepted → Declined**: Official declines the assignment due to changes, or assignor declines on official's behalf

- **Accepted → Revoked**: Assignor pulls back the assignment

- **Accepted → Assigned**: Match details (date, time, site) have changed, requiring reacceptance


## Important Notes

- The system maintains a complete history of all assignments

- Status changes are primarily applicable to current assignments

- Non-current assignments:

  - Are preserved in the system

  - Can be resurrected if there is no current assignment for that position

  - When resurrected:

    - Can become active again

    - Will follow the normal status flow

    - Will become marked as current

- The "Hide" button:

  - Available on the assignment info page

  - Can be used on current assignments that are declined or revoked, and where no other replacement official has been added

  - Marks the assignment as non-current

  - Makes the position appear as open in the assigning workspace

  - Helps manage workspace visibility without losing assignment history

- Assignments will not appear in the assigning workspace if they are:

  - Marked as removed (never released)

  - Manually hidden using the "hide" button

  - Marked as non-current

- Actions by role:

  - **Assignors can**:

    - Remove, release, and revoke assignments

    - Accept or decline on behalf of officials

    - Initiate reassignment due to changes

  - **Officials can**:

    - Accept or decline their own assignments

  - **Note**: Only assignors can revoke assignments; this action cannot be performed by officials




Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article