> ## Documentation Index
> Fetch the complete documentation index at: https://partner-help.letsdothis.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Timing Inbound
> Choose what your timing provider can write back to an occurrence — bib numbers, check-ins, and bib-pack shipments.
You need permission to edit the event to open the **Timing Inbound** page.
There is no view-only version of the page.
Timing Inbound controls what your timing provider can send back to Let's Do
This for one **occurrence** — a specific dated edition of your event, such as
this year's race. Your timing provider can report three kinds of data:
* **Bib numbers** — the race number assigned to each participant.
* **Check-ins** — when a participant checked in, for example at bib pickup.
* **Bib-pack shipments** — when a participant's bib pack was shipped, with
carrier and tracking details.
For bib numbers and check-ins, you choose an **owner**: either Let's Do This or
your timing provider. The owner is the system allowed to set that value. Data
from a timing provider that doesn't own a value is ignored.
**When to use it:**
* Set up Timing Inbound **before your timing provider starts sending data**.
Anything they send for an occurrence you haven't configured is not applied.
* Hand bib numbers to your timing provider when they assign bibs. Keep them with
Let's Do This when you assign bibs in the dashboard, the check-in app, or by
import.
* Hand check-ins to your timing provider when they run check-in or bib pickup on
their own system. Keep check-ins with Let's Do This when your team uses the
Let's Do This check-in app.
Avoid assigning bib numbers in two places. Once your timing provider owns bib
numbers, any bib they send replaces the number currently on the participant's
record, including one you assigned in Let's Do This.
Timing Inbound works alongside the [mika:timing](/docs/integrations/mika-timing)
integration. mika:timing sends your participant list to mika:timing, and Timing
Inbound controls what comes back.
## Setting up Timing Inbound
Set up each occurrence separately.
In the dashboard, open the event occurrence, then go to **APIs +
Integrations** → **Timing Inbound**.
If the occurrence hasn't been set up yet, a **Not receiving timing data**
warning appears at the top of the page.
The **Ownership** section shows your timing provider next to **Provider**.
Mika is currently the only provider.
Next to **Bib numbers**, choose **Let's Do This** or **Timing provider
(Mika)**. The default is Let's Do This.
If you choose the timing provider, a warning appears under the field to
remind you that bibs they send will overwrite numbers assigned in Let's Do
This.
Next to **Check-in**, choose **Let's Do This** or **Timing provider
(Mika)**. The default is Let's Do This.
If you choose the timing provider, check-in times from their system are
written to participants in this occurrence.
Click **Save**. Some saves open a **Confirm timing configuration** window
that lists what will change:
* The first save for an occurrence always asks you to confirm, even if you
keep both owners set to Let's Do This.
* Handing bib numbers or check-ins to your timing provider always asks you
to confirm.
Click **Save configuration** to apply your changes, or **Cancel** to go back
without saving.
Once you save, the warning at the top of the page is replaced by a note
confirming that the occurrence accepts timing provider data.
To undo edits you haven't saved, click **Discard changes**. The page shows
**Unsaved changes** while you have edits pending.
## Data from your timing provider
| Data | When it's applied | Where you see it |
| - | - | - |
| Bib numbers | Only when your timing provider owns bibs | On the participant's record and everywhere bib numbers appear, such as the check-in app and exports |
| Check-ins | Only when your timing provider owns check-ins | On the participant's record, in check-in reports and exports |
| Bib-pack shipments | Always, once you've saved the occurrence setup | In the participant's **Raceday Info** timeline, marked as reported by your timing provider |
Your timing provider can also remove a bib number. When they do, the number is
cleared from the participant's record.
Every bib change from your timing provider is added to the participant's
**Raceday Info** timeline as made **by the timing provider**, so you can see
where a number came from.
Updates are applied in the order they changed at your timing provider. An
older value never overwrites a newer one, even if it arrives later.
## Changing ownership back
To take a value back from your timing provider, set its owner to **Let's Do
This** and click **Save**. No confirmation is needed. From then on, data your
timing provider sends for that value is ignored.
Handing ownership back doesn't undo anything already applied. Bib numbers and
check-ins your timing provider already wrote stay on participants' records
until you change them.
## Good to know
### Shipments after the first save
Shipment reports can't be turned off once you've saved Timing Inbound for an
occurrence. This is why the first save always asks you to confirm, even with
both owners set to Let's Do This.
### Data sent before setup
If your timing provider sends data for an occurrence you haven't set up, it
isn't applied and isn't held to be applied later. The **Not receiving timing
data** warning on the page tells you when this is the case. Save the setup
before your timing provider starts sending, and ask them to resend anything
they sent earlier.
### Occurrence set up under a different organizer
If an event moved to a different organizer account after Timing Inbound was set
up, saving shows **The configuration was not saved** with the message
`This occurrence is already configured under a different organiser — contact support.`
Contact Let's Do This support to fix this.
### Save errors
If a save fails, the page shows **Something went wrong**. Your changes stay on
the page, so you can click **Save** again.
If the page shows **Saved, but this page is out of date**, your changes were
saved but the page couldn't reload them. Reload the page to see the current
setup.
If the page shows **Couldn't load the timing configuration**, nothing has
changed. Reload the page to try again.