What the system sends periodically
Periodic reports for the platform's modules can be sent daily, weekly or monthly. The e-mail contains tables in the body, a PDF attachment with the client's logo and, optionally, an XLSX file. This is enough for a head office that wants to read quickly and also process the figures in a spreadsheet.
The EHS manager therefore does not have to compile a summary by hand from several sources. They do have to decide which modules and which indicators go to the head office, and at what rhythm.
Recommendations for the EHS manager
The recommendations are ordered from the most important. The first concerns indicators, the last concerns language.
Agree the indicator list with the head office
Start with the list the head office already assesses today. If the report contains indicators different from the group standard, you will have to explain them in a conversation rather than on paper.
Match the rhythm to the decisions
A daily report makes sense for events requiring a reaction, a weekly one for current oversight, and a monthly one for comparisons between plants. Sending everything daily leads recipients to stop reading.
Use PDF for reading, XLSX for calculating
A PDF with the plant's logo suits handing over to management. An XLSX is needed by the head office analyst. Enabling both costs little and removes manual retyping.
Check the language of documents and dictionaries
The interface and documents work in six languages, but the dictionaries have an English column in only four cases: types of work, risks, preventive measures and safety signs. The remaining dictionaries display in the language in which they were entered. If the report is to be readable for the head office, local names must be entered deliberately in the target language.
Dictionaries with and without an English column
Limits to be aware of
The report does not change the fact that names entered in the Polish dictionary stay in Polish if there is no equivalent. That is why, before the first sending to the head office, produce a trial report and review it with someone who knows the recipient's language.
Reporting to the head office also does not replace the group's global systems. InnerWeb is an independent complementary system, so data reaches the head office as a summary, not as an integration with its system.
Sample reporting layout
An example for a plant with a head office in another country: a weekly PDF report for management, a monthly XLSX report for the head office analyst, and a daily report only for events requiring a reaction. Each has one recipient responsible for responding.
- Daily: only events requiring a reaction
- Weekly: PDF with the plant's logo for management
- Monthly: XLSX for the head office analyst
How to verify the report before sending it to the head office
Before the first periodic sending, generate a trial report and send it to one person at the head office, asking for comments. Ask three things: whether the indicators are understandable, whether the language of the names is correct, and whether the PDF or XLSX format fits their further work.
After corrections, set the sending rhythm and the recipients. A good practice is a recipient list maintained by one person at the plant, because changes at the head office happen more often than at the plant.
Finally, plan a review of the report after a quarter: which indicators were read and which were skipped. A report nobody opens should be shortened or moved to a less frequent rhythm.
Video
Frequently asked questions
In what formats does the report arrive?
As an e-mail with tables in the body and a PDF attachment with the client's logo, optionally also XLSX.
How often can the report be sent?
Daily, weekly or monthly, for the platform's modules.
Will the head office receive names in its own language?
For the four dictionaries with an English column, yes, provided the values are filled in. Other names display in the language in which they were entered.
Set up reporting to the head office
We will show a periodic report on an example from your plant and agree the rhythm and the format.
Let's talk