Changelog
New features and changes to the hosted service, newest first. Each entry names the release that brought it to the service; an entry marked unreleased is built and reaches the service with the next release.
Release notes
Each entry names who it is for: the people who use the app, their administrators, or this website.
About these notes
UsersAdministratorsUnreleased
A member whose access is limited to some assets can now open, download and attach the files on interventions, workovers and wall-thickness log runs for the wells in those assets. Until now those files were hidden from such members, even on their own wells. Members still cannot see any file on a well outside their assets.
UsersReleased in 2026.10.8
Client admins and integrity engineers now see, on Settings → General, when the alarm engine last ran (for example “last ran at 08:57 (3 min ago)”), and the card says plainly when it is overdue. The alarm engine is the regular scan that raises and clears alarms, sends reminders and escalates; it now runs on its own reserved workers, so large reports or digests can no longer hold it up, and FEEC’s outside monitor checks the same record.
Expensive requests (reports, “send now”, exports, barrier sheet previews and issues, searches and uploads) now have generous per-person limits per minute, and an organisation can have up to 10 reports waiting at once. A request past a limit is refused with a message to try again shortly; nothing is left half-done. A person working normally does not reach these limits.
UsersAdministratorsReleased in 2026.10.9
Governance has a new Anomalies register: one record per deviation your team finds in a reading, a test, a wall-thickness log, an incident or on site. Raise an anomaly from the annuli list, a recorded test, a wall-thickness log run or an incident, or by hand on a well; link it to its dispensations and actions, move it to “under dispensation” or close it with a note, and every change is kept in its own history. A well’s open anomalies are shown under its status, labelled as an annotation that is not part of the assessed status: an anomaly never changes a well’s status. Severity uses your organisation’s own labels (Settings, Anomalies and criteria); until you set them every anomaly is unranked. The same settings page holds your acceptance-criteria library per barrier element kind, with an optional measured criterion and its source: barrier schematic sheets issued after a change print it for elements without criteria of their own, and recording a test can take its acceptance reference from it. The monthly review pack lists the anomalies open on the review date and the dispensations about to expire.
UsersReleased in 2026.10.8
Every recorded assessment run now keeps the date it was assessed as of, the well’s status and the inputs behind it: the barrier elements with their envelope, the limits with their source dates, the open tests and any uncontrolled-flow incident. Why this outcome on the well page now opens with the well level: the status the run recorded and what set it, most severe first, naming the failed element, the test past its grace or the incident behind each contribution. Runs recorded before this change say that their well level was not recorded.
A run is now recorded for every assessable well once a day, late in your own calendar day, so the history exists without anyone pressing a button.
When a review month is locked, its monthly review pack for that asset is produced once and kept with its SHA-256. Generating that month’s pack again returns the same file, byte for byte, even after a barrier element is retired or a limit is restated. A lock that cannot store its pack is refused and the month stays approved. Months locked before this change are produced from the register as before.
UsersAdministratorsReleased in 2026.10.9.3
The sidebar now follows a working day: Daily work (the status overview, alarms, wells, readings, reading imports, field rounds and actions), Integrity records (integrity tests, SCP tests, dispensations, incidents, handovers and the monthly review), Reports and dashboards, and Administration, which starts collapsed. “Import & reconciliation” is now Reading imports and “Register import” is Well register import. Page addresses have not changed, so bookmarks still work.
The status overview opens with My work: your open actions, the overdue tests in your scope, the alarms nobody has acknowledged yet and the readings due on today’s planned rounds. A data provider who opens the app on a phone lands on Field rounds.
A new Alarms page lists every alarm, open or closed, filtered by status, well and severity, and acknowledges several at once with one reason, recorded on each. The alarm card on the overview and the well page now says when the alarms cannot be loaded instead of disappearing. Quick search (Ctrl+K) also finds integrity tests, SCP tests, handovers, reports, Teams & Slack channels and alarms, and opens a dispensation or an annulus directly.
Every action that removes, revokes or ends something now asks in the same confirmation dialog, and every date reads the same way, with recorded times shown in your organisation’s time zone and that zone named.
UsersReleased in 2026.10.9
One annulus reading can now be recorded from the desktop: “Record a reading” on a well’s annulus card, in its new readings history or on the annulus readings list takes the value in the annulus’s stored unit (the display unit is shown beside it), any date up to your organisation’s date, and a note, with the same checks as the import template. The well page’s readings history lists the readings in force, and an integrity engineer or client admin can correct or delete a reading with a required reason: the original is kept in an append-only record, the change is in the audit history, and the next assessment uses the corrected readings and names the correction. “New well”, “New asset” and “Add annulus” create register records without the import, with the import’s rules; a well past the plan’s well count is refused with a link to Plan & usage. The Assessability page’s steps now link to the screen that clears them: the readings history for units that disagree or two readings on one date, the annulus card for a MAWOP/MAP value, and Method profiles or the integrity policy. The set-up guide links to “New well” and the register import.
UsersReleased in 2026.10.8
The pressure and depth display units in Settings now apply across the app, not only in the settings preview. The annulus lists, the well page, field rounds, the dashboards and pressure trends, the SCP tests and the “Why this outcome” panel show pressures in barg, psig or kPa and depths in metres or feet, as your organisation chose. This is display only: every value is still stored exactly as entered, hovering over a converted value shows the stored value and unit, and data tables and exports list values as stored. On field rounds you still type the gauge reading in the annulus’s own unit, and the screen says how it will read elsewhere.
Forms now protect unsaved work. Leaving the wellbore editor, an incident, action, bleed-off, WIT record, SCP declaration or method-profile form with unsaved changes asks first, and closing the tab raises the browser’s warning. When a new version is released while you are typing, the app shows “A new version is available. Reload when you are ready.” instead of reloading. The installed field-rounds app can now rotate on a tablet, offers an install hint on the rounds page, and asks before switching to a new version.
UsersReleased in 2026.10.8
The app now matches the FEEC family of websites: a white page, larger rounded corners on cards and form fields, and links in the amber accent, always underlined so a link never looks like the amber data-gap flag. Blue now appears only in charts and measurements, where it carries meaning. Alert and scheduled-report e-mails use the same typeface, the navy header and an amber button to open the app. Nothing about your data, results or reports changes.
UsersAdministratorsReleased in 2026.10.8.2
The in-app help has new articles on field rounds, well integrity management, alarms and notifications, API keys and webhooks, and troubleshooting, and the existing articles carry what the User Manual used to explain on its own. Members who manage the organisation’s settings also see an Administrator tasks article: what only an administrator controls, where it is, and which controls need a second person. Other members do not see administrator articles in the help or in search.
The User Manual is now generated from these same articles, so the manual and the help say the same thing, and every bold label in the help is checked against the labels the screens show.
UsersAdministratorsReleased in 2026.10.9
Dashboards has a new KPIs tab, and the same pack is a PDF report, monthly or quarterly, in every plan. It counts wells by the status the engine recorded in each well’s assessment run of record, over the last 12 months or quarters, with the wells whose run records a failed or degraded barrier element or sustained annulus pressure. It also counts overdue integrity tests by your own grace and escalation days, open and expiring dispensations, data-quality gaps and open actions by age. A well with no run of record is counted as such, never given a status. The pack shows no benchmark and no target.
Pressure trends can now overlay every annulus of one well on one chart, or compare the same annulus across several wells (up to eight by default), each drawn against its own governing limit. The data table lists every value as stored.
Lists now offer bulk actions on the selected rows: assign or close several actions with one owner or one closure note, mark several annuli monitored or not monitored with a reason, and schedule one integrity test for a set of wells. Each item is changed and recorded on its own, and anything refused is listed with the reason and left as it was.
UsersReleased in 2026.10.9
Integrity test schedules can now be created and edited on the Integrity tests page: the well, what the test applies to (an annulus, a barrier element or the whole well), the test type, the next due date and the interval your own procedure states (your integrity policy records no test interval, so none is proposed). Select a row to open its schedule, with the tests recorded from it, or withdraw it with a reason. “Record this test” on a row opens the record form filled in from the schedule, dated today in your organisation’s day; earlier dates are allowed. A test record now holds its measured value and unit, your acceptance criterion (value, unit, maximum or minimum, and its source; “no criterion recorded” when you enter none), the test pressure, the hold time and the witness’s role title, and evidence files can be chosen before you save. The result stays the one you choose: when your values and your criterion say otherwise, the page shows a notice and changes nothing. After a failed test the page offers to record a barrier-element state change with the test as its evidence; nothing changes unless you record it. The schedule list now pages through every schedule on the server, and “Export all overdue tests” writes every overdue test to CSV.
UsersReleased in 2026.10.9
Locking an approved month now runs in the background. The month shows Locking… on the review board and in its panel while the readiness check runs again and the month’s review pack is frozen, then Locked when it is done. On a large asset this used to take longer than a web request may last; now you can close the panel and carry on. If the lock cannot complete, the panel says why and the month stays Approved, so you can fix the reason and ask again.
WebsiteReleased in 2026.10.9
The methodology page now links to a plain-language summary of the method for offshore platform producer wells: the barrier model, what an assessment reads, the outcomes and statuses and what moves a well between them, SCP handling, wells that cannot be assessed, and provenance. It states the rules only; the thresholds are set in each tenant’s policy. The summary can also be requested as a PDF through the enquiry form. The product page gains a “Try a sandbox” request.
UsersReleased in 2026.10.8
Each screen now names its browser tab (“Wells · BarrierLedger”, “Wellbore editor · A-05 · BarrierLedger”), so tabs and history can be told apart. When you open another screen, the keyboard focus moves to its heading, so a screen reader starts reading the new page. The phone menu, quick search (Ctrl+K) and the tubular library picker now behave like every other dialog: the page behind waits, Tab stays inside, Escape closes, and the focus goes back where you were. The notification list no longer claims to block the page. Form fields keep their guidance visible while they show an error, and both are read out with the field. Wide tables and code samples that scroll sideways can be scrolled with the keyboard. If your system asks for reduced motion, the app stops animating. A guest auditor’s access now ends at midnight on the chosen day in your organisation’s time zone, rather than at midnight UTC. Pages also load faster on first visit, because the well and editor screens are fetched only when opened. Nothing about your data, results or reports changes.
UsersReleased in 2026.10.8
Integrity reports, the Well Barrier Schematic sheet, quotes and invoices now print in IBM Plex, the typeface the app uses. Summary tiles, status chips, placeholders and the exceedance pattern in report legends are filled with a faint grey tint again, so they stand out from the white page as they did before. The read-only guest-access banner is now a neutral grey notice, keeping blue for data. The figures and results in your documents do not change.
UsersAdministratorsWebsiteReleased in 2026.10.8
Professional extension blocks. Professional now includes 250 wells and extends in 25-well blocks up to 500 wells, so an estate between 251 and 500 wells stays on Professional instead of moving to Enterprise. The block price is on the pricing page.
What counts as a well. Every well whose lifecycle state is not plugged and abandoned counts toward your plan. Plugged-and-abandoned wells stay in your register for their history, free of charge: Settings → Plan & usage now counts and says so, marks them not counted, and recording or creating a well as plugged and abandoned never meets your well limit.
Price estimates. The billing page is now Price estimates. It drafts an estimate from the price book for a plan, a well count and a hosting choice, and each estimate says it is not an invoice. It no longer offers invoices, discounts or the self-hosted option: FEEC sends invoices from its accounting tool, and any deal terms are set out in your order form.
Also on the pricing page. The monthly integrity review with period locking, overrides with second-person approval and the actions register are listed as included in every plan; dedicated hosting carries the same 99.5 % availability target as the shared cloud until a warm standby exists; and the Enterprise row states the API-key rate limit.
UsersAdministratorsReleased in 2026.10.9
FEEC can now set up a sandbox organisation for 14 days so you can try BarrierLedger before a pilot: a copy of the fictional Demo Petroleum data, with the register-import template to try your own column mapping on its dummy rows. A banner on every page of a sandbox says that its data is fictional and when it ends. When the sandbox ends, the organisation closes and its pages say why. Ordinary organisations are not affected. Ask for a sandbox through the enquiry form on the website.
UsersReleased in 2026.10.8
The app’s sign-in screen now shows the BarrierLedger logo in a centred card with a single Sign in button, as the other FEEC products do. A Trouble signing in? link explains how to reset a forgotten password and who to contact if you lose the phone you use for one-time codes. How you sign in does not change.
UsersReleased in 2026.10.8
The register lists now share one table: wells, annulus readings, actions, incidents, the integrity-test schedule, dispensations, SCP diagnostic tests, handovers, reading feeds and commercial documents. Select any column heading to sort by it, use “Filter rows” to filter by column, and move between rows with the arrow keys and Enter. The sort, filters and page are kept in the page address, so a filtered list can be bookmarked or shared and survives a reload. “Export visible rows (CSV)” saves the rows on screen with each value’s unit, the organisation (or the fictional demo label), the app revision and the export time in your organisation’s time zone. The actions register gains row selection, and the export then writes the selected rows. The actions register, which stopped at 100 rows, now pages through every action; the integrity-test schedule pages through up to 200 rows; dispensations are listed as a table that opens each record in a side panel.
UsersReleased in 2026.10.8.2
Symbols such as ≥ and →, and names with accented or Central European letters such as Ł, now print in IBM Plex like the rest of your integrity reports, the Well Barrier Schematic sheet, quotes and invoices, instead of in a different fallback typeface. Text in italics is set in Plex’s own italic, and the labels on report charts print in IBM Plex too. The figures and results in your documents do not change.
AdministratorsReleased in 2026.10.8.2
The API description that integrators generate clients from now names the shape of every answer on the integration surface: the API-key routes for wells, well status, annuli, reading batches and feed pushes, the API key and webhook administration, and the reading feeds. It does the same for the most used reads, including the well register, the actions register, the incident log, the test schedule, the dashboards and the quick search. No field was renamed or removed. A request that sends a field the route does not know is now refused with a validation error naming that field, where before the field was silently ignored. From now on a field or route is removed only after this changelog has announced it one release before.
UsersAdministratorsReleased in 2026.10.8
The footer of the app now names the release you are using, for example “Version 2026.10.8” followed by a short build reference, so you can say exactly which release you are on when you ask for support. Each production release is named by the date it was released, and this changelog marks every entry with the release that brought it to the service; an entry marked unreleased is built and arrives with the next release.
WebsiteAdministratorsReleased in 2026.10.8
When your well count crosses your plan’s limit and you move up to the next plan, the monthly subscription price steps up. A one-off transition credit now halves that step-up for your first 12 months on the new plan. It applies once per customer and to the subscription only, not to hosting, set-up, services or the pilot, and it is set out in your order form. The pricing page’s FAQ shows the credit at each plan boundary.
UsersReleased in 2026.10.8
When the service’s job queue could not be reached, requesting a report, sending a scheduled report now or starting an AI-assisted extraction could wait a long time before failing, and slowed other requests meanwhile. Each request now waits a few seconds at most: if the queue does not accept the job, you are told the queue is unavailable, nothing is left half-queued, and you can try again. Nothing changes while the queue is working.
UsersReleased in 2026.10.8
At the larger type introduced earlier today, the element table of an A4 barrier schematic sheet did not fit the page width: the Dispensation column was cut off at the right, “not recorded” broke across lines, and a typical seven-element well moved two rows to the continuation sheet. A4 sheets now print body text at 7.4 pt (A3 stays at 8.2 pt), nothing on either paper prints under 7 pt, the table’s columns are re-balanced and its headings are no longer in capitals on A4, so a typical sheet keeps every element on sheet 1 again. A3 remains the default paper.
UsersAdministratorsReleased in 2026.10.8
A new Assessability page, under Overview, lists every well you can see that has no status from the assessment engine, with the reason the engine recorded and the step that clears it — for example adopting the method profile that covers that well type, or recording a missing limit. Administrators are pointed to the page where they can take the step; other members are told whom to ask. The same cause and next step appear on the well page, and the overview’s Unassessable figure links to the list.
UsersAdministratorsReleased in 2026.10.8
When the Assessability page finds wells that are being refreshed, it asks for the refresh in the background. If the background job queue could not be reached, that request could hold the page, and other pages served at the same moment, for twenty seconds or more. The request is now sent separately, so the page opens straight away either way. If the queue is unavailable, the wells stay marked as being refreshed until the next scheduled refresh stores them.
UsersAdministratorsReleased in 2026.10.8
The Assessability page now shows each well’s stored assessment and no longer assesses wells while you wait. After a new day begins in your organisation’s time zone, an import or an update, a large register could make the page wait minutes for that. Wells whose stored assessment is being brought up to date are shown as being refreshed, are left out of the figures and the list until they are stored, and the refresh starts as soon as the page finds them. The well page still shows its own well’s current cause straight away.
UsersReleased in 2026.10.8
A long well code, name, test reference or other value without spaces now wraps inside its column in the well status report, the monthly review, the integrity summary, the test evidence pack and the barrier schematic sheet, instead of running off the edge of the printed page. If a very long well or asset name will not fit in the title block of a barrier schematic sheet with its drawing, sheet 1 shows the start of the name ending in “…” and says so, and the continuation sheet prints the name in full. Before this change, a sheet like that could not be produced at all.
UsersReleased in 2026.10.8
The wellbore drawing and the well path inset on a barrier schematic sheet, and the wellbore schematic in a well status report, now carry a text description inside the PDF, taken from the report’s own caption or heading, so software that reads a document aloud can say what each drawing is. The colour keys above the pressure trend charts are now drawn as page decoration, so that software skips them and reads only their labels.
Tables that list a label beside each value (well identity, assessment and engine provenance, the test evidence records) now tell that software which label belongs to each value, the barrier schematic sheet’s title is marked as its main heading, and every PDF also carries its title in its embedded document metadata.
These changes come from an automated check of the PDFs. They have not yet been tried with a screen reader.
UsersReleased in 2026.10.8
Every PDF the platform produces (the well status report, the monthly review, the integrity summary, the test evidence pack, the barrier schematic sheet, quotes and invoices) is a tagged PDF: it carries a structure tree with its headings, paragraphs and tables, and declares its language as English, so software that reads a document by its structure can move through it by heading and read a table by row and column. An automated test checks this on every report before each release.
The barrier schematic sheet on A4 now uses the same type sizes as on A3: body text is 8.2 pt (it was 6.8 pt) and nothing on the sheet prints smaller than 7 pt. To make room, the wellbore drawing on an A4 sheet is a little smaller, and the notes print in two balanced columns. When a well has more elements or notes than sheet 1 holds, the rest continue on the continuation sheet as before. A3 remains the default paper and holds more on sheet 1.
UsersReleased in 2026.10.8
The assessment card on each well page now has a “Why this outcome” panel. For every annulus it explains the well’s latest recorded assessment run: the rule that decided the outcome, the thresholds in force when the run was recorded, the governing limit with its source, the readings used, the flags raised, and any SCP declaration or approved override. Every value comes from what that run stored, so a later policy change or a newer run never changes how an earlier run reads. Where an older run did not store a value, the panel says “not recorded for this run” rather than filling one in. If a well has no recorded run yet, an integrity engineer or client admin can record one from the panel.
UsersReleased in 2026.10.8
Photos attached to readings during field rounds now pass through the same malware scan as every other uploaded file before they are stored. A photo the scanner refuses is not stored.
UsersAdministratorsReleased in 2026.10.8
The Time zone setting under Settings → General now sets your organisation’s calendar day, not only how dates and times are displayed. Assessments, the date limits on dated entries and scheduled reports count “today” in that zone, so a reading dated on your local day is assessed as soon as it is recorded. While the setting is unset, the day is counted in UTC, as before. Alarm and notification times now show their time zone.
AdministratorsReleased in 2026.10.8
Restoring a backup is now a scripted drill: it takes a fresh backup, restores it into an isolated database with no network access and compares every table with the live database. Every production deployment now starts with a fresh backup, and the deployment stops if that backup fails.
AdministratorsReleased in 2026.10.8
Where your organisation’s plan is recorded, its limits now apply. An invitation, or a role change that would make a free account a named user, is refused once every named-user seat is in use or invited; read-only, audit and external-verifier accounts never take a seat. Creating wells, by hand or through a register import, stops at the plan’s well limit, and a feature the plan does not include, such as creating API keys and webhooks without API access, is refused with a message that says why. API keys and webhooks that already exist keep working until an administrator revokes them.
UsersReleased in 2026.10.8
An integrity engineer or client admin can declare sustained casing pressure (SCP) on an annulus, with the reason and an optional evidence reference recorded. The declaration stays in force until it is withdrawn, with its own reason, by a second person: another integrity engineer or client admin, never the person who declared it. Withdrawing a declaration removes the declared trigger only; sustained casing pressure that the readings show is still raised.
UsersAdministratorsReleased in 2026.10.8
Evidence attachments and import files are scanned for malware before they are stored, and a file the scanner refuses is never stored. The message says what happened: an encrypted or password-protected file is refused as such, a file too large or too complex to scan is refused as not scannable, and only a detected threat is reported as malware.
UsersAdministratorsReleased in 2026.10.8
A client admin can post chosen alarms and events to a Microsoft Teams channel (through the Teams Workflows app) or a Slack channel (through an incoming webhook), routed by event kind, asset and minimum severity, with a test message and a delivery log for each channel. Scheduled reports e-mail an integrity summary, the monthly review pack or the annual summary to members of your organisation every week or month, and each recipient’s report covers only the assets that member can see.