This is our first-ever update on everything happening in the Deliver Portal, and it feels like the right moment to say thank you. Over the past year, every one of our clients has come on board and made the portal part of how they work with us, and the adoption and feedback along the way has been fantastic to see.
We're continually investing in the platform to keep improving how we deliver for you. Here's a full round-up of what's changed, release by release, from the newest back to the start of the year.
Release 2.4.0 — 5 August 2026
Sign proposals right where you read them
It's 2026 — we're doing away with PDFs flying back and forth. Approving a proposal is now a real, legally binding signature, completed right in the portal, in one sitting.
It's also built so you always know exactly what you're agreeing to, and that the right person is the one agreeing to it:
- Nothing to read elsewhere. The complete Master Services Agreement is shown in full at the moment of signing, not linked off somewhere you'd have to go find. What you're agreeing to is right in front of you.
- A proper electronic signature, not just a status change. Approving in the portal constitutes an electronic signature under the Electronic Transactions Act 1999 (Cth), so it carries the same legal weight as a signed PDF, with none of the back-and-forth.
- Approver and customer entity on the record. The name of the person approving and the legal entity they're acting for are shown before they confirm.
- A clear agreement step. Approval proceeds once the approver confirms they've read and agree to the proposal and the MSA.
- Only authorised people can accept. Approval and rejection are restricted to users holding the Proposal Approver permission, enforced by the system itself.
The commercial layout of proposals has also been refined to mirror April9's standard proposal template section by section, so what you read matches what you're signing:
- Credit Schedule — Development Credits now sit in their own section, with total credit value, validity period, drawdown terms, and what happens on early termination or expiry, all spelled out.
- Ongoing Services — recurring services show their initial term, renewal term, and rolling-renewal notice period up front.
- Module Terms — each commercial section names the Module Terms that govern it.
- Special Conditions — deal-specific conditions get their own unmissable section.
- Clearer pricing — monthly and annual amounts are totalled separately, with a single authoritative statement of cost.
Release 2.3.0 — 22 July 2026
Your whole relationship with April9, on one screen
Two new views tie everything together, giving you a complete picture of what you've bought and what's being delivered.
- Engagements. Every piece of contracted work now appears as an engagement with its own detail view: the schedule of work over time, the releases delivered under it, and the associated documents.
- Support Agreements. Ongoing support arrangements show your credit position at a glance — the annual allowance, what's been consumed, what's reserved against open proposals, and what remains available.
Both appear on your dashboard, so you know exactly where things are at as soon as you log in to the Deliver Portal. Engagements are grouped into Active and Completed, so current work always surfaces first, and status labels are written in plain language — "Getting Started," "In Progress," "Wrapping Up," "Completed" — rather than internal terminology.
Engagement detail pages also include a visual schedule timeline, so you can see the shape of delivery — what's underway, what's coming, and how the pieces sequence.
Also in this release:
- 2.3.1 (27 July 2026) — refined how support credit balances are presented, with consumed, reserved and available credits calculated consistently everywhere they appear, plain-English explanations of each figure, and a clear visual signal when delivery has drawn down more than the agreement covers.
- 2.3.2 (28 July 2026) — improved how release feature lists display on the release detail page.
Release 2.2.0 — 12 June 2026
Requirements made easy to review
Where a feature has been specified in structured form, it now appears in the portal as a proper document with distinct, navigable sections:
- At a glance — a summary of the feature's size and shape
- User stories — who wants what, and why, with priorities
- Edge cases — the scenarios covered and how they're handled
- Functional requirements — the itemised list of what will be built
- Key entities — the business objects involved
- Success criteria — how the feature will be judged once live
- Clarifications — questions asked and answered during specification
- Assumptions — what April9 has taken as given
The same content adapts to where it's being read: a compact layout inside the UAT review panel, and a roomier, print-friendly layout in the Business Requirements Document.
Proposals also got a similar treatment — grouped into Draft, In Progress and Completed, each with a live count, so you can find the one that needs a decision without scrolling through years of history. Status labels here are written for clients too — a sent proposal now shows as "Awaiting Response."
Also in this release:
- 2.2.1 (19 June 2026) — internal data definitions regenerated to stay in step with the platform.
- 2.2.2 (8 July 2026) — improved reliability of release detail pages for all clients.
Release 2.0.0 — 4 May 2026
Built for how larger organisations work
If you sit across more than one entity in your group — a holding company, a group structure, or simply someone who works with more than one April9 client organisation — you can now move seamlessly between them in the portal and see the right data for each, with a single login for everything.
The releases list also got a rework, organised into three categories — Draft, In Progress and Completed — each with a live count, so you can see at a glance what's waiting on you. And the landing page received a visual refresh, giving a stronger first impression when you follow a proposal or release link.
Ongoing refinements
Alongside these larger updates, we've continued to make smaller improvements to speed, reliability and day-to-day polish across the portal — the kind of behind-the-scenes work that keeps everything running smoothly.
Any questions, or suggestions about more ways to improve the Deliver Portal? We'd love to hear from you.
