All Docs
FeaturesDepositClearUpdated March 11, 2026

Deposit Release: The Acknowledgement-to-Release Gap

Deposit Release: The Acknowledgement-to-Release Gap

Version note: This article reflects the behaviour as of v0.1.170. A fix to add automated notifications and work-queue surfacing is tracked for a future release.

How the Deposit Release Workflow Works Today

The deposit release process moves through a series of statuses as parties respond:

draft → sent → pending → acknowledged → released

What happens automatically

When the final party submits their acknowledgement, the recordAcknowledgement mutation (src/lib/routers/deposit-release.ts) detects that all responses are in and automatically advances the release status to acknowledged.

This part works correctly and requires no manual intervention.

What does NOT happen automatically

Once the status reaches acknowledged, the system currently stops. There is:

  • ❌ No in-app notification sent to org admins
  • ❌ No email alert triggered
  • ❌ No work-queue item raised or prioritised
  • ❌ No prompt guiding the agent to initiate the release

The release sits silently at acknowledged status until an agent manually finds it, opens it, and clicks Initiate Release.

Workaround (Current)

Until the automated notification pathway is implemented, agents and admins should:

  1. Regularly check the Deposit Release dashboard and filter by status = acknowledged.
  2. When a release appears in acknowledged status, review it and click Initiate Release to advance to released.
  3. Consider setting a manual reminder or internal process trigger when sending a release, so you know to check back once all parties have had time to respond.

What the Fix Will Deliver

The planned improvement will fire an Inngest event immediately after the acknowledged transition, which will:

1. In-app notification

All org admins will receive an in-app notification:

*"All parties have acknowledged the deposit release for [property] — ready to initiate release."

2. Work-queue prioritisation

The acknowledged release will be surfaced at the top of the deposit release dashboard so it is immediately visible without filtering.

3. Email notification (opt-in)

Orgs with email notifications enabled will receive a parallel email via the existing sendEmail function.

4. Auto-advance to released (opt-in)

Orgs that choose to opt in will have the release automatically transitioned from acknowledged → released with no manual click required.

Status Definitions

StatusMeaning
draftRelease created but not yet sent to parties
sentRelease sent; awaiting party responses
pendingSome but not all parties have responded
acknowledgedAll parties have responded and agreed — awaiting agent to initiate release
releasedRelease has been formally initiated by the agent

Related