What Happens When the Avoiding Service Field Says Yes
A process server who arrives at an address without knowing whether the respondent is expecting or actively avoiding service is operating on incomplete intelligence. The difference between walking up to a door cold and walking up knowing the respondent has already been tipped off by their attorney, has changed their routine, and may refuse to answer shows up in the approach, the documentation strategy, and the number of attempts required.
The Expecting Service and Avoiding Service fields in this template are each three-state: Yes, No, Unknown. Unknown is not the same as No. A respondent whose avoidance status is Unknown warrants a different level of field preparation than one confirmed non-avoiding. When these two fields are both set to Unknown, the server goes in with broad situational awareness. When Avoiding Service = Yes, the server adjusts timing, may attempt substitute service, and documents every attempt attempt-by-attempt in the notes rather than in a single entry.
The Service Opinion Field Is the Billing Decision
Service Opinion captures the pricing tier at the time of assignment: Routine at $65, Rushed at $85, Same Day at $100, Immediate at $125. This is not a post-hoc billing code — it is the client's request classification entered at intake and attached to the case record. When a client disputes the invoice and claims they only requested routine service, the record shows what was selected at the time of the original order. Without this field, the billing conversation relies on memory or email chains that may be ambiguous.
The service pricing tier also informs the server's resource commitment. An Immediate service at $125 gets same-day prioritization over a Routine assignment entered two days ago. When a server is carrying twelve active assignments, the Service Opinion field sorted by tier gives the day's priority stack.
Respondent Descriptors as the Field Intelligence Layer
The Descriptors field holds the physical description that lets the server confirm identity before delivery: height, build, hair color, distinctive features, vehicle in driveway. In cases where multiple adults share an address, this is the disambiguation tool. An incorrect service — delivering to the wrong person at the correct address — creates a return to the court, a delayed case timeline, and a frustrated client.
The respondent name and address fields are the primary search keys. Client name and client organization establish the instructing party, with phone and email providing the direct contact for status updates and complications. Type of Process — Subpoena, Summons, or Other — with a free-text expansion for the Other option covers the standard service types while remaining flexible for less common instruments.
Status (Un-served, Served) is the case closure flag. An active caseload where every un-served assignment is visible at a glance is the operational baseline for a process server managing volume. When a court deadline is approaching on a case still marked Un-served, the record surfaces that pressure before it becomes a missed filing.