Spaces

Partner privacy checklist for rolling stock builders

This checklist shows how a rolling stock builder can protect partner details, delivery plans, drawings and contract terms in chats handled by an AI agent. It is for owners, contract managers and security leads.

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

Before you start

Your chats hold more than names. They carry delivery locations of vehicles, site access routes, depot staff phone numbers, drawing references and sometimes contract wording. Some of that is commercially sensitive and some touches the security of rail operations, so it deserves more care than an ordinary customer chat.

Read each point and mark whether your team already does it. Where you cannot tick a point, decide who will fix it and by when. Share the final version with anyone who can read the chats, including contractors, so everyone treats partner information the same way.

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

[ ] Decide which documents the agent may share and keep the list short.
[ ] Keep contract prices, discounts and terms out of the agent.
[ ] Share delivery addresses and site routes only with the right partner.
[ ] Check who is writing before answering about any project.
[ ] Keep passwords, access codes and gate codes out of chats.
[ ] Give each staff member access only to the projects they work on.
[ ] Remove access the day someone leaves the team or the contract ends.
[ ] Tell partners plainly how their messages are handled and by whom.
[ ] Keep personal numbers of depot and site staff out of replies.
[ ] Review stored chats on a schedule and delete what you no longer need.

Where slips actually happen

Most privacy problems in this sector are small and human. A reply goes to the wrong depot contact, a drawing index is attached to the wrong project, or a gate code is typed in because a driver is waiting. Rules help, but habits help more.

Write down three simple habits for your team and repeat them at the weekly review. Check the name, check the project and check the document list before anything is shared.

What the agent should do with sensitive requests

Tell the agent how to behave when it is asked for something outside its list.

  • Politely decline and name the person who can help.
  • Hand over any request for drawings, software or test data that is not listed.
  • Hand over any message about security, access or an incident.

FAQ

Is it safe to let an agent read partner messages?

It can be, when you limit what it may share, keep the sensitive topics with people and control who reads the chats. Start with low-risk topics such as gates and delivery weeks.

Can the agent send drawings or test records?

Only if you list those exact documents as shareable. Anything else should go to a person, who can check the partner, the project and any restrictions before sending.

What should we do if a message goes to the wrong contact?

Tell your manager at once, ask the wrong recipient to delete it and let the affected partner know. Then find out why it happened and fix the instruction or habit.

More free tools for rail vehicle builders and rebuilders

Read the guide: Keep rail vehicle partner messages moving without extra staff.