> For the complete documentation index, see [llms.txt](https://help.stackdx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.stackdx.com/untitled/resolving-discrepancy-types/extension-types-and-extension-dates.md).
# Extension Types and Extension Dates
### Extension Types and Extension Dates
This is the section to spend the most time on. Extension data is where lease validity actually lives — if it's wrong, you're either holding lands you've lost or letting go of lands you've kept.
{% hint style="info" %}
How Crown Compare handles this differently from most utilities: instead of matching all extension data for a lease against all extension data on the Crown side and hoping for the best, Crown Compare matches **lands and rights first**, then compares extensions within those matching slices. So if you have "Section 20, surface-to-base Mannville" on both sides, the check compares the extension type and date for that specific slice, not the lease blob.
{% endhint %}
{% hint style="warning" %}
Right now, extension type/date matching is Alberta only. Saskatchewan is in progress with the provincial government. BC is on the roadmap after that. Filtering by province will scope your review correctly.
{% endhint %}
{% stepper %}
{% step %}
### Filter by Extension Type
Use the **Extension Type** filter to isolate and review specific lease extension types.
{% endstep %}
{% step %}
### Filter by Extension Date
Apply the **Extension Date** filter to capture extension date mismatches.
{% hint style="info" %}
Filter on both Extension Type AND Extension Date during your review. Some leases have the type entered but not the date (or the date but not the type), so filtering only one will miss cases.
{% endhint %}
{% endstep %}
{% step %}
### Review Extension Data
Expand a row, or all rows see below, to review detailed extension data on a matching agreement.
{% endstep %}
{% step %}
### Identify Discrepancies
Look for a red **X** icon indicating a discrepancy between CS Land and the Crown side.
{% endstep %}
{% step %}
### Review Extension Type Discrepancies
Check the **Ext. Type(s)** column to identify missing extension codes or indefinite date mismatches.
{% hint style="warning" %}
Watch the **82-1 (shallow rights reversion)** cases especially. The Crown is splitting up rights differently than what we're seeing at most clients — Crown will show a "15" plus an "82-1" where your land system has a blanket 82-1 on the whole lease. Expect a lot of these to surface as everyone fumbles through the new SRR process. This is where Crown Compare adds the most value right now.
{% endhint %}
{% endstep %}
{% step %}
### Check Rights Formatting
Review the lease splits to check for improperly formatted rights entries.
{% hint style="info" %}
Sometimes a discrepancy isn't really a discrepancy — it's that the rights were entered as text with parentheses instead of proper rights, which throws off the matching logic. Check the rights column when something looks off. Clean those up while you're in there.
{% endhint %}
{% endstep %}
{% endstepper %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.stackdx.com/untitled/resolving-discrepancy-types/extension-types-and-extension-dates.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.