Reaching the correct address does not necessarily mean that the correct person is standing at the door.

A man opens the door at an address associated with Michael Torres. He looks approximately the right age. When the server asks for Michael, he says, “What is this about?” Is he Michael, a brother, a roommate, or someone who recently moved into the property?

A woman at a workplace says the subject is unavailable. She resembles an older photograph in the case file, but the image is several years old. Is the resemblance sufficient? Should the server ask another question? What if she refuses to give her name?

A person walks toward the vehicle described in the assignment and responds when the server calls the subject’s first name. Does that reaction establish identity, or does it only support further inquiry?

These are ordinary field situations. They are also where a preventable identification mistake can begin.

California Code of Civil Procedure section 415.10 allows a summons and complaint to be served by personal delivery to the person to be served. That short rule creates a practical responsibility: before recording personal service, the server should have a reasonable factual basis for concluding that the person who received the documents is the legally intended recipient.

Identity is also what separates a direct handoff to the named person from delivery to another individual under a different authorized method. New servers should understand the complete distinction between personal service and substituted service before choosing a field result.

The purpose is not to conduct an interrogation. The purpose is to combine reliable assignment information, lawful observation, direct communication, and professional judgment. If the available facts remain materially uncertain, the correct result may be another attempt or an escalation rather than a completed service.

1. Why Identity Matters Before Delivery

Personal service is not simply delivery to a location. It is delivery to the legally appropriate person.

For a civil summons served under Code of Civil Procedure section 415.10, service is complete at the time of personal delivery to the person to be served. California Courts describes personal service as handing the papers to the defendant. The defendant does not need to sign a receipt or agree to accept service.

That makes the identification decision central to the result.

If the server delivers the packet to the wrong person and records personal service on the named defendant, the problem is not limited to a poorly written note. The law firm may rely on the service date. A response deadline may be calculated. A Proof of Service may be filed. The case may move forward based on a factual premise that was never established.

Correcting the problem may require:

• investigating the original event;
• contacting the field server;
• withdrawing or correcting a proof;
• attempting service again;
• recalculating deadlines;
• explaining the discrepancy to the client;
• addressing a challenge to service.

A professional server therefore asks two separate questions:

1. Am I at a location reasonably connected to the subject?
2. Do I have a reasonable factual basis to identify this individual as the person to be served?

The first question supports the second. It does not replace it.

2. Build an Identification File Before the Attempt

Strong identification starts before the server reaches the address.

The assignment should provide enough information to distinguish the intended person from other people who may live, work, or visit at the location. Depending on the matter and what the client lawfully possesses, useful information may include:

• the exact legal name shown on the documents;
• known aliases, former names, or common spelling variations;
• an approximate age or date-of-birth range;
• a recent, reliable photograph;
• a physical description;
• a residential address and unit number;
• a workplace, job title, or department;
• known vehicle make, model, color, or license information;
• lawfully obtained schedule information;
• prior attempt notes and descriptions;
• the relationship of other known occupants;
• special safety or access instructions.

More data is not automatically better. The information should be relevant, current, lawfully obtained, and handled securely. A server does not need unrelated financial, medical, or family information simply to identify a recipient.

Before leaving, the server should review the legal documents before service and compare the named recipient against the assignment profile. If the summons identifies “Alejandro J. Martinez” but the work order says only “Alex Martin,” that inconsistency should be resolved before the field visit.

The operations team should also clarify whether the target is:

• an individual defendant;
• a person sued under a fictitious name;
• an officer or agent receiving papers for an entity;
• a parent or guardian in a permitted capacity;
• another person authorized or designated by law.

The human being who physically receives the documents and the legal party being served are not always described in the same way. The server needs to know the required capacity before trying to establish it.

3. Start With Direct Verbal Confirmation

The simplest identification method is often the strongest: ask the person.

A server might say:

“Hello, are you Jordan Lee?”

If the person responds, “Yes, I am Jordan,” the server has direct confirmation. The note should preserve the wording and the context.

Direct questions can be adapted to the setting:

• “May I speak with Jordan Lee?”
• “Are you Jordan Lee?”
• “I am looking for Jordan Lee. Is that you?”
• “Does Jordan Lee work in this office?”

Avoid unnecessarily revealing the case or allegations to an unidentified person. The initial question can be limited to the name. Once identity is reasonably established, the server can state that the documents are legal papers for the recipient.

Listen to the Exact Response

Not every response is confirmation.

The server should not rewrite “Who is asking?” as “subject confirmed identity.”

Do Not Create a Trap That Produces an Ambiguous Answer

A leading or confusing question can produce a weak record.

For example, “You are Chris, right?” may receive a distracted “yeah” from someone who is responding to the conversation rather than the name. A clearer question and a brief follow-up may reduce ambiguity.

The goal is not to trick a person into saying a name. The goal is to obtain a reliable basis for identification.

4. Use Photographs as Evidence, Not Automatic Proof

A current photograph can be extremely useful, especially when the person refuses to give their name. It can also create false confidence.

Before relying on an image, consider:

• when the photograph was taken;
• where it came from;
• whether the source reliably connected it to the subject;
• whether the image has been edited, filtered, or cropped;
• whether age, facial hair, hairstyle, weight, or glasses may have changed;
• whether the photograph could depict a relative with similar features;
• whether the image shows enough of the face for a meaningful comparison.

A client-provided driver’s license image may carry different weight from a profile picture found under a similar name. A current professional headshot may be more useful than a social image from ten years earlier.

When the server uses a photograph, the field note should describe the role of the photograph without overstating certainty.

Useful:

The adult male who answered was consistent in facial features, approximate age, and hairline with the client-provided photograph dated March 2026. He also verbally confirmed that he was Marcus Chen.

Weak:

Looked like him.

A photograph is strongest when it confirms other facts. It should not cause the server to ignore meaningful differences.

5. Use Assignment Details Carefully

Address, vehicle, schedule, and occupational information can help connect a person to the assignment. These details are supporting evidence, not automatic identification.

Address Connection

A person at the subject’s residence may be the subject, a relative, roommate, guest, contractor, neighbor, new tenant, or delivery worker. Presence at the correct address increases relevance but does not establish a name.

Vehicle Information

A known vehicle in the driveway may support the conclusion that the subject is present. It does not prove that the person who answers the door owns or drives it. Vehicles are shared, sold, borrowed, and left with family members.

Schedule Information

If reliable information says the subject returns from work at 6:30 PM and an individual matching the photograph enters the residence at 6:38 PM, the timing supports identification. It remains one part of the total record.

Knowledge of Private Facts

A person may know the subject’s workplace, family, or schedule without being the subject. Do not treat familiarity as identity.

Possession of Mail or Property

Picking up mail from a box, unlocking a door, or driving a listed vehicle may be relevant observations. They should be described exactly. “Unlocked the front door with a key” is stronger than “obviously lives there,” but it still does not state the person’s name.

6. Evaluate Third-Party Identification

Sometimes another person identifies the subject.

Examples include:

• a receptionist says, “That is Jordan Lee coming down the hallway”;
• a spouse calls the subject by name at the door;
• a building manager introduces the resident;
• a coworker directs the server to the named employee;
• a security officer verifies the person against a workplace directory.

The reliability of third-party identification depends on the source and circumstances.

Consider:

• whether the third party identified themselves;
• their relationship to the subject;
• how they know the subject;
• whether the statement was direct or speculative;
• whether the person being identified responded to the name;
• whether other assignment facts match.

A receptionist who works with the subject daily may provide a meaningful identification. An unidentified neighbor saying, “I think that is him,” provides weaker information.

The note should attribute the statement:

The front desk employee, who identified herself as Maria and stated that she works with the subject, pointed to the man approaching the reception area and said, “That is David Kim.” The man then confirmed, “Yes, I am David.”

Do not convert a third party’s uncertain statement into the server’s certain conclusion.

7. Identifying Someone at a Workplace

Workplaces create both useful verification opportunities and additional privacy concerns.

A server may encounter security, reception, human resources, coworkers, supervisors, customers, or shared-office staff before reaching the subject.

A professional workplace approach should:

• use the subject’s name without announcing unnecessary case details;
• ask whether the person is available;
• avoid disrupting business operations;
• follow lawful access and security procedures;
• record who provided information and in what capacity;
• avoid implying that reception must disclose private employee data;
• move the interaction away from customers when practical.

Suppose a receptionist calls “Anthony” and a person comes to the front desk. The fact that the receptionist summoned him supports identification, but the server can still ask, “Are you Anthony Rivera?” A direct confirmation closes a gap that may otherwise become important later.

If the person says, “There is no Anthony here,” while wearing a company badge that is turned away, the server should not grab the badge, block the person, or create a confrontation. The server can document the response, compare lawful observations with the assignment, and escalate if uncertainty remains.

A workplace is not permission to disclose allegations or discuss the lawsuit with coworkers. Ask only for what is reasonably necessary to locate and identify the recipient.

8. Do Not Confuse an Individual With a Business Recipient

Identification becomes more complex when the defendant is an entity.

The process server may physically hand the documents to a named individual, but the legal service is being completed on behalf of a corporation, limited liability company, partnership, association, or public entity.

The assignment should distinguish:

• the legal entity being served;
• the person physically receiving the papers;
• the person’s title or role;
• the statutory or authorized capacity relied upon;
• the office or business location;
• whether the service is personal on an agent or uses another permitted method.

If the work order says “Serve Apex Holdings LLC through registered agent Taylor Reed,” finding a person named Taylor Reed is not enough if the server has reached a different person with the same name. Conversely, reaching the correct registered agent requires recording both the individual’s identity and the capacity in which the papers were delivered.

The summons itself may include a “Notice to the Person Served” section indicating whether the individual is served personally or on behalf of another party. The service record should match the assignment and applicable law.

When the legal recipient or capacity is unclear, the server should pause. Do not select “authorized agent” because it appears convenient on a proof form.

9. When the Person Refuses to Identify or Accept

People do not have to cooperate with the process server. They may decline to state their name, show identification, open the door fully, or take the documents by hand.

A refusal does not automatically prevent personal service. California Courts explains that a defendant does not need to sign anything and that if the defendant refuses to take the papers, the server may leave them next to the defendant.

The critical questions remain:

1. Did the server have a reliable basis to identify the person?
2. Did the server clearly communicate that the documents were legal papers for that person?
3. Were the papers placed in a location sufficiently connected to the identified person under the applicable law?
4. Can the server accurately describe the entire event?

Refusal After Direct Confirmation

A person says, “Yes, I am Renee Walker,” but refuses the packet. The server identifies the documents and places them immediately beside her as she stands at the doorway.

This creates a substantially stronger identity record than a person who never confirms their name.

Refusal With Independent Identification

A person refuses to state their name, but closely matches a current reliable photograph, exits the exact residence with a spouse who calls them by the subject’s full name, and unlocks the vehicle identified in the assignment.

The combined facts may support identification. The note should state each fact, not simply “subject was evasive.”

Refusal With Insufficient Facts

An unknown person behind a partially closed door says, “Go away,” and the server cannot see their face or connect them to the subject.

That is not automatically a completed personal service. Leaving papers at the door and later stating that the defendant refused service may create an unsupported record.

The difference is not attitude. The difference is identification.

10. Names, Aliases, and Common Name Problems

Names in legal documents, databases, workplaces, and everyday life do not always match perfectly.

Common issues include:

• nicknames, such as Alex for Alejandro or Liz for Elizabeth;
• married and former names;
• hyphenated or compound surnames;
• transliterated names with several English spellings;
• middle names used as first names;
• suffixes such as Jr., Sr., II, or III;
• parent and adult child sharing the same name;
• twins or close relatives who resemble each other;
• common names shared by unrelated people;
• errors in the client’s intake record.

A process server should not decide that two names are legally interchangeable without support.

If the person says, “I am Alex Martinez, but Alejandro Martinez is my father,” the server has learned that a same-name or similar-name problem may exist. The next step is clarification, not immediate delivery based on the first name.

Useful follow-up questions may include:

• “Is your full legal name Alejandro J. Martinez?”
• “Are you the Alejandro Martinez who works in the accounting department?”
• “Is there another person with that name at this address?”

Questions should remain narrow and relevant. The server does not need to collect a full biography.

11. What GPS and Photographs Can and Cannot Prove

Technology can strengthen an attempt record, but it does not answer every identification question.

GPS Can Support Location

GPS or equivalent location data can support that the server’s device was near the service address at a particular time. It does not prove that the server reached the correct door, spoke with the defendant, or delivered the documents.

A Site Photograph Can Support the Attempt Location

A photograph of the residence or business entrance can help establish where the attempt occurred. It does not prove who answered.

A Client Photograph Can Support Recipient Identification

A reliable subject photograph can support visual comparison. It does not replace the server’s assessment of age, image quality, changed appearance, and contradictory facts.

Do Not Photograph People Unnecessarily

The 2027 AB 747 requirements discussed in California Judicial Council implementation materials focus on photographs of the site of covered completed or attempted summons service. The requirement should not be described as a universal instruction to photograph the recipient’s face.

Photography should comply with applicable law, safety considerations, client policy, and the actual documentation requirement. A server should not escalate a tense interaction merely to obtain a portrait of the recipient.

AB 747 Does Not Eliminate the Identity Question

Beginning January 1, 2027, covered service records will contain more location, time, and photographic evidence. That may help verify that an attempt occurred where and when reported. The server must still explain how the person was identified and how delivery occurred.

A stamped photograph of the correct door and a wrong-person handoff can still be a wrong-person handoff.

12. Common Identification Mistakes

Assuming the Person Who Answers Is the Subject

The server reaches the correct address and sees someone of the expected gender and approximate age. No name is confirmed. The server delivers the papers and marks personal service.

Problem: Address, gender, and age range may fit multiple occupants.

Using an Old or Low-Quality Photograph as the Only Basis

The image is eight years old, heavily filtered, or copied from an uncertain social profile.

Problem: The source and current resemblance may be too weak to support certainty.

Treating a Reaction to a Name as Confirmation

The server calls “Michael,” and a person looks over.

Problem: The person may know Michael, share the name, or simply react to a voice.

Confusing a Relative With the Subject

A father and adult son share a name and resemble each other.

Problem: A photo and name may match both. Suffix, age, work, or other distinguishing facts matter.

Trusting a Uniform or Desk Location as Legal Capacity

A person sits at reception or wears a company badge.

Problem: This may show employment, but not necessarily the identity or capacity required for the assignment.

Changing the Note After the Fact

The first note says “unidentified male.” Later, after someone asks whether the subject was served, the description changes to “defendant refused.”

Problem: The later conclusion is not supported by the original observation.

Using “Evasive” as a Substitute for Identification

A person refuses to answer questions and closes the door.

Problem: Uncooperative behavior does not prove the person’s name.

Letting the Deadline Lower the Standard

The deadline expires that evening, so the server decides that a partial match is “close enough.”

Problem: Urgency does not transform weak facts into reliable identification.

13. Field Scenarios and Better Decisions

Scenario 1: Clear Verbal and Visual Confirmation

The server asks for Priya Shah. The woman answers, “I am Priya.” She matches a current client photograph. The address and vehicle also match the assignment.

Assessment: Multiple consistent facts support personal identification.

Record: Quote the confirmation, note the photograph match, record the location, and describe delivery.

Scenario 2: A Person Says the Subject Is Not Home

An adult male answers at the subject’s residence and says, “Daniel is not home.” He resembles the client photograph of Daniel but refuses to give his own name.

Assessment: The statement conflicts with the visual comparison. Neither should be ignored.

Better response: Ask a clear follow-up question, observe without confrontation, document the exact statement and photograph comparison, and avoid claiming personal service unless the total facts support identification.

Scenario 3: Same Name, Different Generation

A man confirms he is Robert Allen Davis. The assignment is for Robert Allen Davis Jr., age 31. The person at the door appears approximately 60 and says his son has the same name.

Assessment: The name alone is insufficient. The suffix and age information distinguish the subjects.

Better response: Do not serve the father personally as the son. Record the clarification and ask whether the son lives there, without assuming another method is authorized.

Scenario 4: Workplace Reception Calls the Subject

The receptionist pages “Monica Alvarez.” A woman comes to the lobby. The receptionist addresses her as Monica, and she confirms her full name when asked.

Assessment: Direct confirmation supported by a workplace introduction provides a strong basis.

Scenario 5: Unidentified Person Behind a Security Camera

A voice through a doorbell camera says the subject is not available. The server cannot see the person and has no independent voice reference.

Assessment: The conversation may show that someone monitors the property. It does not identify the speaker.

Better response: Record the exact exchange and treat the result as an unsuccessful attempt unless another authorized method is completed.

Scenario 6: Subject Recognized in a Public Area

The server sees a person in the apartment parking area who closely matches a current photograph. The person walks to the exact unit and unlocks the door. When asked, the person confirms the full name.

Assessment: Visual match, connection to the unit, and verbal confirmation align.

Scenario 7: Third Party Makes an Uncertain Identification

A neighbor points toward a person and says, “That might be the guy you want.” The person does not respond to the subject’s name and walks away.

Assessment: The statement is speculative and the subject remains unidentified.

Scenario 8: Person Admits the Name After Delivery

The server has strong visual and address-based evidence, identifies the documents, and leaves them beside a refusing individual. The individual then says, “You people keep bothering me, but yes, I am Elena.”

Assessment: The later direct confirmation is relevant. The note should preserve the actual order of events and exact words.

Scenario 9: Photograph Does Not Match

A person at the correct address gives the subject’s full name but looks materially different from a recent verified photograph. The expected subject is 45; the person appears approximately 20.

Assessment: The contradiction requires clarification. The person may be using the same name, joking, confused, or receiving for someone else.

Better response: Ask a narrow follow-up and do not disregard the inconsistency merely because the person said the name.

14. How to Document the Identification Basis

A completed personal-service note should let a reviewer understand why the server believed this was the correct person.

Record:

• the date and exact time;
• the complete location;
• where the interaction occurred;
• the exact name used by the server;
• the person’s exact identity response;
• any reliable photograph comparison;
• the source and approximate currency of the photograph when known;
• third-party identification and the source’s relationship or role;
• relevant vehicle, workplace, badge, unit, or schedule facts;
• material inconsistencies and how they were resolved;
• what the server said about the documents;
• how and where the papers were delivered;
• the recipient’s refusal or other response;
• any required site photograph, timestamp, or location data.

Use complete process server field notes rather than labels that hide uncertainty.

Weak Note

Served defendant at home. He tried to avoid.

Useful Note

At 6:47 PM, I contacted an adult male on the front walkway of the listed residence. I asked, “Are you Kevin Brooks?” He replied, “Yes, but I am not taking anything.” His facial features, approximate age, beard, and eyeglasses were consistent with the client-provided photograph dated July 2026. I stated that I was delivering legal documents for Kevin Brooks. When he refused to take the packet, I placed it on the walkway immediately beside him and stated that the documents had been served. He looked at the packet and entered the residence.

The useful note gives the reviewer the evidence. It does not rely on the word “evasive” to fill the gaps.

Preserve Contradictions

If the person matched a photograph but denied the name, record both facts. If a receptionist identified the person but the person denied working there, record both statements. A contradiction is not a reason to simplify the record. It is a reason to make the record more precise.

15. Review the Proof Before Signing

The Proof of Service should reflect the completed event and the correct recipient.

For a civil summons, POS-010 records the party served, service method, location, date, time, documents, and server information. POS-020 is used for personal service of certain civil papers other than a summons. Other proceedings use different forms.

Before signing, compare the proof with:

• the caption and exact party name;
• the work order;
• the documents in the delivered packet;
• the contemporaneous field note;
• the identification facts;
• the service date, time, and address;
• the method actually completed;
• the capacity selected on the form;
• the server declaration.

Do not sign a proof that says the named defendant was personally served if the original note identifies only an unknown adult. Do not add a recipient name because the client later says the person “must have been” the defendant.

If new reliable information resolves an uncertainty, the file should preserve how and when it was resolved. The proof should describe the actual service event, not a rewritten version created for convenience.

Avoiding these inconsistencies is part of preventing common Proof of Service mistakes.

16. When to Stop and Escalate

A new process server may feel pressure to produce a completed result. Professional judgment sometimes means not completing service.

Stop and request review when:

• the person refuses their name and no reliable independent identification exists;
• the photograph materially conflicts with the person present;
• two occupants share the same name;
• the suffix, age, or other distinguishing detail does not match;
• the assignment name conflicts with the court documents;
• the person appears to be a relative rather than the subject;
• a third party provides only speculative identification;
• the address appears wrong or outdated;
• the server is unsure whether the recipient is being served individually or for an entity;
• the required legal capacity cannot be established;
• the person appears unable to understand the interaction;
• safety conditions make further questioning unreasonable;
• the available service method is unclear.

An escalation should be specific:

Identity not confirmed. Adult male at address resembles the 2019 photograph but appears substantially younger than the subject’s listed age. He denied being the subject and stated that the subject is his father. Please confirm suffix, current photograph, and whether another address is available.

This gives the operations team a usable question. “Could not serve” does not.

17. Personal Service Identification Checklist

Before the Attempt

• Confirm the exact name on the documents.
• Confirm whether service is on an individual or on behalf of an entity.
• Review aliases, suffixes, and spelling variations.
• Review the most current reliable photograph.
• Review approximate age and relevant physical details.
• Confirm the exact residence, unit, workplace, or department.
• Review known vehicles and schedules.
• Read prior attempt notes.
• Confirm the authorized method and correct proof form.

During Contact

• Ask for the person by name.
• Listen to the exact response.
• Ask a clear follow-up if the response is ambiguous.
• Compare appearance with a reliable photo when available.
• Consider address, vehicle, workplace, and schedule facts as support.
• Attribute third-party identification to its source.
• Do not reveal unnecessary case information.
• Do not argue, block, touch, or threaten the person.
• Leave if safety deteriorates.

Before Delivery

• Ask whether the facts consistently identify the person.
• Resolve material contradictions when safely possible.
• Confirm that the complete packet is for this recipient.
• Know whether the event is personal service or another method.
• Do not let a deadline replace missing identity facts.

After Delivery

• Record the note immediately in a safe location.
• Quote the identity confirmation or refusal.
• Describe each independent identification fact.
• Describe the physical delivery precisely.
• Connect required photographs and GPS data to the attempt.
• Compare the field record with the Proof of Service.
• Escalate any inconsistency before the proof is signed or filed.

18. How Managed Operations Reduce Wrong-Person Service

Wrong-person service is rarely caused by one field question alone. It often begins earlier.

The intake contains only a first and last name. The photograph is not dated. The suffix is missing. Previous notes are stored in an email thread the current server cannot see. The deadline is close. The server reaches someone who approximately matches the description and feels pressure to complete the assignment.

A managed workflow reduces that pressure by connecting the information before the attempt.

A well-managed assignment should provide:

• a verified recipient name from the actual documents;
• clearly labeled aliases and distinguishing details;
• current photographs with a known source when available;
• all prior attempts in chronological order;
• one place for address, vehicle, workplace, and schedule data;
• a defined escalation path for uncertain identity;
• structured field-note fields that preserve the identification basis;
• quality review before the proof is released.

This is the operational difference between recording “served” and managing the service event.

The field server still makes the real-world observation. The operations system ensures that the server has the right information, that uncertainty is visible, and that the final documentation does not become more certain than the original facts.

Personal service should be simple when the right person is clearly identified and receives the papers. When the facts are not clear, the process should slow down.

The professional standard is not to complete every assignment on the first contact. It is to complete the correct service on the correct person and preserve a record that explains why the identification was reliable.

This article is for general educational and operational information and is not legal advice. Identification and service requirements depend on the documents, case type, recipient, service method, statute, court order, service date, local procedure, and facts. Process servers should follow lawful instructions and escalate legal questions to the responsible attorney or requesting party.