Search Tips

RULE 36. ENTRY OF JUDGMENT

Effective Date: 10/1/2014

(a) Entry. A judgment is entered when it is noted on the docket. The clerk of the supreme court must prepare, sign and enter the judgment:

(1) after receiving the court's opinion; or
(2) if a judgment is rendered without an opinion, as the court instructs.

(b) Notice. The clerk of the supreme court must send all parties a copy of the opinion, or of the judgment if no opinion was written, and notice of the date the judgment was entered. The opinion or judgment may be sent by mail, by third-party commercial carrier, or by electronic means.

Rule 36 was amended, effective March 1, 1999; March 1, 2003; March 1, 2007; October 1, 2014.

This rule is derived from Fed.R.App.P. 36. It is intended to clarify what constitutes entry of a judgment or order.

Rule 36 was amended, effective March 1, 1999, to allow the clerk of the supreme court to send a copy of the opinion by commercial carrier as an alternative to the Postal Service.

Rule 36 was amended, effective March 1, 2003. The language and organization of the rule were changed to make the rule more easily understood and to make style and terminology consistent throughout the rules.

Subdivision (b) was amended, effective March 1, 2007, to allow the clerk of the supreme court to send the opinion or judgment by electronic means.

Rule 36 was amended, effective October 1, 2014, to replace "supreme court clerk" with "clerk of the supreme court."

SOURCES: Joint Procedure Committee Minutes of April 25-26, 2002, pages 18-19; January 27-30, 1998, page 21. Fed.R.App.P. 36.

STATUTES AFFECTED:

SUPERSEDED: N.D.C.C. §§ 28-27-30 and 29-28-32.

Effective Date Obsolete Date
10/01/2014 View
03/01/2007 10/01/2014 View
03/01/2003 03/01/2007 View
03/01/1999 03/01/2003 View
01/27/1998 03/01/1999 View

 

Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>