QED Commitment Ledger — a tracker for Quadrise Fuels' dated promises
What this is:
A simple, free web tool for tracking the specific, dated commitments that AIM listed Quadrise Fuels has made across its RNS releases — things like "OEM approval expected Q3," "trial to commence Q2 2025," "bilateral agreements in near final form," licence fee payment dates, and so on — pulled from Morocco (OCP), the MSC/Cargill marine trial, Panama (Sparkle Power) and Utah (Valkor).
Why we built it:
After going through several years of Quadrise RNS releases with other forum mods, a pattern kept showing up (as Long Term Retail shareholders are all too aware!) — a milestone described as imminent, followed months later by a new reason for delay, followed by a fresh "close now" statement. It's hard to hold a company to account for that pattern from memory alone, because each new RNS is read in isolation and sounds reasonable on its own. This tool exists to make the comparison explicit: log the promise and its date, then check it against what actually happens.
How it works:
Each row is a milestone with a target date, a status (Pending / Met / Overdue), and a note with the relevant wording from the RNS. You can update the status as news comes in, add your own entries for anything I've missed, and remove anything you disagree with. It's editable by design — this isn't meant to be a fixed "verdict," just a working record.
What it isn't:
This is not an allegation of wrongdoing, and it's not evidence of deliberate deception. Delays at companies like this are often genuinely driven by large counterparties (OCP, MSC, Cargill) moving slower than the small-cap needs them to, for reasons that have nothing to do with management's honesty. What the tool does capture, neutrally, is management's own track record on timing — useful context for judging how much weight to put on the next "imminent" announcement, whatever the underlying cause turns out to be.
One technical caveat:
it saves data locally in your browser (not to any server), so it won't sync across devices, and if you clear your browser storage the log resets to its defaults. Feel free to fork it and improve it.