Exploration Licence & Work Programme Management Documentation

Tenure and the parties on it, the statutory obligations a licence carries and the actions that discharge them, the work-programme and expenditure commitments that prove the ground is being explored, licence conditions, approvals and land access, the submissions lodged to the regulator and the correspondence they provoke, the variations, exemptions, renewals and relinquishments that change the licence, and the compliance-risk register, evidence trail and periodic compliance snapshot that answer one question: are the obligations being met?

This section covers the Exploration Licence & Work Programme Management application specifically. For how the interface works in general (lists, forms, navigation, deletion), see the Framework Guides above.

In This Section

The Application in One Paragraph

Exploration Licence & Work Programme Management runs the compliance record for an exploration project end to end, from the tenure a jurisdiction grants to the decision that the licence's obligations have been met. An exploration project holds one or more tenements — the exploration licences themselves — each with its tenement parties (holder, JV partner, Traditional Owner). Every tenement carries statutory obligations: expenditure, annual and technical reporting, work programme, rent, renewal, data submission. Each obligation is worked off through obligation actions, and the two that matter most to a regulator get their own structures — the work-programme commitment records committed metres and dollars against actuals and variance, and the expenditure obligation tracks the minimum annual spend against eligible expenditure line items, carry-forward, exemption and the resulting shortfall. Around the tenement sit its licence conditions, its approvals and permits, and its land-access agreements. Compliance is proven by lodging statutory submissions, each built from validated submission requirements and answered by regulator correspondence in both directions. When the licence itself must change, a variation application, exemption application, renewal or relinquishment carries that through. Cutting across all of it are the compliance-risk register, the evidence items and their obligation evidence links back to specific obligations, the decisions that record why a course was taken, and the periodic compliance snapshot that rolls the whole project up into one status line. This is app 3 of 3 in the Exploration Assurance Suite — the compliance chain — and it shares the same canonical Copperfield project and tenement keys as its two siblings.