> For the complete documentation index, see [llms.txt](https://docs.everesteer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.everesteer.ai/scoring/partial-scores-and-resolution.md).

# Partial scores and resolution

Your submitted predictions do not change after the round closes. What changes is the target they are scored against. Partial and resolved are not the same target with a longer window. They are different constructions.

```mermaid
flowchart LR
    Close[Round closes] --> Partial[Partial scores]
    Partial --> Resolved[Resolved score]
    Resolved --> Settle[Settlement]
```

{% columns %}
{% column %}

### Partial

Each later business day realises a longer forward return from that exped. Those raw returns are rank-normalised across the cross-section, not quintile-binned. CORR, AIMC and NCORR then run against that running series.

Partial AIMC uses the benchmark series, not the live crowd. Partial CORR is not CORR against mature `target_everest_20`.
{% endcolumn %}

{% column %}

### Resolved

Once the round is in resolved status, scoring uses the mature quintile-binned `target_everest_20`. That is the round's result. Later partial days do not keep revising it.
{% endcolumn %}
{% endcolumns %}

Several rounds can be in this window at once, each on its own exped. That overlapping book is why a given day can update more than one round.

{% hint style="info" %}
The payout factor freezes on the first **successful** scoring pass (in practice the first partial that actually writes scores). An empty pass, with no realised targets, does not freeze it. Resolution inherits the stored factor. It does not recompute it.
{% endhint %}

Call `explain_scoring` for the live blend. These pages do not publish the horizon length, the weights, or the clip as numbers to copy.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.everesteer.ai/scoring/partial-scores-and-resolution.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.