OreLynx
Assess your workflow
Mineral tenure and obligations

Know What Is Due. Prove What Was Done.

Connect each mineral right, permit or commitment to its source, due logic, owner, work, evidence and recorded outcome. Qualified reviewers remain responsible for interpretation and authority engagement.

Review my obligation workflow

Separate the Source, Work and Outcome

A defensible workflow does not treat a calendar reminder as proof of compliance. It records the source and configured interpretation, assigns the operational work, preserves the evidence review and distinguishes internal completion from submission, receipt, acknowledgement or authority acceptance.

Jurisdiction Configuration Requires Qualified Approval

A jurisdiction pack organises local terminology, calendars, obligation types and template metadata. Each configured item retains an attributable source, version, qualified reviewer, approval state and review date. Country coverage is confirmed through the selected pack rather than inferred from a generic template.

Illustrative workflow modelSource-to-outcome workflow
  1. 01
    Register sourceRecord the authority, jurisdiction, source document, version and effective dates.
  2. 02
    Define ruleDescribe the trigger, recurrence, lead time, evidence and escalation in local terminology.
  3. 03
    Approve applicabilityRequire a named qualified reviewer to approve the configured rule and review date.
  4. 04
    Assign workSet an accountable owner and separate preparer, reviewer and submitter roles where needed.
  5. 05
    Review evidenceCheck completeness and preserve the decision, reason and supporting record.
  6. 06
    Record outcomeKeep internal completion, submission and authority acknowledgement as distinct states.
OreLynx configures this path against the selected jurisdiction sources, review responsibilities and customer-approved obligation rules.

Questions to Resolve in Assessment

  • Which sources are authoritative, who can interpret them and how often must they be reviewed?
  • Which dates are fixed, calculated, event-triggered or dependent on authority action?
  • What evidence is required before internal review, submission and closure?
  • Who owns preparation, approval, submission, acknowledgement and escalation?

Tenure and obligation features

Know What Is Due and Preserve the Proof

Responsible teams can connect rights, permits, obligations, submissions and evidence without treating software as legal advice.

01

Rights and permit register

Record identifiers, holders, locations, dates, status, source documents and responsible internal owners.

02

Obligation schedules

Configure due logic, reminders, dependencies, accountable roles and escalation paths for recurring or event-driven work.

03

Submission preparation

Assemble required documents, reviews, approvals and delivery evidence before an authorised submission.

04

Completion evidence

Keep receipts, correspondence, decisions, corrections and the source used to mark an obligation complete.

Bring one real workflow. We’ll map these functions to your roles, records, systems and acceptance scenarios.

Assess your workflow