Define: Application Submitted

What Application Submitted means in a contract

Application Submitted is a milestone term. It marks the moment a completed request has been lodged with the relevant authority or counterparty and, in careful drafting, acknowledged as received for a particular purpose. Rather than describing a thing, it describes an event, and contracts use that event as a fixed point from which other consequences flow. Because so much can hinge on whether and when a submission occurred, the phrase needs a clear definition of what "submitted" and "completed" actually require.

How Application Submitted is defined and measured

The key questions are completeness and acknowledgment. A contract should state whether submission means simply lodging the request or lodging a request that meets the authority's requirements, since an incomplete filing can be rejected and may not count. Many clauses require evidence of submission, such as a receipt, reference number, or acknowledgment from the authority, so the milestone can be proven rather than merely asserted. Where timing drives obligations, the definition should also fix whether the relevant date is the date of lodging or the date of acknowledgment, because the two can differ.

Where it appears

Application Submitted appears wherever a filing conditions later steps. It is central to a patent application, where the submission date can carry significant weight, and it features in procurement processes such as a request for proposal, where a submitted response starts evaluation and deadline clocks. Drafting the notice around such a filing is discussed in this guide to drafting an application notice, which highlights how the moment of submission is recorded and communicated between the parties.

Why the exact wording matters

If the contract does not define what counts as a submission, the parties can disagree about whether an obligation was met at all. One side may treat a partial or provisional filing as sufficient, while the other insists on a complete, accepted application. Ambiguity about the date is equally consequential when the milestone triggers a payment, starts a limitation period, or unlocks a later step, because a difference of days can decide whether a deadline was hit. Requiring acknowledgment and defining completeness turns a soft claim of "we applied" into a verifiable event under the law governing the contract.

Drafting considerations

• Define completeness. State whether submission requires a filing that meets the authority's requirements, not just any lodging.
• Require acknowledgment. Ask for a receipt or reference so the submission can be proven.
• Fix the date. Say whether the milestone is the lodging date or the acknowledgment date, and use it consistently.
• Tie consequences to the event. Make clear which payments, deadlines, or obligations the submission triggers.
• Address rejection. Provide for what happens if the application is returned as incomplete or refused.
• Assign responsibility. State which party is responsible for making the submission and for supplying the information needed to complete it.

Because a submission is the hinge on which later duties turn, a precise definition protects the party relying on it and prevents a routine filing from becoming a contested question of fact. When the contract says exactly what a completed application requires, how its receipt is proven, and which date governs, the milestone can be verified rather than argued, and the obligations that hang from it rest on solid ground under the law governing the contract. That certainty is worth far more than the modest drafting effort it takes to define the event well.