Our subcontracts don't say how an application has to reach us
No form, no route, no named recipient, so anything that turns up has to be treated as an application.
What's happening?
When the subcontract is silent on how applications arrive, anything can be one: an email to the site manager, a spreadsheet in a thread, a one-line invoice with a number in it. Each has to be taken seriously, because the cost of wrongly ignoring a valid application is the payment machinery working against you - an applied sum falling due in full because nobody served a notice against a document nobody recognised as an application.
The fix costs nothing at drafting: applications in a stated form, to a named recipient, by a stated route and date. Downstream of that clause, the payment cycle has edges - the team knows what to log, what to assess and what doesn't count as an application at all. Subcontract drafting builds the clause in; on existing subcontracts, the practice can at least be tightened by agreement.
The solution
Applications with a defined door to arrive through.