More features are not better. Patrol staff wear gloves, stand in backlight, hit weak networks. The page has to be short. Awards and news in a reporting APP are the field version of a vanity project. See Why shipping an APP just to “have one” fails. Employee features people will actually use is in Employee features people will actually use.
Why a PC backfill creates rework
Memory flatters itself. Checking “normal” at night against twenty blurry photos lets exceptions show up as next week’s customer fault. On-site submit pins the timestamp to the point. When a PC will not open, the system does not exist. See If field staff never sit at a PC, the PC system does not exist. Whether you need an offline cache is in No network on site—do you need offline—not every patrol needs offline. Basements and the field come first.
After submit, it must enter the same tickets
If the phone only saves photos to a camera roll and WeChats the lead, the three steps were wasted. Documents must enter the back office so repair, parts and recheck grow from the same exception. Architecture is in one back office. In efficiency you can actually see, “finish once on site” is the first card. See Mobile efficiency you can actually see.
Keep the list short. Someone must catch exceptions
A forty-option patrol sheet gets all-normal on the floor. Keep required checks to the few that hit safety or date. The rest become sample or periodic. When an asset moves or a code falls, someone reprints that day or scan falls back to typing. Once typing is open, points drift again. Watch rework in the first two weeks: a second trip to reshoot. Still reshooting means the on-site loop is not closed.
Point codes are the foundation of the field entry
A crooked, duplicate or stale code after a move makes scan point at the wrong object. The three steps then lie systematically. Name owners: who prints, who posts, who rechecks after repair. Change the point list with the asset ledger. Do not keep two sheets. Replace a fallen code the same day, not at the monthly patrol. The reprint must be traceable.
When submit fails, the photos must still be there
A failed weak-network submit must retry and keep photos, or techs will call the system hostile. Allow a reshoot when a photo is soft. Do not pass a blur by default. Block submit if a required photo is missing. Keep exception levels few: normal and urgent. Too many grades and the floor picks the lowest.
Do not also ship knowledge, points and a community in phase one. A long reporting path sends the floor back to photo-in-group. Write the date the old path closes into acceptance. That is closer to less rework than another splash screen. DaXi Technology accepts reporting by walking three steps at a real point, not a demo account. To turn a checklist into phone actions, go to the mobile service page and bring the current checklist.