InnerWeb
Skip to main content

Recurring reports for multiple plants: best practices

The group's OHS team wants each plant to receive a report on its own locations, and the board to see a consolidated view in one format, without manual file assembly. Below are practices for setting recurring report rules in InnerWeb: scope, recipients, cadence, resilience to duplicates and data consistency.

34 dni
window of expiring trainings in the training report
Source: client report documentation

How recurring reports work

Recurring reports are configured with rules per product: work permits, employees, notifications, training, deliveries. Each rule has a daily, weekly or monthly cadence. The report arrives by email with tables in the body, a PDF attachment carrying the client's logo, and an optional XLSX. For a group of plants the key point is that there can be many rules, and each has independent settings.

Practice 1: a separate rule per plant and a separate one for the board

The scope of locations and recipients is set separately for each rule. Two reports from the same system can therefore have different areas and different recipients. In a group of plants, create a rule for each plant, with the scope limited to its locations and local recipients, and one consolidated rule for the board, covering all plants.

This way the plant manager does not receive other plants' data, and the board sees the whole without any assembly.

Sample number of report rules in a group of five plants

Sample number of report rules in a group of five plantsBar chart: five local rules and one consolidated rule for the board.012345rulesLocal (1 per plant): 5 rules5 rulesLocal (1 per plant)Consolidated for the board: 1 rules1 rulesConsolidated for the board
Source: Sample calculation: five plants, one training report rule locally and one consolidated

Practice 2: the same cadence and layout for group summaries

For the summaries to be comparable, set the consolidated rules with the same cadence, for example weekly, and with the same set of products. Local reports may have a shorter cadence, for example daily, if the plant manager needs a current view of work permits.

Auxiliary practice: build rule names by the pattern product, plant, cadence. Half a year later the OHS team still knows which rule serves what.

Practice 3: guard against duplicates and disable, do not delete

Report dispatch is idempotent: for a pair of rule and period, the system keeps a dispatch log and does not send the same report twice. Re-running the job will not flood mailboxes with duplicates. Disabling a rule stops dispatch without deleting recipients or history, so a plant that temporarily suspends a report can later resume it without reconfiguring.

Rule of thumb: instead of deleting a rule, disable it. The dispatch history remains as evidence for an auditor.

Practice 4: rely on one date format and one data filter

Reports are fed from system data, excluding service accounts and technical alert templates. Dates in email, PDF, XLSX and the panel come from one Polish-language formatter. For a group this has a practical meaning: the same deadline looks the same in every plant and in every format, so conflicting versions do not appear when reports are compared.

Practice 5: the training report as a supervision tool

The training report shows, among other things, trainings expiring within 34 days and people who entered the plant without a valid training. In a group it is worth setting it for each plant and additionally in a consolidated version. The plant manager has time to renew trainings, and the group's OHS team sees in which plant the list of expiring trainings is longest.

The same OHS checklist can be run across many facilities, and the results are comparable between facilities and periods. The recurring report is the natural channel for delivering these comparisons to the board.

Checklist

Video

Frequently asked questions

Can the same report reach several recipients from different plants?

Yes, but the scope and recipients are set separately for each rule. If recipients should see different scopes, separate rules are needed.

What happens if the dispatch job runs twice?

The report will not be sent again. For a pair of rule and period, the system keeps a dispatch log and skips the duplicate.

Does disabling a rule remove the recipients?

No. Disabling stops dispatch, but the recipients and history remain.

Reports for the group in one format

We will show the configuration of rules for your group: scope, recipients and cadence. Arrange a short report demo.

Let's talk