Heat in the kitchen and on the floor: a temperature, break and drinks log that survives a labour inspection
On 11 August 2026 the Polish National Labour Inspectorate published the first results of heat-wave workplace checks: about 300 complaints by 7 August, gastronomy venues on the list, readings above 30°C and sometimes 35°C. A restaurant, caterer or hotel kitchen does not need another BHP slide. It needs a temperature, break, drinks and rota record you can open in front of an inspector.
11 August 2026 — the National Labour Inspectorate published the first results of inspections of work in hot weather. This is not a teaser that “a limit arrives next year”. It is a field report: during the first heat wave at the turn of June and July 2026, district inspectorates received 212 complaints. By 7 August 2026 the total had risen to about 300. Reports came from halls, shops, hospitals, offices, construction sites and gastronomy premises. If you run a restaurant, a catering kitchen, a food truck, a hotel kitchen or a café chain, those figures are not weather colour. They are your inspection season and your hospitality heat-at-work log — or the absence of one.
Chief Labour Inspector Janusz Krasoń said it plainly: rules on maximum workplace temperatures will apply from the start of 2027, but that does not mean workers are left to extremes today, or that an employer has no duties. Inspectors act on complaints about temperatures that put life and health at risk. One complaint spoke of a hall at 50°C; the reading was about 35°C, plus machine heat, plus a rest room almost as hot as the hall. A crane cab hit 35°C against a 28°C limit. Probably following work in full sun at about 38°C, a paving worker died — the accident investigation is ongoing. We do not stretch those numbers onto your kitchen. We take the operational point: the inspector measures, then asks about drinks, the risk assessment and the summer procedure. A hospitality heat-at-work log either survives that, or it dies in the WhatsApp group named “dishpit_july”.
This piece does not replace an online table-reservation system or a own ordering channel without Pyszne and Glovo commission. Those texts are about the table, the channel and the bill. Here we add the layer the August PIP communiqué will not leave alone: who stood at the range, at what temperature, with which break, with what access to a drink, and with what change to the rota. A kitchen heat-rota programme must show one truth: workstation, time, reading or decision source, break, shortened shift, air-conditioning service. GESOFT — Paweł Matusiak, Laravel, Vue, Android — builds that panel when POS, Excel and three messenger groups fail to join the floor to BHP. If a boxed rota is enough for your firm — buy it.
We do not invent tariff fines and we do not promise that an app “will cool the kitchen”. We do not replace PIP, sanitary inspection, air-conditioning UDT or your bookkeeping. We do not burn a working POS if it already holds one truth about the receipt. You write to contact: how many sites, how many kitchen and floor posts, whether a terrace and delivery are daily, whether seasonal staff live on civil-law contracts. The quote returns in 24 hours. If SaaS is enough — we will say so. If the model is odd (two kitchens, a dark kitchen, hotel plus restaurant, a night pastry shift) — we say you need your own panel, not another valley subscription.
What PIP wrote on 11 August 2026 — and what you must not invent from it
The communiqué is dated 11 August 2026 and closes complaints at 7 August 2026. Those frames are narrow. You must not stretch them into “the whole Polish hospitality summer” or “every restaurant in the voivodeship”. PIP wrote that complaints came from warehouses, supermarkets and malls, production plants (including dairies), hospitals, offices, gastronomy premises and construction sites. It did not say how many complaints fell on HoReCa. If a conference speaker claims “PIP is targeting restaurants”, the communiqué does not say that. It says the tool is general, and a kitchen — ranges, dish pit, terrace — lands on the list naturally when the room reads above 30°C, and sometimes 35°C.
Complainants most often reported excessive temperature, no drinks, and broken or weak ventilation or air conditioning. Inspectors, despite the lack of a general maximum-temperature norm in 2026, measured anyway. In many cases the reading was above 30°C. Where a check did not confirm the report, the matter ended there. Where it confirmed breaches, action was limited to orders where a legal basis existed. That matters for your hospitality heat-at-work log: “it is always hot, it is a kitchen” is not an answer. You have to show what you did with drinks, the risk assessment, ventilation service and the summer procedure — and when you did it, not “around July”.
PIP also lists the effect of inspections, not only the sin. After intervention, employers gave unlimited drinking water, air-conditioned rest areas, extra breaks, shorter hours, weather-appropriate clothing and footwear, window screens, fans and portable AC units, drinking-water containers, and noticeboards on first aid for heat stroke. That is your operational catalogue for August and for every future heat wave. A kitchen heat-rota programme must write those decisions against the shift, not into the head of a shift manager who is driving to the second site on Friday.
- 212 complaints during the first heat wave at the turn of June and July 2026, via the hotline and direct to district inspectorates.
- About 300 complaints in total by 7 August 2026 — the communiqué gives neither an exact total nor a split by industry.
- Checks were opened on most complaints; nearly one third were closed by the communiqué date, the rest were in progress or scheduled.
- A complaint of 50°C on a hall: a reading of about 35°C plus machine heat; the rest room almost as hot.
- A crane cab at 35°C against a permitted 28°C limit — an example of a post that already has a hard cap today.
- Death of a paving worker at about 38°C in full sun: PIP speaks of a probable link, the accident investigation continues — we do not treat the cause as settled.
- Readings in inspected rooms often above 30°C, sometimes 35°C, despite the lack of a general maximum limit in 2026.
- Gastronomy premises are on the list of activities from which reports came — with no published count of HoReCa complaints.
We quote those figures only from the PIP communiqué of 11 August and from press copy based on PAP (including TVN24). We do not add an “average restaurant fine”, a “share of venues without water”, or “how many checks end in a ticket”. PIP did not write those on 11 August. A vendor who puts “we will cut BHP risk by 80 percent” in a proposal is selling weather. You are buying a dossier: a reading or a decision to stop the shift, a drinks list, a risk assessment, AC service, a rota annotated with a shortened day. If you want to see how we join the same shift to the table and to no-shows, go back to what an empty hour costs — this article is about the layer PIP is now touching with a thermometer.
Kitchen, dish pit and terrace: why gastronomy venues sit in this communiqué
A kitchen is not an office with a fan. It is a heat engine: ranges, fryers, salamanders, tunnel dishwashers, a convection oven running two banquets. A terrace in full sun at 13:00 is open-air work, not “an exception because guests want to sit outside”. Delivery in a heat wave is another job that does not appear on the floor rota. A hospitality heat-at-work log must distinguish posts. An inspector will not buy “our average is 29, so we are fine”. They will buy a map: hot kitchen, humid dish pit, air-conditioned dining room, unshaded terrace, windowless back office. If that map is not in the system, it lives in the head chef’s head — and on Saturday the head chef is not giving evidence. They are cooking.
PIP did not write that gastronomy is industry number one. It wrote that gastronomy premises are on the list. That is enough to stop treating heat as “a season you wait out with tap water”. A complaint goes through the hotline or the inspectorate. It can come from a cook, a waiter, a student on a mandate contract, a former employee. Your defence is not “hospitality is always hot”. It is an up-to-date risk assessment, drinks in quantities matching need, working ventilation or a documented breakdown and a plan B, extra breaks written into the rota rather than promised “when it is quiet”. A kitchen heat-rota programme holds those facts against the person and the post.
Venue practice is brutal. On Friday at 18:00 you have 40 covers, the kitchen is on two emergency hobs, dining-room AC blows on guests, and the dish pit is 34°C with zero breaks because “there is no one to cover”. The inspector does not grade your Google reviews. They grade whether heat-wave work organisation existed before they walked in, or was born in panic when you saw the badge. If a decision to shorten the shift lives only in an SMS to a student, you do not have a decision. You have a trace that is hard to assemble into a dossier. A table-reservation system can tell you 13:00 is full. It will not tell you that at 13:00 you must not keep a waiter on the terrace with no shade and no rotation.
- Hot kitchen: ranges, fryers, convection ovens — a heat source independent of the weather outside.
- Dish pit: steam, humidity, often the worst microclimate in the venue and the thinnest staffing.
- Dining room: AC for the guest is not automatically protection for the person at the till and at the pass.
- Terrace and garden: open-air work, with drinks and shade thresholds counted differently from a room.
- Hatch and pass: a post in a stream of hot air from the kitchen, often with no reading of its own.
- Delivery by bike or scooter: a job in full sun that the floor plan does not show.
- Night pastry and hotel bakery: a shift when it is cooler outside, but the ovens still heat.
- Food court and dark kitchen: several brands, one hall, one AC plant, three rotas in three spreadsheets.
We do not transfer a 50°C production-hall reading onto your venue. We do not say the kitchen “must be 35”. We say: if you do not measure and you do not record the decision, you do not know. PIP on 11 August stressed that readings were taken anyway. Your hospitality heat-at-work log need not be a laboratory. It must be honest: who measured, where, at what time, what followed for the rota. The rest is BHP theatre on the guest-entrance board.
28°C, 25°C and water: a duty a photo of a bottle in the group chat will not discharge
The rules on preventive meals and drinks — which PIP restates during heat waves — require an employer to provide free drinks when workplace temperature exceeds 28°C, and 25°C for outdoor work. Drinks must be available throughout the duty, in quantities matching need, at a temperature suited to the conditions. That is not “we put a shrink-wrap pack by the dish pit in July and take a photo”. That is continuity. If the water runs out at 16:00 and the shift runs to 23:00, you did not provide drinks. You provided a prop for the first two hours of an inspection that had not yet happened.
On PIP’s list of the most frequent irregularities sit failure to provide drinks and the lack of records of consultation on that point. The second sentence is worse than the first. The water may have been there. What is missing is a trace that you agreed type, place and method with the crew, not with the drinks wholesaler. A hospitality heat-at-work log should bind the 28/25 threshold to a decision: from which hour water is mandatory at which post, who tops it up, where it stands, whether the terrace has its own point or the waiter runs to the dish pit. The inspector asks the waiter, not the owner. A waiter who says “I don’t know, the boss says it is in the fridge” ends your story about a procedure.
Terrace and delivery count more strictly. 25°C outdoors is not “a light heatwave for Instagram”. It is the threshold from which drinks are mandatory for open-air work. An unshaded garden, a south-facing frontage, tarmac under the tables — that is a workstation, not décor. If reservations release the terrace at noon with no staffing cap and no rotation, you are selling a table at a person’s expense. A kitchen heat-rota programme will not replace a parasol. It will record that at 13:00 two people work the terrace on a 45/15 rotation, not one person for the whole shift “because that is how the weekly rota came out”.
We do not quote a fine amount, because the 11 August communiqué does not give one. We do not threaten “prison for no water”. We threaten what PIP wrote: orders where there is a basis, and a catalogue of remedies employers already put in after checks — unlimited water, containers, extra breaks, shorter hours. That is cheaper than the myth that “it will be fine until September”. If you need to join drinks to hours of people on mandate contracts, see also the civil-law contract register after PIP’s 18 August communiqué — in a hospitality season those two topics sit at the same table.
A risk assessment that cannot still carry the date from the previous venue
The most frequent irregularity in the PIP communiqué is no occupational risk assessment, or a stale one, at workstations. In a venue that switched the menu to grill, opened a garden, added a pizza oven or moved to a dark kitchen, a 2019 assessment is a folder ornament, not a document. Heat is a factor you must write in at the kitchen, dish pit, terrace and delivery: heat exposure, solar radiation, dehydration, hot surfaces, rushed work at high temperature. A hospitality heat-at-work log does not replace the risk assessment. It feeds it: readings, internal complaints, AC failures, days with a shortened shift.
A risk assessment nobody showed the crew does not work. A waiter must know where the shade is, where the water is, when they may leave the terrace, whom they call at the first signs of heat stroke. After inspections PIP praised noticeboards on first aid for heat stroke. A board without training is a poster. Training without a date and an attendance list is an anecdote. Your panel can hold: the assessment version, the review date, the posts, the list of people briefed, the next review date after the garden opens. That is not a “compliance module from a brochure”. It is the document the inspector will ask for second, after the rota.
The h3 below is not decoration. Ranges and the dish pit tempt the line “this is a technological process, so limits do not apply to us”. From 11 January 2027 the ordinance on maximum temperatures does provide exceptions where temperature comes from the process and cannot be lowered. A kitchen is not automatically that process in full. The dining room, terrace, till, pass, changing room, manager’s office — still less so. You must not, in August 2026, hide behind an exception that is not yet in force, and behind an exception that will not cover the whole venue anyway. A kitchen heat-rota programme splits posts, instead of stamping “HoReCa = hot” on everyone.
Ranges and the dish pit are not a technological exception to every inspector’s question
The ordinance of the Minister of Family, Labour and Social Policy of 9 July 2026 (Journal of Laws 2026 item 927), described by PIP on 10 July, enters into force on 11 January 2027. A 35°C cap in the workroom and 32°C for heavy work in the open air, plus 28°C / 25°C thresholds for technical or organisational measures. Exceptions exist. They are not a hatch that says “a kitchen may always be 40”. They are a narrow clause for what the process cannot cool. Until January 2027 you have half a year to stop pretending that a kitchen reading is a fad. An inspector in 2026 measures despite the lack of a general cap. In 2027 they will have a hard number. Your register either grows up first, or it grows up in January under pressure.
11 January 2027: 35°C, 32°C, and what you must rehearse in this season
PIP on 10 July and the 11 August communiqué say the same thing in two voices: new caps from the start of 2027, duties already today. From 11 January 2027 temperature caused by weather conditions must not exceed 35°C in workrooms. For heavy outdoor work the stop threshold is 32°C (energy expenditure above 1,500 kcal for men and 1,000 kcal for women per shift). Once exceeded — the work must not be performed, with the exceptions in the ordinance. A kitchen in August 2026 that cannot shorten a shift or close a terrace will not “implement the cap” in January 2027. It will implement panic.
Before you reach a stop, the ordinance requires earlier reaction. Above 28°C in a workroom (and 25°C for heavy work indoors) the employer must provide technical measures that lower or limit the rise — unless technological reasons prevent it — or organisational measures that minimise the effect on health, depending on the work. Outdoors the organisational threshold is 25°C. Measures are set after consultation with the BHP committee or, if there is none, under Art. 237¹¹a of the Labour Code after an occupational-health physician’s opinion. Then you inform the crew in the manner used at the establishment. A hospitality heat-at-work log is where those consultations, decisions and notices stop dying in an email to the bookkeeper.
You rehearse now, not on 10 January. Closing the garden after 14:00, rotating waiters, shortening prep at 35°C in the kitchen, moving a banquet indoors, refusing 80 covers on the terrace at noon — those are decisions that hurt take. That is why they must sit in the reservation system and the rota, not in “the manager’s common sense, who was not in”. If your own ordering channel releases lunch at 13:00 with no kitchen cap, and the rota cannot add a break, you have a clash of aims: take versus BHP. The inspector will not bill you for reviews. They will bill you for organisation. A kitchen heat-rota programme must show that clash before Saturday, not after a complaint.
- From 11 January 2027: max 35°C in the workroom (temperature from weather conditions).
- From 11 January 2027: max 32°C for heavy work in the open air (energy-expenditure thresholds from the ordinance).
- Earlier action threshold: 28°C in a room, 25°C for heavy indoor work, 25°C outdoors.
- Consultation with the BHP committee or Art. 237¹¹a Labour Code plus a physician’s opinion — then notice to the crew.
- Exceptions exist (including some work under Art. 151¹⁰ of the Labour Code, nursery care, officers, technological process) — they are not a general HoReCa waiver.
- Until the cap arrives, drinks at 28/25, the risk assessment, BHP and the right to stop work in the face of danger still apply.
- Source of dates and thresholds: PIP “New duties of firms during heat waves” (10 July 2026) and Journal of Laws 2026 item 927.
We do not promise that a panel will “close the venue by itself at 35°C”. Closing the venue is the owner’s and manager’s decision, with consequences for bookings and staff. We promise the decision will carry a timestamp, an author, the list of people on the shift and an effect on the rota. That is the difference between an inspection you survive and an inspection in which everyone tells a different story. GESOFT does not replace the ordinance. We wire it to your Saturday.
Shift rotas, extra breaks and shorter hours — one truth, not three spreadsheets
After inspections, employers introduced extra breaks and shortened hours for people exposed to high temperatures. In hospitality that sentence costs more than in an office. Cutting a cook’s Friday-night shift by an hour means a second cook, or a menu item killed, or a queue and a furious floor. If that decision is not visible in the rota, the POS and the bookings at once, you took a BHP decision and sabotaged it with take at the same time. A kitchen heat-rota programme has one timeline: person, post, planned shift, actual shortening, reason (reading, summer procedure, AC failure), who approved it.
Three spreadsheets are the Polish venue standard. One with the floor manager, one with the head chef, one with the bookkeeper for hours. In a heat wave a fourth appears: a scrap that says “we cut the dish pit today”. The inspector will be handed the prettiest one. The crew will describe the one that actually ran. The gap is your case. A hospitality heat-at-work log lives in the same panel as the hours, or it does not live. An Android app for the shift manager — not for the IT department — lets you add a dish-pit break at 15:40 before someone “remembers on Monday”. GESOFT builds that in Laravel and Vue, with a phone in a grease-stained pocket, not a desktop nobody opens during service.
Rotation on the terrace and at the pass must be a rule, not goodwill. Forty-five minutes in the sun, fifteen in the dining room. Or 30/30. You set the rule after consultation, you write it down, you announce it. The system watches that at 14:00 the terrace is not still staffed by the person who started at 10:00. If your boxed rota can only do “shift 10–18” and cannot do post rotation, you do not have a heat-wave tool. You have a calendar. A calendar will not survive the inspector’s question: “how did you run the summer procedure on 7 July?”. The answer “by feel, depending on covers” is honest and not enough.
- One person card: employment contract, mandate or B2B — no mixing in a single row labelled “kitchen help”.
- Post by the hour: kitchen / dish pit / floor / terrace / delivery / pass, not a generic “hospitality”.
- Planned shift and actual shift: shortening with a reason and an author of the decision.
- Extra breaks written in, not “when it is quiet” — with start and end times.
- Terrace and pass rotation as a shift rule, not a waiter’s request.
- A link to bookings: a terrace staffing cap, a closed slot, a message to the guest.
- A link to POS: menu items switched off when hands disappear after a shortened shift.
- A day export for the inspector: PDF or sheet with person, hours, breaks, heat annotation.
We do not burn a working rota if it is already the only truth about the shift. We burn the chaos in which the truth lives in three places. If Traffit, Contova or another SaaS already joins your venue — stay. If it does not join the terrace to the kitchen and to the drinks, you write to contact. In 24 hours we will say whether we add a layer, build a panel, or it is enough that you tidy the spreadsheet. The third answer is also a quote. Better than another subscription nobody will open during service.
Bookings, no-shows and heat: when you do not take a table at one o’clock
Heat is the one day on which an empty terrace table can be cheaper than a seated one. The guest wants shade. The waiter wants not to faint. The kitchen wants not to fry itself on two woks. If the reservation system cannot close the garden, shorten a slot or force a terrace covers cap, BHP loses to the calendar. That is the same clash we described at no-show and the cost of an empty hour — with a different rate: here you pay with crew health and complaint risk, not only with take. A hospitality heat-at-work log without a latch on bookings is a diary nobody reads at the moment you must tell a guest “no”.
The guest message must land before the door. SMS, email, website: “terrace until 15:00 or until withdrawn, dining room air-conditioned”. If you have your own ordering channel, the same message goes to delivery: longer times, fewer zones, a courier break. Platforms such as Glovo and Pyszne will not wait for your summer procedure — and they will bill commission on the chaos, which we count in the real cost of Glovo, Pyszne and Uber Eats commission. Your own panel can switch off terrace lunch without switching off the whole venue. A boxed reservation widget often knows only “open / closed”. In a heat wave that is too little.
Shortening the kitchen by an hour must cut the last slot. If the last booking is at 22:00 and the kitchen ends at 21:00 because it is 34°C, you have a lie in the calendar. The guest will come. The crew will stay. An inspector, if they hit that night, will see the split. A kitchen heat-rota programme joins the BHP rule to the table rule. That is not “innovation”. It is closing a door you cannot close by hand on Friday at 16:00 when the phone rings and Instagram is on fire. GESOFT joins this to table reservations if we build you that stack. If you already have a reservation product that can do it — we do not touch it. We add the BHP latch.
KSeF, the catering invoice and a number the kitchen will not type from memory
Heat does not suspend invoices. From 1 February 2026 large taxpayers issue through KSeF, from 1 April 2026 the rest — with a deferral for the smallest until 2027, while receiving invoices in KSeF already covers a wide circle from February. A banquet in a heat wave, an emergency AC unit from the wholesaler, water by the pallet, Saturday ventilation service — those are documents someone must join to the site, the shift and the breakdown. If the AC service invoice lives in the manager’s drawer, and the hospitality heat-at-work log says that on 7 July the AC “worked”, you have a contradiction that shows up faster than in an audit. The duty is set out in KSeF 2026 in a company application. Here only this: a KSeF number will not rise from a cook’s memory.
We do not replace KSeF.gov or your accountancy office. We join the operational event to the document: failure → service call → invoice received → a note on the day you shortened the shift “because the AC died”. A BHP inspector is not a bookkeeper. A bookkeeper is not an inspector. If those two people get two histories, both are true in their own spreadsheet and both are unbelievable together. The panel GESOFT puts on Laravel does not “send JPK for you”. It holds the key: day, site, event, document. The rest stays in the accounting pack you already have. If that pack is enough and BHP lives in a binder — stay with the binder. If the binder vanishes between sites, you write to contact.
An invoice for pallet water and portable fans is not a “soft” cost. It is proof that after a check, or before one, you did what PIP lists as the effect of intervention. Without a link to the day and the site it is a cost. With a link it is a dossier. A kitchen heat-rota programme need not be a KSeF module. It must be able to take a number and a PDF from accounts or from your accountancy office and pin it to the event. Three clicks. No heroics.
Civil-law contracts in season: a waiter on a mandate next to a hot range
A hospitality season lives on mandate contracts, specific-task contracts and “weekend help”. On 18 August 2026 PIP published the first results of checks on whether a civil-law contract was the right choice after 8 July. We do not mix that communiqué with the heat figures — it is another publication, another scope. We mix them operationally: a person on a mandate who is given a rota, an apron, a post at the range and orders from the shift manager is not outside BHP just because the file has a civil label. Heat does not ask for the insurance-title code. It asks whether they drink, whether they have a break, whether they may leave the terrace. The wider contract register is in the article on PIP checks of civil-law contracts. Here: your hospitality heat-at-work log must cover every person on the shift, not only employees.
A student in the July dish pit is the weakest link in the dossier. They do not know the procedure, because nobody showed it. They do not know where the risk assessment is. They are afraid to ask for a break, because “if they complain, they will not be taken in August”. The inspector will hear that first. Your panel must show: the date they were briefed on the summer procedure, the post, the hours, the drinks, who was shift manager. If you cannot show that for a mandate, you cannot show it for an employee — employees simply stay silent longer. We will not reclassify the contract for you. We do not replace PIP. We record facts that will come out anyway.
A rota that hides a mandate under the label “extra” is worse than no rota. Absence is obvious. Concealment is a story you cannot defend. A kitchen heat-rota programme shows the basis: employment contract, mandate, B2B. Each with its own card, the same temperature at the dish pit. If a boxed ATS or payroll pack will not swallow that together with the POS — that is the moment SaaS stops fitting, which we describe honestly in boxed software versus custom software. Your own panel (Laravel, Vue, Android) exists so that card does not need a third system.
Android for the shift manager instead of the “heat_july” group
A shift manager does not sit down at a laptop at 14:00 on Saturday. They stand between floor and kitchen, with a phone in a greasy pocket. If a hospitality heat-at-work log requires a login to a panel nobody will open at the pass, you do not have a log. You have an IT project. An Android app: a reading or a declaration “summer procedure on”, a dish-pit break, a shortened terrace, an AC failure report, a photo of the thermometer at the post, the list of people on the shift. Server time, not “I will send it this evening”. PIP does not ask about the framework. It asks whether the trace was born during the event.
A photo of a thermometer is not an accredited laboratory reading. It is a trace that someone looked and took a decision. Better than nothing, worse than a sensor that writes to the database every 15 minutes. We do not promise sensors if you are not ordering them. We promise a place for the reading, the author, the post and the effect. If you already have temperature monitoring from a refrigeration firm, we do not burn it — we take the reading or a CSV. If you have nothing, we start with the manager’s declaration and a photo. That is ugly and enough for the first season, provided there is one place of truth.
A messenger group dies at an inspection. Scroll, no author, no server time, jokes, stickers, “there is water”. The inspector will not read it. A kitchen heat-rota programme exports the day: 12 events, 8 people, 3 breaks, 1 failure, 1 shortening. PDF. No memes. GESOFT puts that up as an application, not as “a Slack channel with a bot”. A bot will not sign a decision to close the terrace. The shift manager will.
Ventilation, air conditioning and service: jobs the inspector will ask about after the reading
On PIP’s list of breaches: AC and ventilation failures or too little capacity, no devices cutting solar load, failure to run internal procedures for work in the summer period. That last sentence kills venues with a beautiful BHP book. The procedure existed. Nobody switched it on on 2 July. A hospitality heat-at-work log must have a switch: “summer procedure active from – to”, with a list of duties (water, rotation, no terrace at noon, window screens). Without the switch the procedure is a PDF in a folder named “to_print”.
Hospitality AC service fails in the worst week. The firm will come “in a few days”. You are left with 34°C in the dining room and with guests. After inspections PIP noted: portable AC units, fans, window screens, temperature control. Those are actions you must order, receive, pin to the day. A service job with no status in the panel is a scrap of paper with a manager who has gone to the second site. The field app we know from field service works in reverse here: you are the client, not the crew. The status “waiting / on the way / done / not today” must sit against the site, not in the “office@” inbox.
- Asset card: dining-room AC, kitchen extract, dish-pit ventilation, air curtain, portable AC unit.
- Date of last service and date of next — not “sometime in spring”.
- Failure report: who, when, symptom, temperature at the post at the moment of the report.
- Service status and document number (KSeF or invoice) after the job.
- Plan B while it is down: shortening, terrace closed, portable kit, refusal of bookings.
- Window screens and garden shading as procedure items, not seasonal décor.
- Confirmation that the summer procedure was switched on, not only written.
We do not service air conditioning. We are not UDT. We record that someone called, someone arrived, someone did not, and what you did with the crew in the meantime. That is exactly the layer that is missing when the inspector asks “what did you do on 7 July in the afternoon”. The answer “we were waiting for service” with no time of the call is empty. With a time — it is a history.
GDPR, a cook’s complaint and retention of temperature readings
A reading at the post, a thermometer photo, a list of breaks, an internal complaint, medical data after a faint — those are not the same set. A hospitality heat-at-work log holds data on working conditions and working time. It does not hold a medical record in the same field as the dish-pit temperature. If someone fainted, the accident file and occupational-health paperwork go their own way. The panel may have a flag “BHP event — file outside the operational system”. It must not have a sick-note scan in the same gallery as thermometer photos. The wider frame is in GDPR in web applications. Here: retain readings for the season plus as long as you need for an inspection and a dispute, not “for ever, because disk is cheap”.
A complaint to PIP may come from a former waiter. Your logs are not for hunting them. They are for showing that on 7 July the water was there, the break was there, the terrace had rotation. If the logs are for “working out who informed”, you have a problem larger than heat. GESOFT does not build a revenge tool. It builds a dossier. Permissions: the shift manager enters the event, the owner sees the export, the bookkeeper sees hours, BHP sees readings. A waiter does not edit history. An administrator does not delete a day because “it looked bad”. Deleting a day before an inspection is worse than having no day.
Passwords, 2FA, sessions — a kitchen is not a bank, but a panel with hours and complaints is a target. Phones in the dish pit vanish. The manager’s account cannot be “1234”. That is an obvious point venues dislike, and which we describe in 2FA authentication in Laravel. We do not spend three paragraphs on ransomware scares. We say: one shared login on the till tablet ends with nobody knowing who entered the break. The shift manager’s signature must be a signature, not the venue PIN.
Boxed POS, boxed rota or your own panel: when not to burn what already works
If the POS counts bills, reservations hold the table, and the rota more or less closes the month — we do not burn that. We add a heat and BHP layer, or we wire an API, or we say outright: tidy the summer procedure in what you have. GESOFT does not live off every venue needing custom software. It lives off the moment the model no longer fits the box — two kitchens, hotel plus restaurant, a dark kitchen, three tax IDs, a seasonal army of mandates — and the box starts lying. Then Laravel, Vue and Android, Paweł Matusiak, a quote in 24 hours at contact. If the box is enough, we will say so. That sentence is in every text of ours because it is true.
SaaS works when the process is standard: one dining room, one terrace, employees plus two students, AC that works. It fails when you need post rotation, a shortening linked to a booking slot, a mandate card next to an employee, AC service and a KSeF number on the day. Then the “BHP module” in a boxed product is a checklist once a year. A kitchen heat-rota programme is a July tool. The difference is like a fire extinguisher on the wall versus an evacuation procedure someone fires. We do not sell the extinguisher. We sell the firing, if you need it.
A mid-season migration is foolish if it does not have to happen. A heat layer can be thin: an events table, a manager app, a day export, a latch on bookings. POS stays. The till stays. Accounts stay. That is our default scenario. The scenario “we replace your whole stack” is rare and dearer, and we raise it only when the stack lies every day, not only in a heat wave. The wider bill is in what a Laravel application costs. Here: we do not price a “hospitality transformation”. We price a dossier that will survive an inspector and a Saturday.
What GESOFT does not replace and what we will not promise at an inspection
An application will not cool the kitchen. It will not sign a risk assessment in place of a BHP specialist. It will not be a witness in an accident investigation instead of you. It will not “reclassify” a mandate. It will not issue an e-invoice instead of KSeF. It will not be sanitary inspection, PIP, the fire service or an air-conditioning firm. A hospitality heat-at-work log is a layer of facts. You either have the facts or you paint them. Painting comes out with the first waiter who tells the truth. That is why we do not sell a “PIP compliance certificate”. We sell order you can show.
- We do not replace the National Labour Inspectorate, sanitary inspection, UDT or occupational health.
- We do not replace KSeF.gov, e-Deliveries, JPK or your accounting programme.
- We do not replace the tachograph, BDO.gov or systems the law requires as official.
- We do not burn a working POS, reservation system or payroll pack if they hold one truth.
- We do not invent fines, ticket rates or an “average hospitality inspection” that is not in the communiqué.
- We do not promise that AI will plan breaks and close the terrace by itself.
- We do not build a tool for hiding shortened shifts or deleting a day.
We promise an answer in 24 hours at contact: whether SaaS is enough, a layer on your stack, or your own panel. We promise operational language, not a transformation slide. We promise that if the model is simple, you will hear “buy a boxed product”. That is not a hook. It is a saving of your August.
A 90-day checklist: from the PIP communiqué to a dossier you can export
You do not have 90 days until January 2027. You have 90 days to stop pretending the next heat wave “will somehow pass”. The 11 August communiqué is mid-season, not the end of it. The list below is not a statute. It is operational order an inspector will understand, because it repeats what PIP itself listed as remedies after checks: water, rest, breaks, shortening, clothing, screens, fans, heat-stroke information. A kitchen heat-rota programme should hold that list as states, not as a poster.
- Days 1–7: a map of posts (kitchen, dish pit, floor, terrace, delivery, pass) and a thermometer someone can actually read.
- Days 1–7: water at every post, including terrace and delivery; a record of who tops it up after 16:00.
- Days 8–14: review the risk assessment — are heat and sun written in at the terrace and kitchen, or is it a copy from the previous venue?
- Days 8–14: a one-page summer procedure: thresholds, breaks, rotation, who may shorten a shift, who closes the terrace.
- Days 15–30: the rota learns shortening and an extra break with a reason; no more scrap paper in the dish pit.
- Days 15–30: bookings can close the garden and cut the last slot when the kitchen finishes early.
- Days 31–45: AC and extract card: last service, failure, plan B, invoice number.
- Days 31–45: mandates and employees on the same shift are visible, with no “extra” hiding.
- Days 46–60: manager Android: the event during service, not in the evening at home.
- Days 46–60: a PDF day export — 15 minutes on the table for the inspector.
- Days 61–75: consultation of organisational measures with the crew (or the BHP committee) and notice in the usual way.
- Days 61–75: heat-stroke training with an attendance list, not only a poster.
- Days 76–90: an internal dummy inspection: a stranger asks a waiter about water and a break. You note what falls over.
- Days 76–90: a decision: you stay on SaaS, you add a layer, or you write for your own panel at contact.
Ninety days will not fix an oven that runs too hot. It will fix the lie that “it cannot be recorded”. It can. The question is whether you record it in a group chat or in a system. A group will not survive January 2027, when 35°C stops being an opinion. A system you rehearse in August will. That is the only reason this text is long: so you do not implement the cap on the day it arrives.
How to order a quote so that a 24-hour offer is not a guess
At contact we do not need a deck. We need: number of sites, posts (terrace, delivery, dark kitchen, hotel), how many people on the peak shift, employees versus mandates, which POS and which rota today, whether AC has a service history, whether bookings can close the garden. Plus one sentence: what hurt in this heat wave. If nothing hurt and you only want “a BHP module for later” — write that too; we may say a procedure and a thermometer are enough. Not every quote ends in a build. It ends in an honest answer in 24 hours.
- How many sites and how many kitchens — not “a HoReCa network”, the number of doors.
- Whether a terrace / garden / food truck / delivery is on the daily rota.
- How many people on a Friday-night shift and how many of them on a mandate.
- Which POS, which reservation system, which rota — names, not “some programme”.
- Whether the risk assessment is newer than the garden opening.
- Whether anyone has already filed a complaint or whether there was a PIP / sanitary inspection this season — no medical detail.
- Whether KSeF and bookkeeping sit with you or at an office — so we do not promise a second accounts pack.
The quote will have a scope: a heat-event layer on your stack, or a rota panel and Android, or “stay with the boxed product, here is a checklist”. Price depends on the number of sites and on whether we join bookings. Not on the number of slides. If you stay silent about mandates, the quote will lie. If we stay silent about SaaS being enough, the quote will also lie. We prefer a first conversation that ends “do not build”. We can also do the second one, which ends in work.
The inspection dossier: what you put on the table in the first fifteen minutes
An inspector does not want a webinar. They want: the risk assessment, the summer procedure, the day’s rota, proof of drinks, readings or decisions, ventilation service, the list of people on the shift with the basis of engagement. A hospitality heat-at-work log is the clip for those papers, not their replacement. If the clip needs three logins and a plea to the bookkeeper to “send the hours”, you do not have a clip. You have a corridor problem. The panel exports a day and a week. The manager does not call their spouse for the Dropbox password.
Fifteen minutes is not theatre. It is a test of whether the truth is one. If a waiter says “there has been no water since noon” and the export shows top-ups at 11:40 and 15:10, you have a conversation. If the export is silent, the waiter wins. We build a system in which the waiter may be right — and then you fix the water, not the log. A system that always defends the owner is useless at an inspection and dangerous in court. GESOFT does not write your testimony. It holds a timestamp. The rest is yours and your lawyers’, if you call them.
We do not attend the inspection for you. We do not “handle PIP”. If someone promises you that, you are buying theatre. Buy a dossier and a BHP person who can speak. The tool should stay silent when it does not know, and speak when it does. That is the only honest position for a software vendor on the day a badge stands in the door.
Working with BHP and the accountancy office without a third truth in email
A BHP specialist needs posts, readings, a people list, a training date. A bookkeeper needs hours, shortenings, allowances, invoices for water and service. A manager needs tomorrow’s rota. Three truths in three emails end with pay hours that do not match inspection hours. A kitchen heat-rota programme is a third place only if it is the first: BHP and accounts take an export, not the other way round. The accountancy office stays an office — see software for an accountancy office. We do not build a second accounts pack. We build a tap from which accounts and BHP drink the same stream of hours.
e-Deliveries are not a heat topic, but they are an inspection topic. A letter from the district inspectorate, a summons, a complaint — if the ADE box lives with the bookkeeper and the venue learns three days later, you have lost a deadline, not the merits. The e-Deliveries timetable is on gov.pl. The panel can hold a copy of the letter and the read date against the site. It does not replace the box. It signals that a letter landed. In a multi-site group that is the difference between a reply and silence.
If you have a law firm for employment matters, give them an export, not permission to delete. The firm writes the letter. The system holds the facts. Mixing those roles ends with a letter that describes a procedure the crew has never seen. The inspector listens to the crew. The crew does not read law-firm letters. A hospitality heat-at-work log is a day tool for the crew and an attachment for the firm. In that order. The reverse order is LinkedIn compliance.
What we do not transfer from the PIP communiqué onto your venue — a ban list for numbers
You must not — and we must not — say that “300 complaints are gastronomy”. 300 is the total to 7 August, many industries. You must not say that “every third restaurant inspection ends in an order”. The communiqué says nearly one third of all opened checks were closed, with no industry outcome. You must not say that the paving worker and the crane are “the same as a wok”. Those are the Chief Inspector’s examples from other posts, quoted to show the scale of heat in the country, not to stick someone else’s tragedy on you. A hospitality heat-at-work log rests on your posts. Other people’s figures are context, not your KPI.
You must not say that from 11 January 2027 “we always close the kitchen at 35°C”. The ordinance speaks of temperature caused by weather conditions and of exceptions, including the technological process. A kitchen has ranges. The dining room does not. The terrace does not. The till does not. Mixing those posts into one cap is convenient and false. You must not say that an application excuses you from consulting the crew. The ordinance requires consultation of organisational measures. The panel records the result of consultation. It is not the consultation.
You must not say that GESOFT “passes a PIP inspection for the client”. It does not. The client passes or does not, with facts or without. We supply a place for facts. If you do not enter the facts, the place is empty and the quote was wasted. That is why in 24 hours we would rather say “do not build, buy a thermometer and write a one-page procedure” than sell a panel nobody will feed. We leave that sentence at the end because it matters more than the SEO phrase.
The cost of August chaos: not an invented fine, but take, overtime and a complaint
Since we do not invent a ticket, let us name the cost you already pay. A shortened shift with no record ends as an unpaid hour, or an hour paid “on a nod”, or a grievance in August and a complaint in September. Closing the terrace with no latch in bookings ends with guests at the door and a crew that stays “just a moment more”. An AC failure with no ticket in the system ends with service arriving after the banquet, not before. Those are not PIP figures. They are your nights. A kitchen heat-rota programme does not remove heat. It removes the double lie: to the guest, that you can cope, and to the crew, that “tomorrow will be quieter”.
No-show in a heat wave has another face: the guest drops the terrace at the last minute because the city is 35°C, and you still hold the staffing. Or the reverse: the guest arrives, staffing is gone, because someone left after a faint you did not record. An empty hour in a salon and a restaurant is about the table. Here we add the table that should not have been sold. That is dearer than a no-show. A no-show leaves food in store. A bad slot leaves a person in the sun. A system that can refuse to sell a slot is a BHP tool, not only marketing.
A chain of two or three sites multiplies chaos by the number of doors. A procedure written at the first site does not reach the third. The manager of the “young” site does not know the garden may be closed. Android and a shared database exist so the summer procedure is not the owner’s lore. If chain SaaS already gives you that — stay. If each site has a different spreadsheet, you do not have a chain. You have several firms under one tax ID. At contact you write the number of doors, not a dream about an app. The 24-hour quote will be about doors.
How not to play laboratory: a reading that defends a decision, not a scientific paper
PIP measured, despite the lack of a general cap. You do not need a certified logger to decide to stop the terrace. You need a rule: from which value on the terrace thermometer you switch rotation on, from which you close, who reads, how often. Rule written. Reading written. Decision written. That is a hospitality heat-at-work log, not a master’s thesis. If in 2027 35°C becomes a hard weather ceiling, your rule will already have muscle. If you start on 10 January, you will be writing the rule with guests in the room.
A kitchen sensor lies if it hangs above the extract or above the dining-room door. It hangs where a person stands. Dish pit. Range. Pass. Two or three points, not one “for the venue”. An inspector who stands at the dish pit does not care about the sensor above the bar. Your panel shows the point, not the average. An average is a way to dilute 34°C at the dish pit with 24°C in the dining room. We do not dilute. The dish pit is the dish pit.
A “we close the terrace” decision must have an author. A shared login on the till tablet means the author is “the venue”. The venue does not give evidence. The shift manager does. 2FA and separate accounts are not a fad from Laravel application security. They are who will tell the inspector: “I closed the garden at 14:12”. Without that you are left with a chorus. A chorus at an inspection always sings sharp, even when it means well.
Frequently asked questions
- Does the PIP communiqué of 11 August 2026 mean gastronomy is the main inspection target?
- No. PIP listed gastronomy premises among the activities from which reports came: halls, shops, production, hospitals, offices, construction sites, gastronomy. It did not give a HoReCa complaint count. You must not turn that into “they are targeting restaurants”. You may — and should — turn it into this: kitchen, dish pit and terrace are posts where heat is real, and the inspector measures despite the lack of a general 2026 cap. Source: the PIP communiqué.
- How many complaints arrived and how many checks were closed?
- 212 complaints on the first wave (turn of June and July 2026), about 300 in total by 7 August 2026. Checks were opened on most complaints; nearly one third were closed by the communiqué date, the rest in progress or scheduled. PIP did not publish the outcome of each check or fine rates. We do not invent them. Your hospitality heat-at-work log should be ready for a check, not for a national average.
- When do the 35°C and 32°C caps apply?
- From 11 January 2027, under the MRPiPS ordinance of 9 July 2026 (Journal of Laws 2026 item 927). 35°C in the workroom, 32°C for heavy work in the open air — temperature from weather conditions, with exceptions. Action thresholds: 28°C / 25°C. Today, in August 2026, drinks, the risk assessment and BHP still apply. PIP’s note: New duties of firms during heat waves.
- Must we provide water if “the kitchen is always hot”?
- Yes, when the temperature at the post exceeds 28°C indoors or 25°C outdoors — under the preventive-drinks rules PIP restates. Available throughout the duty, quantity matching need, not a pack at the start of the shift. Failure to provide drinks and failure to record consultation are among the most frequent breaches PIP listed. A photo of a bottle in the group chat is not a record.
- Does GESOFT replace a boxed POS and rota?
- Not as a rule. If the POS and rota already hold one truth — they stay. We add an events layer (reading, break, shortening, service) or a latch on bookings. We put up your own panel (Laravel, Vue, Android) when the box will not swallow terrace rotation, mandates next to employees, and a shortening linked to a slot. Wider bill: boxed software versus custom. At contact you may also hear “stay on SaaS”.
- How does this sit with KSeF from February and April 2026?
- KSeF does not count temperature. It counts invoices for service, water, AC units, catering. From 1 February 2026 large taxpayers issue, from 1 April a wide duty, receipt in the system — under the Ministry of Finance timetable. The panel does not replace KSeF.gov. It pins a document number to the day and the site so an AC failure has the same stamp in BHP and in the books. Details: KSeF in a company application.
- Does a student on a mandate also enter the heat log?
- Yes. Heat and BHP do not ask about the contract label. They ask who stood at the dish pit. A season of mandates plus checks on the choice of civil-law contract after 8 July 2026 are two risks at one table. We will not reclassify the contract for you. We record the person, the basis, the post, the hours, the break. More on the civil register: PIP checks of civil-law contracts.
- Will the application replace a BHP specialist and the risk assessment?
- No. A risk assessment is a document that must be current after you open a garden, switch the menu to grill, or add an oven. The panel holds the version, the date, the briefing list, readings as fuel. It does not write the assessment. It does not sign it. It is not a BHP committee. Consultation of organisational measures from 2027 also stays yours — the system records the result.
- What about the terrace and bookings when the city is 35°C?
- The summer procedure must be able to close the garden, cap staffing, force rotation and cut the slot when the kitchen finishes early. A table-reservation system without a BHP latch sells a table at the waiter’s expense. That is dearer than a no-show: you leave a person in the sun, not only an empty place-setting. The guest message must leave before the door, not at the door.
- How do we order a quote and what do we get in 24 hours?
- Write to contact: number of sites, terrace/delivery, people on the shift, POS and rota, what hurt in this heat wave. GESOFT (Paweł Matusiak) returns in 24 hours with one of three answers: stay with the boxed product; we add a layer; we build a panel. No transformation slide. No promise that an app will cool the kitchen. A clear list of what we do not replace (PIP, KSeF.gov, accounts, sanitary inspection).
Describe your project