TenkaTenka
Sign in

Tenka Help Center › Where work gets stuck › Field service order

Field service order

The service order in the technician's hands: geo check-in, execution, photo, and signature on site. The check-in proves WHEN and WHERE the service happened — with no signal, it records and syncs later; the timestamp is that of the check-in, not of the sync.

🕒 Updated on Sep 3, 2026📖 ~1 min read

What you find on this screen

A portrait of the screen, read from the screen itself — it changes when the screen changes.

Available actions

Scan now

The list shows

ProcessScoreRecommendationHours/monthSavable per monthTrail

Start here

What this screen answers
Points out the repetitive, manual steps worth turning into automation, ranked by effort saved. The estimated return assumes the current volume — low volume brings the priority down; it is a suggestion of where to start.

How to

How to read a line
Score 200+ with high structured data = candidate for an AI agent; score 200+ without structured data = native automation (form/flow); score 100–199 = integration between systems; below that, a robot is only worth it when repetitiveness is high. The R$/month is the honest ceiling: activity effort × automation type factor.

Rules

De onde vêm os números
Nothing here is opinion: volume comes from completed executions, hours and cost come from time entries and payroll, and each score keeps its calculation breakdown (the list button on each row). A repeated scan UPDATES the suggestion — the radar follows the operation, it does not freeze a snapshot.
Radar vazio não é "nada a automatizar"
The radar only measures processes with an AS-IS sheet tied to a demand type. If the list is empty, the way forward is Processes ▸ AS-IS: fill in the process sheet and tie it to the demand type that executes it — it will come in on the next scan.
Was this article helpful?

In the same module: Where work gets stuck14

Tenka Academy

Step-by-step learning paths for your industry, inside the platform.

Explore the Academy