Spaces

First-reply checklist for pipeline landowner and shipper messages

This checklist shows what the first reply to a new message should contain when the sender is a landowner, a shipper, a contractor or a neighbour of the line. It is made for pipeline operators and the teams who answer for them.

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

Before you start

People who write to a pipeline company are rarely casual. A landowner may be worried about a survey crew in the field. A contractor may be about to dig. A shipper may be chasing a document before a deadline. A weak first reply sends each of them hunting for a phone number.

Read down the list and tick what your replies already do. Each gap is a place where a sender has to write twice or ring someone. Share the list with whoever answers your messages, whether that is a person on the land desk or your AI agent.

Tick each one as you go. 0 of 10 done.

[ ] Thank them and say which company they have reached.
[ ] Work out who they are: landowner, shipper, contractor or neighbour.
[ ] Answer the plain question first, before any background.
[ ] Give the right team and how it can be reached.
[ ] Ask for the location, such as plot, road or marker number.
[ ] Ask for a phone number and the best time to call.
[ ] Point to your emergency line if the message hints at danger.
[ ] Say what happens next and roughly when.
[ ] Avoid opinions on safety, digging or agreements.
[ ] Keep it short, polite and free of internal terms.

What a good first reply looks like

Imagine a landowner writes, asking what the crew on Miller Road is doing. A good reply says thank you, asks for the plot number, and explains that the land team will confirm what the work is and call back. It does not guess at the work, and it does not promise anything about access.

A contractor asking about a dig gets something different: the steps to request a line location, the lead time you ask for, and a request for the dig address and date.

Slips that cost goodwill

These come up again and again in messages to pipeline companies.

  • Sending a long policy document when the sender asked one question.
  • Saying work is safe, routine or harmless without anyone checking the record.
  • Asking for six details at once, so the landowner gives up.
  • Leaving out the emergency line when someone mentions a smell or a noise.

FAQ

How quickly should a pipeline company reply to a first message?

As soon as you reasonably can, and the same day for contractors planning to dig. A short reply that names the right team and the next step is better than a perfect answer sent days later.

Can the first reply say whether it is safe to dig?

No. It should explain how to request a line location and pass the matter to the team that handles it. Safety and permission calls are made by people with the records in front of them.

What if I do not know who is writing?

Ask one friendly question, such as whether they own land along the line or work for a company. That single answer decides which team picks up the message.

More free tools for pipeline operators and transporters

Read the guide: Answer landowner, shipper and contractor messages in pipeline transportation.