Give your work instructions an excuse to be read. Then confirm it.
Approve the file however you do today. Upload it, press deploy, and every tag pointing at that document opens the new revision: no copies to pull, no sleeves to swap. Everyone who signed for the last revision shows as unsigned against this one, by name, until they have read it.
The tags are free. After that it is $149/month per shop, or $1428 a year, however many people scan, with 60 days to change your mind.
Before you start
Bracket must be at room temperature. Gauge R&R is current through August.
- 1Zero the indicator against the master.
- 2Measure both bores at three depths.
After the copies are swapped
The rev you just released is under a keyboard by Thursday
Walking the floor is the tedious half. The other half is that what you put in the sleeve is an 11pt Word document, and nobody reads one of those mid-job with gloves on. The release completes, the binder is filed, and the work runs the way it always did. A faster way to hand out paper does not fix that.
- Numbered steps become cards, read at arm’s length. An operator who looks away mid-task finds their place again at a glance instead of starting the paragraph over.
- DANGER, WARNING and CAUTION become colored cards rather than gray body text in the middle of a page.
- Text sizes up and down, and the screen goes dark for a dark shop. Both are remembered.
Before the next transition audit
When the standard changes, every sign-off starts again
When ISO 9001 is revised, AS9100 follows. Your documents get reissued, and every sign-off you have collected is against a revision that is no longer current.
- ISO 9001
- AS9100
- IATF 16949
- Who has signed for the new revision and who has not, per document, on the day somebody asks.
- The whole record hands over as a file rather than a screenshot: a PDF to give them, a CSV to keep, and a worklist of who still owes a confirmation.
- Sign-offs are collected from your first day, so the file already exists when the transition date lands instead of being built the week before it.
Scan it the way an operator would.
Your operators will not install an app and will not sign in at a machine, so neither will you. Point the camera you already have at this tag and the whole loop runs on your phone in about three minutes: enroll it, put a setup sheet on the tag, read it back, release a revision, sign for it.
Start the demoFour steps, and none of them is a documentation project
Most shops are not missing the instructions. What is missing is a way to get a new revision in front of the person doing the job, and a way to know it got there. This is the whole of that, start to finish.
- 1
Put the setup sheet in, however it exists today
Word, PDF, a scan of a marked-up print, or a photo of the whiteboard by the machine. It comes back readable on a phone, with the steps and the tables intact.
- The setup lives in one guy’s head and a Word file nobody can find, and quoting the job again next year means working it out twice.
- It is written down once, in whatever shape it is already in, without a documentation project.
- 2
Stick the code on the machine
A QR tag on the machine, the workstation, the inspection bench, the receiving dock. Anywhere a job actually gets done.
- A laminated sheet taped to the machine, three revs old and soaked in coolant, with the current one in a binder in the office.
- The instruction is at the point of use, which is where your registrar goes looking for it.
- Machines and production lines
- Inspection and first article
- Packing and shipping
- Receiving and material
- Tool crib and stores
- Maintenance and PM
- 3
The operator scans it
Their own phone, the camera that is already on it. No app to install, no password at the machine, no account for a temp who starts Monday.
- An operator who cannot get at the instruction stops asking for it and runs the job the way they remember it.
- One scan, current revision, every time, including the agency hire on their first shift.
Do it to the tag above: that is the operator’s side of it, on your phone.
- 4
Release a revision and the wall updates itself
Publish the new rev and every tag pointing at it is current the moment you hit deploy. The sticker never moves.
- Walking the floor collecting obsolete copies, and hoping nobody kept one at their workstation.
- No obsolete copies at point of use, because there are no copies. The tag carries a code, not a document.
What that adds up to: the register, the runs, and the file you hand a registrar.
What comes up before the first tag goes on a machine
Six of them, one picture each. These are the things that decide whether a shop starts, and none of them needs a call to explain.
A code on the machine is not a public link
Your setup sheets stay private. Contractors and service engineers scan tags in shops that are not theirs, and without your shop code they get a screen saying the document is private. The phone of somebody who walks out is revoked in one tap.
One shop code, once per phone
Nothing for an operator to install and nothing to sign into standing at the machine. A phone joins with a short code and a first name, and every scan after that opens right away. That includes the guy who started this morning.
A marked-up print, readable at the machine
Word, PDF, a scan, a photo of the whiteboard. It comes back with the steps as cards and the torque table scrolling instead of shrinking to nothing, and nobody retypes a setup sheet into a template first.
Tags are included, and so is the next one
Durable printed tags are part of the subscription, and one that gets soaked in coolant, painted over or knocked off costs nothing to replace. Print your own on paper any time as well.
Release a rev and everybody is unsigned again
The tag on the machine is current the moment you deploy, and everyone who signed for the last rev shows as not confirmed against this one until they sign again. Nobody rebuilds a list to find out who has not.
The clipboard, without the clipboard
First article, changeover, daily startup: boxes in a .docx become a list an operator works through at the machine, and each run is kept with who did it and which rev they worked from.
All six are on from the first day.
The tags are free and there is nothing to pay when they land. One price for the shop afterward, tags included.
Training that does not depend on the guy who knows
Every shop has one: the person everybody asks, whose knowledge is written down nowhere, who is either retiring or already interrupted forty times a day. This is how that gets out of one head without anybody having to sit down and write a manual.
- A new hire starts on the machine, not in a classroom. Hand them a phone, walk them to the machine, let them scan. The tag teaches the job in the place the job happens.
- Read-and-understood, per person, per revision. An operator confirms they have read revision C. When you release D, everyone is not-confirmed against D until they sign for it.
- Who has not signed, not just who has. A list of completions is the easy half and the half that proves nothing. The register carries the outstanding rows too, which is the column an auditor puts a finger on.
- Checklists they work through at the machine. First article, changeover, daily startup, lockout. Each run is kept as a record of what was done and by whom, rather than a clipboard nobody files.
- The setup guy writes it once. A photo of the whiteboard, a marked-up print, five lines of text. It becomes the thing on the machine, and the next person asks the tag instead of asking around.
The week of the audit, this is already done
“Show me that the operator running this part was trained on the current revision.” The register answers it per document and per revision, including the people who have not signed, with the date each one signed. It hands over as a PDF rather than a screenshot, and sign-offs cannot be quietly edited afterwards.
Whatever you are certified to (ISO 9001, IATF 16949, AS9100), the finding this is aimed at is the common one: obsolete documents at the point of use, and no evidence anybody was trained on the current one.
Stop rebuilding the training record the week before the audit.
Sign-offs are collected from your first day, and the register that turns them into a file you can hand over is included.
Things you only find out on the floor
- Works on whatever phone the operator already owns, Android or iPhone, with the built-in camera.
- A tag can point at a folder, so one tag on a machine opens the changeover, the daily check and the lockout sheet.
- Review dates: past the date, the operator sees a banner telling them to check with a supervisor instead of trusting it.
- Drafts still resolve, so you can print a tag and test the scan before the document is released.
- Text size and dark mode are the operator’s to set, and stay set. Safety glasses at 6am, phone at arm’s length.
- Download everything you have as one ZIP: originals, register, sign-offs, tag mapping.
One price for the shop, not per operator
Every document, every operator, every tag. One price.
Pro
Save 20% yearlyOr $119/mo billed yearly, $1,428 once.
Every procedure on the wall, one scan away.
- Unlimited documents, converted from Word, PDF, text or a photo
- Unlimited operator devices, with no login where the work happens
- A QR tag for every document, printed however you like
Not yet? Have 25 tags mailed to you first, free.
Sign-offs are recorded from the first day and cannot be quietly edited afterwards. Your whole record exports at any time, in formats that outlive this app.
60 days to change your mind
You pay today, and most shops take about 14 days to get tags onto machines and see the first scans. Say the word any time inside the 60 days and we refund the whole thing. Cancel whenever you like.
What shops ask
- My guys are not installing an app. Is this an app?
- No. It is a web address behind a QR code. They open the camera they already use, point it at the tag, and the instruction opens. The one-time step is entering a short shop code on their phone, which takes about ten seconds and never has to happen again on that phone.
- Half the shop has no signal by the back wall.
- Then it will not load there, and we would rather say so than let you find out on the floor. Offline caching is the next thing being built. The honest version is that a first attempt was pulled before any shop saw it, because a bad cached copy is the one failure a deploy cannot fix. Tags near dead spots are worth testing before you order a box.
- What happens when somebody quits?
- Rotate the shop code and their phone stops working the next time it asks for anything. You can also revoke one phone on its own, which is what you want when it went missing rather than the person.
- Will this hold up in a surveillance audit?
- The register shows, per document and per revision, who confirmed and who has not. Sign-offs are collected from your first day, so the file exists before the audit is booked, and they cannot be quietly edited afterwards.
- We are ISO 9001 with two people and no quality department.
- That is the shop this is priced for. Nothing here needs a document controller: you upload what you already have, stick tags on machines, and the register fills itself in as people scan. There is no per-seat charge, so putting every operator on it costs the same as putting on one.
- What about setup sheets that change on the floor mid-job?
- Upload the marked-up version as a new revision. The tag on the machine is already pointing at it, so nothing gets reprinted and nothing gets collected. Everyone shows as not-confirmed against the new rev until they sign for it.