Spaces

Confirmation messages for car requests, pulls and track access

These confirmation messages let a railroad repeat back a car request, a pull or a contractor visit in plain words, so both sides agree on what was asked. Fill in the details and copy the text.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

A lot of railroad trouble starts with a vague yes. A shipper thinks two empties are coming Tuesday. Your planner thinks one, on Wednesday. A confirmation message writes the request back in plain words, so a mix-up shows up on day one instead of at the siding.

Fill in the boxes below and the messages update. Choose the one that fits what was asked, check each detail, and send it. Remember that you are confirming that a request is received, not promising a train time.

Empty car request received

Thanks. [business] has your request for empty cars at [siding] for [when]. Your request is logged, and [contact] will confirm the switch time with you here once the plan is set.

Pull request received

Your pull from [siding] for [when] is logged with [business]. Please keep the cars released and the track clear. [contact] will confirm the timing here, and we will tell you if it changes.

Contractor access request logged

Thanks for your request to work near [business] track at [siding] on [when]. Nothing is agreed yet. [contact] will check access and safety steps, and reply here with what you need to bring.

Change to a request

We have updated your request with [business] for [siding] to [when]. Please check the details are right. [contact] will confirm the revised timing here as soon as the plan is final.

Confirm the request, not the train

The most important word in a railroad confirmation is logged. It tells the shipper you have the request, without saying a train will turn up at a set minute. Dispatch plans move with crews, weather, interchange and track work.

If your agent has a tool that reads the day's plan, it can add a planned time and call it planned. If it does not, a clear promise to confirm timing later is the honest choice.

Details to repeat back every time

Short confirmations should always hold the same few things.

  • The siding or facility and the type of request.
  • The day asked for, and how it was agreed.
  • The number of cars or the work to be done, if known.
  • Who will confirm timing, and where they will reply.

FAQ

Does a confirmation message commit us to a time?

Not if you word it as logged and planned. Say that timing will be confirmed by dispatch, and avoid phrases like will arrive at, which a shipper may treat as a firm promise.

Should the agent confirm requests by itself?

It can log a request and repeat the details back. Anything that changes the switching plan, or needs a yes from the planner, should be passed to a person for confirmation.

What if the shipper corrects a detail?

Update the request, send the confirmation again with the new detail, and keep the thread so everyone can see what changed. A written trail avoids arguments later.

More free tools for railroads and short lines

Read the guide: An AI agent for rail transportation: line-haul and short line railroads and their shippers.