---
title: "Execution record and seasons"
description: "Use the API to record what your company committed to, what happened, and the evidence for each outcome."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.sureshake.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Execution record and seasons

An execution record is a dated history of what your company said it would do and what actually happened. Because a commitment is recorded before the work starts, the original stays visible next to the result.

> **Note**
>
> You work with the execution record through the API today. Its screens aren't
> available in the web app. To get started, see the [developer
> quickstart](/developers/quickstart/) and the [API reference](/reference/).

## How it's organized

- **Baseline**: a snapshot of where the company is before the work begins. Once locked, it can't be edited. Mistakes are fixed with corrections, which keep the original.
- **Season**: an operating window, either an eight-week template or a custom range, with a weekly, biweekly or monthly cadence.
- **Commitment**: a specific thing you say you'll do, closed against what actually happened.
- **Goal**: a manual or financial target within a cycle.
- **Weekly review**: a structured look at what was planned and what happened.

## Run a season

1. **Lock your baseline**

   Record and lock your starting point with `/v2/entities/{entityId}
       /execution/baseline`.
2. **Create the season**

   Choose the template or a custom range and your cadence, then activate it.
3. **Make commitments**

   State the outcome and the evidence you'll show. You can run a quality check
   on the wording. Any suggested rewrite stays pending until you accept it.
4. **Attach evidence**

   Add evidence as the work happens. A commitment with no evidence stays
   visibly unsupported.
5. **Close each commitment**

   Close it against the original wording. Edits are kept as versions. A missed
   commitment can be reset, and the reset links back to the miss rather than
   erasing it.
6. **Review and export**

   File reviews as you go. You can export the record as a Markdown report that
   shows original and current targets and the source-linked history.

## How evidence is labeled

Each label describes the support that exists. None of them says a claim is true.

| Label                | What it means                                                     |
| -------------------- | ----------------------------------------------------------------- |
| Source-verified      | Retrieved from an authorized integration                          |
| Artifact-backed      | Supported by an upload or a Sureshake document someone can review |
| Third-party-attested | An identified person stated what they observed                    |
| Self-reported        | Filed by the founder with no attached evidence                    |

An attestation states both what the person observed and what they didn't verify, so a narrow observation isn't mistaken for validation of the whole claim.

When you attach evidence, you choose who can see it: public, follower, capital, diligence or custom.

## Who can see it

Execution access is separate from report access. Giving someone one doesn't give them the other. To control which reports a follower can open, see [Decide who can follow the company](/founders/company-setup/#decide-who-can-follow-the-company).

If you're on the capital marketplace, you can choose which eligible records appear publicly. See [Raise capital](/founders/raising-capital/).

Sureshake doesn't give your company a single execution score. Readers see the underlying record and draw their own conclusions.

Source: https://docs.sureshake.com/founders/execution-record/index.mdx