Priority-Based Admission

Admit candidates at a boundary by an explicit priority policy so scarce capacity is reserved for higher-priority flows.

The Diagnostic Story

Symptom: Not everyone who wants in can be admitted, but the system is letting in candidates based on arrival order, loudness, or informal pressure rather than on who most needs or warrants the scarce capacity. Critical cases wait while lower-priority ones fill the slots. Decisions feel arbitrary because no one can articulate the criteria. Powerful actors capture capacity that should go elsewhere.

Pivot: Name the priority-relevant attributes explicitly and apply them at the admission boundary. Classify candidates by those criteria, admit the higher-priority cases, and give lower-priority candidates defined alternative handling: deferral, queuing, rerouting, or a clear rejection with appeal path. The criteria must be auditable and correctable.

Resolution: Scarce capacity is reserved for the candidates that warrant it under an explicit, defensible rule. Classification errors can be reviewed and corrected, and lower-priority candidates receive defined paths rather than invisible exclusion. The policy is monitored for gaming, bias, starvation, and drift from the actual system goal.

Reach for this when you hear…

[incident response] “We stopped handling alerts by whoever complained loudest and started routing by severity score, and the critical incidents finally stopped sitting behind false alarms.”

[emergency department] “Triage exists because equal first-come-first-served would let someone die of a heart attack while a broken finger gets treated first.”

[cloud compute scheduler] “If we do not reserve capacity for the critical workloads explicitly, a batch job that someone forgot to tag will starve the production pipeline.”

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (8)

• Admission Control
• Boundary: Defines system limits.
• Classification: Sorting entities into discrete categories by explicit rules, turning unbounded variation into a finite, reusable map for downstream reasoning and action.
• Fairness Policy
• Prioritization: Ordering competing claims on finite resources by a value or urgency metric to produce a ranked sequence of action under constraint, making explicit what gets done first and what does not get done at all.
• Resource Management: Allocation of finite assets.
• Review Or Appeal Path
• Threshold: Safe vs harmful levels.

Also references 11 related abstractions

• Accountability: Responsibility for actions.
• Constraint: Limits possibilities to guide outcomes.
• Equity: Context-sensitive fairness.
• Flow: Structured movement of energy, matter, or information.
• Legitimacy: Accepted authority.
• Observability: Infer internal state externally.
• Procedural Fairness (Due Process): Due process.
• Queueing: Organizes tasks into a waiting line based on arrival and service rates.
• Scheduling: Organizing tasks over time.
• Trade-offs: Balancing competing priorities.

▸ Show 1 more

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Triaged Admission · governance variant · recognized

Admit or serve requests according to urgency, need, risk, or priority classification.