Help & support

Where the documentation lives, how to reach the people who build RailCompliant, and commenting on the RailCompliant blog.

The documentation

This site is RailCompliant's documentation. Click Documentation in the app's sidebar to open it in a new tab from anywhere. It is written for the people who actually do the work — a Saturday volunteer who needs to log a repair, not a compliance officer who reads the CFR for a living — and it is updated whenever the app changes. Good places to start:

• Overview — the big picture: staying legal on one side, running the railroad on the other, and how the two connect.
• Navigating the app — where everything lives.
• The compliance dashboard — how using an engine counts down its inspection clocks.
• Work orders — tracking a repair start to finish.
• Excursions & runs and Calendar & work days.

For the regulations themselves — the text of 49 CFR Part 230 and Part 229, searchable, with citations you can link to — use the Regulations library inside the app.

The support desk

Click Support in the sidebar. Tickets go straight to the people who build RailCompliant, and you can normally expect a reply within one business day.

Opening a ticket

Fill in Open a ticket:

• Type — Question, Problem / bug, or Feedback / idea.
• Subject — a short summary.
• Message — what happened, what you expected, and where you were in the app.
• Attachments — up to three files of 10 MB each, screenshots (JPEG, PNG, GIF) or PDFs. Screenshots say more than words. Every file is scanned for viruses before it is saved, and a PDF can't carry scripts, embedded files or a password; if yours does, print it to a new PDF and attach that. See How your data is protected.

Click Send. The ticket is listed under Your tickets with a reference (RC-1001 and up), its type, status, and when it was last updated. Open it to read the thread, add a reply, or close it once the matter is settled. Replying to a closed ticket reopens it.

Writing a report worth answering

For a problem, include the page you were on, what you clicked, what you expected, and what happened instead. If a number looks wrong, say which number and what you believe it should be. A screenshot of the screen as you found it is usually enough on its own.

For a security concern, open a ticket the same way and say so in the subject.

If you cannot sign in at all, write to help@foxxcyber.com from the address your account uses.

New to the app? Start with Navigating the app.

Comments on the RailCompliant blog

The RailCompliant blog publishes articles on FRA compliance and maintenance for heritage and tourist railroads. Every post ends with a Comments section, and anyone with a RailCompliant account can comment there: ask a question about the article, or share how your railroad does it.

Who can comment

• You need a RailCompliant account with a verified email address. If you aren't signed in, the post shows Sign in to comment. Sign in (two-step sign-in included, if your account uses it) and you come back to the same post's comments. No account? Start a free trial is right beside it.
• Your railroad's billing doesn't matter. Comments belong to your account, so you can comment even while your railroad's subscription is paused.
• Not verified yet? The post says "Verify your email address to comment". Open the link we emailed you, or choose Resend link at the top of any RailCompliant page.
• No name on your account? Comments show your name, so an account without one can't comment. Write to help@foxxcyber.com and we'll add it.

What other readers see

• Your name, as it is on your account, and the date. Never your email address and never your railroad, so a comment is always yours and never reads as your railroad's official position.
• Comments from the people who build RailCompliant carry a RailCompliant badge.
• Comments are plain text, up to 2,000 characters. Line breaks are kept; everything else shows exactly as typed (a web address isn't a link, and there's no bold or italics).

Posting and deleting

Type in Add a comment and click Post comment. Your comment appears straight away for everyone. There is no editing: to change a comment, click Delete beside it (only your own comments have it) and post it again. Deleting can't be undone.

To keep the conversation readable, an account can post five comments in ten minutes and thirty in a day. Past that, the post asks you to wait a while.

Community rules

Comments follow the Acceptable Use Policy, which is linked under the comment box. In short:

• Be civil. No harassment, threats, or abuse, and no spam or ads.
• Leave other people's details out. Don't post anyone's address, phone number, or other personal information.
• Be who you are. Don't pretend to be, or to speak for, a railroad, the FRA, or another person.
• Point to the regulation. When you say what a rule requires, cite the section or link the official text at ecfr.gov. A comment is never an official FRA position.
• Stick to facts about people and railroads. Opinions are fine; statements of fact have to be true.
• Stay safe and on topic. Nothing that encourages trespassing on railroad property or getting in the way of operations, and photos only from where you are allowed to be.

To report a comment, email help@foxxcyber.com with a link to it and what's wrong. Copyright complaints follow the Copyright Policy.