floorsite Open the app

Work standards, written where the work happens.

An operator talks through the job on a phone. floorsite turns the words and photos into a training standard. The desk finishes it, a second person approves it, and everyone finds it at the machine.

See how it works Open the app

Recording00:00

  1. Lock out the pressLock on the main switch before the door opens
  2. Loosen the die clampsCross pattern, so the die stays level
  3. Lift the die out with the hoistTwo people, hands clear of the edge
  4. Listening for the next step

One standard. One source of truth.

All your standards in one place, whether on the phone, at the desk, or on paper. Search by voice or by typing, and the standard you need is never more than a question away. A second kind of document, the standard operating procedure, follows the same path and is in build.

The desk, a published training standard shown exactly as it prints: masthead, header grid, materials and context, the steps table with critical points, reasons and photos.
At the desk. A published standard, exactly as it prints: the sheet people already know, with the photos on the steps they belong to.
The same standard open on a phone at the machine.
At the machine. The same standard on the phone.

How it works

  1. 1

    On the floor

    Press the mic and speak the job out loud. Voice capture records every step and lays it out point by point. Photos go to the shared library. Work autosaves, and captures wait in an offline outbox until the connection is back. Four languages keep the whole team on the same page.

    The phone home screen: Find standard, Create standard.
    The Documents screen: start a training standard by voice or type it, add photos, or continue a draft.
    The capture screen: the header of a training standard filled in by voice, eight of nine fields captured.
    The phone. Find or create, pick what to capture, then talk: the standard fills in as you speak.
  2. 2

    At the desk

    All standards are finished at the desk, for accuracy, and a second person signs off. A supervisor completes the header, tidies the steps and submits. The approver types their name and publishes. Nobody approves their own standard. Every standard has an owner and a review clock.

    The Documents list at the desk, with drafts, published standards, and a Type filter.
    Documents. Drafts from the floor arrive here, next to what is published.
    The approval view: a submitted draft, the changes, and the signature field where the approver types their name.
    Approval. A second person reads it, types their name, and publishes.
  3. 3

    When it's time to work

    Find a standard by task, machine or code, typed or spoken. Ask a question and the answer comes from published standards only, naming the standard and the step. Scan the code on the machine to open its standards. Without a connection, the offline copy still reads.

    Find: results for press, by task and machine.
    Ask: a spoken question and the answer, with the standard and step it came from.
    A machine page opened by scanning its code, listing its standards.
    Find, Ask, the machine. Search, a grounded answer, and the code on the machine.

Approval and history

Every standard has versions. A change becomes a new version and the old one stays readable. History shows what changed between two versions, marked inside the standard itself. Edit history records who changed what. The audit trail says it in plain sentences. Approvals, feedback and review reminders arrive in one inbox, and by email. A standard can be pinned for a site, a role, or a line.

Compare on the History tab: two versions side by side, the changes marked inside the standard, with a summary of what changed.
Compare. Two versions, the changes marked inside the standard, and a summary in plain words.
The inbox: an approval to give and a review that is due.
Inbox. Approvals, feedback and review reminders, in one place.
The audit trail: every change written as a plain sentence, with who and when.
Audit trail. Every change as a sentence: who, what, when.

Sign-in, devices, languages

People sign in with a work email and a six-digit code, or a PIN on the device. Administrators sign in with two-factor authentication as well. The app keeps itself up to date and reloads once work is done, so nothing is lost. Roles, users and sites are managed from the desk. Each person chooses a language, and it follows them across devices.

Users at the desk: people, their roles, and who may approve.
Users and roles. Who is who, and who may approve.

Built for the plant

  • A phone in the pocket for operators, a browser at the desk for supervisors. Nothing to install.
  • Four languages, chosen per person: Dutch, English, German, Turkish.
  • Every change is kept as a record.
  • Two machines, so a release brings no downtime.
  • Monitored around the clock.
  • Hosted in the European Union.
The machine sheet: one QR code per machine, printed for the floor.
Machines. One code per machine, printed and stuck where the work is.

What changes on the floor

Standards that are written once, read everywhere, and never out of date.

  • Less time writing. A standard is captured in the time it takes to do the job once. No evening at a keyboard.
  • One version, always current. Everyone reads the same standard. Old versions stay on file but cannot be followed by accident.
  • Fewer mistakes, less scrap. Critical points and reasons travel with each step, so the way that works is the way that gets done.
  • Less risk on paper and in audits. Nobody approves their own work. Every change carries who, what and when. Retention and redaction follow the plant's rules.
  • Less searching. Find by task, machine or code, ask a question out loud, or scan the code on the machine.
  • No language gap. Dutch, English, German and Turkish per person, and translations approved before they are used.
  • Training that sticks. Assignments, quizzes and refreshers, with a record of who has read what.
  • Grows with the plant. Procedures and problem-solving records beside the standards, templates the plant authors itself, master and local standards across sites, sign-in with the company's Microsoft account.