DEFINITION
Qualification is the process between candidate selection and licensed publication.
A qualified pick is a candidate selection that has been connected to a known event and market, evaluated inside the relevant sport workflow, checked for required publishing fields, and admitted to a customer delivery mode under the active licence.
Qualification does not mean certainty. Sports outcomes are inherently uncertain, and no probability, confidence score, or rationale can guarantee a result. The purpose of the process is to improve record discipline and publishing usability—not to remove risk from the underlying event.
This distinction is important for enterprise buyers. A prediction system can generate a large number of candidate outcomes. A publishing feed should expose only records that meet its operating contract and should remain understandable after they leave the source workflow.
QUALIFICATION PIPELINE
Six stages shape an enterprise-ready sports pick.
- 01
Identify the publishing unit
Every candidate must resolve to the right fixture, fight card, tennis match, or golf tournament. Participants, competition, scheduled time, and sport-specific unit are normalized before a downstream record is created.
- 02
Evaluate candidate selections
Candidate team picks, match picks, player props, fighter selections, or tournament selections are evaluated within the relevant sport workflow. The system does not force every possible market into the feed.
- 03
Apply quality gates
A candidate must satisfy the required identity, timing, confidence, market, field-completeness, and licence conditions for its delivery mode. If a required condition is unavailable, the candidate can be withheld.
- 04
Normalize the contract
Accepted records are expressed through a stable enterprise contract: event identity, market, selection, confidence or probability, rationale, timestamps, status, attribution, and other licensed fields.
- 05
Control delivery
The active licence determines which sports, competitions, territories, channels, fields, and delivery routes are available to a customer credential or partner workspace.
- 06
Maintain lifecycle state
Records are not treated as permanent snapshots. Their status can reflect upcoming, withdrawn, void, settled, or other supported lifecycle conditions so downstream teams can respond consistently.
The exact sport workflow varies. Soccer can include team selections and player props per fixture. Basketball, hockey, American football, baseball, and college packages have their own team and player structures. UFC uses fight and fighter selections; tennis uses match selections; golf uses tournament selections. The coverage index documents the target output for each package.
QUALITY GATES
A healthy feed can return fewer records than the target.
Target output describes the intended product shape, not a promise to fill every slot regardless of quality or availability. Schedule, source state, market availability, model quality, and licence scope can all affect what is delivered.
- The event or participant identity cannot be resolved reliably.
- The required market or schedule state is unavailable.
- A sport-specific quality threshold is not satisfied.
- A required publishing field is missing or inconsistent.
- The record falls outside the active licence or delivery entitlement.
- The selection is no longer suitable for active publication.
CONFIDENCE AND CONTEXT
Confidence is a model output, not a promise of the final score.
Confidence or probability should be interpreted inside the complete record. The event, market, selection, evaluation time, supporting rationale, and lifecycle state all matter. Comparing confidence values across unrelated sports or markets without that context can be misleading.
A customer should also decide how confidence appears on its own surface. Editorial prose, visual labels, member dashboards, and broadcast graphics have different space and disclosure needs. The publishing context layer is designed to help downstream teams express the record without changing its underlying meaning.
CUSTOMER OPERATIONS
Delivery governance continues after the API response.
PowerHouse governs the record and entitlement at delivery. The customer remains responsible for how the record is integrated, displayed, reviewed, and maintained inside its own product.
Confirm the intended channel
Use the record only on the products, territories, and channels included in the active agreement.
Respect record state
Do not continue presenting a withdrawn, void, or otherwise inactive record as a current selection.
Preserve required attribution
Apply the agreed source and brand attribution wherever the licence or delivery contract requires it.
Apply responsible-gambling controls
Maintain the age gating, disclosures, and responsible-gambling requirements that apply to the customer product and territory.
For the commercial boundaries around these operations, review the sports picks data licensing guide and the product governance overview.