Skip to main content

Proposed Orders After a Motion: the Prevailing Party's Five Days, Approval as Conforming, and Electronic Submission — Cal. Rules of Court, rule 3.1312

High confidence· verified October 22, 2026Proposed OrdersCal. Rules of Court, rule 3.1312

A published court requirement that applies in California. Category: Proposed Orders. Cited as Cal. Rules of Court, rule 3.1312. Verified against the official source (California Rules of Court — Judicial Council of California) on October 22, 2026.

Summary

Unless the parties waive notice or the court orders otherwise, the party prevailing on a motion must, within five days of the ruling, serve a proposed order for approval as conforming to the court's order, by a means reasonably calculated to deliver it by the close of the next business day; the other parties have five days after service to say whether they approve and to state any reasons for disapproval, silence being approval, and service-method extensions of time do not apply. When the five days expire the prevailing party promptly transmits the proposed order to the court with a summary of the responses or a statement that none were received. In an electronic filing case, the proposed order is filed electronically as a PDF attached to a Proposed Order (Cover Sheet) (form EFS-020), and an editable word-processing version is sent to the court's designated electronic address with copies to all parties. If the prevailing party fails to act, any other party may; the rule does not apply to an unopposed motion whose proposed order accompanied the moving papers, unless the court orders otherwise.

Applies to

California > Superior courts (proposed orders)

Requirement

(a) Prevailing party to prepare Unless the parties waive notice or the court orders otherwise, the party prevailing on any motion must, within five days of the ruling, serve by any means authorized by law and reasonably calculated to ensure delivery to the other party or parties no later than the close of the next business day a proposed order for approval as conforming to the court's order. Within five days after service, the other party or parties must notify the prevailing party as to whether or not the proposed order is so approved. The opposing party or parties must state any reasons for disapproval. Failure to notify the prevailing party within the time required shall be deemed an approval. The extensions of time based on a method of service provided under any statute or rule do not apply to this rule. (b) Submission of proposed order to court The prevailing party must, upon expiration of the five-day period provided for approval, promptly transmit the proposed order to the court together with a summary of any responses of the other parties or a statement that no responses were received. (c) Submission of proposed order by electronic means If a proposed order is submitted to the court electronically in a case in which the parties are electronically filing documents under rules 2.250-2.261, two versions of the proposed order must be submitted: (1) A version of the proposed order must be attached to a completed Proposed Order (Cover Sheet) (form EFS-020), and the combined document in Portable Document Format (PDF) must be filed electronically; and (2) A version of the proposed order in an editable word-processing format must also be sent electronically to the court, with a copy of the e-mail and proposed order also being sent to all parties in the action. Each court that provides for electronic filing must provide an electronic address or addresses to which the editable versions of proposed orders are to be sent and must specify any particular requirements regarding the editable word-processing format for proposed orders. (d) Failure of prevailing party to prepare proposed order If the prevailing party fails to prepare and submit a proposed order as required by (a) and (b) above, any other party may do so. (e) Motion unopposed This rule does not apply if the motion was unopposed and a proposed order was submitted with the moving papers, unless otherwise ordered by the court.

Source of truth

Source health
Healthy · checked November 21, 2026
Effective date
—
Last verified
October 22, 2026
Provenance record

Verbatim from the California Law Library: the current verified version of Cal. Rules of Court, rule 3.1312 (authority_versions 07df6141-ad18-413d-bef0-a03e996251de; text sha256 c32a0894311f164b4afb09913564f27a28f69f515f85deae442a6a8ada1cefb1; As posted by the Judicial Council of California (read October 22, 2026); composer: compose_crc.py 2026-10-22: the Judicial Council's rule pages read paragraph by paragraph; verify_crc.py's second reading of the Council's per-title PDFs finds every paragraph). Its receipt is the version's own source document, https://courts.ca.gov/cms/rules/index/three/rule3_1312 (fetched 2026-10-22 18:00:00Z, content sha256 6ee85709c23ca45cb755361d0794450f2d2ba48fda5f6ae3f6008546d21e19dd), so no new receipt was registered. Composed 2026-10-26 for California's workflow packs.

Change history

  • November 19, 2026Monitor detected a source-content or hash-basis change. Review the archived bytes before republishing dependent material.
  • November 18, 2026Monitor detected a source-content or hash-basis change. Review the archived bytes before republishing dependent material.
  • November 17, 2026Monitor detected a source-content or hash-basis change. Review the archived bytes before republishing dependent material.
  • November 16, 2026Monitor detected a source-content or hash-basis change. Review the archived bytes before republishing dependent material.
  • November 15, 2026Monitor detected a source-content or hash-basis change. Review the archived bytes before republishing dependent material.
  • November 14, 2026Monitor detected a source-content or hash-basis change. Review the archived bytes before republishing dependent material.
  • November 13, 2026Monitor detected a source-content or hash-basis change. Review the archived bytes before republishing dependent material.
  • November 12, 2026Monitor detected a source-content or hash-basis change. Review the archived bytes before republishing dependent material.
  • November 11, 2026Monitor detected a source-content or hash-basis change. Review the archived bytes before republishing dependent material.
  • November 10, 2026Monitor detected a source-content or hash-basis change. Review the archived bytes before republishing dependent material.

Related rules