# Check administrative closure timestamps before timing work

Illustrative planning brief; no automatic product import.

Synthetic case: A reviewer accepted work at 16:00 on day 1; an administrator closed the record at 09:00 on day 2. The report currently uses the closure time as acceptance.

## Decision

Retain both events and use the documented accepted-finish evidence if it is verified; otherwise mark the chosen clock unresolved.

## Owned work

- Locate event evidence
  - Owner role: Task owner
  - Acceptance evidence: Acceptance and closure have separate dated records.
- Confirm the selected finish
  - Owner role: Acceptance reviewer
  - Acceptance evidence: The 16:00 evidence corresponds to the agreed finish criterion.
- Explain the correction
  - Owner role: Report owner
  - Acceptance evidence: Six hours under the chosen clock is distinct from 23 hours to administrative closure.

## Workflow

1. Write each timestamp’s actual meaning.
2. Check whether the agreed finish event is evidenced.
3. Keep the closure action visible without calling it acceptance.

## Judgment

Do not infer an earlier finish just because a later timestamp is administrative. Unverified acceptance remains unverified.


## Filled review note

Reviewed clock note: 6 elapsed hours to verified reviewer acceptance; 23 hours to administrative closure is a separately labelled span.


## Workflow questions

### Is record closure always the finish?

No. It depends on the agreed workflow and evidence; this example separates two observed actions.

### Should I edit the production timestamp from this worksheet?

No. The kit is manual review guidance and performs no product writes.

## Product connection

Bring this manual reporting policy and its owned checks into your TeamBoostAI work discussion. Native report/export fields and historical reconstruction depend on your account and implementation; this worksheet does not import or change product records.

Confirm account availability before adopting this manual outline.

## Decision workshop

Synthetic examples only. Manual worksheet; no automatic import or product writes.

### Synthetic reporting records

Event | UTC time | Meaning
--- | --- | ---
Active start | Day 1 10:00 | Clock start
Reviewer acceptance | Day 1 16:00 | Candidate finish evidence
Administrative closure | Day 2 09:00 | Separate status action

### Version changes

Boundary | Draft | Revised
--- | --- | ---
Event meaning | Closure treated as acceptance | Acceptance and closure have separate meanings
Clock selection | Latest status timestamp | Chosen evidenced finish boundary

### Draft or earlier version (review its limits)

Draft: 23 elapsed hours to status closure.

### Revised example

Reviewed clock note: 6 elapsed hours to verified reviewer acceptance; 23 hours to administrative closure is a separately labelled span.

### Decision situations

- Acceptance evidence and clock policy agree: Use the acceptance event and disclose the separate closure timestamp.
- Acceptance evidence does not match the policy: Hold the duration correction and resolve the criterion.
- Only administrative closure is known: Report that fact without inventing an earlier finish.

### Evidence dependencies

- Finish criterion → Chosen duration: defines meaning
- Acceptance evidence → Chosen duration: proves event

### Method references

- The Kanban Guide, May 2025: https://kanbanguides.org/the-kanban-guide/2025.5/ — Clock and work-item definitions; examples and local rules are our own.