Products, volumes, prices, taxes, deductions, paid decimals, downtime, and adjustments should reconcile to revenue actually received. Start with the owner statement rather than a basin-wide multiple. Match each payor line to the well, unit, product, sales month, decimal, and net amount, then compare that record with Bakken region production data and the controlling division order. Separate ordinary decline from shut-in time, workovers, corrected statements, and suspense releases. A useful income schedule explains why a check changed and identifies which missing record would confirm the explanation.
Price, deductions, decline, downtime, development timing, title reserves, concentration, marketability, and discounting should be tested separately before scenarios are combined. Changing every input at once can make an attractive forecast impossible to audit. Hold the paid decimal and well list constant while testing commodity price, then hold price constant while testing decline or downtime. Keep existing producing wells apart from permits, offsets, and undeveloped inventory. The resulting range should show which assumption drives the outcome, which evidence supports it, and how quickly the conclusion changes when Bakken activity or owner records change.
A sound income review distinguishes recent observed checks, medium-term decline, and longer-term development assumptions. Shut-in periods, workovers, recompletions, and terminal value remain visible. The first period should tie directly to statements and reported production. Later periods should identify the decline convention, price deck, deduction treatment, and date each assumption was observed. Possible future wells belong in a separate development schedule with operator, spacing, permit, offset, and timing evidence. That separation prevents uncommitted inventory from being presented as current income and gives the owner a clear path for updating the analysis after a new statement or regulatory filing arrives.
The downside schedule can test lower prices, faster decline, longer downtime, higher deductions, delayed development, title-curative cost, and reduced marketability. It should not be a vague percentage haircut. Record the changed assumption, the reason for the change, and the line of the Bakken signal file it affects. For a concentrated Bakken region package, also test an operator delay, a single high-volume well going offline, and a title reserve that postpones payment. Comparing that case with the observed case helps an owner understand whether an offer reflects ordinary uncertainty or depends on an unusually pessimistic view of the property.
An investment file is easier to refresh when it retains deeds, leases, division orders, statements, production records, operator notices, tax records, well lists, assumptions, and observation dates. Give every figure a source and every scenario an as-of date. Keep the legal-description schedule beside the well schedule so a later analyst can see which tracts and depths were included. Preserve unresolved questions instead of burying them inside a single value. When a new royalty statement, permit, order, or title document arrives, the owner should be able to replace one input and see the effect without rebuilding the entire property file from memory.
Keep Reading
Bakken owner desk
Share the county, owner name, interest type, producing status, recent statements if available, and the decision that needs a clearer answer.