Published

A customer sends a complaint and an appointment confirmation. The receipt says “submission successful,” but one attachment cannot be opened and a required visit report is still missing. The customer assumes the case is ready; the caseworker is waiting for more evidence.
Acknowledge the stage that actually succeeded: receipt, file checks, registration or completeness review. Tell the sender which documents need attention and how to supply them against the existing submission. Keep the final case decision separate from those intake messages.
Record the submission reference and received items, including any uncertain transfer outcome.
Show file-check results, missing requirements and the action needed for each exception.
Record the completeness decision and identify the review or response that follows.
| Message | Evidence behind it | What happens next |
|---|---|---|
| Submission received | The receiving channel recorded the transfer and its item list. | Run the configured file checks and reconcile missing items. |
| File checks complete | Each item has a recorded result for the required technical checks. | Release eligible files or request action on the named exceptions. |
| Documents registered | Recorded documents have FormKiQ identifiers and the intended case relationship. | Check whether they satisfy the case's evidence requirements. |
| Further information required | A file exception or missing business requirement has an owner and reason. | Provide the requested replacement or additional evidence using the same case reference. |
| Ready for review | The configured completeness review confirms the evidence needed for the next stage. | The responsible reviewer considers the case. Its outcome is still pending. |
These states need not occur in a fixed storage order. An intake workflow can record an original document while holding it outside normal processing or review. A “checks complete” message must show failed or unresolved results, rather than implying every file passed. The malware workflow guide explains how configured scan outcomes affect release; a scan result does not establish business completeness or guarantee that a file is harmless.
Keep a submission reference, each transfer attempt and the individual item references distinguishable. Retain the source reference, received time, expected item list, recorded document identifiers and check results. A repeated delivery can then be compared with the original attempt before it creates more case work. The same filename alone cannot establish that two files are the same. Verify the sender's authority to contribute to the identified case before accepting a replacement against it.
For a partial package, tell the sender what was received, what is held or missing, and which item to replace. Agree whether eligible files can proceed independently or the whole package must wait. Link a replacement to the original requirement and preserve the earlier result. If a transfer times out, reconcile the known reference before asking the sender to start again; the upload-integrity guide covers that technical boundary.
Use the verified contact or authenticated channel associated with the submission. A receipt can provide a reference, current stage, outstanding action and support route without exposing sensitive filenames, case details or document links in ordinary email. Keep protected-file handling in the approved intake process described in the password-protected submission guide.
Track notification delivery separately from case progress. A bounced acknowledgement needs follow-up even when the documents arrived successfully. Give pending checks, unmatched replacements and undelivered requests an owner and an agreed review interval. Show the time of the status update so an older receipt is not mistaken for the current case position.
This fictional configured intake extends the missed-visit scenario in the Case Management example. The customer's complaint names an appointment confirmation, while the case also needs the technician's visit report.
The email intake records a complaint and an appointment attachment under one submission reference. Its receipt says that two attachments arrived and that file checks are pending. The intake coordinator connects the submission to CASE-1042.
The appointment attachment cannot be opened under the configured intake policy, so the sender receives a replacement request. The case checklist also shows that the technician's visit report has not arrived. One is a problem with a received item; the other is a missing business requirement.
The customer supplies a readable appointment confirmation using the submission reference. Intake records its checks and replacement relationship. A repeated delivery is reconciled against that reference before another document or case task is created.
The caseworker obtains the visit report, checks the case's evidence requirements and records readiness for the next review. The status message identifies that next step; it does not promise a particular resolution.
The caseworker prepares the proposed resolution for the authorised reviewer. The final response and any confirmed replacement visit follow the Case Management workflow, retaining the intake, replacement and review history in CASE-1042.
A useful acknowledgement tells both sides which submission they are discussing, what succeeded and what remains outstanding. Connect file outcomes and replacement requests to the case so the sender can respond once and the caseworker can see when the evidence is ready for review.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.