About
About & Editorial Policy
Who is responsible for FRMCS Atlas, how content is produced, and which review status applies to which content.
Interests
Disclosure: the editor is employed by Frequentis, a supplier listed in the supplier directory (control-centre and MCX communication). The Frequentis entry is additionally marked there and follows the same research and wording rules as every other entry. There is no ranking of suppliers and no paid content.
Methodology and review status
Database articles (versioned workflow): Each version is scored against six criteria (factual accuracy 30, source quality 20, relevance 20, currency 15, independent analysis 10, clarity 5). Only a version scoring at least 85, with no blocking issues, at least one linked source and a human approval of that exact version can be published. Any change to text, sources or claim references requires a fresh review and approval. These rules are enforced in the database for every path (editor, scheduling, automation); automation can neither approve nor publish.
Static legacy content: Knowledge articles, the standards, supplier and railway directories, and the two static news entries were created before or outside this workflow. No documented quality review or approval is stored for them. They are labelled accordingly; the news entries can be re-reviewed via a draft and are replaced by the reviewed version once approved.
Sources: Each source carries a status: “Original retrieved” (content checked on the stated date), “Link not re-checked” (exact address known, content not confirmed — e.g. maintenance pages) or “Evidence pending” (no exact address substantiated yet). Maintenance or error pages never count as confirmation.
The score is an editorial aid, not a probability of truth.
Badges
NEW marks content first published within the last seven days; UPDATED marks a material change within the last seven days. Event dates are shown separately.
Corrections and contact
Material corrections to database articles create a new version with a change-log entry. No public email address is configured at present; reports reach the editor through this form.
Found an error or a better source? Describe it here. No account needed; an email address is optional and only used to ask follow-up questions.