SOPA notices and SMS: deadlines, records and evidence

Security of Payment legislation gives contractors and subcontractors a fast, strict statutory process for getting paid. The operative word is strict: the process runs on fixed timeframes and documents, and it is routinely won or lost on records and timing rather than on the merits.

What is SOPA, in one paragraph?

Every Australian state and territory has security of payment legislation (in NSW the Building and Construction Industry Security of Payment Act 1999; other jurisdictions have their own Acts, and the details differ). The common shape: a claimant serves a payment claim; the respondent must reply with a payment schedule within a fixed statutory window or become liable for the claimed amount; unresolved disputes go to fast-track adjudication, again on fixed timeframes. Miss a window and rights can lapse — sometimes permanently.

Where does SMS fit into a SOPA process?

Two distinct roles, worth keeping separate in your head:

• SMS as the surrounding record. This is the uncontroversial one. The instructions, variations, delay notifications and payment conversations that led to the claimed amount usually happened by text. When you assemble a payment claim or an adjudication application, that correspondence is your supporting evidence — if you can find it, date it and organise it.
• SMS as the service method for statutory documents. This is a legal question. Valid service methods depend on the applicable state Act, your contract, and electronic transactions legislation. Do not assume a text message validly serves a payment claim or schedule — confirm the service method with your legal advisor, and use SMS as the fast, recorded companion channel rather than the sole formal channel unless advised otherwise.

Why do records decide SOPA outcomes?

• The timeframes are unforgiving. Response windows are typically in the range of 10–15 business days depending on the state — and adjudication windows are shorter. Proving when something was sent and received is often the whole argument.
• Adjudication is documents-only. There is rarely a hearing. The adjudicator decides on what you can put in writing, fast. A complete, organised, dated message trail beats a shoebox of screenshots.
• The claimed amount is built from events. Variations directed by text, delays notified by text, work accepted by text — each needs a contemporaneous record to survive scrutiny.

How do you keep SOPA correspondence organised in SMSuni?

1. Send payment-related messages classified as SOPA statutory — payment claim, payment schedule, dispute notice, adjudication notice categories — linked to the project and contract.
2. Set the notice period on each message; SMSuni calculates the response due date and flags overdue notices on your dashboard before a window closes silently.
3. Use notice chains to link a payment schedule to its payment claim, so the paper trail reads as a sequence, not a pile.
4. When a dispute escalates, export the SOPA Pack — a PDF containing only the SOPA-relevant messages for the project, with a SHA-256 integrity hash, organised for review and submission preparation.

The step-by-step workflow lives in the contract administrator docs.