A new process server often begins an assignment by looking at two things: the name and the address.

Those details matter, but they are not enough.

The documents may identify a different legal name than the order email. The packet may be missing an exhibit, blank response form, or issued summons. The hearing may be close enough that the promised timeline is unrealistic. The client may expect personal service while the field instruction describes something else. The Proof of Service form may not match the case type.

If those problems are discovered after the field attempt, the trip may have no useful result. The server may need to return to the address, the client may need to rebuild the packet, and the final proof may become difficult to reconcile with the field notes.

Reviewing the documents before dispatch is therefore not administrative busywork. It is the first quality-control stage of process serving.

This article expands on our guide to handling a first process serving assignment. The focus here is narrower: how a new California process server should inspect the assignment and identify issues before printing, scheduling, or approaching the recipient.

The process server is not being asked to provide legal advice or make the attorney’s strategic decisions. The server is confirming that the operational instructions, documents, deadline, recipient, and anticipated completion record fit together.

1. Understand the Scope of Document Review

A process server’s review is operational. It asks whether the assignment can be performed accurately from the information supplied.

The review should identify:

• the court and case;
• the party or nonparty to be served;
• the exact documents in the packet;
• the deadline and priority;
• the service address and alternate locations;
• the service method requested or authorized by the client;
• any special instructions;
• the reporting expectation;
• the correct Proof of Service workflow;
• any required follow-up mailing or filing responsibility.

The server should not decide whether the client’s lawsuit has merit, interpret disputed allegations, calculate a legal response deadline for the recipient, or provide advice to the person being served. The review exists to detect inconsistencies, not to become substitute counsel.

This boundary is important for beginners. Reading legal papers carefully does not mean pretending to be an attorney. It means noticing that the document says “Superior Court of California, County of Orange” while the order was entered as Los Angeles County. It means seeing that the subpoena commands appearance on a date that has already passed. It means recognizing that the packet contains a family law summons but the proposed proof is POS-010 instead of the family law form identified by the case materials.

The appropriate response is usually a question:

The case number and caption in the order do not match the attached documents. Please confirm which packet and case information should control before we dispatch the assignment.

That question protects the client, the server, and the integrity of the final record.

2. Confirm That You Can Accept the Assignment

Before reviewing the packet in detail, confirm that you are qualified and practically able to perform the work.

California Courts generally explains that the person serving papers must be at least 18 years old and cannot be a party to the case. Separate registration rules apply to people performing compensated service at sufficient volume. Subject to statutory exceptions, California Business and Professions Code section 22350 generally requires registration when a natural person makes more than 10 compensated services of process in California during a calendar year.

If you are building a professional service business, review the current California process server registration requirements, including county filing, Live Scan, identification, bond, and renewal procedures.

Qualification also has an operational side. Ask whether:

• the assignment is within your service area;
• you can make the first attempt within the requested window;
• you have enough time for additional attempts before the deadline;
• the matter requires experience, security planning, language ability, or access you do not have;
• the client expects a service, mailing, filing, or records function outside your agreed scope;
• a conflict or relationship makes you an inappropriate server.

Do not accept an assignment merely because the address is nearby. A job that cannot be completed or documented properly is not a good first client opportunity.

3. Match the Case Information Across Every Source

Most assignments contain several sources of case data:

• the client’s order form;
• the email subject and message;
• the court caption;
• the summons or subpoena;
• the complaint, petition, request, or notice;
• the proposed Proof of Service;
• internal notes or a vendor portal.

Compare them. Do not assume they agree.

Court and Branch

Confirm the court name, county, branch, and courthouse address when relevant. A case filed in one county may involve a recipient in another county. The service location is not necessarily the court location.

Case Number

Check every digit and letter. Case numbers can contain similar characters, leading zeros, hyphens, or county-specific formats. A single wrong character can connect the proof to a different matter.

Case Caption

Compare the plaintiff, petitioner, defendant, respondent, and other party names. The caption may contain multiple parties, but the assignment may concern only one recipient.

Document Version

Look for terms such as amended, first amended, corrected, reissued, renewed, temporary, or order after hearing. A revised document is not interchangeable with the earlier version merely because the title looks similar.

Filed or Issued Status

Determine whether the papers show the filing, issuance, signature, seal, or clerk information expected for the assignment. A server should not create or alter court issuance information. If the supplied version appears incomplete, ask the client whether it is ready for service.

Create a discrepancy note whenever one source conflicts with another. Do not silently “correct” the court caption based on an email or modify the assignment based on what seems more likely.

4. Identify the Correct Recipient

The named recipient is not always obvious from the first page.

The target may be:

• an individual defendant or respondent;
• a nonparty witness;
• a corporation or limited liability company;
• a partnership or association;
• a public entity;
• a registered agent;
• a custodian of records;
• a person acting in a stated representative capacity;
• several people who each require separate service.

Compare the recipient name in the client instruction with the summons, subpoena, petition, complaint, and caption. Record aliases and alternate spellings without treating them as interchangeable unless the client confirms the relationship.

For an individual, request available identifying information:

• full legal name;
• middle name or initial;
• aliases or prior names;
• photograph;
• approximate age;
• physical description;
• vehicle information;
• workplace or schedule information;
• known household members when relevant and lawfully provided.

For a business, separate three concepts:

1. the legal entity being served;
2. the individual who may physically receive the documents;
3. the legal capacity in which that person receives them.

A receptionist’s name is not automatically the name of the registered agent. A trade name is not necessarily the legal entity. A location where the company does business is not automatically an authorized service address for every method.

If the instruction says “serve the business” but does not identify the entity or intended recipient capacity, request clarification before dispatch.

5. Inventory the Complete Service Packet

Open every file. Then create a document inventory.

An inventory can include:

• exact document title;
• form number when present;
• file name;
• page count;
• version or filing date;
• whether the document appears signed or issued;
• which recipient receives it;
• number of copies required;
• whether a blank response form or attachment is included.

This is especially important when the client uploads several PDFs. A folder containing seven files is not proof that the printed packet contains all seven in the right order.

Check for Missing Pages

Review page numbering, exhibit labels, attachment references, and signature pages. If a declaration says “Exhibit A attached” but the file ends before the exhibit, ask whether the packet is complete.

Check for Duplicate or Conflicting Versions

A client may upload an original complaint and an amended complaint. Do not choose one based on the newest file-modification timestamp. Confirm which documents must be served and whether both belong in the packet.

Check Blank Forms

Some proceedings require a blank response form or other document to be included. For example, the California Courts domestic violence restraining order forms page identifies a blank DV-120 response form as part of the papers given to the person from whom protection is requested. The server should not assume that every packet uses the same blank form. Confirm the case-specific list.

Check Language Versions

California Judicial Council forms may be available in multiple languages, but translated forms can have different legal status or use instructions. Do not substitute a translated version for the official filed or mandatory form without direction. If the client supplies both English and translated copies, inventory both.

Check Confidential Information

A service packet may contain addresses, dates of birth, financial data, medical information, or information about minors. Protect the documents in transit. Do not photograph or upload sensitive pages merely for convenience. Limit evidence capture to what is necessary and permitted.

6. Recognize the Document and Case Type

California does not use one universal service packet or one universal Proof of Service form. Document recognition helps the server ask the right operational questions.

The examples above are a routing guide, not a complete statement of every required document or available method. Local court rules, court orders, case-specific forms, and the client’s legal instructions may add requirements.

Civil Summons and Complaint

California Courts describes SUM-100 as a summons telling a defendant that a civil case has started and warning what can happen if a response is not filed. Before dispatch, confirm that the named defendant on the summons matches the assignment and that the client has identified all documents to be delivered.

Do not assume that a PDF titled “Complaint” is the entire service packet. Notices, statements of damages, alternative dispute resolution information, local forms, or other papers may accompany it depending on the case.

Family Law Papers

Family law cases can include a summons, petition, declarations, child custody forms, property documents, and blank response forms. FL-115 tells the court when and where the spouse, domestic partner, or other covered party was served and who performed service.

The server should use the document list provided for the specific case. A divorce packet with minor children may differ from another family law packet.

Small Claims Papers

Small claims papers include a hearing date that directly affects the available service window. California Courts identifies SC-104 as the Proof of Service used to show that papers starting the small claims case were served.

Check whether the defendant is an individual, business, or public entity. The identity of the recipient and applicable timing may differ. If the client provides the papers too late to make the promised attempts, disclose that before accepting the assignment.

Subpoenas

Do not refer to every subpoena as a records subpoena. California uses several subpoena forms for different purposes.

• SUBP-001 orders a nonparty witness to appear and testify at a civil trial or hearing.
• SUBP-002 addresses personal appearance and production of documents, electronically stored information, and things at trial or hearing.
• SUBP-010 addresses production of business records.
• SUBP-015 addresses personal appearance at a deposition.
• SUBP-020 addresses deposition attendance with production of documents and things.

Review the witness or custodian name, appearance or production date, location, issuing attorney or clerk information, attached descriptions, and any consumer or employee notice documents supplied by the client. Do not decide whether statutory notice requirements have been satisfied. Identify the materials and ask the client when the record appears incomplete.

Restraining Order Papers

Protective order matters are deadline-sensitive and form-specific. Review the request, notice of hearing, temporary order, blank response, and any other documents the court or client identifies for service. Confirm the protected and restrained parties carefully, especially when similar names appear in the packet.

California Courts identifies DV-200 as the form used to prove personal service on the restrained person in a domestic violence matter. Civil harassment, elder abuse, gun violence, workplace violence, and school violence proceedings use different form families. Do not select a DV proof merely because the packet contains a restraining order.

7. Find Every Date That Can Affect the Assignment

The service deadline may appear in more than one place, and not every date has the same meaning.

Review for:

• hearing or trial date;
• deposition date;
• document production date;
• subpoena compliance date;
• expiration or return date;
• court-ordered service deadline;
• client’s requested completion date;
• internal first-attempt deadline;
• date by which a Proof of Service must be returned or filed.

Do not assume the client’s requested date is the legal deadline. Ask the client to identify the controlling service deadline when it is not explicit.

Then work backward. The available timeline may need to include:

1. document clarification;
2. printing and packet assembly;
3. the first attempt;
4. additional attempts at different times;
5. address verification or skip tracing;
6. client review of an alternate method;
7. required mailing;
8. proof preparation and signature;
9. court filing when included.

A hearing next week does not necessarily mean there is a full week available for field attempts. The applicable advance-service period may make the assignment urgent today.

The server should not calculate contested legal deadlines independently when the client has not supplied them. The operational duty is to expose the timing issue and obtain clear instructions.

8. Separate Client Instructions From the Legal Method

Client notes often combine a goal with a method:

Please serve today. If the defendant is not there, leave it with anyone over 18.

That instruction may be incomplete. Whether papers can be left with another person depends on the document, recipient, prior attempts, applicable statute, court order, and required follow-up steps.

Separate the instruction into questions:

• Is personal service required?
• Is substituted service potentially available?
• Is prior diligence required?
• Who may receive the papers?
• At what type of location?
• Is a mailing required?
• Who performs and documents the mailing?
• Does a court order authorize another method?

The process server should follow lawful, authorized instructions. When the instruction appears inconsistent with the document or field facts, pause and escalate rather than forcing the event into a preferred result.

Do not preselect the service result before the attempt. The server may expect personal delivery but encounter a person who cannot be identified. The client may anticipate business service but the location may be vacant. The field record must describe what actually occurred.

9. Review the Service Address

An address is part of the case data, not merely a destination for navigation.

Confirm:

• street number and street name;
• directional prefix or suffix;
• apartment, unit, suite, floor, or building;
• city, state, and ZIP code;
• residential or commercial classification;
• business or complex name;
• gate, access, reception, or security instructions;
• known alternate addresses;
• source and date of the address information.

Mapping software can place the pin at a side entrance, leasing office, rear alley, or nearby parcel. Use the written address as the assignment record and verify the physical location when you arrive.

If a client provides a residential address and a workplace, do not decide casually which one to use. Confirm the attempt priority and whether both are authorized. Keep each address and its attempt history separate.

When the unit is missing, ask for it before dispatch if the building cannot reasonably be searched. An incomplete address can consume the entire service window while producing no meaningful attempt.

10. Plan the Proof Before the Attempt

The proof should be prepared from the verified field result, but the proof workflow should be identified during intake.

Ask:

• Which Proof of Service form applies?
• Does the form include space for every document?
• Will an attachment be needed?
• Does each recipient require a separate proof?
• Will the server sign electronically or manually?
• Who reviews the proof before release?
• Who performs any required mailing?
• Who files the proof?
• How will filing acceptance or rejection be monitored?

Basic caption information can be entered in advance when verified. Do not complete the recipient, method, date, time, location, mailing details, or signature based on what is expected to happen.

The form should match the matter. POS-010 is not the universal proof for every California service event. FL-115, SC-104, DV-200, other Judicial Council forms, and form-specific proof sections exist for different proceedings.

A pre-dispatch proof check catches problems early. If the proposed proof contains only three document lines but the packet contains 12 papers, arrange the proper attachment before the server returns from the field. If the proof requires recipient capacity, ensure the attempt workflow prompts the server to record it.

For a deeper quality-control review, see our article about common Proof of Service mistakes.

11. Control Printing and Packet Assembly

Printing is a quality-control stage. A correct digital file can become an incorrect paper packet.

Use a Final Approved File Set

Move the approved documents into one final packet location. Do not print from a mixed download folder containing drafts, prior versions, and proofs.

Confirm Page Counts

Record the expected page count before printing. After printing, compare the physical packet. Watch for printers that skip blank-backed pages, scale oversized exhibits, print only selected pages, or stop when a paper tray empties.

Preserve Readability

Names, case numbers, QR codes, barcodes, signatures, stamps, and fine print should remain legible. Do not shrink a form so aggressively that critical information becomes difficult to read.

Separate Recipients

Use a clear packet for each recipient. If two people at the same address receive different papers, label the packets internally without exposing confidential information on the outside.

Protect the Documents

Use folders or envelopes that protect the pages from rain, dirt, and vehicle damage. Do not leave visible legal papers unattended in a parked vehicle.

Do Not Modify Filed Documents

Do not edit the legal text, remove pages, add names, or correct dates without authorized replacement documents. Operational labels should remain separate from the papers being served unless the client directs otherwise.

12. Manage Revised Documents and Late Changes

Assignments change. The risk comes from allowing only part of the workflow to change.

Imagine that the server receives a revised complaint at 11:00 AM after printing the original packet. The case system is updated, but the physical packet in the vehicle is not. The attempt occurs at 2:00 PM. The final proof is prepared from the new digital list even though the old paper version was delivered.

That single change creates three conflicting records.

Use a controlled revision process:

1. record who supplied the change and when;
2. identify exactly which documents were added, removed, or replaced;
3. pause dispatch when necessary;
4. withdraw or destroy obsolete working copies securely;
5. rebuild the packet;
6. verify the new page count and document inventory;
7. confirm that the server has the current version;
8. update the future proof document list;
9. preserve the change history.

Do not rely on a message that says “use the new one.” Record what “new” means.

13. Know When to Stop and Request Clarification

A good process server does not push every assignment into the field. Some issues should stop dispatch.

Escalation does not need to be dramatic. A short, specific message is usually enough:

Before dispatch, please confirm three items: the order lists Maria L. Torres, the summons lists Maria Torres-Sanchez, and the proposed proof lists Maria Torres. The service address also lacks a unit number. We will hold the assignment until the recipient name and complete address are confirmed.

This is more useful than sending a general message that says the paperwork is confusing.

14. Use a Repeatable Pre-Dispatch Checklist

A checklist should not replace judgment. It should prevent routine information from being forgotten when volume increases.

Case Check

• Correct court and county
• Correct case number
• Caption matches the documents
• Current document version identified
• Filed or issued status reviewed

Recipient Check

• Full legal name confirmed
• Individual or entity classification confirmed
• Recipient capacity identified when applicable
• Aliases and spelling differences documented
• Photo or identifying information attached when available

Packet Check

• Every file opened
• Document inventory created
• Page count checked
• Referenced exhibits included
• Required blank forms included
• Correct packet assigned to each recipient
• Obsolete versions removed

Timing Check

• Hearing, trial, deposition, or production date recorded
• Service deadline confirmed by the client
• First-attempt deadline scheduled
• Time reserved for additional attempts
• Mailing, proof, and filing time considered

Field Check

• Complete service address verified
• Address type identified
• Access instructions recorded
• Known schedule or vehicle information available
• Safety information reviewed
• Attempt priority and reporting timeline confirmed

Completion Check

• Expected service method identified without preselecting the result
• Correct proof form identified
• Required mailing responsibility assigned
• Proof preparation and review responsibility assigned
• Filing responsibility confirmed
• Client update method confirmed

Complete the checklist before route planning. A server who discovers the missing packet at the curb has already lost time.

15. How ProofSer Supports Document Review

Document review becomes harder when intake is spread across email, text messages, shared drives, and handwritten notes.

ProofSer Platform is designed to connect the review with the assignment record.

The case can organize:

• court and case information;
• recipient names and identifying details;
• service addresses and alternate locations;
• uploaded legal documents;
• document lists and packet versions;
• deadlines and priority;
• client instructions and communications;
• field assignments and attempts;
• evidence and Field Notes;
• client updates;
• Proof of Service workflow.

A structured intake can require important fields before dispatch. If the unit number is missing, the deadline is blank, or the recipient classification is unclear, the assignment can be flagged for review instead of silently moving to the field.

AI assistance can help summarize the packet, identify potential inconsistencies, create a document inventory, and draft a clarification request. It should not decide that a particular service method is legally available or change filed documents. The responsible server, operations team, client, and attorney still review the underlying facts and law.

The goal is not to make document review automatic. It is to make the review visible, repeatable, and connected to everything that happens afterward.

Document Review Is the First Attempt at Quality

The first meaningful action in a process serving assignment may occur hours before the server reaches the address.

It occurs when someone notices that the unit is missing.

It occurs when the page count does not match.

It occurs when the hearing date makes the routine timeline impossible.

It occurs when the proposed proof belongs to a different case type.

Every issue caught before dispatch is one less problem that needs to be reconstructed after the attempt.

A professional process server does not need to provide legal advice to add value at intake. The server needs to read carefully, compare sources, preserve changes, ask specific questions, and refuse to replace missing facts with assumptions.

That is how a clean field record begins.

This article is for general informational and educational purposes and is not legal advice. Service requirements depend on the documents, case type, recipient, court orders, local rules, service method, operative law, and circumstances. Process servers should follow authorized instructions and request legal direction from the responsible attorney or client when appropriate.