Step 1: Always check if we already have the Route!
Step 2: If the person doesn't provide enough information or a GPX file (GPX is REQUIRED) then you should immediately kick it back to them, point them to the Guidelines, and have them resubmit the route with complete information. That's on them, not you. They should say where the route begins and ends, and if it's complex they should provide a written description of the route, so that someone doesn't have to rely 100% on the GPX track. If the submitter can't provide a GPX track you can suggest they resubmit the route after they run it.
The main thing with adding a route is deciding whether it is actually a good FKT route. I hate crushing someone's dreams as much as the next guy, but we do need to have standards or the whole FKT concept loses its validity. Some guidelines:
-A whole named trail is basically always valid, and can be run one way or out & back. However, we rarely allow for directional FKTs (I always say, "Go whichever way is faster"), be they point-to-point or loop.
-"Official" segments of a longer trail are acceptable as separate Routes. Examples are an official segment of the Pacific Crest Trail, or a "Stage" of a long trail, such as are commonly delineated in Europe. But not a random section of a longer trail, and not an FKT route for 2 (or more) consecutive segments of a long trail. There are simply too many possibilities if we start allowing random combinations of segments / Stages.
-Running up, or up & down, a mountain by the standard trail, or really any logical route to the top of a mountain, is basically always a valid route. A mountain might have multiple route Variations such as different trails to the top.
-Established trail running routes. The person should explain why the route is considered established or classic, rather than something they just came up with. Provide a link that shows people have been doing the route. If a trail has a website then it's pretty clear that it is legitimate (the website should be linked on our page).
-Traversing or circumnavigating a notable terrain feature is generally good. Make sure the route does what the person says it does.
-Routes that simply link 2 notable locations are usually NOT accepted. There are just too many possibilities. Note that we have some routes on our site that do exactly this. If we had it to do over we probably wouldn't have approved those routes, but we're not going to remove them (yet). So, this also points to the general principle that: "Just because we have something similar, doesn't mean we will add your route now." For example, I approved a few routes that one guy submitted that run between major airports in various metropolitan areas. However, no one else has ever run any of these, and I would not approve something similar today.
-We don't prefer routes that simply cover a standard distance, like a marathon or 100 miles. Those are RACE distances, while an FKT route should have inherent logic beyond a simple (arbitrary) distance.
-When in doubt ASK the person for explanation. Tell them why you don't think their route counts. If you are confident in your assessment simply tell them it doesn't meet the Guidelines. Feel free to consult with Peter, who has vetted literally thousands of routes! If you ask for more info and they don't respond you should simply drop it. The onus is on the person who submits the route.
-IMPORTANT: Be sure to switch any unapproved route from "Draft" to "Unpublished"!
Guidelines for processing a route:
-We prefer route names that give some indication of what the route is. "Cute" names are acceptable if the name is already in general use. Feel free to change the name to something that will be more clear to the general user.
-Things like "one way", "west to east", "out & back", "ascent", "up & down", etc., are for the route Variations, and generally should not be in the route name. We are phasing out "Standard Route" as a variation name in favor of more descriptive terms, such as those just mentioned, so please change "Standard Route" to a more appropriate descriptor (commonly: one way, out & back, ascent, up & down, loop, open course). "Open course" is used for any route (variation) where the goal is to reach certain points, while the route between points is "open". The Bob Graham Round is an example - you have to reach the summits, but how you get between them is up to you.
-In the USA, always add the 2 letter state code in parentheses after the route name. In Canada we use the province code + "Canada", e.g., (BC, Canada). In Australia we use the state code + "Australia" (NSW, Australia). Everywhere else we generally put only the country in parentheses as part of the route name.
-The distance & vertical gain fields should match the FIRST Variation listed. Make sure the person correctly selected km or miles, and m or ft.
-Feel free to make changes to the route description to improve for clarity and completeness.
-Make sure the person selected the country (USA) and state/province/etc in that field.
-Add any Related Routes you can think of.