Description
Compare supplied priorities, using largerPriorityFirst to orient their difference.
Administrative workflow summaries depend on capacity, counted waiting, uncertain time envelopes, priority policies and delegated or retention intervals. A local predicate or deadline arithmetic does not establish a lawful fee, signature, retention decision or fair service priority. Boundary and denominator policies must be explicit.
Compare supplied priorities, using largerPriorityFirst to orient their difference.
When to use this tool
Use Appointment Queue Priority Tie Rule when checking the stated administrative count, timing, priority or policy-boundary convention.
How to use the tool and how it works
- Enter firstPriority, secondPriority, firstArrival, secondArrival, largerPriorityFirst. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read order, priorityTie. Inspect priorityTie before interpreting the associated values.
Compare supplied priorities, using largerPriorityFirst to orient their difference. On equal priorities, compare arrival times. Return -1 when first precedes second, +1 when second precedes first, and zero on a complete tie.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| firstPriority | First Priority | Required. Finite number. |
| secondPriority | Second Priority | Required. Finite number. |
| firstArrival | First Arrival | Required. Finite number. |
| secondArrival | Second Arrival | Required. Finite number. |
| largerPriorityFirst | Larger Priority First | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| order | -1 first precedes second, +1 second precedes first, 0 complete tie; no full queue is sorted. | Required. Safe integer. |
| priorityTie | Priority Tie | Required. Boolean. |
{
"input": {
"firstPriority": 2,
"secondPriority": 1,
"firstArrival": 20,
"secondArrival": 10,
"largerPriorityFirst": true
},
"output": {
"order": -1,
"priorityTie": false
}
}Limitations and assumptions
- Only a pair is compared; the tool does not implement a full queue, choose an appropriate priority policy or establish fair access.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Review verified records and the governing organizational/legal requirements with responsible professionals for actual service, authority or retention decisions.
References
Similar or alternative tools
- Workflow Reentry Loop Count
Track previously seen state tokens.
- Public Counter Appointment Utilization Term
Utilization fractions divide by available slots; noShowFraction divides booked-attended by booked.