---
title: "Build a unified policy period timeline"
summary: "Build a unified policy period timeline."
status: draft
owner: Technical Writer
last_reviewed: 2026-07-31
library: SAIF.Business.Policy.Core
reference_type: package
operation_id: "OP-003"
trigger: "any consumer needing the full period history of a policy across both administration systems"
---

# Build a unified policy period timeline

Build a unified policy period timeline describes the corresponding policy-core workflow and its BOF or Oracle touchpoints.

| Field | Value |
| --- | --- |
| **Operation ID** | OP-003 |
| **Trigger** | any consumer needing the full period history of a policy across both administration systems |
| **Inputs** | data portal, policy number (or `IEnumerable(Of Decimal)` of policy numbers, or an association type) |
| **Outputs** | `clsPolicyPeriodBaseCollection` of `iPolicyPeriod` items |
| **Primary components** | ``clsPolicyPeriodBaseCollection.GetPolicyPeriods(inDataportal, inPolicyNumber)` (`clsPolicyPeriodBaseCollection.vb`)` |
| **Entry point** | `Business\SAIF.Business.Policy.Core` |

## Steps
1. Retrieve modern periods via `clsPolicyPeriodCollection` (tables `POLICY_PERIOD`, `POLICY_PERIOD_MASTER`).
2. Retrieve legacy periods via `clsLegacyPolicyPeriodCollection` (tables `POLICY_PERIOD_NON_WCIS`, `NON_WCIS_STAT_TRANS`).
3. Merge both sets into one collection ([BR-010](../business-rules.md#br-010-a-policys-period-history-is-the-union-of)).
4. Sort ascending by `EffectiveDate`.
5. Call `LinkItems()` to establish prior/next period links, then `SetCurrent(0)`.
6. Overloads: the `IEnumerable(Of Decimal)` overload applies `SelectMany` across policy numbers; the association-type overload unions both sources and orders by `EffectiveDate` **descending**.
7. Return the merged collection.
8. Consolidate supporting references.
   - Related business rules: [BR-004](../business-rules.md#br-004-the-current-period-is-the-first-period-flagged), [BR-005](../business-rules.md#br-005-experience-rating-base-periods-are-those-whose-begin-date), [BR-010](../business-rules.md#br-010-a-policys-period-history-is-the-union-of), [BR-011](../business-rules.md#br-011-association-based-period-retrieval-uses-a-different-predicate-per), [BR-012](../business-rules.md#br-012-an-association-type-outside-the-supported-set-is), [BR-013](../business-rules.md#br-013-standard-premium-is-sourced-from-wcis-for-wcis), [BR-014](../business-rules.md#br-014-a-modern-policy-period-is-considered-issued-when), [BR-015](../business-rules.md#br-015-a-legacy-policy-period-is-never-reported-as), [BR-016](../business-rules.md#br-016-coverage-bound-status-is-sourced-from-wcis-for-modern), [BR-031](../business-rules.md#br-031-a-policy-period-is-flat-cancelled-when-its-effective), [BR-032](../business-rules.md#br-032-preliminary-audit-is-required-when-the-wcis-edit)
   - Related SQL statements: [SQL-012](../sql/SQL-012-saif-business-policy-core.md), [SQL-033](../sql/SQL-033-saif-business-policy-core.md), [SQL-061](../sql/SQL-061-saif-business-policy-core.md), [SQL-062](../sql/SQL-062-saif-business-policy-core.md), [SQL-063](../sql/SQL-063-saif-business-policy-core.md), [SQL-078](../sql/SQL-078-saif-business-policy-core.md), [SQL-079](../sql/SQL-079-saif-business-policy-core.md), [SQL-080](../sql/SQL-080-saif-business-policy-core.md), [SQL-081](../sql/SQL-081-saif-business-policy-core.md), [SQL-082](../sql/SQL-082-saif-business-policy-core.md), [SQL-083](../sql/SQL-083-saif-business-policy-core.md), [SQL-088](../sql/SQL-088-saif-business-policy-core.md), [SQL-091](../sql/SQL-091-saif-business-policy-core.md), [SQL-134](../sql/SQL-134-saif-business-policy-core.md), [SQL-155](../sql/SQL-155-saif-business-policy-core.md)
   - Related tables: [DUAL](../database-tables.md#dual), [POLICY_PERIOD_MASTER](../database-tables.md#policy_period_master), [POLICY_PERIOD_NON_WCIS](../database-tables.md#policy_period_non_wcis), [POLICY_PERIOD](../database-tables.md#policy_period)

## Process flow

The following diagram visualizes this operation's control flow.

```mermaid
flowchart TD
    Start([Trigger]) --> S1[Apply policy-core logic]
    S1 --> D{Validation or branch?}
    D -->|Continue| S2[Execute BOF SQL or Oracle call]
    D -->|Stop| EndErr([Return error or empty result])
    S2 --> EndOk([Return populated result])
```

## Failure and edge-case behavior
- Error, warning, and empty-result behavior follows the rules and SQL cited in the steps above.
- Stored-procedure-backed paths depend on Oracle-side logic outside this repository.**

## Related documentation
- [Operations and processes](../operations-processes.md)
- [Business rules](../business-rules.md)
- [SQL catalog](../sql/index.md)
- [Database tables](../database-tables.md)

> **Note:** Statements marked with * were inferred from code structure, naming conventions, or
> contextual evidence where direct confirmation was not available in source artifacts. Statements
> marked with ** could not be confirmed; treat as unknown until verified.

## Sources
- `Business\SAIF.Business.Policy.Core\clsPolicy.vb`
- `Business\SAIF.Business.Policy.Core\clsPolicyPeriodBase.vb`
- `Business\SAIF.Business.Policy.Core\clsPolicyPeriod.vb`
- `Business\SAIF.Business.Policy.Core\clsLegacyPolicyPeriod.vb`
- `Business\SAIF.Business.Policy.Core\clsCancelReasonOverride.vb`
- `Business\SAIF.Business.Policy.Core\WCISInquiry.vb`