process_server_field_operations v1.0.0

name: process_server_field_operations description: "Running process service work so every attempt holds up in court: assignments checked for the right person, address, and deadline before the first drive, attempt logs written at the door with time, description, and result, diligence built across varied days and hours instead of three knocks in one afternoon, skip tracing kept inside legal and platform rules, and affidavits of service drafted from the attempt log instead of from memory. Use when taking a service assignment, planning attempts, logging an attempt, deciding whether diligence supports substituted or posted service, tracing a moved subject, or drafting an affidavit of service or non-service."

Process Server Field Operations

Purpose

Run a service assignment as one chain that a court can follow later: a checked intake sheet, a planned pattern of attempts, a log written at each door, a lawful trace when the address fails, and an affidavit built only from that log. Job tracking software holds addresses, statuses, and invoices, and association training is mostly aimed at servers inside large firms. Neither ships a method. This skill is the method, for a solo server or a small firm, from assignment to filed proof.

The record is the product. A serve nobody can prove is a serve a defendant can challenge, and a false or padded record is worse than a failed serve. New York prosecutors built the American Legal Process case on exactly that: the Attorney General said the firm claimed 98,000 serves in about 20 months, filed false affidavits for serves that never happened, and left defendants learning about lawsuits from frozen bank accounts. The owner pleaded guilty to scheme to defraud in January 2010. Every rule below exists so a file never looks like that file.

Workflow

1. Check the assignment before the first drive

• Confirm the court, case name, and case number against the papers themselves, and list every document in the set by title. An affidavit that names a document the server never carried, or omits one that was served, is wrong on its face.
• Confirm the subject as named in the papers, the recipient type, and the method rules that type carries. An individual, a business, a registered agent, and a government body are not served the same way, and a rule borrowed from the wrong type voids the serve.
• Write the service deadline on the assignment with the rule it comes from. As a federal baseline, Federal Rule of Civil Procedure 4(m) gives 90 days after the complaint is filed. A state case runs on the state rule, so read that rule and use its figure, not the federal one.
• Confirm the server qualifies where the serve will happen. The federal baseline in Rule 4(c)(2) is a person at least 18 years old who is not a party. Many states and some cities add registration, licensing, or bonding. Check the requirement for the place of service on every assignment, and do not carry a qualification from one state into another.
• Record every address with its source and date, the fee limit, the rush level, whether substituted service is wanted if personal service fails, and any hazard the client knows about. A missing description or photo is a question to the client now, while it can still be answered, not a gap to discover at a door.
• Full intake field list: references/field-forms-and-diligence.md section 1.

2. Plan diligence before the first knock

• Spread attempts across different days and different times of day from the start. Three knocks in one afternoon prove persistence for one afternoon and nothing about a person who works, and courts reading a diligence record look for varied days and hours.
• Use the planner for a starting pattern, then adjust it for real signals in the file, such as a night shift job, and write the reason for each change on the assignment:

python3 scripts/process_ops.py plan --start 2026-11-02 --attempts 4

attempt_1: 2026-11-02 (Mon) weekday_early 07:00-08:30

attempt_2: 2026-11-03 (Tue) weekday_evening 18:00-20:00

attempt_3: 2026-11-07 (Sat) weekend_morning 09:00-11:00

attempt_4: 2026-11-09 (Mon) weekday_midday 12:00-13:30

• Check the days and hours allowed for service in the place of service before using any slot. A slot the local rule forbids, for example a restricted day, is not an attempt, it is a violation with a timestamp.
• Turnaround clocks start at receipt. Under the NAPPS forwarding definitions used when servers send work to each other, DO TODAY means attempted the same day received, RUSH means attempted within 48 hours, and ROUTINE means a first attempt within 4 days. A client or court deadline that is shorter beats all three.

3. Work the door

• State who you are and why you are there, plainly and once. Do not explain the case, argue the merits, offer legal advice, or negotiate with the person at the door. None of that is the server job, and all of it creates a record problem.
• Establish identity before papers change hands, and use two legs where you can: the person stating their own name, plus a description or photo match, or a document or detail only the subject would know. Write down which legs you used. Serving the wrong person with the same name is a real failure mode at multi unit addresses and in families.
• If the subject refuses the papers, follow the rule for the place of service on what counts as delivery in the face of refusal, state out loud that you are serving legal papers and what they are, and record the exact words and actions. Do not touch the person, block a door, or follow them into a building.
• Stand back from the door, keep an exit path, and leave when told to leave. Safety beats completion on every attempt. A serve can be reattempted, an injury or an arrest at a door cannot be undone, and no fee covers either.
• Respect access limits. Do not enter a home, a garage, a fenced yard, or a non-public business area, do not open or climb a locked gate, and do not misrepresent yourself to a guard or a building system to get in. Where a gated community or secured building blocks access, work through the guard or manager lawfully, record the refusal and who made it, and report it. Trespass rules are state specific: California, for example, gives a registered server a narrow exemption to go to and from a front door under Penal Code 602(n), and that exemption still does not allow entering a dwelling. Know the rule where you stand, or stay on public ground.
• Photograph only what the firm policy and the local rule allow, from a place you may lawfully stand. A photo supports a log row, it never replaces one.

4. Write the attempt log at the door

• Write one row per attempt before driving away, with date, time at the door, exact address including unit, result code, who was contacted, a physical description of anyone served, and notes limited to what was seen and heard. Field list and good and weak row examples: references/field-forms-and-diligence.md section 2.
• Keep opinion, labels, and guesses out of the log. Write the observation or write nothing. A log is read aloud in court exactly as written, including the parts the server wishes were not there.
• Use the result codes in the checker, so months of attempts can be read as data: served_personal, served_substituted, no_answer, refused, not_at_address, bad_address, access_blocked, other.
• Log a failed attempt with the same care as a serve. The failed rows are the diligence record, and they are what a judge reads when substituted service, posting, or publication is challenged.
• Run the checker before reporting an address as exhausted:

python3 scripts/process_ops.py check --file attempts.csv

attempts: 3

distinct_days: 3

distinct_time_bands: 2

distinct_addresses: 1

served_rows: 1

problems: none

A clean check means the log is complete, varied across days and time bands, and every served row carries a description. On a weak log the checker names the problem, for example three attempts on one day in one time band with empty notes, and that file goes back for real attempts, not for better wording.

5. Decide the next method from the record, not from frustration

• Personal service stays the goal until the record shows it cannot be done with diligence at the addresses the record supports.
• Substituted service only when the rule for the place of service allows it for this recipient type, the diligence before it meets that rule, the person receiving papers meets the rule test and was told what the papers are, and the follow up mailing the rule requires is done and logged. California Code of Civil Procedure 415.20(b) is one worked model: leave at the dwelling or usual place of business with a competent household member or person apparently in charge who is at least 18 and informed of the contents, then mail a copy to the same address, with service deemed complete on the 10th day after mailing. Read the local rule, do not import the California one.
• Posting, service by publication, and any method a court reserves to order come after a court order, not after a server decision. The affidavit of non-service and diligence is the evidence for that request, which is why its rows have to be exact.
• When the record shows the subject has moved or never lived at the address, stop attempting there and say so to the client in writing. Extra attempts at a dead address inflate a bill and weaken a diligence claim, because they show the server stopped reading their own log.
• Full checklist: references/field-forms-and-diligence.md sections 3 and 4.

6. Trace a moved subject inside the rules

• Work in order: re-read the papers and client file, fix obvious address errors, ask the client in writing for newer information, ask a narrow question at the address about whether the named person lives there now, then public records and open sources, then a regulated database only where the firm holds an account and the purpose is recorded. Log every step and every dead end. Order and stop conditions: references/field-forms-and-diligence.md section 5.
• Record the permissible purpose for a regulated search before the search runs, in the file, in words tied to this assignment. Service of process in a court proceeding is a listed permissible use for motor vehicle record data under 18 USC 2721(b)(4). That listing covers that data class for that purpose, it is not a general licence to pull any record on any person.
• Treat every trace hit as a lead with a source and a date, not as a confirmed address. An old address from a dated filing earns attempts, it does not earn a substituted serve until someone has been found there.
• Never pretext. Federal law at 15 USC 6821 and following bars getting financial institution customer information by false pretenses, and the same move in other settings, lying about who you are or why you are asking, risks the serve, the database account, and in some places a licence. Do not impersonate law enforcement, a delivery driver, a utility worker, or anyone else. Do not ask a neighbour, employer, or relative for information beyond what the service question needs.

7. Draft the affidavit from the log, then file the return

• Draft with the tool, which copies log rows and adds nothing:

python3 scripts/process_ops.py affidavit --file attempts.csv --server "Sam Carter" --subject "J. Example" --case "Example County Court, Example v Example, No. 26-CV-000" --documents "Summons and Complaint"

• Read the draft line by line against the log before signing. Check names and case numbers against the papers, the document list against the intake sheet, and every date, time, and address against its log row. Fill any BLANK marker from a source you can point to, or delete the line with a reason, never from memory.
• For non-service, the affidavit lists every attempt and every verification step, because that document is the basis for any request for another method. A summary line such as attempted three times, subject not found gives a court nothing to decide on.
• The server who made the attempts signs. Under Federal Rule 4(l)(1), proof of service must be made to the court unless service was waived, and except for a US marshal or deputy, proof must be by the server affidavit. Add the oath or notarization block the court requires, and only state it was done if it was done.
• Return the proof inside the clock set at intake. Under the NAPPS forwarding definitions, proofs go back within 1 day on DO TODAY and RUSH papers and within 4 days on ROUTINE papers. Report the completion date in writing where a method has a deferred completion date, as substituted service does, so the client calculates response time from the right day.
• Worked end to end example, intake to signed affidavit, with a stale address, a public record trace, and a night shift serve: references/worked-difficult-serve.md.

Output Contract

• An intake review returns: missing or conflicting fields named one by one, the deadline with the rule it came from, the qualification check for the place of service, and a go or no go for the first attempt.
• An attempt plan returns: attempt dates, days, and time bands, the signal each slot is timed for, any slot the local hours rule rules out, and the turnaround clock the assignment is on.
• An attempt report returns the log rows as written, plus the checker counts for attempts, distinct days, distinct time bands, distinct addresses, and served rows, with every problem the checker found listed, not summarised away.
• A method decision returns: the method, the local rule that allows it, the diligence rows relied on, the mailing or order step still owed, and the calculated completion date with the rule it was calculated from.
• A trace report returns: each step taken with its source and date, each lead found labelled as a lead, the steps not taken and why, and the fee position against the client limit.
• An affidavit package returns: the draft affidavit with every line traced to a log row or intake field, a list of any BLANK markers left and what source is needed to fill each one, and the signed, filed status once the server confirms it.

Operating Rules

• This skill is field method, not legal advice. Service rules, licensing, hours, and methods are set by the court and the place of service. When this skill and a local rule disagree, the local rule controls, and the file records which rule was followed.
• Never sign, backdate, or file an affidavit for an attempt that did not happen, an attempt another server made, or a detail the log does not carry. That conduct has a name in the cases, sewer service, and it ends firms and draws criminal charges.
• Never pad diligence. Repeated attempts at an address the record shows is wrong, attempts logged at times the server was elsewhere, and attempts written up in a batch at the end of a week all read as padding to anyone who audits the file, and audit tools check time gaps and GPS records against claimed attempts.
• Never invent a deadline, an attempt count a rule requires, a description, or a statement by a person at a door. Where a source is not in hand, say so and get it before acting.
• Keep subject information inside the file. Addresses, descriptions, schedules, and database results for a named person go to the client on the assignment and nowhere else, and regulated database results are never reused for a different case or a different purpose.
• Do not serve a person you have reason to believe is not the named subject just to close a file. Stop, record the doubt and its basis, and ask the client.
• If a door turns threatening, leave, log it from a safe place, and report it the same day. Do not return alone to an address where a threat was made without a plan the firm has agreed.
• Client papers and personal data in a vehicle are the server responsibility. Keep sets separated by case, never leave papers visible, and return or destroy unserved copies as the client instructs, recording what was done.