The phone that lives on the shop floor: eighteen forms moved back to where the work happens

Leave, overtime, gate entry, shift handover, patrol inspection, incoming inspection, material issue, transfer — all of it happens at a machine, a gate, a warehouse or a test bench, and all of it used to be written down in an office after hours. This Android app does one thing: it puts eighteen business forms back on the phone. Log in with an employee number, pick the shift from a dropdown, take the photo on the spot, send it up a three-step approval, and read the result in Messages. The record is made in the same minute as the action.

Industry
Discrete manufacturing · several workshops and shifts (grinding, auxiliary materials, assembly), office separated from floor
System type
Android app sharing one set of employee numbers, org structure and master data with the PC back office
Key techniques
One form engine · repeatable line items · three-step approval chain with CC · on-site photo upload · calendar and location clock-in · approval results pushed to Messages
Jiding role
Mobile interaction and form design, approval-chain configuration, field reduction, pilot on the floor, go-live training
18 formsfive HR, five gate and admin, five quality, three material
5 domainsplus three everyday entries: clock-in, approval inbox, messages
3 stepsteam lead → manager → general manager; CC never blocks the chain
1 structureevery form shares the same five parts, so learning one teaches eighteen

Three Gaps

Action at nine, record at seven: paper has three lags

The problem with paper is not the paper. It is that time and place stop matching. Inspection finishes at 09:12 and is written up at 19:20. A leave form needs three signatures, and one of the three is out of town. At month end a clerk retypes a pile of forms into Excel, mistypes one number, and the whole month's cost is off. Three lags stacked together turn the shop floor into a memory exercise.

Leave request: leave type, period, start and end time, 15 hours derived automatically, reason and photo attachments
Fill: nine fields per leave requesttype, period, start, end, hours, reason, plus two proof photos
Shift handover: team, shift, date, handover notes, production status, safety status and open issues, each with photos
Hand over: three photos, not a verbal storyproduction, safety and open issues each get a picture
Messages: system notices and interaction messages, chat list, and the three-tab bar for messages, office and me
Close the loop: the result arrives in Messagessystem notices carry approval outcomes, so nobody phones to ask

The usual mistake is shrinking the PC table until it fits a phone — which only moves the after-hours data entry onto a different device. This app makes the opposite trade: fields follow the order of the work, anything pickable is a dropdown, line items become cards, and photos hang off the record. The goal is not "it can be filled in on a phone", it is "it can be finished next to the machine".

Three Tabs

Three tabs, three tenses

The whole app has three first-level entries: Messages, Office, Me. That is not an arbitrary navigation choice; it is three time scales. Messages is what has already happened, Office is what is happening now, Me is what has accumulated. Almost every action in a shift can be filed under one of those three words.

Messages: system notices (approval results, rejection reasons) and interaction messages (colleague messages, pushed articles). It answers one question — where has the thing I submitted got to.
Office: the entrances to five domains, i.e. the eighteen forms. HR, gate and admin, quality, material — all of it starts here.
Me: clock-in, approval inbox (waiting for me / approved by me / started by me / copied to me), profile. It answers what I did this month.

The split has a hidden benefit: training takes three sentences. "To do something, go to Office. To see a result, go to Messages. To look something up, go to Me." The shorter the explanation, the longer a shop floor keeps using it.

Function Map

Twenty-one screens, five kinds of errand

The feature list is organised by department, so it looks like five systems. Organised by who is acting on what, there are only five: person on company (leave, onboarding, resignation, transfer, overtime), person on gate, vehicle and shift (site entry, handover, vehicle request, general approval, shuttle statistics), person on material (five inspections), material on location (receipt, issue, transfer), and time on person (clock-in, approval, messages).

01Everyday officeEmployee · 5
LLeavetype, period, start, end, hours, two proofs
OOnboardingID details and a photo of the ID
RResignationemployee no., department, position, duties
TTransferemployee no., department, position, reason
XOvertimeteam, shift, headcount, hours, people picked
02Gate & adminGate · 5
GSite entrytype, zone, people, goods carried, escort
HShift handoverteam, shift, production / safety / issues
VVehicle requestuser, purpose, route, passengers, times
AGeneral approvaltype, description, images — the catch-all
SShuttle statisticsdate, stop, slot, headcount by department
03Quality controlQuality · 5
PIPQC patrolproduct, process, line, defects and rate
IIQC incomingmaterial, supplier, batch, received / inspected
QOQC outgoingline, customer, sample size, defect list
DDelivery checkproduct, customer, pass/fail per item, photos
CLab analysisline, process, bath range, measured value
04Material flowMaterial · 3
RGoods receiptsupplier, nature, batch, lines, start inspection
MMaterial issuerequesting dept., nature, parameters, quantity
FMaterial transfertype, from, to, arrival, release, receipt
05Everyday entriesPersonal · 3
KClock-incalendar and location, in and out
BApproval inboxto approve, approved, mine, copied
NMessagessystem notices, interactions, chats
Shuttle statistics: date, stop and time slot, headcount by department, total of 45 at the bottom
Shuttle statistics: one screen, one answer nobody has to ask for.Which day, which plant, which slot, how many people from which department — totalling 45 at the bottom.

The manual's feature list also names production plan, daily production report, daily cost report and safety team as part of the same app. This case does not cover them: it only walks through the eighteen forms whose fields are visible in the screenshots. A case study earns trust from the fields you can see, not from the length of the menu.

Anatomy

Five parts per form: subject, lines, evidence, approval, CC

Eighteen forms look alike on purpose. Learn one and you have learned all of them: say who you are (subject), say how many things this involves (lines), take a photo if there is something to see (evidence), send it to whoever signs (approval), tell whoever needs to know (CC). Every form is a different arrangement of those five parts.

01
SubjectWhoThe employee number fills in name, department and team — nobody types it. Team and shift are dropdowns: "Quality Team 1, Dept. 1" and "day shift" must be options, not something a pinyin keyboard has to guess.
02
Line itemsLinesOne form usually holds more than one thing: a leave period, a list of people on overtime, several defect types, several materials received, several chemicals in a bath. Lines are cards; tap add for one more, and each card keeps only the three fields that matter.
03
EvidenceProofThe camera is the only sensor a phone has. Proof for leave, an ID for onboarding, the bench for a handover, the defect for an inspection, the finished goods for a delivery. JPEG only, a few per form, attached to the record rather than left in the gallery.
04
Approval chainApprovalFixed at three: team lead → manager → general manager. The chain is derived from the org chart, not chosen by the submitter — a process where you pick your own approvers is not a process.
05
CCCCCC is not an approval step, only a notification. Quality forms copy process engineering and production; vehicle requests copy admin. The people who need to know get told, without holding up the clock.
IPQC appearance inspection: product, process, line, first-article check, sample size 500, defect lines for white spots 10 and scratches 5 with rates, approvers team lead, manager and general manager, four people copied
All five parts on one screen: subject (line, inspection type) → lines (defect, quantity, rate) → evidence (bench photo) → approval (team lead, manager, GM) → CC (four people). One tap to submit.
Inspection type
First article, patrol, final. One dropdown switches the judgement inside the same IPQC form, so there is no need for three separate forms.
Sample size
How many pieces were drawn from this batch. It anchors the defect rate, so it has to be a number, not a sentence.
Defect type
White spot, scratch, tool mark — all from a fixed list. Free text here means giving up on statistics.
Defect count / rate
Count is entered, rate follows. People are responsible for what they saw; arithmetic is the system's job.
Time
Defaults to now, editable. Edits are logged, because a backfilled record and a live one are not the same thing.
Approvers
Three avatars on one line, order visible at a glance. Any rejection returns the form to the submitter with the reason in Messages.

Five Checks

Five inspections, five judgements: do not merge them

Quality is where "unify everything" does the most damage. Incoming inspection judges a supplier's batch. Patrol judges a process on your own line. Delivery inspection judges the box in the customer's hands. The lab judges the chemistry in a bath. Different objects, different frequency, different judgement — force them into one form and every field ends up saying "depends".

IPQCpatrol
Judges
product, process, line
Against
defect type and count
Trigger
first article / timed patrol
IQCincoming
Judges
material, supplier, batch
Against
item, standard, tool and method
Trigger
"start inspection" on the receipt line
OQCoutgoing
Judges
line, customer, batch, sample
Against
each defect pass or fail
Trigger
before finished goods ship
Deliveryhand-over
Judges
product, customer
Against
pass or fail per item
Leaves
photos plus a written note
Labbath chemistry
Judges
line, process, chemical
Against
process range (e.g. 70–90 g/L)
Leaves
measured value, additions and dose

The lab form shows best how a judgement should be designed. The operator does not enter "pass", they enter a number: the process range is 70–90 (80) g/L, the measurement is 82, and the system judges it acceptable. A second block records "chemical added and how much", keeping the correction on the same record as the reading.

When a bath drifts, that one record answers three questions: what was measured, was it in range, what was added and how much. A form that only records pass/fail records nothing.

One process may involve three or four chemicals (etchant, sulphuric acid, DMAB), each with its own range. The form becomes "one card per chemical" and adding a dose is one tap — the structure follows the process, not the spreadsheet.

Lab form: line C, process etch 1, etchant with a process range of 70-90 (80) g/L, reading 82 judged acceptable, preservative added at 20 g/L; a second card for process 3 with DMAB

Evidence

A photo is not an attachment, it is the judgement

Text can say "slightly scratched". It cannot say how many, how long, or on which face. The photo is the useful part of an inspection record: packaging and label for incoming goods, product and carton for delivery, equipment and bench for a handover. So the camera is a first-class part of the form, not a fallback "upload attachment" button.

IQC incoming inspection: material, batch 202052354, 600 received, 500 inspected, inspection items with standard, tool and method, record and pass/fail, overall result and site photos
Incoming: standard first, record secondeach inspection item carries its own standard and method, so nobody judges from memory
OQC outgoing inspection: product, line, customer, sample size 15, batch, defect cards for scratch, white spot and tool mark with pass/fail and defect rate
Outgoing: one defect per carditem, pass or fail, rate — three fields, three cards on one screen

A phone screen is narrow, so line items cannot be laid out sideways. The answer is one card per defect: the card holds three fields — item, pass or fail, rate. Five defects means five stacked cards and a thumb scroll, which beats dragging a table left and right. This is the biggest design divergence from the PC: the desktop optimises for seeing everything at once, the phone for finishing the entry.

Approval

Three steps, three views, one message

Approving on a phone fails for two reasons: you cannot find what is waiting for you, and you cannot tell where your own request went. So "Me" holds exactly three views: waiting for me, approved by me, and the ones I started or was copied on. A form goes from submitted to closed in at most three taps.

Four records, four states — that is the entire vocabulary of the chain: in progress (someone else's turn), approved (carry on), rejected (back to the submitter, reason required), pending (nobody has touched it).

A rejection must carry a reason, and not out of process pedantry. On a shop floor, a form that comes back with no explanation means a phone call, a re-edit and a second rejection. Putting the reason next to the button saves three phone calls.

Separating CC from approval is what makes the chain fast: three people sign, ten people may need to know. Mix them and ten people who carry no responsibility are allowed to slow the clock.

Approval inbox: tabs for waiting and already approved, each row showing submitter, date and status of approved, rejected or pending

A Day

Six opens a day: the record follows the work

Put the app inside one team leader's day and it becomes clear what it replaces. Each of the six moments below used to be a paper form, and all six used to be saved up for after the shift. Now each is finished in the minute it happens.

07:52
Clock inAttendanceCalendar plus location. On success a card appears: 08:48, the location, name and department.
08:05
Shift handoverGate & adminNight to day: production, safety, open issues, one photo each, then "agree" to close the handover.
09:40
First-article checkIPQCProduct, process and line from dropdowns, sample size 500, two defect types with counts, then team lead → manager → GM.
11:20
Material issueMaterialRequesting department, material nature, product parameters, quantity. The warehouse starts picking as soon as it lands.
14:30
Material transferMaterialShipment type, from, to, arrival; release time and receiving time are both stamped.
17:45
Clock outAttendanceSix records are already in the system. Nobody has to "remember" the daily report afterwards.

Clock-in deserves a note of its own. Its value is not the location, it is framing the day. With an in and an out, the five records in between finally have an owner: who was on shift, which record belongs to that shift, and which hours count as overtime.

The success card is deliberately plain: 08:48, clock-in successful, location. It needs nothing more, because a worker only cares about two things — did it register, and at what time.

Attendance: 1 June 2020, Zhang of the R&D department, popup confirming clock-in successful at 08:48, with a calendar timeline behind

Material Flow

Three material forms, one batch number

Material movement only needs three documents: in (goods receipt), out to the line (material issue), out of the plant (transfer). They look like three separate segments, but they share two anchors — the batch number and the material line. The batch makes traceability possible; the line makes "how many kinds of goods are on this truck" answerable.

In · goods receiptsupplier → store
Header
supplier, supplier name, material nature, batch
Lines
code, name, spec, received quantity, unit, PO no., delivery note
Next
"start inspection" sends the batch to IQC
Use · material issuestore → line
Header
requesting department, material nature, product parameters
Lines
material and quantity, one or many
Purpose
one document for picking and for consumption
Out · transferplant → customer
Header
shipment type, material type, reason, from, to
Times
arrival, gate release, receiving
Sign-off
same three-step approval chain
Goods receipt: supplier, material nature, batch, then material lines with code E75, 150 zircon sand, 25 kg per carton, 50,000 cartons, PO and delivery note, and a start-inspection button per line
Receipt: one card per material linename, spec, quantity, unit, PO and delivery note — six fields per line
Material transfer: shipment type, material type, reason, from, to, arrival, gate release and receiving times, a material line of 5 cartons and the approver chain
Transfer: three timestampsarrival, release, receipt — if any two disagree, the goods are in limbo

The "start inspection" button at the end of a receipt line is the shortest cross-module path in the app: the storekeeper taps once and the batch, with its number, enters IQC; the verdict comes back onto that batch, and only a pass continues into stock. Material and quality are not two modules, they are two faces of the same action.

Roles

Five people, five different first looks

One app, five reasons to open it. Before go-live we worked through this table with the client: what each role looks at first, how many times a day, and what they can actually do on the phone. If the table does not line up, no amount of features will help.

WOperator2–3 times a day

Clock in, leave, overtime, read the verdict. Uses it least — and blocks the project if it does not work.

LTeam leader5–8 times a day

Handover, first article, approve overtime and leave, and glance at the team's inspection records.

QInspector10+ times a day

Patrol, incoming, outgoing, lab. Every entry means a photo. The phone is their logbook.

SStorekeeper5–6 times a day

Receipt, issue, transfer. Batch and quantity must be right; one wrong digit breaks traceability.

MManager / GM3–5 times a day

Two actions only: approve or reject. One inbox, with the detail, the photo and a reason field.

The table also settles one thing: there are no reports on the phone. Trends and exports belong to the PC back office; the phone only carries the action of the moment. Treating a phone as a small computer is the easiest mistake to make in this kind of project.

Delivery & FAQ

Five questions every plant asks in week one

Mobile projects rarely fail for lack of features. They fail because the app is installed and nobody opens it. These five questions come up in the first week of every pilot.

Q1Our operators are not comfortable with smartphones. Will it take?
It will, provided the field order matches the paper form and anything pickable stays pickable. Team, shift, line, material and department are all dropdowns; only quantity, reason and inspection notes need typing. One form per screen, submit at the bottom — operators do not fear forms, they fear not knowing which box to fill.
Q2The screen is narrow. How do inspection lines work?
As cards: one defect per card, three fields inside — item, pass or fail, rate. Five defects means five cards; scrolling down beats dragging a table sideways. Material lines work the same way: code, name, spec, quantity and unit on one line, overflow on the next.
Q3Three approval steps — what if the manager travels?
Approval was designed for mobile from the start: waiting and already-approved are separate lists, each record opens to the applicant, time, lines and photos, and approve or reject is one tap. The result lands in Messages. CC is not a step — people who need to know are notified without holding the chain.
Q4Will photos pile up and fail to upload?
Photos attach to the record, a few per form, JPEG only, never left loose in the gallery. Inspection, handover and delivery require them; the rest are optional. A photo is the evidence — and the converse holds too: a record with no photo is of little use when something goes wrong.
Q5Can we start with only some modules?
Yes, domain by domain. The usual order is quality plus material flow first (records are thinnest and disputes are loudest), then gate and admin, and HR last. Switching everything on at once is the fastest way to annoy everyone at once.

MORE CASES

More Related Cases

Industrial smart manufacturing app
EC AppMobile applications, industrial intelligent manufacturing

Industrial smart manufacturing app

Leave, overtime, gate entry, shift handover, patrol inspection, incoming inspection, material issue,...

View Details →
EV charging service app
EC AppSmart charging pile

EV charging service app

A mobile service system for EV owners: book an installation by city district and follow it through t...

View Details →
Pool-cleaning robot companion software system
EC AppIntelligent robot, intelligent cleaning

Pool-cleaning robot companion software system

Companion software for a pool-cleaning robot: a PC back office plus Android / iOS apps; devices come...

View Details →

View All Cases →

Planning a similar production line or enterprise system?

Start with our pricing logic, then let's talk requirements — cost structure, technology comparison and acceptance criteria, all laid out in the open.