# Lifecycle Current-Stage Time Interpretation

Keep completed stage-duration properties separate from time still accumulating in the current stage.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Record IDs, entry/exit history, latest/cumulative stage-time exports, current stage and plan evidence.

## Workflow
1. Map every duration field to its named stage.
2. Record Professional/Enterprise requirement for latest and cumulative time properties.
3. When currently in a stage, preserve documented blank or prior-visit duration behavior rather than using it as a live timer.
4. Return interpretable history and unknowns without changing CRM fields.

## Output contract
record | stage | currently_in_stage | prior_visits | latest_time | cumulative_time | interpretation_hold

## Fictional acceptance test
Fictional A re-enters SQL and has a previous visit of 600 seconds. Its supplied 600-second latest-time field is not proof that the current visit lasted 600 seconds. Missing exit keeps current duration held.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://knowledge.hubspot.com/records/use-lifecycle-stages

Checked October 13, 2026. Oct13 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude43, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia103. Social calendar/reporting topics follow parent-query leads; other professions follow documented workflow needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.