Sense workflows

Intelligence that moves the work forward.

Purpose-built workflow patterns for the document, data, ownership, revenue, asset, and transaction work surrounding real assets.

Explore workflows
More than a prompt

The anatomy of a Sense workflow.

A specific trigger starts a bounded unit of work.
Sense gathers only the permitted evidence and operational context required.
Deterministic code, AI, and approved tools each handle the work they are suited for.
Uncertainty becomes a visible exception instead of a silent guess.
A person remains in control of consequential decisions and changes.
Sources, approvals, actions, and outcomes remain traceable.
Workflow library

Start with the work that needs to move.

17 workflows

01Documents & data

Intelligent document intake

Turn incoming files into classified, connected work instead of another folder or inbox backlog.

OperationsLandAccounting

Trigger

A document is uploaded, received, or added through an integration.

Sense workflow

  1. 1Classify the document and preserve the original source
  2. 2Extract required fields, tables, and supporting evidence
  3. 3Match the file to the correct assets, parties, and records
  4. 4Route complete work forward and exceptions to an owner

Human control

A reviewer resolves uncertain classifications, missing required fields, and conflicting identity matches.

Faster intakeVisible exceptionsConnected records
02Documents & data

Structured data extraction

Convert PDFs, scans, spreadsheets, and legacy exports into validated data without losing source context.

DataOperationsAnalysts

Trigger

A supported document or data package enters a defined extraction workflow.

Sense workflow

  1. 1Read text, layout, tables, and document-specific structure
  2. 2Map extracted values into a typed business schema
  3. 3Validate formats, totals, required values, and relationships
  4. 4Publish accepted data with field- or row-level provenance

Human control

Low-confidence or invalid values remain reviewable and are never silently converted into authoritative facts.

Less rekeyingTraceable dataReusable structure
03Documents & data

Evidence-aware knowledge search

Answer operational questions across permitted files and records while keeping the answer tied to evidence.

Asset teamsExecutivesNew hires

Trigger

A user asks a question about an asset, party, obligation, payment, or operating history.

Sense workflow

  1. 1Resolve the question to relevant entities and time periods
  2. 2Retrieve permission-aware records, documents, and relationships
  3. 3Synthesize the answer with source references and uncertainty
  4. 4Let the user inspect evidence or advance the result into work

Human control

The user sees the evidence behind material claims and remains responsible for consequential decisions.

Faster researchSource-grounded answersShared knowledge
04Documents & data

Entity resolution and catalog enrichment

Connect aliases and source identifiers to stable owners, operators, properties, wells, and other real-world entities.

DataLandRevenue

Trigger

A new source record cannot be confidently joined to the existing asset or party catalog.

Sense workflow

  1. 1Normalize names, addresses, identifiers, and location signals
  2. 2Generate candidate matches from canonical records and aliases
  3. 3Score agreement, conflicts, and effective-date context
  4. 4Accept a match, create a governed record, or queue review

Human control

Ambiguous and high-consequence matches require review before they affect canonical records or downstream workflows.

Fewer duplicatesStronger joinsBetter downstream AI
05Land & ownership

Lease and obligation review

Surface material terms, dates, obligations, and evidence across leases, amendments, and related instruments.

LandLegalAsset management

Trigger

A lease package is received, acquired, amended, or scheduled for periodic review.

Sense workflow

  1. 1Identify the governing documents and superseding instruments
  2. 2Extract terms, clauses, dates, parties, and legal descriptions
  3. 3Connect obligations to the relevant property and interest
  4. 4Create review work for conflicts, missing evidence, and upcoming actions

Human control

Land and legal specialists interpret consequential language and approve updates to authoritative terms.

Visible obligationsFaster reviewBetter evidence
06Land & ownership

Acreage dedication and contract coverage

Connect agreement language, amendments, dedication exhibits, land descriptions, wells, and maps to answer commercial coverage questions with evidence.

CommercialLandGISDevelopment

Trigger

A tie-in, forecast, acquisition, divestiture, amendment, or development decision requires confirmation of dedication coverage.

Sense workflow

  1. 1Identify governing agreements, amendments, exhibits, and effective periods
  2. 2Extract dedication scope, priority, products, exclusions, and location rows
  3. 3Resolve land descriptions to canonical acreage, wells, units, and geography
  4. 4Prepare overlaps, gaps, candidate coverage, and source evidence for review

Human control

Commercial, land, legal, and GIS owners approve the contractual interpretation and mapped coverage before it informs a consequential decision.

Faster contract researchVisible overlapsEvidence-backed coverage
07Land & ownership

Division order validation

Compare proposed parties and decimals with effective-dated ownership evidence before a division order is accepted.

Division orderLandRevenue

Trigger

A new or amended division order is received for review.

Sense workflow

  1. 1Extract the property, parties, interest types, and decimals
  2. 2Resolve the document to current ownership and source instruments
  3. 3Calculate and explain party- or decimal-level differences
  4. 4Prepare approval, correction, or follow-up work with evidence

Human control

A division-order specialist approves acceptance or communicates a discrepancy to the counterparty.

Explainable differencesConsistent reviewFewer downstream corrections
08Land & ownership

Ownership change intake

Move deeds, assignments, probate materials, and owner changes through a consistent evidence-backed process.

LandOwner relationsAsset management

Trigger

A document or request indicates that ownership, payment direction, or contact information may have changed.

Sense workflow

  1. 1Classify the request and identify affected owners and properties
  2. 2Extract conveyance, effective-date, and supporting details
  3. 3Check completeness and compare with current ownership records
  4. 4Route the change for approval and preserve the resulting history

Human control

Authorized specialists verify legal sufficiency and approve any change to the ownership system of record.

Consistent intakeComplete packagesAuditable history
09Land & ownership

Courthouse record monitoring

Monitor authorized record sources for relevant filings, connect them to the right parties and assets, and route possible changes for evidence-backed review.

LandOwner relationsLegalAsset management

Trigger

An authorized courthouse, public-record, or licensed data source publishes a new or corrected filing within the monitored scope.

Sense workflow

  1. 1Preserve the source observation, recording reference, image, and coverage context
  2. 2Classify the instrument and extract parties, dates, descriptions, and evidence
  3. 3Resolve candidate owners, entities, properties, and related records
  4. 4Create reviewed ownership, lease, curative, outreach, or diligence work

Human control

Qualified land and legal reviewers determine legal effect and approve downstream work or authoritative record changes; monitoring does not constitute a title opinion.

Earlier visibilityFocused review queuesConnected filing evidence
10Revenue & finance

Revenue statement reconciliation

Normalize statement detail, validate the remittance, and turn discrepancies into reviewable exceptions.

Revenue accountingAuditAsset management

Trigger

A royalty or revenue statement is imported from a spreadsheet, PDF, or supported data feed.

Sense workflow

  1. 1Parse every canonical line item without dropping statement detail
  2. 2Resolve payors, operators, properties, wells, products, and periods
  3. 3Roll up totals and run deterministic validation and audit rules
  4. 4Write explainable exceptions and route the statement for review

Human control

Revenue professionals resolve ambiguous mappings, validate material exceptions, and approve statement status.

Canonical detailFaster reconciliationPrioritized exceptions
11Revenue & finance

Exception-to-recovery workflow

Carry a supported revenue discrepancy from detection through review, recovery work, and resolution.

Revenue assuranceAsset managementOwner relations

Trigger

An audit identifies an open exception with evidence and potential financial consequence.

Sense workflow

  1. 1Assemble the exception, statement, calculation, and source evidence
  2. 2Prioritize work by status, confidence, and potential consequence
  3. 3Create a linked recovery case and assign the next action
  4. 4Track correspondence, approvals, resolution, and realized outcome

Human control

A reviewer decides whether the evidence supports outreach or recovery and approves consequential actions.

Focused queuesConnected evidenceClosed-loop recovery
12Revenue & finance

Production volume audit

Compare source-verbatim production observations with statement and asset context to surface review candidates.

Revenue assuranceEngineeringOperations

Trigger

Production observations are imported for an asset and production month.

Sense workflow

  1. 1Preserve vendor observations at their original reporting grain
  2. 2Resolve the asset, product, units, and reporting period
  3. 3Compare compatible observations and record unresolved context
  4. 4Route supported variances for specialist review

Human control

Specialists resolve unit, quality, timing, and source differences before treating a variance as recoverable.

Comparable evidenceEarlier reviewFewer unsupported assumptions
13Revenue & finance

JIB and AFE variance review

Organize billing detail against approved expenditure context and send material variances to the right owner.

JIB accountingOperationsFinance

Trigger

A joint-interest bill, invoice package, or expenditure export enters review.

Sense workflow

  1. 1Extract vendors, wells, cost categories, periods, and amounts
  2. 2Match charges to the relevant asset and authorization context
  3. 3Run duplicate, allocation, coding, and variance checks
  4. 4Prepare exceptions and supporting detail for approval or dispute

Human control

Accounting and operating owners validate contract and authorization context before approving or disputing charges.

Faster reviewVisible variancesConsistent evidence
14Asset operations

Asset issue evidence package

Assemble the records behind an operating issue so a specialist can investigate with context already in hand.

OperationsEngineeringAsset management

Trigger

A user, monitor, or scheduled review identifies an asset question or anomaly.

Sense workflow

  1. 1Resolve the issue to the correct asset, interval, and time period
  2. 2Gather permitted production, document, work, and relationship context
  3. 3Summarize relevant changes, gaps, and candidate contributing factors
  4. 4Create an assigned review package with links to source evidence

Human control

Engineers and operators diagnose root cause and approve any field, financial, or system action.

Faster investigationShared contextTraceable decisions
15Asset operations

Scheduled review and exception queues

Turn recurring checks, reminders, and agent reviews into owned work instead of calendar-driven follow-up.

OperationsComplianceTeam leads

Trigger

A schedule, due date, board rule, file event, or unresolved exception reaches its defined condition.

Sense workflow

  1. 1Identify eligible records using tenant and workflow policy
  2. 2Gather the minimum evidence needed for the scheduled task
  3. 3Run the bounded check or queue independent review work
  4. 4Record outcome, next date, ownership, and any escalation

Human control

Board owners define the rules, permissions, cadence, and approval boundary for every automation.

Less follow-up driftOwned queuesVisible automation health
16Transactions

Acquisition diligence workspace

Connect a target portfolio’s documents, interests, production, revenue, obligations, and open diligence questions.

AcquisitionsLandFinance

Trigger

A target asset package or data room enters evaluation.

Sense workflow

  1. 1Inventory files, records, assets, parties, and missing materials
  2. 2Extract and connect ownership, obligations, performance, and economics
  3. 3Surface conflicts, gaps, and diligence questions by asset
  4. 4Track review, valuation inputs, decisions, and closing evidence

Human control

Deal, land, legal, and finance owners approve assumptions, valuation inputs, and transaction decisions.

Connected diligenceVisible gapsFaster handoffs
17Transactions

Acquisition pipeline coordination

Move opportunities from discovery through verification, valuation, negotiation, escalation, and close in one governed workflow.

Business developmentAcquisitionsLeadership

Trigger

A candidate asset or owner enters the acquisition pipeline.

Sense workflow

  1. 1Create the candidate and connect available asset and owner context
  2. 2Verify evidence and prepare a deterministic valuation range
  3. 3Advance outreach and negotiation with recorded approvals
  4. 4Preserve accepted terms, closing documents, and ownership transfer history

Human control

Authorized deal owners approve outreach, pricing, negotiation boundaries, and closing decisions.

Consistent pipelineControlled pricingAuditable close
Start narrower

The best first workflow is measurable and bounded.

Choose one trigger, one eligible population, one accountable owner, and one outcome the team can observe. Prove the operating loop before expanding the boundary.

A strong starting brief

  • 01The work and its current owner
  • 02The trigger and eligible population
  • 03The authoritative evidence and systems
  • 04The exception and approval rules
  • 05The baseline and success measure
Model the potential impact
Your workflow will be specific

Bring us the version that exists in the real world.

Map a workflow