TenkaTenka
Sign in

Tenka Help Center › Where work gets stuck › Service order

Service order

The record of the field service: customer, scope, parts, hours, and signature. A closed service order is the basis for billing and warranty — closing it without logging parts and hours loses revenue and the traceability of what was done.

🕒 Updated on Oct 9, 2026📖 ~3 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 nowFilterClearResolveAssign ownerAssign and resolveCancel

Form fields

AchadoO que está incoerente, escrito para quem vai resolver.
Tipo do achadoCategoria da incoerência: processo sem dono, indicador sem meta, cliente sem responsável.
EntidadeQue tipo de registro está órfão: processo, indicador, contrato, cliente.
SituaçãoAberto ou resolvido. Resolvido sai da fila de trabalho mas continua no histórico.
Onde resolverAtalho para a tela em que o achado se conserta, sem procurar no menu.
Detectado emQuando a varredura encontrou a incoerência. Achado antigo aberto é dívida acumulando.
Resolvido emQuando alguém consertou. A distância até a detecção é o tempo de reação da casa.

Start here

O que esta tela responde
It runs rules that point out contradictions in the data (active contract without billing, completed request without hours). Each check is a symptom, not a verdict: some have legitimate exceptions — address the recurrence, not the isolated case.
O que esta tela faz
The continuous audit of the management model: the system sweeps the data and lights up, one by one, the inconsistent points (process without owner, indicator without target, expired SOP, ineffective action plan) and the orphan results (contract, result center, client, indicator, target, project or macroprocess without owner). Each finding brings the link that resolves it and owner assignment in one click.
Para que esta tela existe
The continuous audit of the management model: the system sweeps the data and lights up, one by one, the inconsistent points (process without owner, indicator without target, expired SOP, ineffective action plan) and the orphan results (contract, result center, client, indicator, target, project or macroprocess without owner). Each finding brings the link that resolves it and owner assignment in one click. — this is the role of the "Consistency checks" screen within the platform.

How to

As quatro ações de cada achado
"Resolve" opens the point's source screen — the place where the correction actually happens. "Assign owner" (only in orphan result findings) opens the dialog, you choose the user and the point is resolved upon assignment. The check marks it resolved without leaving the screen, for what you already fixed elsewhere. And the bell SILENCES: the point does not return in the next sweeps — use it sparingly, because silencing is accepting the state as it is.

Rules

Checagem reprovada não bloqueia, aponta
As checagens de coerência mostram onde dois números deveriam bater e não batem; nenhuma trava a operação. O que trava é a regra da tela de origem — a checagem diz onde olhar.

Frequently asked questions

Que pergunta do dia a dia se responde aqui
"What in my management model is without an owner or without a target right now?" — when that question comes up, this is the screen that answers it.
Do I need to trigger the sweep or does it run on its own?
Both: the sweep runs on its own every day, and the "Sweep now" button forces an immediate pass — useful right after assigning owners or fixing records, to see the scoreboard drop on the spot. Each detector is an independent query on the real data, so a new finding enters as soon as the data reveals it, and what was fixed disappears when the condition ceases to exist.
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