Outbound Submissions

Submissions is the outbox for things you must send to somebody official: court filings, statutory returns, regulator portals, insurer notifications, funding claims, framework reporting.

Where to find it

These features have no dedicated Architect Panel section of their own. They are configured through their datastores, opened from All Datastores, and most of what a caseworker sees appears on the record itself rather than on an admin screen.

Why an outbox

These sends differ from ordinary correspondence in that they have a destination that answers back, a deadline, and consequences for getting the format wrong. An outbox gives you a queue you can inspect, retry and evidence, rather than a series of one-off actions somebody performed.

What a submission carries

The payload, the destination, the state, and what came back. Where the destination expects a compiled pack rather than a single document, a submission can carry a bundle — the assembled set, in order, paginated as the recipient requires.

Deadlines

Pair a submission with an obligation so the deadline is tracked and escalated like any other. A filing deadline that lives only in the submission is one nobody sees until it passes.

Failures

Watch for repeated failures against one destination — they usually mean a format or credential problem rather than a transient one, and each retry consumes time you may not have before the deadline. Treat a second failure as a signal to look rather than to retry again.

Keep the acknowledgement

Whatever the destination returns — a receipt, a reference, a rejection — belongs on the case. It is the evidence that the obligation was discharged, and it is the first thing asked for when a regulator says nothing arrived.