HLT Cloud
Schedule a demo
Menu

5S Audits · available in HLT Cloud

5S audits made for the shop floor.

Walk the area with a phone, answer clear criteria, capture evidence and leave with findings that someone owns. The starter template is HLT’s universal 5S audit for every kind of area, and your site can adapt it.

We use your email only to answer your request. No account is created. Privacy notice

Already using HLT Cloud? Sign in

A submitted audit on a desktop: the result, the answers of the first category (Yes / No and a count of defects) and the findings below.
A submitted audit, shown the way it was answered, with its result and findings. Screenshot of HLT Cloud with sample data.

How it works

From the walk to the fix.

  1. 01Inspect

    Record what you see

    Choose the area, score each criterion on a phone and capture photos where they help.

  2. 02Act

    Fix what matters

    Weak answers become findings with an owner and the evidence attached. Nothing to chase by email.

  3. 03Revisit

    Show the progress

    Open findings are waiting at the next audit, and every area shows its trend over time.

On a phone

From area to submitted audit in four steps.

Designed for one hand at 360 pixels wide, with large answer buttons and visible save status.

1
Choose the area

Pick the area and time, or scan the QR code posted at the area. The default template is preselected.

2
Answer the criteria

Each question shows its criteria and what each answer is worth. The screen stays on the question while you add evidence.

3
Add remarks and photos

Type a remark, take or attach photos, or dictate when your organization has enabled voice input.

4
Review and submit

The review lists missing answers, N/A reasons and unfinished uploads. Submitting creates an immutable revision and the findings.

The audit editor on a phone: the question on marked walkways and emergency exits answered with several defects, and a remark about a pallet blocking the walkway.
Answering an audit on a phone. Every answer and remark saves as you go. Screenshot of HLT Cloud with sample data.

Scoring

Scores you can explain to the team.

Each answer is a defect count, a maturity level from 0 to 4 or a Yes/No with fixed points. Questions are averaged within each of the five S, then the five S are averaged equally. Safety checks are shown beside the score as safety findings. Scores are shown out of 10, never as unexplained percentages.

The HLT 5S starter template
CategoryQuestionsAnswersIn the score
Safety checks5Defect count (10, 8, 6, 4, 2 or 0)No
Sort (Seiri)6Defect count (10, 8, 6, 4, 2 or 0)Maturity level 0–4 (0 to 10)Yes
Set in order (Seiton)5Defect count (10, 8, 6, 4, 2 or 0)Yes
Shine (Seiso)4Defect count (10, 8, 6, 4, 2 or 0)Yes
Standardize (Seiketsu)4Maturity level 0–4 (0 to 10)Yes
Sustain (Shitsuke)5Yes or No (10 or 0)Defect count (10, 8, 6, 4, 2 or 0)Yes

Worked examples

  1. Safety checks fail, everything else is perfect

    Result: 10.0/10

    Every safety check finds a problem and all five S earn full points. The 5S result stays at full score, and the five safety findings are shown beside it instead of being averaged away.

    29 of 29 required questions answered

    5 safety findings beside the score

  2. Two questions answered Unknown

    Result: 7.2/10

    Two questions could not be checked during the walk. They are left out of the score instead of being counted as zero; Unknown still counts as answered.

    29 of 29 required questions answered

  3. Audit still in progress

    Result: 8.7/10

    Sort and Set in order are answered. The provisional quality uses the answers so far; completion is shown separately, so a good start is not mistaken for a finished audit.

    11 of 29 required questions answered

Findings

Every weak answer becomes a finding.

When an audit is submitted, each answer below full score opens one finding with the remarks and photos recorded for it. The owner and selected collaborators mark it Fixed, optionally with a note or photo.

  • Open findings for the area appear before the next audit.
  • Two states only: Open and Fixed. Reopen keeps the history.
  • Observations at full score can be marked for follow-up explicitly.
An open finding on a phone: tools not back in their marked places, with the answer, the auditor’s remark about a loose torque wrench and the responsible owner.
A finding created from a weak answer when the audit was submitted. Screenshot of HLT Cloud with sample data.

Reports

Reports that match the analytics page.

Overview, Audit comparison, Areas and Findings follow-up come ready to use. Consultants build their own dashboards, and every page exports as a PDF or image with your logo.

  • Choose two or three audits and compare them side by side.
  • A missing previous result is shown as “Not scored”, never as zero.
  • Every page can be saved as a PDF for the next meeting.
The Overview page of Analytics on a desktop: average score, audits completed and open findings of the last 12 months, and a score trend rising over four months.
The ready-made Overview page: scores, findings and trends across areas, exportable as PDF. Screenshot of HLT Cloud with sample data.

Adaptable criteria

Your criteria, with stable history.

The starter template is a reviewed starting point, not a fixed checklist. Workspace administrators adjust it to the site and publish new versions.

  • Edit and publish templates

    Change wording, criteria, weights, N/A rules and the display scale (out of 10 or 100). Publishing freezes a version; audits keep the version they started with.

  • Import from CSV

    Bring existing checklists in through the documented CSV format, with row-level error messages before anything is saved.

  • Areas and QR codes

    Areas describe places and processes, not people. Each area can have a printed QR code that starts an audit after sign-in.

  • Five interface languages

    English, German, Spanish, French and Turkish. Text your team enters is translated automatically for colleagues who work in another language.

Optional AI

AI assists, people decide.

Every workflow works without AI. AI features are off until an organization administrator enables them, and every suggestion is reviewed before it is used.

  • Template drafts from a short interview, reviewed and published by a workspace administrator.
  • Voice dictation for remarks, with the raw transcript available for review.
  • Rewrite suggestions shown as a word-level comparison; the original stays until you accept.

AI requests go through OpenRouter to approved models only, with provider data collection denied. Customer content is not used to train models. Raw audio is deleted after processing, at the latest after 24 hours.

AI output is not a statement of legal, safety or certification compliance.

Questions about 5S Audits

Can we keep our own audit criteria?

Yes. Workspace administrators adapt the starter template to the site or bring existing checklists in through the documented CSV format, and publish new versions when criteria change.

Does it work on a phone?

Yes. The 5S audit is designed for a phone held in one hand: large answer buttons, photos and remarks at the question, and every answer saved as you go.

Who sees our audits?

Audits are private by default until their owner shares them. Roles are granted per workspace, and organization administration does not open private audits.

See it with your own areas.

After a demo, HLT sets up your organization, a first workspace and the starter template, then invites your administrator.

We use your email only to answer your request. No account is created. Privacy notice