A Declaration of Due Diligence often reaches the law firm after several unsuccessful service attempts. By that point, the deadline may be closer, the client may be asking for an update, and the legal team may be considering substituted service, posting and mailing, publication, a different address, or another case-specific procedure.

That makes the declaration more than a summary of where a process server went. It may become the factual record counsel uses to evaluate whether the attempts were meaningful, whether the address appears reliable, whether another service method may be available, and what should happen next.

A weak declaration simply counts visits. A useful declaration explains them.

For law firms using recurring process serving for law firms, reviewing due diligence should be a defined operational step. The reviewer should not ask only, “Were there three attempts?” The more important question is whether the record shows a coherent, accurate, and case-appropriate effort.

What a Declaration of Due Diligence Actually Does

A Declaration of Due Diligence is generally used to document efforts to complete a type of service that could not be accomplished despite reasonable efforts. In a common California civil workflow, it records unsuccessful attempts at personal delivery before substituted service of a summons and complaint. It may also help support a request for another method when the governing statute or a court order requires evidence of diligent efforts.

The declaration is not a universal form for every document or proceeding. The required showing depends on the papers, recipient, service method, case type, statute, local procedure, and court order. A declaration prepared for a civil summons should not automatically be reused for a subpoena, restraining order, unlawful detainer matter, family law document, or request for publication.

Its practical role is to preserve field facts in a form the legal team and court can review.

A useful declaration can help answer:

• Where did the server attempt service?
• When did each attempt occur?
• What did the server do at the location?
• What access conditions affected the attempt?
• What objective signs connected the subject to the address?
• Who did the server speak with, and what did that person say?
• Did the timing vary in a meaningful way?
• Did new information change the strategy?
• Why was personal delivery not completed?
• What factual basis exists for the next procedural decision?

The declaration should not decide legal sufficiency for the attorney. It should supply the facts needed for that decision.

A Declaration Is Not the Same as a Proof of Service

The two records may be filed together, but they serve different functions.

The Proof of Service identifies how completed service occurred. A Declaration of Due Diligence documents the efforts that preceded a method requiring diligence or supports a request for another method. California Rule of Court 2.150 states that a declaration of diligence may be attached to a compliant Proof of Service of Summons or inserted as item 5b(5) when the rule’s conditions for a computer-generated or typewritten form are met.

California Courts guidance for substituted service describes the server recording every attempt, including dates, times, and results, signing the declaration under penalty of perjury, and attaching it to the Proof of Service.

A law firm should therefore review the declaration and the final proof as connected records. If one says the process involved three unsuccessful personal attempts followed by substituted service, the other records should support the same sequence.

Understand the Legal Context Before Reviewing the Declaration

A due diligence review should begin with the governing procedure, not with a preferred number of attempts.

California Code of Civil Procedure section 415.20 addresses substituted service of a summons and complaint. The relevant subdivision for many individual recipients provides that if personal delivery cannot be made with reasonable diligence, copies may be left with a qualifying person at a qualifying location and another copy mailed as specified by the statute.

That sequence matters. The declaration may document the personal-delivery efforts. The Proof of Service should document the completed substituted delivery. The mailing record should document the additional mailing step. Treating any one of these as the complete file creates an incomplete operational picture.

Reasonable Diligence Is a Legal Standard

The process server reports what was attempted. The responsible attorney evaluates whether those efforts satisfy the applicable legal standard.

As of September 2026, the current version of section 415.20 uses the phrase “reasonable diligence” for the relevant subdivision but does not state a universal attempt count in its text. A later version becomes operative January 1, 2027. For the relevant subdivision, that version states that reasonable diligence is shown by good-faith personal-delivery attempts on at least three occasions, on three different days, at three different times.

Law firms should be careful with shorthand such as “three attempts always equals due diligence.” Even when a statute specifies a minimum structure, the attempts still need to be made in good faith, at a relevant address, and in a way that reasonably tests whether the person can be found. Other service statutes and proceedings may use different requirements.

Other Procedures May Require a Different Showing

California Code of Civil Procedure section 415.45 addresses posting in an unlawful detainer action after the court is satisfied by affidavit that the party cannot with reasonable diligence be served through other specified methods. Section 415.50 addresses service by publication when the party cannot with reasonable diligence be served in another manner specified in the article and other statutory conditions are met.

Those procedures involve court review and requirements beyond simply attaching a list of attempts. A declaration that may be adequate to explain attempts before substituted service should not automatically be treated as sufficient for publication or posting.

The reviewer should confirm:

• which documents were being served;
• which recipient was being served;
• which statute, rule, or court order applies;
• what method the firm is considering or relying upon;
• whether a specific Judicial Council or local form is required;
• whether the declaration must support a motion, application, or completed proof.

Read the Declaration as a Timeline, Not a Collection of Visits

The fastest way to review a declaration is to read it chronologically.

Each entry should identify the date, exact time, complete address, action taken, material observations, relevant contact, access issue, and result. The sequence should show what the server knew at each stage and whether later attempts responded to earlier information.

Consider this simplified record:

This timeline contains more useful information than three entries that each say “no answer.” It shows varied timing, a changing set of observations, and an increasing factual connection between the subject and address.

Check the Sequence for Internal Logic

A declaration should not describe events in a sequence that could not have occurred.

Potential chronology problems include:

• an attempt date before the assignment was received;
• two attempts at distant locations with impossible travel time between them;
• a mailing date before the substituted delivery;
• a declaration signed before the final listed attempt;
• an alternate address attempt that occurred before the record says the address was discovered;
• a reference to a conversation that is missing from the corresponding field report.

Chronology errors may be clerical, but they should be corrected from the original record rather than explained away after filing.

Evaluate Attempt Quality, Not Only Attempt Count

Attempt count is easy to measure. Attempt quality requires judgment.

If a server visits a residence at 2:00 PM on three weekdays and nobody answers, the fourth visit at 2:00 PM does not automatically add meaningful diligence. It may simply repeat the same test under the same conditions.

A reviewer should examine whether the attempts:

• occurred on different days;
• used meaningfully different time windows;
• accounted for ordinary work and commuting schedules;
• included morning, evening, or weekend timing when appropriate;
• responded to vehicle, occupancy, or schedule information;
• tested another verified location when available;
• addressed access problems identified during earlier visits;
• stopped repeating an address once reliable information indicated it was bad.

Timing Should Have a Reason

Varied timing does not mean random timing. Each attempt should have a reasonable operational purpose.

If the first attempt occurs during business hours and the subject is believed to work outside the home, an evening attempt may test a different availability window. If a vehicle associated with the subject appears early in the morning, a later morning attempt may be useful. If a business receptionist states that the subject works remotely on Fridays, a Friday workplace attempt may not be the best use of the remaining deadline.

The declaration does not need to contain an essay explaining every scheduling decision. The overall history should nevertheless show progression rather than repetition.

Effort Should Be Proportionate to the Information Available

A server cannot use information that was never provided. If the client has a photograph, vehicle description, gate code, employer, alternate address, travel schedule, or known working hours, the assignment should make those details available before they become relevant too late.

The review should therefore consider both field performance and assignment management. An incomplete declaration may reflect weak reporting by the server, but a weak attempt strategy may also begin with incomplete intake or delayed client instructions.

Review the Address and Location Evidence

A precise record of visits to the wrong address is still a problem.

The declaration should identify the full address used for each attempt, including apartment, suite, building, or unit information. If the location changed during the assignment, the record should distinguish the addresses rather than combining every attempt into one list.

Ask What Connects the Subject to the Address

Relevant information may include:

• the address provided in filed documents or client records;
• a current business listing or public record reviewed by the client;
• a name on a directory, mailbox, or suite listing;
• a vehicle linked to the subject;
• a resident, manager, receptionist, or other person confirming a connection;
• prior successful contact at the location;
• recent address research performed through lawful sources.

None of these facts should be overstated. A name on a callbox may support an address connection, but it does not prove the person was present during the attempt. A parked vehicle may be relevant, but it does not independently prove residence.

Recognize Address Warning Signs

The declaration should make material address concerns visible. Examples include:

• the unit number does not exist;
• the property appears vacant or under construction;
• mail or packages are accumulating;
• a leasing office reports that the person is not a current tenant;
• business signage has been removed;
• the suite is a virtual office or commercial mailbox;
• the named company is not listed in the building directory;
• the address belongs to an unrelated person or entity;
• the client supplied a street address without a necessary unit or suite.

Once a credible address problem appears, continuing to incur field fees without reassessment may not improve the record. The next step may be client confirmation, another known location, address verification and skip tracing, or counsel’s evaluation of another lawful method.

Separate Objective Observations From Conclusions

A declaration is stronger when it states what happened without converting limited observations into unsupported conclusions.

Compare the following statements:

The factual versions do not weaken the record. They make it more credible because counsel can see what the conclusion would need to rest upon.

Third-Party Statements Need Context

If the server spoke with another person, the declaration should identify the source as accurately as appropriate and distinguish what the person said from what the server inferred.

Useful details include:

• where the conversation occurred;
• whether the person identified themselves;
• the person’s apparent relationship to the property or business;
• the substance of the statement;
• whether the statement was definite, uncertain, or based on assumption;
• whether the person appeared to have reliable access to the information.

“Property manager stated the subject moved out in June” carries different operational weight from “unidentified neighbor thinks the subject moved.” Both may be recorded. They should not be treated as equivalent.

Do Not Label Every Difficult Assignment as Evasion

An unavailable person may be at work, traveling, caring for family, entering through another part of the property, or simply not present. A locked gate, incorrect unit, outdated address, or irregular schedule can make service difficult without showing intentional avoidance.

Possible evasion should be described through a documented pattern, not inserted as a default explanation. If the pattern becomes more complex, difficult-service coordination may help the team evaluate timing, alternate locations, stakeout parameters, research needs, and the remaining deadline.

Compare the Declaration With the Original Source Record

A declaration should be prepared from contemporaneous field information, not reconstructed from memory days or weeks later.

The law firm’s review should compare the declaration with the available assignment record, including:

• timestamped attempt reports;
• dispatch addresses and routing history;
• GPS or location data when collected;
• lawfully captured site photographs;
• server notes or dictated updates;
• communications with the client;
• address research added during the assignment;
• vehicle and subject descriptions;
• mailing records;
• the final Proof of Service.

A structured assignment history makes this comparison easier because the declaration can be prepared from one connected case record rather than from separate emails, text messages, screenshots, and handwritten notes.

Location Data Supports a Visit, Not Every Conclusion

GPS data may help show that a device associated with the server was at a location at a particular time. A photograph may show the exterior conditions the server encountered. Neither automatically proves that the correct person lived there, that the server knocked, that a conversation occurred exactly as described, or that a particular legal standard was satisfied.

Evidence should be used for what it can establish. Strong documentation combines location information with a specific narrative and consistent case history.

Every Material Attempt Should Be Accounted For

The declaration should not selectively list only the attempts that make the record appear stronger. Omitting an attempt can conceal useful information, including a contradictory address statement, access problem, server error, or timing pattern.

If an attempt was cancelled before the server reached the property, it should not be represented as a field attempt. If a visit was rescheduled, the client-facing status should distinguish scheduling activity from an actual attempt.

Common Red Flags in a Declaration of Due Diligence

Some declarations look complete because they contain several dates. A closer review may reveal that the record does not support the conclusion the firm is being asked to rely upon.

1. Identical Time Windows

Three weekday attempts within the same narrow time window may show repeated effort but little strategic variation. Ask whether a different time was reasonably available and why it was not used.

2. Generic Results

Entries such as “no answer,” “not home,” or “unable to serve” do not explain what the server did, whether access was possible, or whether the address appeared active.

3. Missing Unit or Suite Information

A declaration listing only the street address may hide the fact that the server never had the correct apartment or office suite.

4. Unsupported Evasion Language

Terms such as “hiding,” “avoiding,” or “refused to answer” should be supported by specific observations. A lack of response is not automatically evasion.

5. Contradictions With Field Notes

If the declaration says the gate was open but the attempt report says access was blocked, the discrepancy should be resolved before reliance or filing.

6. Address Concerns With No Escalation

If the first attempt produced reliable information that the subject moved, repeated visits to the same address without reassessment may add cost without improving diligence.

7. No Explanation of What Changed

If the final attempt occurred at a new address or different workplace, the record should make clear how that information entered the assignment.

8. Premature Signature

A declaration signed before the last listed event or before all notes were reviewed may indicate that the document was prepared from anticipated facts rather than completed activity.

9. Wrong Recipient or Case Information

Names, captions, case numbers, and recipient capacity should be checked against the filed documents. A correct attempt history attached to the wrong person’s proof is still a serious documentation problem.

10. The Declaration and POS-010 Do Not Match

The dates, address, recipient, method, and mailing information should tell one consistent story across the declaration and Proof of Service.

What Law Firms Should Do When the Review Finds a Problem

The response should depend on the type of problem and whether the document has already been signed or filed.

If Information Is Missing

Return to the contemporaneous source record. Ask the server for factual clarification while the attempt is still recent. Do not ask the server to add a conclusion that the field facts do not support.

If the Address May Be Wrong

Pause repeated attempts long enough to confirm the location. Review client records, known alternate addresses, employment information, lawful research, and any reliable statements obtained in the field.

If Timing Was Poorly Varied

Determine whether the deadline permits another meaningful attempt. A corrective visit should test a new availability window rather than repeat the same schedule.

If the Declaration Conflicts With Another Record

Resolve the discrepancy before the declaration is signed, delivered, or filed. The correction should reflect what actually happened. Documentation should never be edited to create a cleaner story than the field event supports.

If the Declaration Has Already Been Filed

The responsible attorney should evaluate the significance of the issue and the proper corrective procedure. The answer may depend on whether the problem is clerical or material, whether service has been challenged, and what the court record currently shows.

Operational staff should preserve the original declaration, field notes, communications, and corrected version. A correction should not erase the history of how the issue was identified and resolved.

Declaration of Due Diligence Review Checklist

Case and Document Information

• Does the caption match the filed documents?
• Is the case number correct?
• Is the correct recipient identified?
• Are the documents being served accurately described?
• Does the declaration relate to the correct assignment and method?

Attempt Details

• Is every attempt listed by date and exact time?
• Is the complete address shown for each attempt?
• Are unit, suite, building, and access details included where relevant?
• Does each entry explain what the server actually did?
• Does each entry state a clear result?

Attempt Quality

• Were the attempts made on appropriate days?
• Were the time windows meaningfully varied?
• Did the strategy account for known work or travel schedules?
• Did later attempts respond to information learned earlier?
• Was repetition avoided after a credible address problem appeared?

Address and Occupancy

• What connects the subject to the location?
• Did the address appear active, inactive, vacant, or uncertain?
• Were directories, unit numbers, signage, or public areas checked lawfully?
• Were any alternate addresses identified?
• Were material address concerns escalated to the client?

Observations and Contacts

• Are observations stated objectively?
• Are third-party statements attributed accurately?
• Are assumptions separated from direct facts?
• Is any evasion language supported by a documented pattern?
• Are access problems described specifically?

Consistency and Execution

• Does the declaration match the attempt reports?
• Do timestamps, photographs, and location data support the entries?
• Does the declaration agree with the Proof of Service and mailing record?
• Was it signed by the person with personal knowledge of the attempts?
• Was it signed after the described events occurred?
• Is the declaration made under penalty of perjury when required?
• Are the correct attachments and filing instructions included?

Legal Review

• What statute, rule, court order, or local procedure governs?
• Is the declaration being used for substituted service, publication, posting, or another purpose?
• Does the applicable procedure require court approval?
• Has counsel evaluated whether the facts satisfy the legal standard?
• Have current law and forms been verified for the service date?

How Managed Assignment Oversight Improves Due Diligence

A strong declaration is usually the result of a strong assignment process.

If the process serving company waits until the end of the job to reconstruct the history, small facts are easily lost. The server may remember that nobody answered but not whether the gate was locked, which vehicle was present, what the receptionist said, or how long the server waited.

A managed workflow captures the relevant information after each attempt and reviews it before the next one. That allows the operations team to:

• identify an address problem early;
• vary timing intelligently;
• request a missing unit, gate code, photograph, or schedule from the client;
• compare vehicle and occupancy observations;
• escalate a possible difficult-service pattern;
• monitor the remaining deadline;
• prepare the declaration from verified field data;
• review the declaration against the final Proof of Service.

Proofser coordinates California service assignments through centralized intake, structured attempt reporting, deadline visibility, address escalation, and documentation review. The goal is not to create a longer declaration. It is to create a more reliable record that helps the legal team understand what was tried, what was learned, and what decision remains.

This article is for general informational purposes and is not legal advice. Due diligence and service requirements may depend on the documents, case type, recipient, service method, court orders, local rules, current statutes, and circumstances of the matter.