The most common support request we receive involves helping legal professionals format documents for the Utah Court’s filing system. While your Rich Text Format (.rtf) documents may look perfect in Word or WordPerfect, the Court’s specialized processing system handles them differently, which often introduces unexpected formatting errors.

Understanding how the Court processes these files is the first step toward a successful, rejection-free filing.

Why does the Court require .rtf files?

The Court requires the .rtf format for documents that require a clerk’s or Judge’s signature, such as:

  • Default Certificates
  • Writs of Garnishment
  • Proposed Orders
  • Proposed Judgments

The Reason: Unlike a PDF, an RTF file remains editable. This allows the Court to make necessary adjustments or corrections before applying a digital signature stamp via their judicial review software.

Why .rtf instead of Word (.docx)?

Rich Text Format is a universal file type. It allows the Court to remain “software agnostic.” Whether you use Microsoft Word, WordPerfect, OpenOffice, or Google Docs, you can export to .rtf. This ensures that the Court doesn’t force any firm to purchase a specific brand of word-processing software.

How the Court Processes Your Document

When you upload an RTF, it undergoes a complex conversion process that can “break” certain formatting:

  1. RTF to HTML: To view your document in a web browser (Chrome, Edge, Firefox), the Court’s software converts your RTF into HTML.
  2. Review & Sign: The Judge reviews the HTML version and places a digital signature stamp.
  3. HTML to PDF: Once signed, the system converts the HTML document into a final PDF for permanent storage and distribution.

Checklist of RTF dos and don'ts based on the text in this article

How to Remove Drawing Objects from RTF Documents

Common Formatting “Deal-Breakers”

The conversion from RTF to HTML is sensitive. If your document contains complex elements, the Court’s software may fail to display it correctly, leading to a “Declined to Sign” status.

High-Risk Elements (Often lead to rejection)

  • Text Boxes: Word text boxes often disappear or float over text.
  • Columns: WordPerfect or Word columns rarely convert cleanly to HTML.
  • Embedded Images/Drawings: These can bloat file size or fail to render.
  • Headers and Footers: The conversion process often strips these or misplaces them.
  • Nested Tables: Tables inside of tables are a primary cause of layout collapse.

Low-Risk Elements (Often lead to ugly formatting)

These might not cause a rejection, but they often make the final PDF look unprofessional:

  • Auto-Numbering/Bullets: In HTML, these often trigger unwanted indentations.
  • Paragraph Returns: Standard “Enters” often lead to a double-space in HTML.

Pro Tip: Use Line Breaks (Shift + Enter) for tighter spacing.

Why was my filing rejected for a “Drawing Object”?

Even if you can’t see a drawing object, your file might contain “hidden” metadata. This often happens if you:

  • Use “Track Changes” or revision tracking.
  • Copy and paste content from a website or another document.
  • Accidentally activate drawing tools while inserting a table.

If your RTF was rejected due to drawing objects, headers, or revision tracking, follow our step-by-step guide to fix your RTF file: Remove Drawing Objects from RTF Documents