Without a mobile entry
- Photo on site. Send it to the crew group.
- Back at the office, open a PC and backfill from memory.
- Photos, time and ticket number do not match. QA walks it again.
- A lead who wants status can only flip chat or call.
Reading “mobile entry” as “do we have an APP icon” undersells it. What actually differs: when people are not at a desk PC, can a patrol, a report or a redeem finish on the spot. Without an entry the floor drops evidence into WeChat and backfills from memory at night. With an entry the action is the document. Why a PC system does not match the floor. See If field staff never sit at a PC, the PC system does not exist.
With a usable mobile entry
- Scan brings the object. Nobody hand-copies a number.
- Photo, tick, submit. The document enters the same back office.
- Weak network can enqueue. Sync when there is signal.
- Management sees it immediately. Nobody waits for a return to the office.
Note: an APP nobody opens is close to “without.” Cannot find the entry, login too heavy, paper still accepted—the system is just another formality. When unused, split it with the checklist. See Launched, unused: how to diagnose. WeCom chat alone does not replace a business entry with state. See WeCom chat is not a business entry.
After you have an entry, the gap also shows up as rework and support calls. Shot clearly and submitted then means one fewer “I will backfill later.” Customers who can look up status themselves cut calls. See How a customer mini program cuts support calls and Mobile efficiency you can actually see. After store and HQ stock connect, redemption no longer rides a manager’s verbal count. See After the store app shares HQ stock and membership.
The comparison must land on “can they finish on the spot”
Split one patrol into a timeline. Without an entry: 10 minutes looking at equipment, 20 minutes backfilling at night, another trip if it does not match. With an entry: 12 minutes on site including submit, no office backfill. You do not save the cost of building an APP. You save rework and argument. Why work has to happen on the phone. See Why work has to happen on the phone. When DaXi plans mobile we walk a loop with the floor first: where evidence lives now—notebook, group or PC—then decide whether phase one is employee or customer. Start from the Apps & Mini Programs and send the roles and the actions that must finish on a phone.
Delivery, install and store walks draw the same two paths. Without an entry, ETA lives in the driver’s head. A customer who calls “where are you” must call dispatch again. With an entry, after a node submits the customer can see it and calls drop. The gap is “did the fact leave the person’s camera roll.” The employee side makes submit a habit. See Employee features people will actually use. Finishing on site is what cuts rework. See Finish patrols on site, cut rework.
If leaders still only count paper after you have an entry, the path gap will not appear by itself
Rule that some document types only count as a system submit. A tool becomes a habit before the comparison becomes efficiency. Without an entry companies often buy delay with overtime. With a phone that can submit you can talk about “close the ticket the same day.” The path gap becomes a lead-time and complaint gap.
The comparison must land on a management action: a new ticket must point at one system record. If it cannot, you are still in the no-entry habit—just with an extra unused icon.