basindeckbasindeck.com

Corporate planning for Canadian oil and gas

Run the company on accepted assumptions.

basindeck keeps your reserves database live and puts the whole team on one page: the forecast everyone reads is the one the company accepted, updating it takes minutes, a scenario is a question you ask and not a week you spend, and the board gets a book that ties to the record.

A complete economics package underneath. Asset-level analysis beside it. The calculation engine reconciles to published evaluator reports.

0 2,000 4,000 6,000 8,000 boe/d, company interest approved budget 2027 programme PDP base, published v3 FY27 Q1 Q2 Q3 Q4 FY28 Q1 Q2 Q3 Q4 senior debt / EBITDA 1.4× · headroom to 3.0× · no breach
accepted PDP basethe programme, re-timed to the capital capapproved budget
The forecast the board approved, the base it stands on, and the programme on top, by fiscal quarter. Illustrative figures.

One record, the whole team

Everyone works from the forecast the company accepted.

A reserves database is only useful if it is the one people actually use. basindeck holds one working version the evaluators edit and one published version everyone else reads, so the engineer's well page, the planner's budget and the board's book agree because they are the same record.

1 · Accept

Publish the version

Working and published versions, sign-offs that lock the inputs, a change history and a snapshot to revert to. The published version is what the organization reads.

2 · Update

Change it in minutes

Re-import the evaluator's file, bulk-edit costs across an area, pull this month's published price deck, load last month's production. What changed since the published version is marked on every page.

3 · Ask

Run the scenario

Price, costs, delay, a programme added or dropped, a capital cap, hedge coverage. Each is a cached run against the approved version, with what binds named.

4 · Decide

Take the board a book

The board page, the budget's board book, the filing tables and a cash-flow statement for any well, area or case, every one stamped with the version it came from.

The platform

Corporate decisions on top. A complete economics package underneath. Asset analysis beside it.

Three layers, one engine. The corporate layer never re-computes an economics number; it reads the same runs the evaluators sign off.

Corporate decisions

Budget · forecast · strategy · board

  • Budgets and multi-year forecasts on a published version: G&A, hedges settled at the deck, the revolver and term debt with a monthly cash sweep, distributions as a policy, covenants by quarter with headroom.
  • Approved versions and re-forecasts, with the variance between any two.
  • The idea generator: levers as variants, and "what breaks first, and at what price".
  • Strategy generators that schedule the inventory to an objective within funding and covenants, and become a budget in one step.
  • After-tax on Canadian pools; internal against external capital.

The economics package

Run your evaluations here

  • Declines as an evaluator keeps them: multi-segment curves, ratio-derived streams, economic limits, EUR caps, on-time.
  • Royalties from the published frameworks: Alberta's MRF and the pre-2017 ARF, freehold with the mineral tax, overriding royalties and deductions, Saskatchewan, Manitoba, British Columbia.
  • Common-termination areas, where the facility's cost and turnarounds decide when every member stops.
  • The reserves hierarchy, the filing tables, net volumes in kind, reconciliation to the prior evaluation, the look-back against recorded production.
  • A printable report and a printable cash-flow statement.

Asset-level analysis

Well · area · play

  • The well page: history, the accepted curve and our own fit side by side, ratios, every royalty term inspectable and editable.
  • Statistical type curves over a peer group, and a check of any booked curve against its peers.
  • The Discovery canvas: the book as one picture, value by area, liabilities by year, reality against the booking, with a year scrub.
  • The map on real positions with a basemap; areas, locations and programmes; a cash-flow statement with a drill from total to part to month.

Scenarios

A scenario is a question, not a project.

Every lever runs the whole book against the approved version and comes back as a column: value, free cash, net debt, the tightest covenant and its headroom, the KPIs met, and what binds. Results are cached, so the second look is instant.

"What breaks first" searches the price axis for the point where a covenant trips or the facility is drawn past its limit, and names which.

Price

WTI and AECO by percent or flat, on the deck's own curves.

Costs

Operating cost moves across the book, escalation kept.

Timing

Delay a programme; the capital and the on-stream month move together.

Programmes

Add, drop or move one. A capital cap re-times them in on-stream order.

Hedges

Scale the book, or change instruments: WTI in US$ or C$, Edmonton or WCS differentials, AECO.

Compare

Any two versions, a working copy against the published one, a case against another.

Dashboards and board reports

The board reads what the engineers signed.

Nothing on a dashboard is recomputed for the dashboard. Every tile reads a run that already exists, and every document says which version it came from.

The board page

Value and reserves against the prior evaluation as waterfalls, funding and tax, the areas behind or ahead of their booking, the abandonment liability by year, a price grid of whole-book runs.

The board book

One printable document from a budget: the cover with its basis, the variance to the approved version, cash flow by quarter and by fiscal year, the hedge book, a page per covenant, the KPIs against targets.

Saved reports

Cash-flow statements for a well, an area or a case, saved as definitions that re-run on any version; the reserves report in the filing's own tables; every one stamped and exportable.

Your data

Manage the reserves database you already have.

The evaluation you paid for is the starting point, not something to re-key. Bring it in, keep it current, and let the public data fill in what the file does not carry.

Your evaluator's file

A ValNav project imports directly: curves, ratios, ownership and lease chains, dated costs, capital, abandonment, the areas with their cost centres, the price deck, the type wells with their peers. Re-import refreshes the same project and records what changed.

Public production, every month

Petrinex volumetrics and well headers for Alberta and Saskatchewan from 2022, pulled from the app. The look-back tests the booking against what the wells actually did.

Published price forecasts

Pull the current published forecast into a deck in one click, or enter a deck at any granularity. The organization can pin the deck budget season runs on.

Sign in with Microsoft 365. The organization is the tenant; projects are shared by default, experiments are private until shared, roles decide who edits.

Limits

What is approximate says so, on the page.

Every calibration and placeholder carries a flag where it appears. A number nobody can inspect is indistinguishable from a number that is wrong.

  • calibratedFreehold mineral tax unit-value factors, calibrated to one report.
  • placeholderA flat gas cost allowance where the evaluation carries none.
  • proxyNGL component par prices from the deck; Saskatchewan price inputs from the realised price.
  • approximateThe working-capital covenant, with no balance sheet behind it.
  • not modelledBC's producer cost-of-service allowance and 2027 framework.
  • not a bookingAnything valued on our own fit inside an evaluation.