06 Sep 2026
Process Serving
"Serving" a legal document just means giving someone formal, provable notice that a proceeding involving them exists — a summons, a statement of claim, a notice to vacate. The document itself rarely changes; what changes case to case is how confident you can be, later, that it actually reached the right person.
What actually needs to be served
Getting this step wrong isn’t a paperwork technicality — a court that isn’t satisfied a defendant genuinely knew about a proceeding can set aside a judgment made in their absence, sending the whole matter back to square one. That’s the real reason service is treated so carefully: everything downstream depends on it holding up.
Service requirements aren’t identical across every kind of document — a statement of claim starting a civil case, a summons compelling someone to appear, a notice to vacate, and a bankruptcy notice can each carry their own rules about who serves them, how, and within what timeframe. The common thread is that anything intended to trigger a legal obligation or deadline for the recipient needs to be delivered in a way that can later be proven, not just sent and hoped for.
The different types of effective service
Most service happens one of two ways: personal service, where the document is handed directly to the person named, or substituted service, used when someone’s genuinely avoiding contact and a court has agreed another method (leaving it with someone at their address, posting it, sometimes even a notice in a newspaper) will do. Personal service is the default because it’s the hardest to challenge later — there’s no argument about whether the right person actually received it.
Substituted service isn’t a shortcut you reach for because personal service is inconvenient — it typically requires showing a court that genuine, reasonable attempts at personal service were made and failed. That means the attempts themselves need to be documented as carefully as the eventual successful service, since they’re what justifies the court agreeing to a different method at all.
Identifying the right person in the field
A surprising amount of service work comes down to a genuinely practical problem: confirming you’ve actually got the right person standing in front of you, especially when they have every incentive to say they’re someone else. Checking ID where it’s offered, noting physical description when it isn’t, and being specific in your own records about how identity was confirmed all matter more than they might seem to at the time — because “I served the man who answered the door” is a much weaker record than “I served a man who confirmed his name and showed ID matching it.”
Evasion is common enough to plan for — deliberately not answering, sending someone else to the door, claiming the named person doesn’t live there. None of that stops service from eventually happening, but it does mean the attempts leading up to a successful service (or a substituted-service application) need their own clear record, not just the final successful one.
How do you prove service was effected when it is contested?
The part that actually gets contested isn’t the serving itself — it’s proving it happened. A good affidavit of service records who was served, when, where, and how they were identified, and the more of that you can back with something objective rather than memory, the stronger it holds up if the other side pushes back. This is the part of the job that’s easiest to get sloppy on when you’re doing six attempts a day, and the part that costs you most when a case turns on whether service actually happened.
GPS-tagged, timestamped photos logged the moment an attempt happens — not written up from memory back at the office — are exactly the kind of detail that makes an affidavit hard to argue with. When a challenge does come, it’s rarely “you’re lying about serving me” outright — it’s more often “I wasn’t at that address” or “that wasn’t actually me” or “that was a different date.” Independent, automatically-captured location and time data closes off exactly those angles, in a way a written note from memory can’t.
When service goes wrong
If service is later found to be defective — the wrong person, an unauthorised method, insufficient proof — the consequences land on whoever relied on that service, not just the process server who carried it out. A judgment obtained on the back of bad service is vulnerable to being set aside, and a case can end up needing to be re-served and re-filed, costing everyone involved real time and money. That’s the underlying reason careful process servers treat documentation as part of the job itself, not paperwork bolted on afterward.
Rules of service can differ slightly depending on which court and which kind of proceeding you’re serving for, so it’s always worth checking the specific requirements for the matter at hand rather than assuming one method covers every case.
