“Submitted” hides several different questions
Which opportunity was the application for? Which candidate details were used? Which CV version was attached? Were employer questions answered? Was AI-assisted text included? Which consent version applied? When did the submission occur?
If a product cannot answer those questions later, its receipt is mostly a status label. A candidate deserves a record that can help reconstruct the reviewed submission instead of forcing them to trust a transient success screen.
A useful receipt preserves the reviewed state
KUL's internal application receipt is designed around that principle. It can preserve a private record of the opportunity snapshot, candidate snapshot, reviewed CV reference, employer questions and answers, consent version, whether reviewed AI-assisted text was included, the submission method and the submission time.
The point is not to collect more data. The point is to retain the minimum evidence needed to make the application state understandable later.
Delivery certainty has to come from authority
There is another distinction that matters: recording an attempt, confirming KUL committed an internal submission, and proving that an external destination accepted an application are not the same thing.
If an external system does not return authoritative confirmation, a responsible product should not manufacture one. “Outcome not yet confirmed” can be less satisfying than a green tick, but it is more useful than false certainty when a duplicate submission could harm the candidate experience.
Ambiguity should trigger reconciliation, not blind retry
Network failures create a dangerous edge case: the browser may not know whether the server committed the submission before the connection disappeared. Automatically retrying can create duplicates. Automatically saying “failed” can be equally wrong.
A safer pattern is to check authoritative state first. If a verified receipt exists, surface it. If the state is still unknown, say so and guide the candidate without pretending the system knows more than it does.
Trust is a product surface
Application UX is often optimized for the moment before submission: fewer fields, faster completion, better autofill. The moment after submission deserves the same care.
A private, inspectable receipt turns “I think I applied” into a durable record of what KUL can actually prove. That is a small interface detail with a larger consequence: candidates can act with less uncertainty.