Skip to DART content

Locations, time, and rest

Track where people have worked and for how long. Use that history to review time at a location and rest needs.

Separate a person’s location record from an actual visit

A residence of record, permanent duty station, and temporary duty assignment describe where a person is based. They have dates and a saved place identity. A deployment visit instead records actual arrival and departure.

Authorized editors record or correct a person’s location assignments. A correction links to the earlier version rather than erasing it. Shared place definitions also have versions, so an address correction can be traced.

A canonical location gives a place a stable identity across records. Its kind, time zone, and policy area support later calculations. Matching display names alone is not enough to combine places.

Private address lines are shown only to the person and permitted editors. Other readers may receive a reduced location view. Medical leave details are also reduced for readers without the required access.

Count occupied time and explain the source

Time at a place comes from intervals with a known start and end. An open visit ends at the review’s cutoff for calculation purposes. Future time and invalid intervals do not add to the total.

The cumulative view groups visits by location identity and physical or remote kind. Overlapping intervals in the same group count once. The output retains visit and deployment IDs behind the total.

A location-policy review can use actual visits or dated temporary assignments as its source. That choice is part of the approved rule, not a guess made by the report.

The rule can group places by location or policy area. It sets whether remote time counts, how nearby periods join, and whether duration means occupied time or elapsed time. Those choices can produce different findings.

Place totals clip actual visits to the review cutoff, separate physical and remote groups, and count overlapping time only once while retaining the source IDs.Visit AArrival and departureVisit BMay overlap visit AGroup by place +kindStable locationidentityClip at cutoffOpen visit ends atreview timeMerge overlapDo not add the sametime twiceCumulative hoursVisit and deploymentIDs kept
Place totals clip actual visits to the review cutoff, separate physical and remote groups, and count overlapping time only once while retaining the source IDs.

A gap between orders is not proof of rest

Rest review distinguishes recorded time away from time that has no supporting record. Between deployments, the calculation clips the permitted status intervals to the gap and counts overlaps once. The remaining hours stay unverified.

The approved rest rule chooses which statuses count. It sets minimum recorded hours and the largest permitted unverified gap. A finding marks a gap for review when either limit is missed.

A within-deployment rule can also check periods without enough recorded rest. This uses the current versions of status records tied to the deployment. Unknown time does not silently become rest.

These evidence checks differ from the planning policy’s minimum days between assignments. Planning limits affect a proposed assignment; the location review explains the recorded time and its sources.

The gap between deployments is split into recorded permitted time away and unverified time. The approved rule tests both quantities; an empty gap is not proof of rest.EarlierdeploymentRecorded periodGap between workClip status evidenceto gapNext deploymentRecorded periodRecorded time awayOnly permittedstatusesUnverified timeNo supporting intervalRecorded andunknown limitsmet?Saved restfindingReview source evidence
The gap between deployments is split into recorded permitted time away and unverified time. The approved rule tests both quantities; an empty gap is not proof of rest.

Use the place and date context saved with the work

An incident-local day, a dated location assignment, and an actual timestamp serve different purposes. Operational visits keep actual times. Availability and incident checks interpret dates in their saved time zones.

Changing a place definition keeps a new version and a reason. It does not rewrite the recorded arrival time. Daylight-saving changes must be handled through the relevant zone rather than a fixed clock offset.

A source record must provide the place identity or policy area required by the rule. Missing facts are a reason to check the source, not permission to assume a location.

Approve examples before applying a location rule

A personnel steward drafts the organization’s location and rest rules with a source reference and expected examples. A different policy approver checks the latest draft. The examples are checked both when drafted and when approved.

A review needs the approved rule and the source records at its cutoff. Each work period needs one unambiguous residence or permanent-duty origin, as the rule requires. An actual-visit rule stops if required deployments have no visit record.

The saved result keeps its policy version, input snapshot, source fingerprint, and review cutoff. Later source changes are flagged instead of rewriting the earlier result.

A finding is a policy review to inspect against its sources. It does not automatically change a responder’s qualification, approve a benefit, or certify compliance with an agency rule.

The location rule and source records are checked together. A missing or ambiguous origin stops review; a saved finding retains the rule, input, and cutoff.YesNoRule + examplesSteward suppliessourceDifferentapprover?Approved ruleVersion and effectivedatePlaces + workrecordsOrigin, visits,statusesRequired sourcescomplete?Saved reviewRule, input, cutoffSource changed flagEarlier finding stayssavedCheck missing sourceNo guessed origin
The location rule and source records are checked together. A missing or ambiguous origin stops review; a saved finding retains the rule, input, and cutoff.