What's New

The same leak, on the three other pages that had it: your Out Here link, and both unsubscribe pages.

• Yesterday's fix took your crew link out of the crew page's own head markup. The page your people open to follow you live had the identical problem, and worse: it published your link three times, not twice. The third one was the banner that offers to open the app, which carried the whole address as its argument.
• All three tags are gone from that page. The canonical link and the share URL now point at the page that describes Out Here, which is public and carries nothing about you. Tapping your link on an iPhone still opens the app straight to your session, because that has always been handled by the link itself rather than by anything printed on the page.
• The unsubscribe pages had it too. That link is a different kind of key: it names one person's account, and an unsubscribe address is about the most forwarded and most machine-fetched address a product has. Both pages now name navrun.app and nothing else. There is no public version of "you are about to stop these emails", so they point at the site rather than borrow some other page's subject.
• The check that catches this reads the rendered page and sweeps every tag in its head, so the next tag to carry a link fails it the day it is written. That is how the third tag on the Out Here page was found.

The crew page was printing its own address, token and all, into the tags that get copied when a page is shared or saved.

• The link you hand your crew is the whole key to your live position and the notes they keep on your race. The page carried that full address twice in its own head markup: once as the canonical link, once as the Open Graph URL, which exists so that other services can copy it and republish it.
• Crawlers were already told to stay away, by header and in robots.txt. That covers a search engine that asks first. It does not cover a page saved to somebody's phone, a copy mailed on, or anything that reads the markup rather than obeying a header.
• Both tags now point at the public NavRun Crew page. Nothing in the head of your crew page carries your link any more. The page works exactly as it did, and a test now reads the rendered page and fails if any tag in the head ever carries the token again.
• The machine-readable description of the API the iOS app talks to had fallen behind the code, so the plan-sharing routes were missing from it. It has been regenerated from the running app.

The "Copied." confirmation on your crew link was always showing, so it never told you anything. And the cutoff line said "25m", which reads as metres on a page of miles.

• On the page where you hand your crew the address to follow you, the word "Copied." sat there from the moment the page opened, before you had pressed anything. It never appeared and never went away, so it could not tell you whether the copy had worked. On the one action where getting it wrong means sending somebody a link that is not the link, that is worse than having no confirmation at all.
• It is hidden now until you press Copy link, then it shows for four seconds and goes. If it says Copied, the address is on your clipboard.
• The room before a cutoff was written as "25m". Every other number on that page is miles, so the one number that is not miles was the one written like it might be. Your crew were reading a time as a distance. It says "25 minutes" now, and "1 hour 30 minutes", in words that cannot be taken for anything else.
• When that room gets short, the line used to open with "Cutting it closer". The person reading it is standing in a car park and cannot run a step of it for you, so there is nothing for them to do with being leaned on. It states the room and where it counted from, and leaves it there. The number is allowed to be small. The sentence is not going to make anything of it.

A brand new account could not open its own training plans. The page you signed up for said it did not exist.

• Making an account got you as far as the front door and no further. Activities and training plans both answered with a missing page, because the app decides who sees the running side by watching for your first run or your first connected account, and a minute-old account has neither. The link was right there in the sidebar, and it went nowhere.
• Both pages open now from the moment the account exists. Nothing has to be connected first. If you came here to see what a plan looks like before you hand over anything, you can.
• There is a plan waiting for a runner with no history at all: eight weeks of run and walk, built without needing a single mile of data. That is the whole point of it, and it was sitting behind a page that claimed not to exist.
• Nothing is decided about you at the door. Opening a page marks nothing down. People who make an account to follow somebody else's race still get the crew side and not a runner's screens, and that is still decided by what a runner shares with them, not by what we assume the day they sign up.

The other way of taking a crew link back had the same gap. Both are closed now.

• There are two places a link can be taken back: the crew link on your race, and the list of people you have shared a plan with. Taking one back from that second list stopped the connection their app reads your plan through, and left the page showing your position on the course still open. Someone holding the address could keep watching where you were.
• Taking a link back now closes everything that address reaches, from either place. The page, the position on it, and the plan behind it stop together.
• Sharing your plan with somebody new never touches a link you already have out. Taking one person's access away leaves everyone else's exactly as it was.
• If you shared a plan with somebody who never had a page, taking it back still works the way it reads. There was nothing to close on that side and it does not go looking for one.

Your activities and your training plans went missing if your account is older than yesterday. They are back, and nothing of yours was ever deleted.

• A change we shipped yesterday started asking every account a question before it opened the activities or training plans pages: does this account run? Accounts created from now on answer it when they connect Strava or Apple Health. Accounts that already existed were never asked, so the answer came back empty and both pages said the page did not exist. Years of synced runs, sitting right where you left them, behind a page that claimed to be nothing.
• Every account that has ever run, planned, entered a race or connected Strava has now been answered for, in one pass. If that is you, the pages are back with everything on them.
• Where we could not tell, we said yes. An account we get wrong in that direction sees a page it may not use. An account we get wrong the other way cannot reach its own history, and that is not a trade worth making.
• The pages ask again themselves now. If an account arrives without an answer and its own runs, plans or races say it trains, it is let through on the spot rather than shown a missing page.
• Accounts here to follow somebody else's race are unchanged: crew still see the crew side, and still do not get a runner's screens.

Withdrawing a crew link from the app left one half of it still working. It does not any more.

• When you withdrew a link from the iPhone app, the page your crew opens stopped opening. That is the half you can check, so the link looked withdrawn. The same address kept working in the other half: the connection your crew's app reads your plan through. Someone still holding that address could read your plan there, and change it if you had given the link that.
• Withdraw now closes both halves in the same press, whether you press it in the app or in a browser. The address stops working everywhere at once.
• Creating a link from the app opens both halves too, so a link made on your phone and a link made on your laptop are the same link with the same reach.
• If you take a link back and make a new one, the new one has a different address and the one you took back stays closed. That holds now however you took it back.

You can now set up your crew link from a browser. Until today it only existed inside the iPhone app.

• The link your crew opens on race day could only be created, read, or withdrawn from the app. If you were on a laptop the night before a race, there was no way to reach it at all.
• It now lives on your race strategy page, in the race day section, as Share with your crew. From there you create the link, see the full address, and copy it in one click.
• You choose what the address can do before you send it. Read only means they can see where you are, your plan, your aid station times and the notes you wrote for them. Read and write also lets them edit your race notes, your per mile notes and your race day checklist from their phone. You can move it either way afterwards.
• Withdrawing is on the same page. The address stops opening straight away, including for people you already sent it to, and a new link gets a different address so the old one stays dead.

The biggest line on the crew page was rendering at the size of every other line, and the cutoff sentence was sharing a row with two lines beside it.

• The answer at the top of the crew page, whether to move now, is meant to be the largest thing on the screen. It was rendering at body size, so the line somebody reads first in a dark car park looked like all the rest. It is the size it was designed at now.
• The arrival time, the note under it and the cutoff sentence were laying out side by side in three narrow columns, squeezing each other. They stack now, the arrival time first. The cutoff sentence is there so nobody does arithmetic at mile 45, and it gets a full line to say it in.
• The bar showing where your runner is along the course was drawn shorter than the slot it sits in, so the marker on it sat short of the mile it was reporting. It runs the full width now, and the marker is where the mile says it is.
• What your runner asked for at the next stop now has a small label above it instead of a sentence the same size as the note, so their own words are the part your eye lands on.

The biggest line on the crew page could send you to a stop crew are not allowed at.

• The stop that page was about, the one in the leave line, the arrival window and your runner's note for the next stop, was whichever aid station came next by mile. Whether crew can meet there was never part of the question. So the largest line on the screen could name a stop that is closed to you, and promise a drive time for it that was never going to exist, while the stop you can reach sat in a row further down the page.
• It now names the next stop ahead that you are not barred from. Every stop still ahead is listed exactly as before, the closed ones included, because knowing where you cannot go is part of planning the day.
• Where nobody has checked whether crew can meet at a stop, that stop is still offered to you. Dropping it would cost you a stop you may well be able to reach, on the strength of a fact nobody has looked up. Its row now says nobody has checked crew access there yet, which is what we actually know.

The race plan breakdown is not on the page your crew reads any more, and this is where it went.

• When the crew page became one screen, the table listing your plan's legs came off it: the leg name, its miles, the effort and the pace. That was a decision, not something that fell out along the way. The page answers where your runner is and when to be at the next stop, and a second table answering a different question is one more thing to read past at 3am.
• Nothing has gone from your plan. The full leg by leg breakdown is still on your own race strategy page, effort note and all.
• What your crew reads instead, for every stop still ahead: the arrival window, the drive, the walk in from parking, whether crew can meet them there, and whatever you wrote for that stop.
• If you crewed off that table and want it back, it comes back as one section under the stop list. Saying so is enough.

A crew page that had gone quiet could stay quiet forever, with no way to check again.

• If your runner's tracking session had already ended by the time someone opened your crew link, the page never asked the server for anything again. It looked live. It was a photograph.
• It now says so, plainly, the moment the page loads: this tracking session has ended, and that's about the phone, not about your runner. Check again is right there, not held back until an hour of failures had already passed.
• If the page just has not heard from the phone in a while, that is a different line: we have not heard anything recently. It keeps trying quietly in the background, and Check again shows up well before an hour goes by either way.

A crew link now has to be opened before it can change anything, on the app's side as well as the page's.

• The protections a share link got last week covered the page. The part your crew's app talks to had none of them, so a link that was forwarded on, previewed, or pasted somewhere could change a checklist, a stop's instructions, or your race notes without anybody ever opening it. Now a change has to come from something that read the plan first, on every route, including any route added later.
• Saving a note for one stop used to hand back everything written for that stop, whoever wrote it. It now hands back only what you just wrote. What you can read is decided by what your link is for, and saving is not a way around it.
• Your crew page is now told to stay out of search results, the same way the live race page already was. The link is the only thing protecting what is on it, so an indexed copy would hand a stranger your position and your crew's notes.
• A course file that will not open is now remembered as tried. Before, every crew member's page re-opened it every thirty seconds for the whole race. A course that will not open still says so, rather than saying you have no course.

Four fixes to the numbers on the crew page. Every one of them was making your runner look worse off than they are.

• Room before a cutoff is now worked out in the race's own clock. For any race outside UTC it was off by the whole time difference, so a runner with an hour in hand could be shown as though the cutoff came first. That is the one sentence this page must never get wrong, and it no longer can: there is now a single place where two times are compared, so no future line can reintroduce it.
• Leave times and arrival windows are shown in the race's clock too, for the same reason.
• A long stop now widens the arrival window by the whole stop. A phone keeps sending positions while your runner sleeps, and the window was reading the gap between the last two of them, so four hours in a cot widened the window like a ten minute breather.
• Against-the-plan now keeps counting past the last mile in the plan table. Plans are written per whole mile and courses are measured off a map file, so the finish is rarely a round number. A runner holding their own pace to the line through that last stretch was told they were putting more time into it than the plan expected.
• On a lap or out and back race, the pass your runner is on is now the one they are running toward, not the one they are nearest to. Halfway round a loop, the nearest stop is the one already behind them, whose alert has already gone, so the leave alert stayed silent for exactly the pass it exists to catch.

The arrival window and the leave now line were going blank on the crew page.

• Two of the five lines your crew reads, when to leave and the arrival window, could render as an empty line even though the time was already worked out. Fixed, and covered by a test that checks the words actually on the page, not just the ones the app computed.

The dashboard and the stop rows say who they mean, instead of leaving you to work it out.

• The section of your dashboard that lists the races you are following used to carry a one word heading, the same word the membership goes by. It now says who is in it: the runners you are following.
• When nobody has shared a race with you yet, it says that, instead of "No races saved yet." Nothing was saved because nothing was sent, and the old line read like something you had forgotten to do.
• On the crew page, each stop's crew column is headed "Crew access" and a stop that allows crew reads "This stop is open to crew." Same fact, said once, in the words the race itself uses.

The copy check now reads the crew page's words. Until today it read the page around them.

• Almost every sentence a supporter reads on the crew page lives in Python, not in the template. The check that scans NavRun's copy opened the templates, found placeholders, and reported clean. It now opens the five modules where those sentences actually are.
• The rule that guards that word no longer fires on capitalisation. "Crew Access" over a form control says exactly what "crew access" says, and a rule that made a label worse to go green was checking the wrong thing.
• Tests pin both, so neither can be quietly undone.

A lap or out and back race now gets a leave alert on every pass through a station, not just the first.

• Crewing Javelina or any looped course used to mean one leave alert for the whole race: after the first pass through a station, your crew heard nothing on laps two through five, even though your runner was going through the same stop again.
• Each pass now gets its own alert, worked out from your runner's own resolved position on the course rather than guessed.
• When the course genuinely cannot tell two passes apart, no alert fires for that moment rather than risking a wrong one. A guess here would either spam your crew or go silent, and both are the harm this fixes.

The crew page is joined up. What the last few weeks built now shows on it.

• Line one tells you whether to move, line two says where your runner is with how they are going beneath it, line three is the arrival window, and the bottom of the page carries your runner's own words for the stop ahead.
• Every stop still ahead now carries its own arrival window, the drive, the walk in, whether crew can meet them there, and whatever your runner wrote for that stop. A stop nobody has confirmed still reads as not confirmed, never as a no.
• All of it still refreshes together, on one clock. A slot that has nothing to say says so in plain words and holds its place.
• Share links got their protections. The link never leaves in an outbound request, a preview in a group chat shows a name and nothing of the plan, and saving a link takes a browser that actually opened the page.

The crew page now tells you when to leave, and how wide the arrival window really is.

• The first line answers the only question you have in a car park at 3am: plenty of time, getting close, or leave now. It carries the time to leave for the next stop, worked back from when your runner is likely to get there, the drive, the walk in from parking, and a quarter hour of slack so you are there before they are.
• The arrival window is as wide as the truth needs it to be. Mile 20 is a narrow window. Mile 85 is not, and it says so rather than pretending. Night, climb, technical footing and how far out the stop still is all widen it.
• When your runner stops moving, at an aid station or asleep in a cot, the window gets wider and the middle of it stays put. It no longer treats a chair as a very slow pace.
• Every window says what it is made of: live pace, or the planned one, and why.
• Room before a cutoff is shown as a plain sentence about the clock. No colours, no countdown, nothing that reads as a warning.

The crew page now says where your runner actually is, not just that the page refreshes.

• The "where they are" line reads your runner's real place on the course: the mile, and the stations on either side of it.
• If the last position doesn't land on the marked route, it says so plainly instead of guessing a mile.
• If the course crosses itself and two spots are equally likely, it says both rather than picking one.
• If there's no course map on file for the race yet, you still see your runner's raw position rather than a blank line.
• A position that's gone quiet for a while turns amber, never red, and never claims to be more current than it is.

How your runner is doing against their own plan, in one line.

• Built the comparison your crew page will show under where your runner is: moving quicker than the plan, right on it, or putting more time into the stretch than the plan expected. No pace, no percentage, no number to read out loud, just the plain read.
• When there's no course map or no signal to check against, it says so plainly instead of guessing.
• Not on the crew page yet. This lands the comparison itself; the page wiring is a separate piece of work.

The crew page is one screen with five lines that never move.

• The page your runner shares with you is rebuilt. Whether to leave now is the first line, every time. Under it: where they are, the arrival window, the button to navigate, and whatever your runner asked you to bring. Same five places on the tenth look as on the first.
• Everything on it refreshes together or not at all. There is no longer any way for one line to be current while the line under it is an hour old.
• When the reception goes, nothing turns red and nothing says anything failed. The lines stay where they are and the one line under them tells you which moment you are looking at.
• Below the five, the stops still ahead: the mile, the arrival window, the drive, the walk in from parking, and whether crew are allowed there at all. A stop nobody has confirmed says so rather than looking like a no.
• If you are following someone's link and want the updates yourself, you can save it now.

Sharing your race plan now says exactly what someone can do with it, and for how long.

• When you share your plan with your crew, you pick what they can do: see it, or see it and change it. Letting someone update it is off by default. You turn it on when you want it, for the person who needs it.
• You can give this to more than one person now, each with their own settings. Your pacer can update your drop bag notes. Your parents can just watch. One link is no longer all or nothing.
• Give a link an end time if you want one, or leave it open. Turning off someone's ability to change your plan, or shutting off their access entirely, takes effect the next time their page loads. Nothing lingers.
• Your race day checklist is still free for every runner, whether or not you have a paid pacing plan, and sharing it works the same way either way.

Muting a noisy chat can no longer take the leave-now alert with it.

• If you crew for someone, notifications now live on the same Preferences page you already use, once you've saved a runner's link. Voice messages from the runner's chat can be turned off on their own. The alert that tells you when to leave for the next stop cannot be turned off at all: it has no switch, on purpose.
• On a course with laps or an out-and-back, that leave alert now fires every time you pass the same station, not just the first time.

"Nobody has checked" is not the same as "no," and now the app says so.

• Whether crew can reach an aid station, and whether it holds a drop bag, used to have two answers: yes or no. There was a real third one, nobody has confirmed it yet, and it was quietly being read as no everywhere: the printed crew sheet, the drop bag sheet, the CSV export, the elevation chart, and the add/edit form on your race's aid station page. All of them now show a station that's never been confirmed as its own thing, not a silent "no."
• Race day cutoffs that fall after midnight, or a full day later on a hundred-miler, now carry their own day, so a cutoff at 10pm on day two of your race reads correctly instead of guessing wrong.
• When you adopt a race from the catalog, the crew's own parking spot for each aid station comes along now too, not just the station's own pin.

The route map on a run now draws when you open the Map tab.

• Opening the Map tab on a run could show an empty panel: no map, no route. The map was being built while that tab was still hidden, so it had no size to work out where to point, and it never recovered once the tab opened.
• It now works out the view when the tab opens, so the route is there when you look at it.

The maps stop saying "API KEY REQUIRED" across the middle of them.

• Every map in NavRun had a diagonal "API KEY REQUIRED" stamp across it. The company serving our map tiles started requiring a key at the end of August and marks every tile that arrives without one. Nothing was broken, but every course map, every run, and every race in the ultras catalog was reading like a broken demo.
• The maps now draw from OpenFreeMap, which is built from OpenStreetMap and needs no key. Same quiet grey cartography, light and dark, and the stamp is gone.
• The map credit is now on the page. OpenStreetMap and the people who build these tiles give the maps away, and they were not named anywhere in NavRun before this.

One link for the bio, and it knows what phone you are on.

• There is a page at navrun.app/links/ now. It is the single link that goes in NavRun's Instagram, TikTok and YouTube bios, and it is a short list of where to go: the race database, the free calculators, races on film, the writing, and the Crew.
• Open it on an iPhone and the first thing on it is the App Store. Open it on anything else and the first thing is the web app, which is all of NavRun in a browser.
• There is no Android app yet. The page says so rather than sending you to a store page that does not exist.
• It is not in search results on purpose. It is a signpost for people arriving from somewhere else, not another page competing with the front door.

Going quiet on somebody is not invisible to them, and the app says so now.

• When you go quiet on somebody in Out Here, the page they are on tells them it is not taking their messages. The app used to say they are not told anything. That was wrong, and it was wrong in the one place you are making a decision about another person.
• They can still open your link and follow along. What stops is their voice reaching you. None of that has changed.
• Reporting still takes the message off the page for everyone, and a person reads it.
• This is in the iPhone app and arrives with its next release.

The pricing page stops selling nutrition analysis that is not in there.

• The paid race-day plan was described as pacing, nutrition and conditions analysis, on the pricing page and again on the page you land on after joining. There is no nutrition or hydration anywhere in what that plan works out. It reads pacing, elevation and weather.
• Both lines now say what it actually gives you: pacing per aid station, the cutoff maths, and the weather your race is getting.
• Nothing about the plan itself has changed. You could always write your own fuelling into the notes, and you still can.
• The fuelling calculator is where the carbs and sodium maths lives, and it is free with no login, same as it was.

Some tidying on the feature pages, and a check that will catch the next lot.

• The wording on eleven feature pages had stray double hyphens in it, thirty six of them, left over from copy written before the house style settled. They are commas, colons and full stops now. Nothing any of those pages tells you has changed.
• Three of them said "AI-powered" where the sentence read better without it.
• The reason nobody had noticed: the checker that reads every word NavRun publishes could not see these pages at all. Their words live somewhere it never looked. It looks there now, so the next stray one is caught before it ships rather than after.

A page that explains Out Here to the people who are not running.

• There is a page at navrun.app/features/out-here/ now. It says what happens when you send the link, what your people see, and what they can send back.
• It is written in three parts, one for the runner, one for whoever is driving to meet them, and one for whoever is at home, so you can read the part that is yours and skip the rest.
• It says out loud what Out Here needs and what it is not. It needs cell service at both ends, it is not a satellite beacon, it does not replace the gear your race makes you carry, and it uses more battery than a usual run.
• The features list has a new heading, Run With Your People, and it comes first.
• Nothing about how Out Here works has changed. This is a page about it.

The front page is the app now, not a picture of one.

• The home page still opens with "You're never out here alone", then says which races this is for, and then shows six real screens: a logged run, the free predictor, a plan week, an aid station table with the cutoffs beside your arrival times, the page your crew watches, and the sheet they drive off. Every word on those screens is the word the app itself uses, and a test holds each one against the file it came from, so a screen cannot quietly go stale.
• The old page carried a made-up dashboard: 378 runs, 2,107 miles, a chart of nothing. Numbers invented to look like a product. They are gone.
• Under the headline is a list of who this is for, from a first 50K to a fifth hundred, and it ends by letting in anybody who is on none of the lines.
• The race catalog card counts the courses when the page loads instead of carrying a number somebody typed in once.
• The page fits a phone. The two screens in the header stack instead of running off the side, and the wide tables scroll inside their own panels rather than dragging the whole page sideways.

Shared posts show a trail, not a dark rectangle.

• Every NavRun post now shares with a photograph behind the title, chosen to match what the post is about. There are eleven, one per category.
• The four posts from this week were also pointing search engines at a logo file that is not there. They point at the real one now.

Your taper is three settings now, and the page shows what each one costs.

• A races, B races and C races each get their own taper length on your preferences page. That was already how NavRun built your plans, but the page carried one box, so two of the three were being set by something you could not see or change.
• Next to each one is your own next race of that kind, with its date, and what the setting does to that week: how many weeks come down, when the first one starts, and roughly what race week comes to against your usual week.
• Zero is a real answer and the page treats it as one. A C race set to zero says the week stays whole, rather than showing you an empty box.
• A race of 50 miles or more keeps at least three days whatever the setting says. Where that applies, the page names the race and says so, instead of showing a number that is not the one being used.
• If you have no race of a given kind yet, that setting is still on the page with what it will do, so you can set it before you add the race.
• A question on the "How AI training plans work" post said NavRun enforces the 10 percent rule. It does not. The weekly increase limit is yours to set and 10 percent is only where it starts, so the answer now says that.

The iPhone app shows the taper for the race in front of you.

• The dashboard worked out where you are in a block from a flat fourteen days, whatever the race was. A training race you meant to run straight through could read "taper time" on your phone while the website said you were still in the work.
• It reads the same number your plan was built from now: your setting for an A or B race, none for a C race, and at least three days for a race of 50 miles or more.
• Set your own taper for one race and the phone follows that too.
• A race you run through reads as what it is, a week of training with a race in it. Nothing on the phone counts you down to a taper that was never planned.

Your hikes stop counting as running miles you then have to go and run.

• The ceiling on next week is built from your running, road and trail. Hiking was going into that number too, so 57 running miles plus your usual time on the ridge came back as a 70 mile plan against a 12 percent setting.
• The same hikes were also counted as load, so one plan could ask for more running and say to keep the midweek days gentle, off the same hours.
• Your hiking has not gone anywhere. The plan is still built knowing about it, as hours on your feet, and those hours no longer decide how far you are asked to run.
• Trail running is running here, and it always was. If your miles are all trail, your ceiling is exactly what it was.

Your plan reads four months of your training, and stops backing off for races you meant to run through.

• The plan generator used to read your last thirty runs. If you go out six days a week that is about a month, and the oldest week of it arrived half counted, which pulled your average down and put a ceiling on next week that sat under what you had just done. It reads four months now and builds the ceiling off your last four full weeks. The week you are in the middle of is not counted as a full week any more, so running more today no longer makes next week's plan smaller.
• Next week can be as big as last week plus your own weekly increase. Before, a mean of four weeks of building lagged behind you, and a 57-mile week could come back as a 49-mile plan.
• If last week had a race in it, or one or two runs that were most of the week, that week is set aside as a starting point and the ceiling comes off your average instead. You are never asked about it and never scolded for it. The "What the AI will see" panel says which way it went, because that panel lists everything the plan is built from.
• Races carry their own taper now. A and B races use the taper setting on your preferences page, a C race uses none, and a race of 50 miles or more keeps at least three days unless you have answered for that race yourself. Your existing setting carries over onto A and B.
• A short C race in the week no longer collapses the days around it. The race distance counts inside the week's normal total and the rest of the days are planned as training, which is what a training race is for. A C race of 50 miles or more still gets its three days, and the week around it is still small, because 50 miles is 50 miles.
• If you are inside a taper right now, this change does not move it. Your current setting was written onto that race before the new ones took effect.
• The week has a bottom as well as a top. If a plan comes back well under what you can do, NavRun asks for it again once before saving.
• On the web, anywhere NavRun told you a taper was starting now says what that race actually tapers. A race that tapers none says so, instead of counting down to a day that never comes. The iPhone app still shows the old fourteen-day figure and will catch up in its next release.
• The message about next week's plan can arrive as a notification if you have the app, and arrives once either way. The unsubscribe link in it stops the emails for that one message and leaves the rest of your email alone. Notifications are separate, and you turn those off in the app.

Three new reads from UTMB week.

• Rachel Entrekin took second at UTMB and told an interviewer she does not do workouts. That clip went a long way around the internet. What she actually did was run the course on repeat for a month, and she says arriving a week out instead would probably have ended her race at 50 kilometers. The post is about what course-specific training is worth, and how to get some of it without moving to Chamonix.
• Full UTMB 2026 results: every finish time in both top tens, plus CCC, OCC, TDS, MCC, ETC and PTL, the two-hour storm delay, why the two fastest times in race history are not course records, and the finish rate that does not make headlines. 1,681 of 2,407 started and finished, the last of them at 45:53:17.
• UTMB expanded its parenthood policy this year, and the version going around social media has the deferral length wrong. We read the actual policy document: what it covers, how long you can really defer, and the line stating that miscarriages and failed cycles stay covered and never have to be disclosed.

How the UTMB lottery actually works, on one page.

• Running Stones, the two-year rule, and what the UTMB Index really is (a check that you finished something of roughly the right distance, not a score to beat). Plus how the draw actually runs: each stone is worth ten entries, the low-carbon travel commitment makes it thirteen, and your highest random number wins.
• Every route into Chamonix that is not the lottery, including TDS, which needs no stones at all and is the door most people miss, and a medical priority policy open to every runner with a deadline on September 27.
• Written from UTMB's own documents. Where two official pages contradict each other, and they do, the post says so instead of picking one. Where nothing has been announced for 2027, and almost nothing has, it says that too.

Alerts stop going to an address that cannot take them.

• When a mailbox refuses one of our messages for good, NavRun stops writing to it. That covers every race the address was following, not only the one whose message came back.
• A mailbox that is full, or having a bad day, is left alone. That is temporary, and it is no reason to drop anybody off a list they asked to be on.
• Mark a NavRun alert as spam and that is the end of it. No link in any older message will start it again.
• If your alerts have gone quiet and you cannot see why, write to [email protected]. We can tell you what your mail server said and put you back on.

One mailbox is one place on the list.

• Ask a race page for alerts as [email protected] and again as [email protected] and NavRun reads those as the one mailbox they are. It used to read them as different people, so one address could sit on a race a dozen times over and hear about every change a dozen times.
• Stopping the emails covers every spelling of the address. A stop pressed from one of them used to leave the others running.
• Press "stop emails about every race" and nobody can put that address back on any race in the catalog by typing it into the form. That already held for the races you had asked about. It holds for all 59 now.
• The line at the foot of every alert saying when the address was put in prints the day it went in. On a signup from before this week it was printing the day the watch started, which is a different day.
• The page after you ask no longer says an email is on its way. There is not always one on the way, and the page said it anyway.
• Google hands out @gmail.com and @googlemail.com for the same inbox, and NavRun reads them as one. The two lines above held for plus signs and for dots, and that second spelling walked past both.
• An address the mail already gave up on does not get started again on a new race. Five failed sends, or a bounce the mail server reported back, and NavRun stops writing to it.

Putting your email in is the whole signup now.

• Ask a race page to tell you when it changes and that is it. There is no confirmation email to go and find, and no button to press before it works.
• An email arrives right away saying what you just asked for, which race it was, and how to stop it. After that, nothing until something on the race moves.
• Every message says where and when the address was put in, so one that turns up three months later is not a mystery.
• One click still gets you out, that click still covers every race you follow, and nobody else can put you back on.
• If you put an address in earlier today and never pressed the button in that email, nothing has changed for you. That email said doing nothing meant nothing more would arrive, and that still holds. The link in it still works if you want it.

A race page now says what NavRun does for you, whoever you are on the day.

• Partway down every race page there is a new part: "Running, crewing, pacing or still deciding". It names four people, the one running it, the one crewing it, the one pacing, and the one still deciding whether this is a race they could do, and says what NavRun does for each of them on that race. Until now the page made one ask, at the very foot of it, and only to the runner.
• The places and the times in it are read off the race's own record: a real aid station, its mile, and the cutoff the race publishes. It never prints an arrival time or how much time you would have in hand. Those are yours, and they come from your training.
• The count in it is the aid stations, not the start line and the finish, and it only says a cutoff sits beside each of them when each of them really has one. On a race that publishes ten cutoffs across seventeen stops, it says the ten and stops there.
• The last part says the thing this race actually asks of you. Western States runs a lottery, so it says lottery. A race that wants a qualifier first says that instead.
• The crewing part is only there when the race says your crew can reach a stop and we hold the directions to it. The pacing part is only there when the race allows pacers and we know where they join. A race whose course we have not filled in yet gets none of it, rather than a promise it cannot keep.

Turning a notification off is a setting, not a fault.

• Switch off one kind of email, with no phone signed in, and there is nothing left for NavRun to reach you on. It used to file that as a delivery that broke. It files it now as the setting you chose. Nothing about what arrives for you changes.

The race catalog can tell you when a race changes.

• Every race page has a button now: "Notify me if this race changes". Put your email in, confirm it, and NavRun writes to you when something on that race moves. The date, a cutoff, the time limit, when entry opens.
• The email says what changed, from what to what, and where we read it. Not "something changed, go and look".
• One email for a whole batch. When a race gets twenty fields filled in at once, that is one message and not twenty.
• No account, and nothing to cancel. One click gets you out, that click covers every race you follow, and nobody else can put you back on.
• Free, like the rest of the catalog. Your address does nothing else here.