Filing and Service Are Different Acts
A document has to reach two different places, on two timetables, governed by two sets of rules. Treating all of that as a single task is how parties end up having filed something perfectly properly and served it a week late, or else the reverse.
The rule in short
Filing places a document on the record of a matter; service delivers it to the other parties. The two have different deadlines, different permitted methods, different proof requirements and different consequences for failure. Confusing them produces documents lodged correctly and delivered late, and periods calculated from the wrong event entirely.
Every document in a contested matter has at least two journeys to make. They are governed separately, and the failure to notice that is among the most routine procedural errors there is.
What each one is
Filing puts a document on the record. It is the act of lodging with the forum, and it is what makes the document part of the matter.
Service delivers it to the parties. It is the act of bringing the document to the other side, and it is what makes it operative against them.
They have separate deadlines. Frequently the same date and frequently not, and assuming they coincide is where errors begin.
They permit different methods. Electronic filing may be compulsory while service by post remains permitted, or the reverse.
They generate different proof. A filing receipt and a certificate of service are different documents recording different acts.
They fail differently. A rejected filing and a defective service produce different problems with different cures.
They may be done by different people. Which is precisely why one of them gets forgotten.
Both are usually required. A document filed but never served, or served but never filed, is frequently ineffective for its intended purpose.
Some documents need only one. Purely internal filings and purely inter-party correspondence exist, and knowing which category a document falls into is part of reading the rule properly.
Where the deadlines differ
Service before filing. Some rules require a document to be served on the parties before it is lodged, with a stated interval.
Filing before service. Others require lodging first, so that the served copy bears a stamp or a case reference.
Same-day requirements. Many systems require service promptly after filing, sometimes on the same day.
Different cut-off times. Electronic filing may be available until midnight while service by another method is not, per the last day and what time it ends.
Additional time for service methods. Where post is used, extra days may apply to what the recipient must do next.
Periods running from different events. A response period may run from service while a right of appeal runs from filing or from issue.
Weekend and holiday interaction. Filing may be possible electronically on a closure day while service is not.
Contractual notice on top. Where an agreement also requires notice, that becomes a third obligation with its own third timetable.
Joined parties and their own periods. A party added part way through a matter may have deadlines counted from when they were served rather than from anything that happened earlier.
| Aspect | Filing | Service |
|---|---|---|
| Destination | The forum | The other parties |
| Proof | Filing receipt | Certificate of service |
| Common method | Electronic | Electronic or post |
| Failure | Not on the record | Not effective against a party |
| Cure | File late, seek relief | Serve late, seek relief |
What goes wrong
Filed on time, served late. The commonest version, and it exposes the party to an argument about the effectiveness of the step.
Served on time, never filed. Which leaves the record incomplete and the document technically outside the matter.
Assuming electronic filing serves everybody. Many systems do serve registered participants automatically, and many do not, and some parties are not registered.
Overlooking unrepresented parties. Who frequently sit outside electronic service arrangements and require conventional delivery.
Calculating from the wrong event. Counting a response period from filing where the rule counts from service, or the reverse.
Different documents, different rules. Applying one document's arrangement to another in the same matter.
Missing the certificate of service. Which can render an otherwise complete filing deficient, per proving that notice was given.
Splitting the task between people. Where one person files and another serves, each assuming the other dealt with the whole of it.
A completed step produces a filing confirmation and a service record. Where only one exists, half the task was done, and the half that was missed is usually discovered by somebody else.
Doing both properly
Identify both deadlines before starting. Written down separately, with their sources, rather than treated as a single date.
Check the permitted methods for each. Filing and service rules are frequently in different parts of the same instrument.
Confirm who must be served. Every party, including those not registered for electronic service and those without representation.
Prepare the certificate of service with the document. Rather than afterwards, since it forms part of what is lodged in many systems.
Keep both receipts. The filing confirmation and the service record, filed together against the same document.
Diarize what follows. Response periods triggered by the step, calculated from whichever event the rule specifies.
Assign the whole task to one person. Splitting it is efficient and is the most reliable way of losing half of it.
Check the record afterwards. Confirming that the document actually appears on the file catches rejections nobody noticed.
When one of them failed
Establish which. The cure for a late service is different from the cure for a rejected filing.
Act immediately. Both problems shrink dramatically if addressed the same day.
Complete the missing step. Serving late is usually better than not serving, and filing late is usually better than not filing.
Tell the other side. Raising it is better than having it raised, and it supports any application that follows.
Seek relief if needed. Where a deadline has passed, an application may be required, per filing late and asking to be heard.
Check whether anything downstream is affected. Periods that were meant to start may not have started, which affects the whole timetable.
Correct the record. A certificate of service filed late is better than one never filed at all.
Fix the process. One task, one owner and two receipts is the arrangement that prevents any repetition.
Check the other documents in the sequence. Where one step was half-completed, the ones filed around it by the same person on the same day deserve a look as well.
Filing places a document on the record and service delivers it to the parties, and they are separate obligations with separate deadlines, methods, proofs and consequences.
Deadlines diverge in both directions: some rules require service before filing, others the reverse, and cut-off times frequently differ between the two acts.
The recurring failures are filing on time and serving late, assuming electronic filing serves everybody, overlooking unrepresented parties, and counting a period from the wrong event.
Doing both properly means identifying both deadlines with their sources, confirming who must be served, preparing the certificate of service alongside the document and keeping both receipts.
Where one of them failed, establishing which, completing the missing step the same day, telling the other side and seeking relief if needed are what limit the damage.
Points to carry away
- Filing and service are separate obligations.
- Their deadlines are frequently different.
- Permitted methods differ between them.
- Each has its own proof requirement.
- Periods may run from either, depending on the rule.
Questions readers ask
Does electronic filing automatically serve the other parties?
In many systems it serves participants who are registered for electronic service, and in those systems no further step is needed for them. It does not serve parties who are not registered, which frequently includes unrepresented litigants and sometimes includes newly joined parties whose registration has not caught up. Because the answer varies both by system and by party, the reliable approach is to identify every person requiring service and confirm how each of them will receive the document.
What happens if a document is filed on time but served late?
It depends on the rule and on the consequence attached. The filing may stand while the step is ineffective against the party served late, which can matter a great deal where a period was supposed to start running for them. Serving as soon as the error is discovered, telling the other side, and seeking relief if a deadline has passed are the standard responses, and all of them work far better on the same day than a week afterwards.
Should a response period be counted from filing or from service?
From whichever the applicable rule specifies, and the two are frequently different for different documents in the same matter. Response periods commonly run from service, while rights of appeal frequently run from the issue or entry of a decision rather than from anything either party did. Writing down which event each period runs from, at the time the deadline is diarized, prevents the most consequential version of this error.
Sources
- Federal Rules of Civil Procedure — Rule 5, Serving and Filing Pleadings and Other Paperslaw.cornell.edu
- Federal Rules of Civil Procedure — Rule 5(d)(1), Required Filings; Certificate of Servicelaw.cornell.edu
- Federal Rules of Civil Procedure — Rule 6(a), Computing Timelaw.cornell.edu
- Federal Rules of Appellate Procedure — Rule 25, Filing and Servicelaw.cornell.edu
- United States Courts — Electronic Filing (CM/ECF)uscourts.gov
- Legal Information Institute — Certificate of Servicelaw.cornell.edu
Urban Justice Docket is a publication, not a law firm. This article states general rules and cites its sources; it is not advice about any particular case, and the law differs by state and changes over time.
More in Filing, and When It Counts
System Outages on the Last Day
Most electronic filing regimes provide for extensions or alternative routes where the system is unavailable. Obtaining that relief requires contemporaneous evidence: timestamps of attempts, error messages, screenshots and any official outage notice. It also requires distinguishing a system failure, which usually attracts relief, from a problem at the filer's own end, which usually does not.
A Fee That Blocks a Filing
Many filings require a fee, and where payment is a condition of acceptance a failed transaction prevents the filing entirely. Fee waivers and deferrals exist, take time to obtain, and have their own evidential requirements. The practical protection is arranging payment before the deadline evening and applying for any waiver far enough ahead that its processing time is not the problem.
Amending a Document Already Filed
Amendments fall into categories: clerical corrections, amendments permitted without leave within a window, and amendments requiring permission. The crucial question is whether the amended document is treated as filed on the original date or on the date of amendment, because where a period has expired in the meantime the answer decides whether the new material survives.