Editorial process
Corrections and feedback
Roads, restrictions, services, and ferry arrangements change. Specific, dated reports help the editorial team investigate and update a guide.
Submit a correction
TwistAtlas is a static site and does not run a contact-form backend. Corrections are submitted through the project's external GitLab issue tracker, where the report can be reviewed against the versioned route content.
Open a new correction report on GitLab →
GitLab may require an account, and submitted issues may be public. Do not include private contact details, precise home or overnight locations, or other sensitive personal information.
What to include
- Route title and the URL of the affected page
- The statement, map section, or GPX segment that may be wrong
- The date you observed the issue or checked the source
- A clear location, road name, or approximate kilometre reference
- What you observed and how it differs from the published guide
- A current official source or non-sensitive supporting evidence, if available
First-hand observations are useful, but one report does not automatically establish a permanent condition. Please distinguish between a temporary closure, seasonal issue, and an enduring change.
What happens next
The editorial team compares the report with the published route, current authoritative sources, and any existing field evidence. A supported correction may update the guide, its sources, review date, or review status. A report alone does not upgrade a route's verification method.
TwistAtlas cannot promise an individual response or immediate update. For an active danger, closure, emergency, or illegal access, contact the relevant authority and use current official information rather than relying on this correction channel.
General feedback
The same issue tracker can be used for factual feedback about how route information is presented. The pilot does not provide public comments, user accounts, route submissions, or a private support inbox.