InnerWeb
Skip to main content

Use case: Monday report instead of manual summaries

A report on Monday morning, covering the full previous week, can replace tables assembled by hand from emails. We describe a production plant scenario in which the shift supervisor and the plant director receive the same document without anyone working on it at the keyboard. This is a concept based on the features of the reporting module, not a description of a specific client.

5 min
how often the report dispatcher runs
Source: reporting module documentation
90 min
assumed weekly time for a manual summary
Source: sample calculation

Starting point: a summary that eats up Monday

Consider a production plant with several departments and many external contractors on site. Every Monday, someone from the safety or technical department collects data on work permits from the previous week: how many are open, how many are closed, which contractors worked most often, which hazardous tasks took place. The data arrives in emails and spreadsheets, so the summary is assembled by copying and pasting.

This approach has three weaknesses. First, the summary is late, and the director sees a week that ended three days earlier. Second, every person building the tables calculates things slightly differently, so figures from different weeks are hard to compare. Third, the person preparing the report loses time that could be spent on plant walks and conversations with contractors.

Solution: a report rule instead of a spreadsheet file

The reporting module lets you set a recurring report rule for work permits. The rule has a weekly cadence, a day of the week and a sending time, so the report can go out on Monday at a fixed hour. The email body contains tables, and a PDF with the client logo is attached, optionally with an XLSX file.

The weekly report always covers the previous full week, from Monday to Sunday. This matters for the reader: they do not receive data from the middle of a period, but a closed set that does not change after sending because of late entries.

What the work permit report contains

The report shows the number of open, closed and active permits, the median time from opening to closing, a ranking of external contractors, totals per department, and a breakdown of hazardous work by type and subtype.

  • number of permits: open, closed, active
  • median time from opening to closing
  • ranking of external contractors
  • totals per department
  • hazardous work by type and subtype

Issuers table in the weekly layout

In the weekly report, the issuers table shows each person broken down by day of the week. The shift supervisor sees at once on which days the issuing workload was unevenly spread and can plan staffing accordingly. In the daily report the same table is a ranking, and in the monthly report it splits the data by the weeks of the month.

Time spent assembling the permit summary per week

Time spent assembling the permit summary per weekBefore and after chart: manual table assembly takes 90 minutes and 0 minutes with the recurring report, reading takes 15 minutes in both variants.020406080100minManual summary (Assembling tables): 90 min90 minRecurring report (Assembling tables): 0 min0 minAssembling tablesManual summary (Reading): 15 min15 minRecurring report (Reading): 15 min15 minReading
  • Manual summary
  • Recurring report
Source: Sample calculation: 90 minutes of assembly and 15 minutes of reading per week are illustrative assumptions

Who receives the report and in what form

Recipients of a rule are specified by email addresses and by roles. Administrator, supervisor, safety, technical and deliveries administrator roles can configure rules. In the scenario, the shift supervisor and the plant director are both listed as recipients of the same rule, so they read identical figures and the Monday discussion starts from a shared reference point.

The format is chosen per rule: PDF, XLSX or both, in Polish or English. The director may receive a PDF for a quick review, while the safety department also gets an XLSX for its own analysis. The logo is embedded in the email body, so it displays even in mail clients that block remote images.

Dates in the report are written out in Polish words, using one formatter across the email, PDF, XLSX and the panel. This way the same period looks identical everywhere, and there is no dispute over whether a week corresponds to one date or another.

Effect in a sample calculation

We calculate the effect on sample assumptions that every plant should replace with its own. We assume that a manual permit summary takes 90 minutes a week and involves one person, and that after the initial setup the recurring report requires no table assembly. The manual variant therefore costs 90 minutes a week, which comes to about 78 hours a year for assembly alone at 52 weeks.

We do not treat this as a promise of savings. It is an order of magnitude to compare with your own working time. The second effect may matter more: the report keeps the same layout each week, so changes in the figures are visible and not hidden behind formatting differences.

The report does not replace a conversation about safety. It provides audit evidence and shared figures, while the decision on what to change on the shop floor remains with people.

How it fits into existing plant systems

InnerWeb works as an independent system that complements the client's existing systems, such as access control, time and attendance, HR and ERP. InnerWeb reports cover data collected within InnerWeb, so they do not mix with summaries from other systems and do not pretend to cover their scope. This is an advantage during an audit: it is clear where each figure comes from.

The report is sent by a dispatcher that runs every 5 minutes and sends a document only once for a given rule and period. An error in one rule does not stop the others, and switching a rule off with a single toggle pauses sending without deleting recipients or history. In the scenario, this makes it possible to pause the report during a review and turn it back on without reconfiguring it.

Conclusions for the plant

Start by choosing one report, for example the permit report, and set a weekly rule for Monday. Before you enable sending to the director, review the preview in the panel or download the PDF to confirm that the layout meets expectations. Only then add further recipients.

Once the report starts arriving regularly, use the first Monday meeting to discuss one figure rather than the whole table. This rhythm builds the habit of using the data faster than a perfectly prepared but one-off review.

Example calculation

Yearly time spent assembling the permit summary

Assumptions
ParameterValue
Time for manual summary90 min/week
Number of weeks52 weeks
Assembly time after report rollout0 min/week

Result: 78 hours a year on table assembly alone, which the system takes over in the recurring report variant

Note: Sample calculation on illustrative assumptions; each plant should substitute its own time and number of people.

Video

Frequently asked questions

Does the Monday report cover the current week?

No. The weekly report covers the previous full week, from Monday to Sunday, so the data is closed and does not change after sending.

Can the report be reviewed before the first sending?

Yes. You can view the report in the panel preview and download it as PDF or Excel without waiting for the schedule.

What happens if one report rule fails?

An error in one rule does not stop the others. The report for a given rule and period is sent only once, so recipients do not get duplicates.

See the permit report using an example from your plant

We will show a preview of the weekly report and set up the cadence, recipients and format with you. Book a short demo of the reporting module.

Let's talk