Funded-bettor evaluation design: rules that measure what you intend

Before setting a target or loss limit, describe what the evaluation is intended to identify. A useful prompt is: a participant qualifies when the program has enough defined evidence that they can demonstrate a particular selection and staking behavior while remaining within stated constraints. The blank should be filled by an operator decision, not by a generic template.

Possible dimensions include price discipline, stake discipline, market diversification, consistency across an observation period, or compliance with concentration limits. None should be described as automatic proof of skill. The evaluation is a commercial and operational filter whose rules determine which records advance.

The thesis also reveals which evidence is missing. If the intended behavior involves repeatability, one isolated result cannot answer the question. If the intended behavior involves stake discipline, a profit target without pre-acceptance stake rules is incomplete.

Every rule needs a name, participant-facing definition, calculation basis, effective time, exact boundary, interaction notes, examples, and owner. Phrases such as daily limit, minimum activity, or allowed odds range remain ambiguous until reset time, qualifying activity, accepted-price basis, and inclusive or exclusive boundaries are stated.

The rule dictionary should cover evaluation and funded stages separately. It becomes the source for participant terms, product configuration, support responses, testing, reporting, and dispute review. If those surfaces use different definitions, the program has a governance problem rather than a copy problem.

Profit measures the change in the simulated ledger over a stated scope. Win rate measures the share of selections graded as wins but does not make records at different prices directly comparable. Return on stake can add context only when the denominator, timeframe, and treatment of pushes and voids are defined. Each metric answers a narrower question than qualified or unqualified.

Price movement can also provide context, but it requires a named comparison source, cutoff, and market-matching rule. It should not be presented as automatic proof of ability or misconduct. A participant record is better reviewed as a combination of settled results, price context, stake sizing, concentration, variance, and rule compliance.

Operators should decide the minimum evidence needed for their proposition without copying a universal count. Minimum graded selections, minimum active days, and market-diversity requirements collect different kinds of evidence and create different participant experiences.

A target depends on settlement finality. A loss boundary interacts with unresolved exposure. Minimum activity depends on how pushes and voids count. An odds restriction depends on which displayed price becomes accepted. A qualification decision depends on open selections, identity state, and correction policy. Testing a rule in isolation misses these dependencies.

Write an explicit precedence rule when conditions collide. For example, reaching a target may create a pending qualification review rather than an immediate pass while selections remain unresolved. A later result can then be applied under the purchased terms without silently reversing a promise the product never should have made.

The staking and exposure guide covers aggregate policy design, while the settlement edge-case guide defines the outcome and correction decisions on which the ledger depends.

Give every evaluation and funded-stage rule set a stable version and effective date. Store the version with the participant record, display it where the participant can retrieve the applicable terms, and retain it after the program changes. An updated marketing page should not rewrite an evaluation already in progress.

Separate a non-material wording clarification from a rule change that alters qualification, loss, activity, settlement, or reward treatment. Material changes should receive product, operations, and legal approval, then pass the same scenario suite as the original version. Old and new versions may need to operate concurrently until every older record has closed.

The pre-launch suite should include a target reached exactly, a loss boundary reached exactly, a target reached with an open selection, several individually valid picks that exceed aggregate exposure, an accepted price on each odds-range boundary, a push or void on the final activity requirement, a postponed event across a reset, and a correction after provisional qualification.

After launch, review pass and failure outcomes by rule version, time and graded selections to decision, breach reasons, stake and market concentration, manual-review reasons, settlement corrections, support contacts, refund reasons, and funded-stage outcomes. These are diagnostic operating measures, not public benchmarks.

The challenge builder can be evaluated against this specification: the objective is one approved rule definition that remains consistent across the participant experience, operational review, and reporting.