Phase 02 · Assign

Issue the Tag, Then Close the Return

Connect a crew alias, vehicle alias, tag alias, and return responsibility in one internal assignment record.

CREW-02 PAINT VAN A BLUE TAG

Why this step matters

Make issue and return responsibility visible

One open record per tag alias helps expose missed returns, vehicle changes, or tags that need a separate incident workflow.

Who received the tag
Which vehicle carried it
When it should return
Whether it returned to the vehicle

Interactive browser-local worksheet

Build the internal record

The calculated status reflects this internal record only. It does not prove who drove, whether a trip occurred, or how an account was charged.

Crew Alias *

Driver First Name or Employee Code *

Use only a first name or non-confidential internal code.

Vehicle Alias *

Tag Alias *

Issue Date and Time *

Expected Return *

Actual Return

Project Nickname

Returned to Vehicle *

Status *

Exception Notes

Explain only the operational exception; omit personal or official account data.

Latest calculated status

Saved in this browser

Record history

Review, edit, archive, or remove local entries. Historical aliases are preserved when referenced.

Hiker wearing a white cap and hydration vest resting among alpine wildflowers — A pause point is a useful time to confirm a return. Editorial field image; not a depiction of company vehicles, tags, crews, or services.

Close the loop

Do not let an expected return become an assumption

Record the actual return and confirm where the tag went. If it is missing, start a separate internal incident sheet and use the official channel when appropriate.