Legal Services Offshore blog
Set a process server attempt log that preserves every service attempt
An attempt log that captures each date, address, and outcome in the same structure so the affidavit and the matter record agree.

Key takeaways
Service of process is a sequence of attempts, and the log should show the sequence rather than only the final result. Each entry records the date, the time window, the address, the person who attempted service, and the outcome. A single line that says service was unsuccessful hides the facts a court may later ask about. The log gives the firm a readable history.
The log and the affidavit serve different purposes, so keep both and compare them. The server prepares the affidavit, while the firm records the assignment and the delivery of the paperwork. A mismatch between the two is easier to find before filing than after. Record the comparison and the person who completed it.
Record a failed attempt in the same structure as a successful one. A locked gate, an unknown resident, and an address that no longer exists are different outcomes. Each one supports a different next step. Uniform fields make those differences visible without interpretation.
Keep the log within the matter record and restrict access to the people who need it. The log contains home addresses and personal details that deserve protection. Record who can edit and who can only read. Review access when an assignment ends.
Capture the assignment before the first attempt
Record the documents to be served, the person or entity to be served, and the authority that issued the process. The assignment should name the court and the case number exactly as they appear. A server who receives only a name and an address cannot confirm the match. The support worker prepares the assignment from the approved documents.
Write the service address as it appears in the instruction and keep any alternate address separate. Combining two addresses into one field creates ambiguity about where the attempt occurred. Record the source of each address, such as the client or a public record. The lawyer decides which address may be used.
Record the deadline or the target date for service and the person who calculated it. The server needs to know the urgency without being asked to interpret the rules. Record the instruction as given rather than a new legal conclusion. The lawyer confirms the date that governs.
Confirm the server's identity and the scope of the assignment in writing before the first attempt. Record the company, the individual, and the contact details used. A verbal assignment is difficult to reconcile with an invoice later. Keep the confirmation with the log.
Record each attempt with the same fields
Use one field structure for every attempt so entries can be compared without retelling the story. Date, time window, address, outcome, and the person attempting service should appear in the same order. Add a free-text note only for detail that the fields cannot hold. Consistency makes a later review possible.
Record the time as a window when the server can only provide a range. A precise time that the server did not record is worse than an honest window. Write the source of the time beside the value. The difference matters when the other side describes the same visit.
Describe the outcome in plain words and avoid conclusions about validity. Attempted service, left with a resident, and refused are observations. Whether an attempt satisfies a rule is a legal question. Record the observation and route the question to the lawyer.
Attach the server's photograph, note, or receipt when the assignment produced one. Record the file name and the date received. A photograph without a date is weaker evidence than one filed with the attempt entry. Keep the attachment in the approved location.
Keep the affidavit separate from the log
The server prepares the affidavit, and the firm should not rewrite it to match the log. Record the affidavit as received and compare it with the attempt entries. A difference in a date or an address is a question for the server. Record the question and the answer.
Check that the affidavit names the person served and describes the documents delivered. A missing document description is a gap that may matter at filing. Record the check and the person who completed it. Send any correction request in writing.
Keep the signed affidavit in the matter record with the log entry it supports. A reader should be able to move from the entry to the affidavit without searching. Record the storage location and the date. The two documents should remain linked.
Do not treat the affidavit as proof that service was legally sufficient. Sufficiency is a legal question for the court and the lawyer. Record what the document states and what remains open. The log supports review rather than replacing it.
Handle a failed attempt without guessing
Record the reason a failed attempt is being escalated and the next approved option. Options may include another attempt, a different address, or a request for an alternative method. The lawyer chooses among them. The log should not present a preferred option as a decision.
Keep the failed entries visible after a successful attempt. Deleting them makes the history look shorter than it was. A court may want to see the sequence that led to service. Record the success in a new entry rather than overwriting the earlier ones.
Note any instruction from the client that changes the plan, such as a new address or a request to pause. Record the instruction, the date, and the person who gave it. Confirm the change with the server before the next attempt. A plan that changes without a note is hard to reconstruct.
Route a repeated failure to the lawyer with the entries and the server notes attached. A pattern of failures may call for a different approach or a filing. The support worker can summarize the pattern without recommending a legal step. Record the handoff and the next owner.
Store the proof where the matter can find it
Store the assignment, the attempt log, the server notes, and the affidavit in one matter folder. A folder that separates the log from the proof creates work for every later reader. Record the location in the matter index. The index should name the service documents.
Use access controls that match the sensitivity of the content. Home addresses and personal details should not be visible to the whole team. Record who has access and why. Review the list when the assignment closes.
Record the delivery method and the tracking number when physical documents travel to the server. A package that cannot be traced is a gap in the record. Record the date sent and the date received. Attach the receipt to the log.
Check that the stored files open after any system migration. A link that no longer works is not proof. Record a sample check and the date. Review old service folders during the next records audit.
Review the log before the service deadline
Review the log against the service deadline a few days before the date, not on the day. The review should confirm that each attempt is recorded and that the affidavit is present. Record the reviewer and the result. An early review leaves time for a further attempt.
Compare the log with the matter calendar and the court docket for the same period. A service entry that appears in one place but not the others may signal a recording gap. Record the discrepancy and the owner. Do not correct one system without checking the others.
Sample a few completed assignments and check that the log and the affidavit agree. Record the differences and the correction requested. The sample is process evidence for the firm. It is not a score for an individual server.
Review the assignment template with the lawyer who handles service questions. A field that is never used should be removed, and a missing field should be added. Record the change and the date. The next assignment should start with a better template.
A supervised support lane can prepare the assignment, maintain the attempt log, and compare it with the affidavit while the lawyer decides what service requires. litigation document review.
Sources
- American Bar Association, Model Rules of Professional Conduct
Used for supervision, confidentiality, competence, and communication boundaries in legal support work.
- U.S. Courts, Federal Rules of Civil Procedure
Used for the litigation, service, and production workflow context that these controls support.
- GAO, Standards for Internal Control in the Federal Government
Used as a general reference for documented ownership, review evidence, and exception handling.
- NIST Cybersecurity Framework 2.0
Used for access control, monitoring, and recovery language around shared legal records.