# Forecast Period Default Date Screen

Flag automatically supplied close dates before treating them as buyer-backed forecast timing.

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

## Inputs
Deal create date/source, close date, account default settings, date history and documented buyer timing.

## Workflow
1. Identify whether the date was supplied by a buyer or may come from a creation default.
2. Keep desktop custom-default behavior separate from other creation paths.
3. Group records with default-date evidence without moving them to another forecast period.
4. Return timing confidence and missing source evidence; no close-date edit.

## Output contract
deal | creation_path | close_date | default_evidence | buyer_timing | forecast_timing_hold

## Fictional acceptance test
Fictional open deal createdOct 10 with no buyer timing and close dateOct 31. A last-day default can explain the field, not prove the buyer will signOct 31. Unknown creation path remains unknown.

## 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/properties/hubspots-default-deal-properties

Checked October 10, 2026. Oct10 live AIS Search Console through Oct6: marketing Copilot 37 impressions, Planable/Claude 33, Planable/ChatGPT 23, campaign brief 12, investor agent 19. Social-review/reporting topics follow these parent-query leads. Other professions follow documented workflow needs, not measured exact search intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.