What a recurring report rule does
Recurring report rules, for deliveries, permits and training among others, generate reports daily, weekly or monthly. The report arrives by email: with a table in the body of the message and a PDF attachment carrying the client's logo. The recipient sees the summary straight in their inbox and has the details in the attachment.
The delivery data behind the report comes from the deliveries module. A delivery has the status active, trailer-only or archived, and closing can happen separately for each driver tag or in bulk for all of them. This matters when reading the report: a delivery closed in bulk and one closed per tag may have different closing times.
The report is a tool for the recipient, not for the administrator. A well-configured one has a single addressee responsible for it, not a list of twenty people each assuming someone else will read it.
Setup in six steps
The plant administrator makes the configuration in the panel. Before you start, agree with the logistics manager what question the report must answer: how many deliveries there were yesterday, how long the stops at the docks lasted, which deliveries became active after the night shift.
- Choose the report type: deliveries.
- Set the frequency: daily for operations, weekly for trend review, monthly for management.
- Enter the email recipients: preferably a shared logistics department address, not private mailboxes.
- Check that the table in the body includes the key columns and that the PDF attachment carries the client's logo.
- Generate a test report and compare the figures with the deliveries panel for the same day.
- Save the rule and, after a week, ask the recipient for comments.
Report rhythm and number of sends in a month (30 days)
Daily, weekly or monthly: which to choose
A daily report makes sense for people who react to yesterday's events: the delivery coordinator, the ramp foreman, the shift manager. It should be short and contain mainly exceptions, because ten ordinary deliveries need no attention.
A weekly report serves comparisons: whether the number of deliveries is growing, whether the distribution across hours is changing, whether a carrier regularly waits longer. This is the best format for a logistics manager who plans unloading windows.
A monthly report is for management and the quality department. It is worth attaching telemetry data from appointment code reads, to see what share of deliveries were handled automatically and what share manually.
Audit evidence and common pitfalls
The recurring report is also evidence for a client audit: it shows that the plant monitors delivery traffic at an agreed rhythm. An archive of sent reports (a shared mailbox with a retention rule) documents this continuity.
The first pitfall is too many recipients. The second is no check: a report whose figures nobody has compared with the panel loses credibility at the first discrepancy. The third is filters that are too narrow, so the report skips deliveries with a trailer only.
Checklist
Video
Frequently asked questions
Does the report have to be downloaded from the panel?
No. It arrives by email with a table in the body and a PDF attachment carrying the client's logo.
Can the report also be sent as XLSX?
It depends on the rule setting. Always check in the test report which attachments the recipient gets.
How often should the delivery report be sent?
Daily for operations, weekly for trend analysis and monthly for management.
Let's set up the report for your logistics
Book a call. We will show the report configuration and match the rhythm to the questions your logistics manager asks.
Let's talk