Corporate planning for Canadian oil and gas
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.
One record, the whole team
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 versionWorking 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 minutesRe-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 scenarioPrice, 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 bookThe 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
Three layers, one engine. The corporate layer never re-computes an economics number; it reads the same runs the evaluators sign off.
Budget · forecast · strategy · board
Run your evaluations here
Well · area · play
Scenarios
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.
WTI and AECO by percent or flat, on the deck's own curves.
Operating cost moves across the book, escalation kept.
Delay a programme; the capital and the on-stream month move together.
Add, drop or move one. A capital cap re-times them in on-stream order.
Scale the book, or change instruments: WTI in US$ or C$, Edmonton or WCS differentials, AECO.
Any two versions, a working copy against the published one, a case against another.
Dashboards and board reports
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.
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.
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.
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
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.
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.
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.
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
Every calibration and placeholder carries a flag where it appears. A number nobody can inspect is indistinguishable from a number that is wrong.