Phase 📝
Official URL: https://bcgov.github.io/nr-pies/docs/standard/element/process_tracking/phase
Purpose
Phase is a business-level category of engagement with an authorization. It distinguishes whether the record is still being created and assessed e.g., Application or is already in effect and being managed e.g., Post-issuance. If defines the why part of work on the authorization, not process categories of work, see Stages below.
Usage
Phase is set to Application when an authorization record is created and is updated to Post-issuance once the permit is formally issued. Consuming systems rely on this value to invoke the appropriate workflows, controls, and reporting logic, signalling whether the authorization remains in development or is an active instrument.
Guidance
- Exactly one Phase is active at any time.
- Phase does not define the specific operational categories of work, these are defined at the Stage level.
- Phases are about what type of work is happening, not when it happens (see Milestone dates).
Properties
- Data format: string
- Null: Cannot be
null– every authorization must have a phase. - Relationships:
- Lifecycle → Phase: A phase is a subset of a lifecycle (Lifecycle → Phase is 1-to-many).
- Phase → Stage: A stage is a subset of a phase (Phase → Stage is 1-to-many).
- Change control: A phase should change at most once per authorization.
Allowed values (by Lifecycle)
Permitting Lifecycle
| Name | Description |
|---|---|
| Application | Indicates that the authorization is currently undergoing the application process e.g. creating, vetting, evaluating... and has not yet been issued. |
| Post issuance | Indicates that the authorization has been issued and is now active or being managed e.g., through amendments, renewals, or maintenance activities. |