← Back to home

Finding a race: the calendar, its entries, and proposing an event that is missing

Updated on 2026-10-30

For:Musher guide

What you will do

Find a race on the public calendar (/evenements), read when to enter each class, put it in your Plan with “I want to take part”, say you have entered with the organiser, follow your race path for the season — and, if a race is not there, propose it: one by one, or a whole season as a file.

What you need

  • Nothing to read: the calendar and a race's page open without an account.
  • An account and a kennel for “I want to take part”; only the kennel owner puts the race in the Plan and ticks “I've entered with the organiser”.
  • A MushMate account (free, no kennel required) to propose an event. Having a text or a PDF read by AI needs a full-access account.

Step by step

Finding the race

  1. Open the calendar: /evenements on the website, or Manage › Organization › Events on the phone. Upcoming events, then those of the last six months, sorted by month; at the top, the “Entries in the next 14 days” strip.
  2. Filter: the search (“Search for a race, a place, an organiser…”), then Country, From / To (months), Terrain (“All”, “Snow”, “Dry land”) and Discipline, and “Filter”. The filters are written into the address: a copied link opens the same list. An empty list offers “Widen to the neighbouring months”.
  3. Read the map: each event at its place, “Snow” or “Dry land”; “Trail of an edition” when MushMate has the route; “Off the map” for an event with no position. “With MushMate” marks a race that has a partner code.
  4. Open a race's page (/evenements/<name>): its days, its total km and its elevation gain, then “Entries” — one card per class: its state written next to the husky (“Not open yet”, “Open”, “Closing soon”, “Late entry”, “Waiting list”, “Full”, “Closed”…) and the next action (“Enter before …”, with the next fee step); Opens, Closes “before …”, Late entry, Fees; “Checked on …” or “Not checked”; “Enter the race ↗”. Times are local to the place; a date that isn't certain says “to be confirmed” or “announced”. Further down: “Stages”, “Editions and trails” and “With the organiser” (“Enter the race”, “Rules”, the organiser's website).

Putting it in your Plan

  1. “I want to take part”: pick “Your class” if there are several. Without an account, you create yours (“Create my account”), then your kennel, and you come back to the race; signed in, the objective form opens pre-filled (the race, the start day of the class). Nothing is created before you confirm. A class that is closed, cancelled or over, or that has no race in the catalogue, is not offered. “I have a code” opens the partner-code entry when the race has one.
  2. “I've entered with the organiser”: once the race is “In your Plan”, its class card carries this box. Tick it when you have entered on the organiser's website; the class state becomes “Entered with the organiser · starts …”.
  3. Follow your race path: signed in, the calendar shows “Your race path” — your races of the season linked on the map by an ink line, in date order, “Next step · n” and its next action, then the numbered list. “Hide” removes it, “Show your race path on the map” brings it back. “My itinerary” opens the season page (/plan/itineraire), private until the owner turns on “Make the page public”.

An event is missing? Propose it

  1. At the bottom of the calendar, “Is an event missing?”: “Propose an event” (“Sign in to propose” without a session). Fill in the six fields: “Event name” (without the year), “Start”, “End” (or tick “Dates to be confirmed”), “Place”, “Country”, and the “Organiser's website or registration page” (https://). Optional: “Terrain”, “Disciplines”, “A line for the admin” (140 characters).
  2. Answer the duplicates, shown while you type (from three letters of the name, or the start and the country):
    • “This looks like an event already on the calendar” blocks sending until you answer: “It's the same one (propose a correction)” or “No, it's a different one” (“Change my mind” to go back);
    • “To check” (the same days in the same country) blocks nothing;
    • “Already proposed, waiting for an admin”: if it is the same one, no need to send it.
  3. “Send the proposal”: while something is missing, the button is inactive and says what. Once sent: “Thank you — an admin checks before publishing”.
  4. Correcting an existing event: “It's the same one (propose a correction)” opens its page “On the calendar today” (the name, the country and the terrain stay with the admin) and “What you can correct”: the dates, “Dates to be confirmed”, the place, the link, “The event is cancelled”. “What changes (n)” updates as you go; “Send the correction”.
  5. Follow the decision in “My proposals” (/evenements/mes-propositions, also under the box: “My proposals · n pending, m decisions to read”): “Pending”, “Published”, “Applied”, “In part” (what was taken, and what was not), “Refused” (the admin's reason, word for word) or “Withdrawn”. “Withdraw” a pending proposal; “See the event page” for a published one. An unread decision carries “New”. An email tells you of each decision.

A whole season: proposing a file

  1. “or as a file” under “Propose an event” (or “Several events? Propose a file” at the top of the form): drop a CSV, an Excel (.xlsx) or the import JSON — read in your browser, without AI, for every account. A PDF or a pasted text (“Or paste a text ›”) is read by AI, for full-access accounts only. “CSV template” and “Excel template” give the columns; your own headers work too (“Race”, “From”, “Town”, “Link”…).
  2. “Check the table before sending”: one row per event, each with its state — “Ready”, “Correction ready”, “To complete”, “Looks like”, “To check”. A cell says “missing”, “invalid”, “corrected” or, when read by AI, “to check”. Correct in the table, “Remove” a row, answer each “Looks like” as in the form; two rows of the file for the same event: “Keep both” or remove one.
  3. Rows set aside (“Rows set aside (n)”) each say why: “Already over.”, “This country is not (yet) on the calendar.”, “Already on the calendar, unchanged.”, a row identical to another; “Put back” one you removed.
  4. 50 rows per batch: beyond that, “Download these n rows (CSV)” keeps the rest for a second file. Then “Send the n proposals”.
  5. The batch in “My proposals”: a single entry (“File … · n rows”), its tally and its state (“In progress”, “Decided”, “Withdrawn”); “See the n rows” unfolds each row with its decision; “Withdraw the batch” withdraws the rows still pending. A single email sums up the batch when its last row is decided.

On the phone

  1. Manage › Organization › Events: the list, its search, “Filters” and the map; a race's page, “I want to take part” (“Which class?”), “I've entered with the organiser” and “Your race path”. On iPhone, a partner code is typed in on the website (“The code is typed in on the website”).
  2. At the bottom of Events, “Missing an event?”: “Propose an event” (the same six fields, the same duplicates) and “My proposals”, which also reads your batches (“See the n rows”, “Withdraw” a pending row). Both need a connection. A file is dropped on the website: the “Propose from a file” row of “My proposals” opens it there.

What you should see

  • One card per class on a race's page, with its entry dates written out, never a colour alone.
  • Signed in, on the list: “Enrolled” (your kennel typed the event's code), “In your Plan”, “Entered with the organiser”, and your clubs' outings.
  • After sending: the proposal (or each row of the batch) “Pending” in “My proposals”, and nothing new on the calendar until an admin has decided.

What others see

  • The calendar is public and shows no entrant.
  • Your race path stays with your kennel, and the coach or expert you invited. “My itinerary”, made public by its link, shows your races, their dates and places and the ones you took part in — never a time, a rank, your dogs or your tracks.
  • Your name never appears on the calendar for an event you proposed. “My proposals”, and the name of a dropped file, are visible to you only.

What it does not do

  • MushMate does not enter you with the organiser and does not check “I've entered with the organiser”: it is your declaration.
  • “Enrolled” is not “entered with the organiser”: the first says your kennel typed the event's code (Club and leaderboard), the second is the box you tick.
  • Nothing is published without an admin: they publish, correct the existing event or refuse with a reason. Classes, registration dates, fees and the position on the map stay with the admin — write what you know in the line for them.
  • At most 10 pending proposals per account; a batch counts as one.
  • The file is not kept: only the rows you send are. Reloading the table starts again from the file.
  • No file drop on the phone: the review table stays on the website.

If something goes wrong

  • “Send the proposal” stays inactive: the sentence under the button says what is missing, or which “looks like” to answer.
  • “You have 10 pending proposals”: wait for a decision, or withdraw one in “My proposals”.
  • “Reading a text or a PDF is reserved for full-access accounts”, or today's AI readings are used up: drop a CSV, an Excel file or the template.
  • “.xls and .ods files are not read”: save it as .xlsx or CSV.
  • “I want to take part” does not appear: the class is closed, cancelled or over, it has no race in the catalogue, or your role does not write objectives (the owner does).

Going further

Mushmate n’utilise que des cookies strictement nécessaires et fonctionnels (session et préférence de langue) — aucun traceur publicitaire. La mesure d’audience du site (Umami) se fait sans cookie.