Spaces

Message workload planner for terminal and pipeline teams

This planner turns messages a day, minutes per reply and days worked into hours a week, so a terminal or pipeline operator can see how much time chats take.

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

Before you start

Messages arrive in small pieces, so the time they take is easy to miss. Four minutes to find a gate number, check a slot and reply feels like nothing, but forty a day across six days adds up to a whole working day each week. A scheduler is often the one doing it between other jobs.

Put in your own numbers for a normal day, and the planner shows the hours a week and a month. Use it to decide who should answer, when you need extra cover, and whether an AI agent could take the repeated questions and leave your people the decisions.

Every starting figure is an example. Change each one to your own.

Under your figures

Hours a week spent answering16
Hours a month (4.3 weeks)69
Working days a month (8-hour days)8.6

This is an estimate based on your own figures, so use an honest average and not your best or worst day.

How to read the result

The hours a week show how much of your team time goes to chat. The hours a month and the working days help you picture it as a part-time role. If the result surprises you, check your numbers by counting for one real day.

Remember that interruptions cost more than the minutes. A scheduler pulled away from a slot plan has to find their place again, which is why quick questions feel heavier than they look.

Where the minutes tend to hide

Look for these common time sinks.

  • The same question about hours asked by many drivers.
  • Searching for a gate or paperwork rule in several places.
  • Chasing buyers for the volume or date needed for a slot.

FAQ

How do I count messages a day?

Look at one busy and one quiet day and take the middle. Count every separate chat, including quick one-line questions, since each one still takes your attention for a while.

What is a realistic time per message?

Routine questions take one or two minutes, slot requests longer, and disputes much longer. Use an average across the day, and be honest about interruptions.

Does this include phone calls?

No, only chat messages. Add your call time separately if you want the full picture, since many drivers who get no chat reply end up phoning instead.

More free tools for fuel terminal and pipeline operators

Read the guide: Keep fuel distributors and terminal drivers moving with faster replies.