Three Meanings of “Service Completed”

The most useful way to prevent premature closure is to stop using one status for three different concepts.

This framework prevents a field notification from creating the wrong downstream assumption.

For example, a process server may validly leave a summons and complaint with an appropriate substitute recipient. That event matters, but under an applicable substituted-service procedure the mailing may remain incomplete. The assignment should not move directly from “served” to “proof ready” if the proof must include facts from both events.

Similarly, a provider may deliver a correct signed proof to the law firm. If filing was not included in the order, the provider’s work may be complete even though the court has not received the document. The status should make that distinction explicit.

Why the Service Method Controls What Happens Next

There is no universal post-service workflow for every document.

The required next step may depend on:

• whether the papers include a summons and complaint;
• whether service was personal, substituted, by mail, electronic, posted, published, or performed under a court order;
• whether the recipient is an individual, corporation, partnership, public entity, minor, conservatee, witness, attorney, or another category;
• whether the case is civil, family, small claims, unlawful detainer, restraining order, probate, or another matter;
• whether service occurred inside or outside California;
• whether the documents, statute, rule, local practice, or order require a specific proof form or supporting attachment;
• whether a follow-up mailing, acknowledgment, witness fee, original, affidavit, publication record, or filing step is required.

The process serving company should accurately document what happened and identify the operational steps within its scope. Counsel should determine whether the method was legally permitted, when service became complete, and which litigation deadline follows.

That division of responsibility should be clear. A provider should not silently make legal decisions that belong to the attorney. It also should not close an assignment while an obvious operational component remains unfinished.

Personal Service: Delivery May Complete the Service Event

California Code of Civil Procedure section 415.10 provides that personal service of a summons is deemed complete at the time of personal delivery.

That makes the field delivery and legal completion event closely aligned. The provider may still need to complete several operational tasks:

• confirm the identity of the person served;
• finalize the date, exact time, and complete location;
• confirm the documents delivered;
• record how identity was established;
• document a refusal or unusual delivery when relevant;
• prepare the correct Proof of Service;
• review and obtain the server’s signature;
• deliver or file the proof according to the assignment;
• return any required originals or supporting materials.

The phrase “personal service completed” should therefore communicate the field and method result, not imply that the proof has already been filed.

Business Personal Service Requires Capacity Review

When the named party is a business or organization, the operations team should distinguish the entity being served from the person who physically received the papers. The final record may need the individual’s name, title, and capacity.

A delivery to a person at a corporate office does not become service on the corporation merely because the individual accepted an envelope. The legal basis depends on the applicable law and actual facts. The proof should describe the real recipient and supported capacity without upgrading a receptionist, office employee, or mailroom worker into an authorized agent by assumption.

Substituted Service: Field Delivery Is Only Part of the Workflow

Substituted service is the clearest example of why a “served” notification can be premature.

Under the version of California Code of Civil Procedure section 415.20 operative during 2026, specified substituted service of a summons includes leaving a copy with a qualifying person in the circumstances described by the statute and thereafter mailing another copy to the person being served at the place where the papers were left.

For service under the relevant provisions of that section, service is generally deemed complete on the tenth day after the mailing.

The workflow may therefore involve:

1. prior personal-service attempts when reasonable diligence is required;
2. the substituted delivery event;
3. documentation of the substitute recipient;
4. the required mailing;
5. calculation of the statutory completion event by counsel;
6. Proof of Service preparation using both delivery and mailing facts;
7. filing and downstream deadline review.

If the provider closes the assignment immediately after step two, the remaining work becomes vulnerable to omission.

What the Field Record Should Preserve

The server’s report should capture the person who received the papers, the person’s apparent relationship or role, the location, the date and time, what the person stated, how the server described the nature of the papers, and other facts required by the applicable procedure and form.

The operations team should not reconstruct those details days later from memory. They should be collected promptly enough to support the mailing and proof workflow.

Mail With Notice and Acknowledgment Has a Different Completion Event

Mailing papers does not always mean service is complete.

California Code of Civil Procedure section 415.30 provides a procedure for summons service by mail with notice and acknowledgment. Under that section, service is deemed complete on the date the written acknowledgment of receipt is executed, if the acknowledgment is returned to the sender.

The assignment should distinguish:

• documents mailed;
• acknowledgment awaiting return;
• acknowledgment received and reviewed;
• service completion date identified;
• proof package prepared;
• proof filing responsibility confirmed.

If the acknowledgment is not returned, the next step may involve another authorized service method and attorney direction. The provider should not change “mailed” to “served” merely because a delivery carrier reports that the envelope reached the address.

Other Service Methods and Court Orders Require Their Own Closeout Rules

Posting, publication, out-of-state service, electronic service, service on a public entity, subpoena service, and court-ordered alternative service can have different elements and proof requirements.

For example:

• a publication assignment may require publisher affidavits and proof of a mailing when applicable;
• posting may be paired with a mailing and a completion rule specified by statute or order;
• out-of-state mail service may require evidence of actual delivery;
• electronic service must be permitted, required, consented to, or ordered under the authority applicable to the matter;
• a subpoena may involve witness fees, original handling, document-specific proof, or personal-delivery requirements;
• a court order may define the method, recipients, timing, supporting evidence, and proof format.

A provider handling Proof of Electronic Service should not reuse the closeout logic for a residential summons. Likewise, a process server should not convert an unsuccessful personal attempt into another method without attorney authorization and a lawful basis.

The operational rule is simple: the closeout checklist should be based on the actual documents and method, not on a universal “served” template.

Review the Field Result Before Closing the Assignment

A successful field report should answer enough questions to support the next stage.

The operations team should verify:

• which person or entity was intended to be served;
• who physically received the documents;
• how identity was confirmed;
• the recipient’s title, relationship, or capacity when relevant;
• the exact date and time;
• the complete address, unit, suite, or location;
• which documents were delivered;
• what method the facts support;
• whether any refusal, drop service, security interaction, or unusual circumstance needs explanation;
• whether another required step remains open.

The review should happen before a client-facing completion notice creates reliance.

Do Not Force Ambiguous Facts Into a Successful Status

Sometimes the server has delivered papers but the legal characterization remains uncertain. The person may have refused to identify themselves. A receptionist may have accepted documents while denying authority. The client may have named a corporation, but the location belongs to a different legal entity.

The provider should report the facts and escalate the issue. It should not select a favorable method simply to close the assignment. Counsel can then determine whether the event should be relied upon, whether a corrected or additional service is needed, or whether another action is appropriate.

Complete and Document Every Required Mailing

When mailing is part of the selected method, it should exist as a separate tracked task.

The mailing record should generally identify:

• the person or entity to whom the envelope was addressed;
• the complete mailing address;
• the documents included;
• the mailing date;
• the location from which the mailing occurred;
• the person who performed the mailing;
• the mail class or tracking information when applicable;
• the connection between the mailing and the field delivery or court order.

The assignment should remain open until the mailing is completed or counsel changes the instruction. A field server should not assume office staff will mail. Office staff should not assume the field server already did.

Where the legal completion date depends on mailing, the case update should state the delivery date, mailing date, and that counsel should confirm the operative completion date and resulting deadline.

A Mailing Timestamp Is Not a Legal Conclusion

The operations team records when the mailing occurred. Counsel applies the governing rule to determine when service is complete and what deadline follows. Keeping those roles separate reduces the risk of a vendor making an unsupported legal calculation.

Prepare the Correct Proof of Service From Verified Facts

The Proof of Service should document the completed event. It should not predict one.

Some basic information may be entered in advance, including the court, case number, caption, and anticipated documents. The final recipient, method, date, time, location, mailing details, and declaration must reflect what actually happened.

California Code of Civil Procedure section 417.10 requires proof of specified summons service to show the time, place, manner, and supporting facts. The proof may also need the name of the person to whom the summons and complaint were delivered and that person’s title or capacity when appropriate.

Proof preparation should confirm:

• the correct form for the documents and matter;
• the current case caption and number;
• the exact party served;
• all documents in the delivered packet;
• the method supported by the field record;
• the recipient’s name and capacity;
• the date, time, and place;
• the mailing event when required;
• server information and registration details when requested or required;
• the declaration and signature;
• required attachments or diligence information;
• the agreed delivery and filing instruction.

Different case types and documents may use different Judicial Council forms. POS-010 is not a universal proof for every civil, family, small claims, restraining order, subpoena, or post-appearance service event.

Compare the Proof With the Source Record

Proof review is not merely checking spelling. It is a consistency test across the entire assignment.

The reviewer should compare:

1. the documents and caption submitted by the law firm;
2. the final packet delivered to the field server;
3. the server’s contemporaneous field notes;
4. the recipient and capacity information;
5. the mailing or acknowledgment record;
6. the draft Proof of Service;
7. the filing instruction.

Common conflicts include:

• the proof states personal service while the notes describe delivery to another person;
• the proof lists a residence while service occurred at a workplace;
• the recipient name appears only on the proof and not in the field notes;
• the proof identifies a registered agent while the notes identify a receptionist;
• the service time or address differs from the field record;
• the proof lists documents that were not in the final packet;
• the mailing date is missing or inconsistent;
• multiple parties are combined when separate documentation is needed.

A discrepancy does not automatically determine the validity of service. It does mean the proof should not be released or filed until the facts are clarified.

Resolve Proof Discrepancies and Corrections Before Reliance

When a potential error appears, the correction process should return to the original event.

The team may review:

• the server’s contemporaneous notes;
• timestamp and location record;
• recipient description;
• communications from the field;
• mailing documentation;
• the packet transmitted to the server;
• client instructions and later changes.

The proof should be corrected to reflect what happened. It should never be edited to describe an event that did not occur or a capacity that was not established.

If the issue may affect the method, recipient, completion, or legal sufficiency, the provider should present the facts to the responsible attorney. The attorney can determine whether a corrected proof, supplemental declaration, re-service, court application, or another action is appropriate.

Track Why Corrections Occur

A recurring correction rate is an operations signal. The cause may be incomplete intake, weak field notes, manual re-entry, incorrect form selection, missing mailing data, or inadequate proof review. Categorizing the reason allows the firm and provider to fix the workflow rather than repeatedly fixing individual PDFs.

Give the Law Firm a Useful Completion Update

“Served” is a result, not a complete client communication.

A useful update should identify:

• the party or entity served;
• the person who received the documents;
• the recipient’s relevant capacity or relationship;
• the date, exact time, and location;
• the method reflected by the field event;
• whether a required mailing or acknowledgment remains open;
• whether the Proof of Service is being prepared or reviewed;
• the expected proof-delivery timing;
• whether filing is included;
• any fact requiring attorney review.

When appropriate, the update should use staged language:

Field delivery completed on September 8 at 6:42 PM. Documents were left with the identified office manager at the service address. The required follow-up mailing is scheduled for September 9. Proof preparation will begin after the mailing details are recorded. Court filing is not included in this assignment.

This is more useful than “served” because it tells the paralegal what happened and what remains.

Confirm Proof Filing Responsibility and Court Acceptance

Proof preparation, proof delivery, court submission, and court acceptance are four separate milestones.

California Code of Civil Procedure section 417.30 provides that after summons service, proof as provided by sections 417.10 or 417.20 shall be filed unless the defendant has previously made a general appearance.

The case-specific filing procedure and timing should be confirmed by counsel. Operationally, the assignment should state who is responsible.

If the Law Firm Files

The provider should deliver the signed proof in the agreed format and say clearly that filing is not included. The law firm should record receipt, review the proof, submit it through the correct filing channel, monitor acceptance, and retain the accepted or court-stamped copy.

If the Process Serving Provider Files

The provider should know:

• which court and case the proof belongs to;
• whether attorney approval is required before filing;
• the filing target;
• which filing fees are authorized;
• how to report submission;
• how to monitor acceptance or rejection;
• which clerical corrections may be handled operationally;
• which substantive issue must return to counsel;
• how the final accepted copy will be delivered.

A filing rejection should reopen the relevant task. The assignment should not remain “closed” while the proof is outside the court record.

Protect Deadline Calculations After Service of Process

Legal deadlines may depend on the document, method, service-completion rule, location, court order, and applicable statute or rule. A vendor’s “served” timestamp should not become the firm’s deadline calculation without review.

The risk is especially clear when:

• field delivery and legal completion occur on different dates;
• an acknowledgment must be executed and returned;
• service occurs outside California;
• a court order defines a special completion event;
• mailing or electronic service affects timing;
• the recipient or capacity is under review;
• multiple parties were served on different dates;
• a correction changes a material service fact.

The provider should supply accurate event data. The responsible attorney should determine the operative legal completion date and calculate responsive, hearing, default, objection, or other case deadlines.

For a rush service assignment, this review should happen quickly. Urgency does not eliminate the distinction between delivery and completion.

Return Originals, Fees, and Supporting Records

Some assignments involve physical or supporting items beyond the service packet.

The closeout checklist may need to address:

• an original subpoena or court-issued document;
• unused or delivered witness fees;
• original acknowledgments or return receipts;
• publisher affidavits;
• mailing receipts or tracking records;
• court-stamped proofs;
• declarations of diligence;
• permitted photographs or location records;
• client-provided photographs, identifiers, or confidential materials;
• unused document packets.

The workflow should state whether the item will be mailed, couriered, uploaded, retained, or securely destroyed. A completed assignment should not leave an original document in a field server’s vehicle or an untracked envelope in an office tray.

Close Billing, Records, and Retention Tasks

Operational closure also includes administrative accuracy.

The final invoice should match the agreed scope and identify the matter, recipient, address, service level, additional attempts, mileage, mailing, witness fees, research, stakeout, filing, or other approved charges.

The firm should be able to connect the invoice to the assignment history without asking what a generic line item means.

The provider should also apply its agreed retention and security rules to:

• documents served;
• field notes;
• recipient information;
• photographs and location data when collected;
• mailing records;
• proof versions;
• filing confirmations;
• client communications;
• billing records.

A centralized assignment workflow can preserve the connection among those records and reduce the risk that the final proof exists separately from the facts supporting it.

Know When a “Served” Result Requires Immediate Review

Some successful-delivery reports contain facts that should stop automatic proof preparation.

Immediate review may be appropriate when:

• the recipient refused to identify themselves;
• the named person denied being the subject;
• the server relied on recognition from a photograph but could not confirm identity;
• papers were left after a refusal in circumstances requiring a detailed narrative;
• a business employee accepted but denied authority;
• the business name at the location differs from the named legal entity;
• the field address differs from the dispatched address;
• the server used a different method from the instruction;
• the final packet may have omitted a document;
• the recipient appears to be a minor or otherwise not the intended qualifying person;
• the service event conflicts with a court order;
• safety conditions prevented ordinary documentation;
• the assignment is a high-risk or difficult-service assignment likely to face challenge.

The provider should preserve the facts and ask for attorney direction. “Successful” should not mean that uncertainty disappears from the record.

Prepare for California’s 2027 Proof Workflow Changes

Law firms and providers should distinguish current requirements from future operative law.

As of September 2026, the current version of California Code of Civil Procedure section 417.10 remains operative through December 31, 2026. A later version scheduled to become operative on January 1, 2027 adds photograph and readable date, time, and GPS or equivalent location-stamp requirements for specified effected and attempted summons service, with stated exceptions and explanation requirements.

That transition may affect:

• field capture procedures;
• device permissions and signal exceptions;
• server safety documentation;
• photograph review;
• privacy and retention controls;
• proof attachments;
• quality-control checklists;
• client delivery formats.

A provider relationship continuing into 2027 should include change management. It should not apply the future rule inaccurately to every 2026 assignment.

Post-Service Completion Checklist for Law Firms

Field Event

• Was the intended party or entity identified correctly?
• Who physically received the documents?
• Is the recipient’s identity, title, relationship, or capacity documented?
• Are the exact date, time, and location recorded?
• Does the field report explain any refusal or unusual circumstance?
• Were all documents in the final packet delivered?

Method Completion

• Does the field result support the selected service method?
• Does the method require a mailing, acknowledgment, posting, publication, fee, or another step?
• Has every required operational step been assigned?
• Has counsel confirmed the legal completion event?
• Has the next deadline been calculated by the responsible legal professional?

Proof of Service

• Is the correct proof form being used?
• Does the caption and case number match the filed documents?
• Are all documents served listed accurately?
• Do the method, recipient, date, time, location, and mailing details match the source record?
• Is server information complete?
• Is the declaration signed?
• Are all required attachments included?
• Was the proof quality-reviewed before release?

Filing and Closure

• Who is responsible for filing?
• Was filing submitted within the required workflow?
• Was the filing accepted or rejected?
• Was any rejection corrected and resubmitted?
• Did the firm receive the signed and accepted versions required?
• Were originals, receipts, fees, and supporting records returned?
• Does the invoice match the authorized work?
• Does the closure notice state exactly what was and was not completed?

Metrics That Matter After Service of Process

Many provider scorecards stop at success rate. That leaves the post-service workflow invisible.

Law firms may also measure:

The goal is not to close every case immediately. The goal is to ensure that a case remains open for a known reason, with a named owner and next action.

How Proofser Manages the Assignment After Field Delivery

Proofser coordinates managed process serving through a connected workflow rather than treating successful delivery as the final administrative event.

After a field result, the operations team can review the recipient, location, method, documents, notes, deadline, and client instruction. If mailing or another follow-up step is required, the task remains visible. Proof preparation begins from verified service facts. The proof can be reviewed for consistency before it is delivered or filed.

The client update can distinguish:

• field delivery completed;
• follow-up mailing pending or completed;
• Proof of Service in preparation or review;
• proof delivered to the firm;
• filing not included;
• filing submitted;
• filing accepted or requiring correction;
• assignment operationally closed.

This approach gives attorneys and paralegals a more reliable answer than “served” because it explains both the completed event and the remaining work.