Utility Repair Request Stamps for Dispatch Continuity

A utility repair request can pass through customer service, a control room, dispatch, field crews, contractors, inspectors, and billing before it is truly closed. A generic “IN PROGRESS” mark does not tell any of them whether the location was verified, a crew was assigned, service was restored, or follow-up remains open.

The right stamp system is a compact state map. It connects the customer’s report to the correct asset, preserves handoffs across shifts, and keeps restoration separate from administrative closure. It does not replace emergency procedures, field-safety rules, or the utility’s system of record.

At intake, record what the customer or monitoring channel reported without turning it into a field diagnosis. A useful first mark can contain:

• service request number;
• reported date and time;
• intake channel;
• reported address or service point;
• customer wording or a short report code;
• intake operator identifier;
• callback or communication requirement.

Use “REPORTED OUTAGE” or “CUSTOMER REPORTED LEAK” when that is all the desk knows. Reserve “CONFIRMED” for an authorized check. This distinction prevents an initial description from becoming an unsupported fact as the record moves downstream.

If a report may involve immediate danger, staff should follow the utility’s emergency escalation procedure first. A stamp can document that escalation, but it should never delay it.

Address text is not always enough. Apartment entrances, rear meters, shared service lines, cross streets, and similarly named roads can send a crew to the wrong place. The record should show which identifiers were matched and which remain uncertain.

A compact asset-validation block could include:

The companion article on covers the earlier intake boundary between permits, repairs, and general service questions.

Priority labels must reflect the utility’s approved criteria. A red impression may attract attention, but color can disappear in scans and should not be the only signal. Include a readable priority code, the basis or source, the assigning role, and the timestamp.

For example:

• EMERGENCY PATH ACTIVATED — SEE INCIDENT PROCEDURE;
• PRIORITY P1 — ASSIGNED BY CONTROL ROOM;
• ROUTINE SERVICE — TARGET WINDOW RECORDED;
• PRIORITY REVIEW NEEDED — CONDITION UNCONFIRMED.

Do not let a free-text “URGENT” stamp bypass the decision authority. The label should identify who applied the level and which protocol governs it.

The dispatch state needs more than a crew name. It should connect assignment, acceptance, travel, access, and dependency information:

• DISPATCHED — crew / contractor / time;
• ASSIGNMENT ACCEPTED;
• EN ROUTE;
• SITE ACCESS PENDING;
• CUSTOMER CONTACT ATTEMPTED;
• TRAFFIC CONTROL / PERMIT / LOCATE DEPENDENCY;
• REASSIGNED — reason code;
• HOLD — next review time.

For field-service boards where ownership changes at a shift boundary, use the more detailed . Freight and transport operations have a different chain of custody; that distinction is covered in the .

A caller reports loss of service at 18 River Street. The account record points to 18 River Road, while the mapped meter is behind a shared building entrance. The desk should not silently choose one.

The packet can show:

LOCATION MISMATCH · CALLER: 18 RIVER ST · ACCOUNT: 18 RIVER RD · ASSET MATCH PENDING

After verification, a second mark preserves the resolution:

LOCATION VERIFIED 14:26 · SP-9031 · SOURCE: FIELD CALLBACK · DISPATCH RELEASED

Both impressions stay in the history. A later reader can see why dispatch paused and which evidence resolved it.

Field findings belong in their own block with crew identity, arrival time, inspected asset, observed condition code, work performed, materials or contractor reference, and any follow-up. The customer’s original report remains intact.

Useful states may include:

• CREW ON SITE;
• CONDITION CONFIRMED / NOT FOUND;
• TEMPORARY REPAIR COMPLETED;
• PERMANENT REPAIR REQUIRED;
• PART / CONTRACTOR / PERMIT PENDING;
• SITE LEFT SAFE PER PROCEDURE;
• INSPECTION OR TEST REQUIRED.

The wording and authorization must match local operating and safety rules. A document stamp is a routing and evidence device, not technical repair instruction.

“Service restored” may describe the customer-facing outcome while excavation repair, inspection, pavement restoration, invoice review, or regulatory reporting remains open. Give these events separate states:

1. SERVICE RESTORED — time and confirming role.
2. CUSTOMER NOTIFIED — channel and attempt result.
3. PERMANENT WORK OPEN — owner and due date.
4. INSPECTION PASSED / FOLLOW-UP REQUIRED.
5. RECORD COMPLETE — required evidence attached.
6. CLOSED — authorized role and date.

This prevents a restored case from disappearing before the organization finishes its obligations. It also stops an administrative “closed” label from being mistaken for proof that service was restored.

Create labels in the with a strong state line, a small set of fixed fields, and room for the request ID. Avoid decorative borders that compete with handwriting or disappear on a low-resolution scan.

A durable layout uses:

• a state phrase at the top;
• request and asset IDs in the center;
• date, time, and owner at the bottom;
• an exception code beside—not over—the main state;
• a fixed placement zone on the service-request cover sheet.

A can document the initial event, while later operational marks should be visually distinct enough that staff do not confuse receipt with assignment or completion.

Sample closed and still-open cases. For each one, ask whether a reviewer can reconstruct:

• what was reported;
• which asset and location were used;
• who set priority;
• every dispatch or reassignment;
• the field finding;
• restoration time;
• remaining work;
• customer communication;
• final closure authority.

If one of those answers depends on an inbox search or someone’s memory, add the missing field to the responsible state—not a new catch-all stamp. The strongest service board is small, legible, and explicit about unresolved work.