Spaces

Message workload planner for plant, terminal and blender teams

This planner works out how many hours a week your team spends answering messages at a refinery, asphalt plant or lubricant blender, from the number of messages, the minutes each takes and the days you work.

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

Before you start

Most plant managers underestimate how much time goes into chats. A slot question here, a sheet request there, a call back about a delivery. Each is only a few minutes, but across a busy day, they add up to hours that dispatch and the office could spend on loading and customers.

Enter a typical day: how many messages arrive, roughly how many minutes each takes to answer, and how many days a week you handle them. The planner shows hours a week, a month and in working days. Use honest figures from a normal week, not your quietest or busiest.

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

Under your figures

Hours a week spent answering18
Hours a month (4.3 weeks)77
Working days a month (8-hour days)9.7

This is an estimate built from your own figures, so the closer your counts are to a real week, the more useful the result.

Reading your result

If the answer is a few hours a week, chats are a small part of the job. If it is closer to a full working day or more, you have found a real cost. That time comes out of loading, safety checks, customer calls and rest.

Look at the busiest mornings too. Averages hide peaks, and the peak is when slow replies cost the most trucks.

Where the time usually goes

In most plants the time sits in a handful of repeated tasks.

  • Slot and availability questions.
  • Requests for safety data and spec sheets.
  • Gate rules, hours and paper checks.
  • Chasing details that were missing from the first message.

FAQ

How do I count messages a day?

Look at your chat history for a normal week and divide by the days worked. If you cannot, ask dispatch to tally for three days and take the average. A rough count is enough.

Should I include messages that need a long answer?

Yes, but use an average. A quick slot reply may take one minute and a technical question may take fifteen. Pick a figure that reflects the mix across a normal day.

What do I do with the result?

Use it to decide where time is being lost. If it is large, look at which repeated questions could have ready answers, and which chats must stay with a person.

More free tools for refiners, asphalt plants and lubricant blenders

Read the guide: Answer terminal, plant and distributor messages around the clock.