Choose your language

EnglishEspañolPortuguêsFrançais日本語DeutschItalianoالعربيةБеларускаяአማርኛУкраїнськаÍslenskaMagyarAfrikaansČeštinaCymraegHrvatskiMāoriРусскийKiswahiliBosanskiCatalàGalegoGàidhligБългарскиLietuviųTiếng ViệtCebuanoລາວМонголမြန်မာខ្មែរFilipinoBahasa MelayuગુજરાતીBasa JawaTürkçeAzərbaycanՀայերեն繁體中文Euskara简体中文DanskNederlandsहिन्दीSuomiBahasa IndonesiaGaeilgeҚазақшаNorskPolskiRomânăСрпскиSvenskaไทย한국어עברית

Explore TTH Pergola

TTH PERGOLA

Blog

Retractable awning choices

Who closes the restaurant awning? Make the shift handover specific

Record the unit, confirmed state and outstanding tasks so the last person leaving knows who completed the action and how it was checked.

A complete extended folding-arm awning above a terrace, with a plain handheld remote on a table and an unlabelled wall switch.
Concept illustration: A complete extended folding-arm awning above a terrace, with a plain handheld remote on a table and an unlabelled wall switch.

One checkbox can conceal different interpretations

A checklist saying close the terrace may mean clearing dishes, switching lights off or locking doors without defining the awning state. Give each unit a recognizable zone name and assign the instructed leaving actions to a role or shift. A general reminder to watch the weather does not identify who confirms completion. Avoid unnecessary personal data, but preserve accountable execution and handover. Separating equipment closure from general clearing reduces the chance that front-of-house staff, cleaners and the manager each assume someone else completed the relevant task.

Angled underside view of the retracted awning cassette with its support arm folded beneath it.
Product detail: Angled underside view of the retracted awning cassette with its support arm folded beneath it.

Record the confirmed state, not merely a button press

Pressing retract does not necessarily complete every leaving requirement. Follow the equipment and control instructions for observation and confirmation. Distinguish action performed, state confirmed through the required method and unresolved abnormalities instead of treating an app icon or sent command as automatic physical proof. Check each zone individually where several units exist. Document automation’s actual role and the checks still assigned to staff. A useful record communicates the state and basis of confirmation rather than leaving the next shift with one unexplained completion tick.

Give exceptions an identified recipient

If closing does not behave as expected, staff should neither cycle repeatedly until one attempt succeeds nor tick completion to finish paperwork. Follow the instructions for the current state, record symptoms and notify the assigned manager or support contact, identifying who takes responsibility. Wet-retraction drying also needs handover rather than disappearing under a closed label. Actual response times and charges require agreement; immediate attendance is not assumed. An exception process ensures the issue has a recipient and record after the last employee leaves.

Check the record through a handover rehearsal

Have a trained new employee explain which equipment each entry covers, where instructions are found and whom to contact. If essential information still depends on a veteran’s memory, add it to the record. Keep the checklist brief and update it after equipment changes instead of adding meaningless ticks. User handover, control custody and support contacts belong to operations beyond opening day. Alongside appearance and coverage, a useful proposal can be closed reliably during a busy shift and leaves the next team knowing exactly which conditions have been confirmed.

  • Link each entry to an actual named zone.
  • Separate actions, confirmed states and outstanding tasks.
  • Assign recipients for abnormalities and wet-fabric follow-up.

Is “awning closed” enough on a restaurant closing checklist?

Identify the unit, responsible role, instructed action, confirmation method and outstanding abnormalities or drying tasks. A command is not necessarily confirmed completion, and multiple units need separate entries. Assign exception recipients instead of forcing repeated operation to obtain a tick, so the next shift understands what remains.

More questions, practical answers →

Continue planning

Topics

Closing ownershipVerified stateException handover
View system details →Contact TTH
← Blog

Privacy