// Railcar repair shops · Repair estimate approvals
A car owner's repair approval request, drafted from your inspection findings and that owner's written rules.
A car rolls in, your inspector writes up what's wrong, and someone in the office turns those findings into a request the car owner can say yes to. A free AI proof of concept has AI draft those requests from copies of 20 to 30 cars you already released. Your reviewer, the person on your staff who knows each owner's rules best, lays every draft beside the request that actually went out. It never decides what repair a car needs.
- Released cars
- 20 to 30
- Repairs chosen
- None
- Requests sent
- None
// The one job
From an inspector's findings to a request an owner can answer
Your inspector walks the car and records what is wrong. Your office then writes it up for the car owner: car initials and number, each defect and where it sits on the car, the work your shop proposes, and whatever that owner's written instructions say needs its say-so. Then the car waits for a yes, a no or a change.
In the test, AI reads copies of those findings and drafts the approval request: the defects as recorded, the work lines your shop proposed, the owner's written threshold or instruction each line falls under, and the items a person must confirm before it goes. Nothing is sent, no repair is chosen and no live estimate is opened.
the owner's rules
// What makes it hard
Where a repair approval request goes wrong
The yes can belong to more than one party. On a tank car, 49 CFR 180.503 makes the owner the person the reporting marks are assigned to in the Universal Machine Language Equipment Register. It separately names a service equipment owner, who bears the cost of maintaining loading, venting and pressure relief equipment, and a coating or lining owner, who carries financial responsibility for the lining. Section 180.513 has the facility get the equipment owner's permission before work affecting repair, alteration, conversion or qualification. So the draft names who each line goes to and leaves a blank where the file doesn't say. Marks move as well: Railinc's repair shop FAQ describes the new and former mark owners both being notified when a car is restenciled in Umler.
Not every repair needs the same yes, or the same price. The Railway Supply Institute's 2020 newsletter on the Interchange Rules describes running repairs as non-discretionary work that a handling railroad or registered agent may perform and bill, with limits on the hours of heavier work done without first securing car owner authority. Most major accident and derailment repairs happen in contract shops, which still bill them at Office Manual pricing, while pricing for owner's repairs is a matter of contract between the two parties, though the repairs themselves still have to comply with AAR rules. The draft marks each line by what your records say it is, and asks where they don't.
The car arrives with paper already on it. A defective car moved for repair carries a tag under 49 CFR 215.9, marked "bad order" or "home shop for repairs", with the reporting mark and number, the inspecting railroad, the place and date, the nature of each defect, movement restrictions and the destination. A damaged car can add an electronic defect card; Railinc's FAQ says AAR Rule 115 has required those since 2011 and a paper card no longer counts. When your inspector finds more than the card lists, the FAQ says to ask the car mark owner for permission first. The draft keeps card lines and added findings in separate groups.
The codes set the price later, so they can't drift now. Railinc's Billing Repair Card guide, updated in February 2026, says the AAR price on a line follows from the repair date, job code, why made code, responsibility code and condition code, and contract work goes through as manual pricing. The price has to match the Price Master in force on the repair date, and the RSI newsletter notes that the matrix is issued quarterly. Field Manual Appendix D, the American Rail Car Institute codes, revised April 1, 2026 and kept up quarterly by an RSI task force, adds job codes for repairs the standard AAR list leaves out, among them bottom outlet valves, manway covers and interior coatings and linings, with why made codes such as 25 for owner's request and 33 for derailment damage under Rule 95. Railinc's page on it says those codes carry neither a material nor a labor price and that the Interchange Rules don't make them mandatory, and several of its sections simply send the shop to the car owner for criteria. The draft carries the codes your estimator wrote and flags a line with none.
What your reviewer will watch. Does each defect keep your inspector's words and its place on the car? Does every work line trace to a finding, with nothing added? Is the owner's own rule named for each threshold, and is any line that rule doesn't settle held back? Rule 112 of the Office Manual covers exceptions taken after a bill settles, so the request is the paper a billed line gets held against. Nothing on this page is legal or engineering advice.
// What you send
Cars your office already closed
20 to 30 released cars
For each one, the inspection findings, the request that went out and the owner's answer. Mix in a car where the owner cut a line, one with damage found after arrival, and one from an owner whose rules changed.
Work orders and billing records
What was actually done and billed, including repair card printouts. Railinc recommends printing repair and defect card data before release, since a shop loses its view of it afterward, so these may sit in your job folders.
Each owner's thresholds, if you may share them
For tank cars, 49 CFR 180.513 stops a facility from passing an owner's confidential instructions or manuals to anyone without that owner's permission, and our NDA doesn't lift it. Where you don't have that permission, we build look-alike rules with your reviewer: same shape, made-up limits.
Copies only, after an NDA
Signed before anything moves. No one from Massmarket logs in to your shop system, a car owner's portal or any Railinc application, and no live estimate is opened. A file that can't leave the shop becomes a stand-in made with your reviewer.
// Before it starts
Settled before a single file is copied
Your shop's owner pins these down with whoever answers to the car owners.
- Your reviewer
- Named by the shop's owner, usually whoever writes estimates to car owners
- Success criteria
- In writing: fields that must match, and lines that must be held
- Car owners
- Only those whose files you may share; others become look-alikes
- Who decides
- Your inspector and shop manager, on every line
- Price
- A range for the live month, stated up front
- NDA
- Signed ahead of any copying
// How the test is judged
The request you sent, beside each draft
| Across the same 20 to 30 cars | Request your shop sent | Draft from the test |
|---|---|---|
| Car initials and number, and who the request went to | Filled in from your cars | Filled in from your cars |
| Each defect in your inspector's words, at its place on the car | Filled in from your cars | Filled in from your cars |
| Every proposed work line traced to a finding | Filled in from your cars | Filled in from your cars |
| Defect card lines kept apart from added findings | Filled in from your cars | Filled in from your cars |
| Job and why made codes carried as your estimator wrote them | Filled in from your cars | Filled in from your cars |
| The car owner's threshold or instruction named for each line | Filled in from your cars | Filled in from your cars |
| Items a person must confirm, listed and left unfilled | Filled in from your cars | Filled in from your cars |
// After a yes
About 30 days on incoming cars
With your reviewer's yes, cars arriving over the next 30 days or so get the same draft.
Someone on your staff approves each request before it reaches a car owner, and your inspector's findings and your shop manager's decisions stay exactly where they are today.
Another job, if you want one, is its own decision at its own price, with monthly support after that.
// Possible next jobs
After approval requests, if you want more
- 01Next
Tank car qualification files
Each qualified car's report assembled from shop records, with gaps listed for the person who signs.
- 02Then
Billing exception replies
An owner's exception to a billed repair set beside the work order, the approved request and the repair card.
- 03After that
Car release reports
The work done and any damage or failed parts observed, written up in the form each owner's instructions ask for.
// One hard limit
It never decides what repair a car needs.
Findings come from your inspector and proposed work from your shop. The proof of concept never touches your shop system, a car owner's portal, a live estimate or a live record. It never decides what repair a car needs, judges an inspection result, signs a qualification, sets a price or sends a request to anyone. A qualified person at your shop makes every technical call and signs every record. Defense and aerospace work stays outside the test, and nothing here is legal or engineering advice.
Priced per job. You get a range before the proof of concept and a fixed price before you sign.
Rob gives the range on the call once he knows how many cars you release a month and how many car owners' instructions your office works from.
// Questions
Approval request questions
Will the AI decide which repairs a car needs?
Can we send a car owner's shop instructions for the test?
Does it pick the AAR price or our contract rate?
What happens when the shop finds more damage after the car arrives?
Our findings are handwritten and our estimates live in spreadsheets. Does that work?
Can the sample mix tank cars, covered hoppers and gondolas?

Rob Eason, founder
// Book a proof of concept call
Bring a month of requests you already sent.
Thirty minutes with Rob about your shop, your role, the job you'd try first and how many cars you release in a month. Findings, estimates and car owners' instructions stay put until the NDA is signed.
- Co-owned a 60-employee financial services firm and sold his share to his partner.
- Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
- 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
- 4.3/5 from 6 Google reviews of Massmarket AI.
- Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
- Takes every proof-of-concept call himself.
