Oregon court documents: UTCR 2.010 formatting; Multnomah + Washington County Circuit Court + county roll-up; ORS 697 / Oregon UTPA consumer-debt bundle. Full detail in the plugin README.

GitHub stars
26

Install

/plugin install or-court-docs@claude-legal

Run it inside Claude Code after adding the marketplace with /plugin marketplace add codearranger/claude-legal.

Contents

Discovered from source

Skills 21

Oregon Consumer-Debt Defense

This skill is the subject-matter bundle for Oregon consumer-debt litigation: debt-buyer cases, original-creditor collection actions, and any matter turning on FDCPA / Reg F / Oregon UTPA / ORS 697.

It assumes the procedural framework is already in place via the matter-neutral skills. This skill adds:

  • Substantive law: FDCPA, Reg F, Oregon UTPA, ORS 697 Collection Agency Registration Act
  • Chain-of-title doctrine: what a debt-buyer plaintiff must prove to recover
  • Evidence patterns: business-records foundation (OEC 803(6) / 902(11)) and authentication (OEC 901)
  • Fact-pattern triage: 5 common debt-defense scenarios and the matching defenses / counterclaims
  • Discovery banks: pre-built RFPs and RFAs targeting the weak spots of a debt-buyer's case
  • Example filings: synthetic answers, declarations, motions, and orders for a debt-buyer-defense fact pattern

NOT LEGAL ADVICE. Consumer-debt defense is fact-specific and outcome-dependent. This skill provides a procedural and substantive framework — not strategic advice for any specific case.

Five common Oregon debt-defense fact patterns

Pattern 1: Debt-buyer suit on an unfamiliar account

Defendant doesn't recognize the account, the account number, or sometimes the original creditor. Plaintiff is a debt buyer that purchased a pool of charged-off accounts.

Defenses commonly raised in this pattern:

  • Lack of standing — Plaintiff cannot prove chain of title from the original creditor to itself
  • Statute of limitations — ORS 12.080 6-year SOL may have run on the open account
  • Lack of registration — Plaintiff (if a debt buyer) may not be registered with DCBS as required by ORS 697.015
  • OEC 803(6) / 902(11) foundation — Plaintiff cannot authenticate the original creditor's records

Counterclaims commonly considered in this pattern:

  • FDCPA (1692e, 1692f, 1692g) — false representations, unfair practices, failure to provide validation
  • Oregon UTPA (ORS 646.605 et seq.) — equivalent state-law claims, often with broader remedies
  • ORS 697.085 — if plaintiff is unregistered

Pattern 2: Original creditor collection on a known account

Defendant recognizes the account but disputes the amount, the charges, or the validity of certain transactions.

Defenses commonly raised in this pattern:

  • Account stated / objection — defendant timely disputed the account
  • Statute of frauds (ORS 41.580) — for accounts requiring written agreement
  • Fraudulent transactions — identity theft, unauthorized use
  • Statute of limitations — ORS 12.080
  • Failure of consideration — for goods/services not received

Counterclaims:

  • Defamation — if creditor made false statements to credit bureaus
  • FCRA (15 USC § 1681s-2) — willful or negligent furnishing of inaccurate information
  • Oregon UTPA — for unfair or deceptive collection practices

Pattern 3: Time-barred debt (zombie debt) revival attempt

Plaintiff is suing on a debt that is past the 6-year SOL but claims a partial payment or written acknowledgment re-started the clock.

Defenses commonly raised in this pattern:

  • Statute of limitations, with detailed factual analysis of when the SOL ran
  • No revival — under ORS 12.230, a payment alone does not re-start the SOL on most debts; only a written promise to pay can revive

Counterclaims:

  • FDCPA (1692e(2), 1692e(5), 1692f(1)) — suing on a time-barred debt is misleading and unfair
  • Oregon UTPA — equivalent

Pattern 4: Default judgment entered improperly

Defendant didn't answer; default judgment entered. Now in collection.

Approach:

  • Motion to vacate under ORCP 71 — see or-post-judgment
  • Exemption claims on garnishment under ORS 18.700+
  • FDCPA / UTPA claims for continued collection on a fraudulent judgment

Pattern 5: Unauthorized debt collection

Plaintiff is a collection agency that is NOT registered with the Oregon Department of Consumer and Business Services (DCBS) as required by ORS 697.015.

Defenses:

  • Lack of capacity to sue — unregistered collection agencies cannot maintain an action (ORS 697.105)
  • Motion to dismiss under ORCP 21

Counterclaims:

  • ORS 697.085 — private right of action for unregistered collection
  • Oregon UTPA — unregistered collection is an unfair practice

Substantive law — quick reference

FDCPA (15 USC § 1692 et seq.)

The federal Fair Debt Collection Practices Act. Applies to debt collectors (not original creditors) collecting consumer debt.

SectionSubject
1692cCommunication restrictions
1692dHarassment / abuse
1692eFalse or misleading representations
1692fUnfair practices
1692gValidation notices
1692kCivil liability ($1,000 statutory + actual + fees)
1692k(d)1-year SOL

See references/fdcpa.md for the full annotated FDCPA.

Regulation F (12 CFR pt 1006)

The CFPB's implementing regulation, effective November 30, 2021. Implements and supplements FDCPA. Key provisions:

SectionSubject
§ 1006.6Communication with consumers
§ 1006.18False or misleading representations
§ 1006.22Unfair or unconscionable practices
§ 1006.26Time-barred debt
§ 1006.30Notice requirements (replaces FDCPA validation)
§ 1006.34Validation information

See references/reg-f.md for the full annotated Reg F.

Oregon UTPA (ORS 646.605–646.656)

Oregon's consumer-protection statute. Broader than FDCPA in some respects:

  • Applies to ALL persons collecting consumer debt, not just "debt collectors"
  • No $1,000 cap; actual damages, $200 statutory minimum, punitive damages, injunctive relief
  • Prevailing-party fees mandatory under ORS 646.638(3)
  • 1-year SOL from discovery; 6-year repose under ORS 646.638(6)

Key sections:

  • ORS 646.607 — unconscionable tactics list
  • ORS 646.608 — unlawful trade practices catalog
  • ORS 646.638 — private right of action

See references/utpa.md for the full annotated UTPA.

Oregon Collection Agency Registration Act (ORS 697)

Regulates collection agencies (debt collectors) in Oregon.

  • ORS 697.005 — definitions; "collection agency" includes debt buyers
  • ORS 697.015 — registration required with DCBS
  • ORS 697.058 — prohibited practices
  • ORS 697.085 — private right of action; actual damages, $200 statutory minimum, attorney fees
  • ORS 697.105 — registration is condition of capacity to sue (unregistered agency cannot bring an action in Oregon courts)

See references/ors-697.md for the full annotated ORS 697.

Chain of title

A debt buyer must prove every link in the chain from original creditor to itself. Typical chain:

Original Creditor (Bank of America)
       ↓ Bulk Sale Agreement, Bill of Sale, Assignment
Debt Pool Purchaser 1 (e.g., Asset Acceptance)
       ↓ Bulk Sale Agreement, etc.
Debt Pool Purchaser 2 (e.g., Velocity Investments)
       ↓ Sale to current Plaintiff
Plaintiff (LVNV Funding, LLC)

Each link requires:

  • Bill of Sale — the document evidencing the sale
  • Assignment Schedule — the inventory listing the specific accounts assigned
  • Authentication — under OEC 901 / 902(11), the bill of sale must be authenticated by a witness from the assigning entity

Debt buyers often produce only a summary bill of sale and a redacted assignment schedule. The defendant's discovery target: the un-redacted versions, plus the cardholder agreement between defendant and original creditor.

See references/chain-of-title.md for the full doctrine.

Discovery banks (subject-matter-specific)

Pre-built request banks for debt-defense discovery. These plug into the procedural framework in or-discovery:

  • references/rfp-debt-buyer.md — First Requests for Production targeting chain of title, original-creditor records, plaintiff's records of the account, communications, collection history
  • references/rfa-debt-buyer.md — Requests for Admission locking in foundational facts (plaintiff's corporate form, registration status, dates of acquisition)
  • references/interrogatories-debt-buyer.md — Interrogatories in mandatory arbitration (where allowed by arbitrator) — Oregon does NOT have written interrogatories in standard ORCP discovery
  • references/meet-and-confer-debt-buyer.md — Sample meet-and-confer letters and follow-up emails

Evidence patterns

The OEC 803(6) / 902(11) foundation question is the critical evidentiary battleground in Oregon debt-buyer cases. The plaintiff's typical declaration:

"I am the custodian of records for [Plaintiff Debt Buyer]. Plaintiff maintains records of accounts in the ordinary course of business. Account number ending XXXX was assigned to Plaintiff on [date] by [Original Creditor]. Plaintiff's records show a balance of $[amount] owing on the account. True and correct copies of the records are attached."

This declaration typically fails as foundation because:

  1. The declarant is the debt buyer's custodian, not the original creditor's
  2. The original creditor's records are hearsay — the declarant cannot attest that they were made in the regular course of the original creditor's business
  3. The "remote custodian" doctrine — the debt buyer cannot speak to the trustworthiness of records it didn't create

See references/evidence-debt-buyer.md for the doctrine and the specific objection language.

Key cases — Oregon and 9th Circuit

Oregon

  • Phillips v. Beaverton Aluminum Co., 314 Or App 257, 498 P3d 814 (2021) — ORCP 46 fee-shifting in discovery disputes
  • Denson v. Ron Tonkin Gran Turismo, [verify cite] — UTPA standing in consumer transactions
  • Pearson v. Philip Morris, 358 Or 88, 361 P3d 3 (2015) — UTPA class certification standards
  • Ziegler v. Hill and similar trial-court decisions on business-records foundation in debt cases (look for recent Oregon Court of Appeals decisions)

9th Circuit / federal

  • Henson v. Santander Consumer USA, Inc., 582 US 79, 137 S Ct 1718 (2017) — definition of "debt collector"
  • Heintz v. Jenkins, 514 US 291 (1995) — attorneys as debt collectors
  • Sheriff v. Gillie, 578 US 317 (2016) — state actors
  • Marx v. General Revenue Corp., 568 US 371 (2013) — attorney-fee shifting under § 1692k

See references/key-cases.md for full citations and holdings.

Companion procedural skills

This subject-matter bundle composes with:

  • or-statewide-format — UTCR 2.010 formatting
  • The relevant court skill — or-multcc / or-wccc / or-county-courts
  • or-pro-se — pro-se drafting framework
  • or-law-references — citation conventions, online sources
  • or-discovery — discovery framework; layer the debt-buyer-specific banks on top
  • or-first-30-days — initial response (affirmative defenses + counterclaims selection)
  • or-deadlines — SOL computation (ORS 12.080 6 years; FDCPA 1 year; UTPA 1 year/6 years)
  • or-fact-check — citation verification
  • or-quality-check — format pass
  • or-draft-* — drafting the specific filings
  • or-post-judgment — if default judgment already entered

References

  • references/fdcpa.md — FDCPA section-by-section
  • references/reg-f.md — Regulation F annotated
  • references/utpa.md — Oregon UTPA (ORS 646.605 et seq.)
  • references/ors-697.md — Oregon Collection Agency Registration Act
  • references/or-statutes-of-limitations.md — Oregon SOLs for debt and consumer-protection claims
  • references/chain-of-title.md — chain-of-title doctrine
  • references/evidence-debt-buyer.md — OEC 803(6) / 902(11) foundation in debt cases
  • references/fact-patterns.md — five common debt-defense fact patterns
  • references/key-cases.md — Oregon and federal decisions
  • references/recent-decisions.md — recent Oregon Court of Appeals and 9th Circuit opinions
  • references/fees-consumer-debt.md — fee-shifting in debt-defense cases
  • references/rfp-debt-buyer.md — RFPs targeting chain of title
  • references/rfa-debt-buyer.md — RFAs locking in basics
  • references/interrogatories-debt-buyer.md — interrogatories (only available in arbitration)
  • references/meet-and-confer-debt-buyer.md — sample meet-and-confer correspondence
  • references/ucc-article-9.md — UCC Article 9 (ORS 79) on secured transactions in debt-buyer chain-of-title
  • references/online-sources-consumer-debt.md — authoritative URLs for debt-related research

Oregon county circuit courts (non-Multnomah / non-Washington)

Use this skill in addition to or-statewide-format when filing in any Oregon circuit court other than Multnomah County or Washington County.

NOT LEGAL ADVICE. These notes describe each venue's procedural mechanics as a drafting aid, not legal advice. Local rules and judge-specific practices change; verify with the clerk and the current SLR before relying on anything here.

Oregon has 36 counties and 27 judicial districts (some districts combine multiple counties — e.g., the 21st District is Benton County only; the 22nd District is Crook and Jefferson). Every county has at least one circuit court courthouse. The high-volume counties below have their own SLR, judicial assistants, and established motion practice.

County / venue table — Oregon's most populous counties (after Multnomah & Washington)

CountySeatCourthouse / addressJudicial DistrictCivil contact
ClackamasOregon City807 Main St, Oregon City OR 970455th(503) 655-8447
LaneEugene125 E 8th Ave, Eugene OR 974012nd(541) 682-4020
MarionSalem100 High St NE, Salem OR 973013rd(503) 588-5105
JacksonMedford100 S Oakdale Ave, Medford OR 975011st(541) 776-7171
DeschutesBend1100 NW Bond St, Bend OR 9770311th(541) 388-5300
LinnAlbany300 SW 4th Ave, Albany OR 9732123rd (with Benton)(541) 967-3845
BentonCorvallis120 NW 4th St, Corvallis OR 9733021st(541) 766-6800
YamhillMcMinnville535 NE 5th St, McMinnville OR 9712825th(503) 434-7470
PolkDallas850 Main St, Dallas OR 9733812th(503) 623-3154
DouglasRoseburg1036 SE Douglas Ave, Roseburg OR 9747016th(541) 957-2410

Pull current contacts from the OJD county-court page: https://www.courts.oregon.gov/courts/Pages/find-a-court.aspx

Phone numbers and street addresses change. Verify the current contact before drafting a date-request email or mailing working copies.

Caption — county variant

The court header line uses "FOR THE COUNTY OF [NAME]":

            IN THE CIRCUIT COURT OF THE STATE OF OREGON
                  FOR THE COUNTY OF CLACKAMAS

Case numbers follow the statewide format (25CV12345, 25SC12345, etc.) — same across all counties.

Scheduling models across counties

Oregon counties use one of three motion-scheduling models:

ModelCounties (typical)How motions are set
Centralized motion docketSome smaller counties; varies by yearA single judge hears all civil motions on a rotating week; date reservation through court coordinator
Court-administrator schedulingLane, Marion, Jackson, DeschutesCivil motions set by Court Administrator or Civil Department clerk
Individual JAMultnomah; some larger civil departments in Lane, MarionDate requested directly to assigned judge's JA

To determine which model a county uses, look at its SLR Chapter 5 (Motions) and its court website. When in doubt, call the Civil Division of the relevant courthouse.

Per-county notes

Clackamas County Circuit Court — Oregon City

  • 5th Judicial District (Clackamas only)
  • Multi-judge civil department; lightly centralized scheduling
  • SLR available at courts.oregon.gov/courts/clackamas/rules
  • Mandatory arbitration ($10K–$50K) follows ORS 36.400
  • Civil counter: 807 Main Street, Oregon City OR 97045
  • Active legal-aid presence: Legal Aid Services of Oregon — Clackamas branch

Lane County Circuit Court — Eugene

  • 2nd Judicial District (Lane only)
  • Largest court in the Willamette Valley after Marion
  • Strong individual-JA practice for most civil judges
  • Lane SLR has detailed motion-practice rules (SLR Chapter 5)
  • Multiple branch courthouses: Eugene (main, 125 E 8th Ave), Florence (small claims and limited civil; check current hours)
  • Civil contact: (541) 682-4020

Marion County Circuit Court — Salem

  • 3rd Judicial District (Marion only); 5 civil judges
  • Salem is the state capital; Marion sees significant administrative-law and state-government civil filings
  • Marion SLR available at courts.oregon.gov/courts/marion/rules
  • Civil Department on Floor 2, 100 High Street NE, Salem
  • Mandatory arbitration program follows ORS 36.400
  • Active pro bono panel through Marion County Bar

Jackson County Circuit Court — Medford

  • 1st Judicial District (Jackson and Josephine combined)
  • Civil division at 100 S Oakdale Ave, Medford OR 97501
  • Lightly centralized motion scheduling
  • Significant rural-civil docket; FED (landlord-tenant) cases prominent

Deschutes County Circuit Court — Bend

  • 11th Judicial District (Deschutes only)
  • Fast-growing; civil filings up significantly since 2018
  • Civil scheduling through court coordinator
  • Bend courthouse at 1100 NW Bond Street

Linn County (Albany) — Benton County (Corvallis)

  • 23rd Judicial District is Linn-only; 21st is Benton-only
  • Distinct courthouses in Albany and Corvallis; share some administrative resources
  • Smaller-population counties; centralized motion docket common

Yamhill, Polk, Douglas

  • Smaller counties with centralized motion dockets
  • Many filings handled by the court coordinator rather than individual JAs

Authoritative source — pull the current court page per county

For each county, the canonical source for judges, courtrooms, JAs, hours, and SLR is:

https://www.courts.oregon.gov/courts/[county-slug]/Pages/default.aspx

Examples:

  • /courts/clackamas/
  • /courts/lane/
  • /courts/marion/
  • /courts/jackson/
  • /courts/deschutes/

Each county page links to its current SLR PDF. Pull the current PDF before relying on any SLR section.

Filing fees

Statewide schedule under ORS 21.135-21.170; identical across all 36 counties. Verify against https://www.courts.oregon.gov/services/fees/Pages/default.aspx

Fee waiver (ORS 21.682) and in forma pauperis (ORS 20.140) apply identically across counties.

eFiling

All Oregon circuit courts use OJD File and Serve (Tyler Tech) statewide. Document codes are the same statewide; the filing user picks the county at filing.

  • Portal: https://oregon.tylertech.cloud/
  • Self-help page: courts.oregon.gov/services/online/Pages/efile.aspx
  • Help line: (855) 642-9748 (Tyler Tech support)
  • File size: 25 MB per document; split larger filings

Mandatory arbitration

ORS 36.400 et seq. applies statewide. Every county uses the OJD arbitrator panel. The arbitration program differs slightly across counties in how arbitrators are assigned (random vs. party selection) — see the county's SLR Chapter 8.

Document set (typical for any Oregon county)

  1. Motion
  2. Memorandum in Support (if argument over 1 page)
  3. Supporting Declaration(s) with exhibits
  4. Proposed Order ("[PROPOSED]" in title)
  5. Notice of Hearing
  6. Certificate of Service
  7. Working copies (for motions over the local SLR threshold)

The set is the same statewide; the timing of when the Notice of Hearing is filed and the threshold for working copies vary by county SLR.

Scheduling email — generic county template

To:      [Civil Division / court coordinator / JA email]
Subject: Hearing Date Request — [Case Short Title],
         Case No. [Cause Number]

Civil Division:

I am [Counsel of record / Defendant, pro se] in [case short
title], Case No. [cause number], assigned to [Judge Name (if
known)].

I am requesting a hearing date for [Motion Title], to be filed
[date]. Estimated argument time: [X minutes].

Proposed dates:
   [Date 1]
   [Date 2]
   [Date 3]

If the Court prefers WebEx or telephone, please advise so I can
include the connection details on the Notice of Hearing.

Thank you,
[Name][, pro se / OSB #]
[Contact info]

References

  • references/county-courts-directory.md — full directory of all 36 Oregon counties, their seats, judicial districts, and contact numbers
  • references/filing-and-service.md — county-by-county quirks in filing and service practice

Oregon Case Deadlines

This skill computes deadlines in Oregon civil cases — when to answer, when to file or respond to motions, when to claim exemptions, when to appeal, and the statutes of limitations that bound new actions.

NOT LEGAL ADVICE. Verify every deadline against the current rule and statute. The legislature can amend ORCP and ORS without notice.

How time is computed in Oregon (ORCP 10)

ORCP 10 A — Computation:

  • Exclude the day of the triggering event (the day of service, the day of filing, the day of the order)
  • Include the last day of the period
  • If the last day falls on a Saturday, Sunday, or legal holiday, the period extends to the next business day

ORCP 10 B — Intermediate weekends and holidays:

  • Periods less than 7 days: exclude weekends and holidays
  • Periods of 7 days or longer: include weekends and holidays

ORCP 10 C — 3-day mail rule:

  • When service is by mail, 3 additional days are added to any prescribed response period
  • Applies only when the triggering act was service by mail; not if the triggering act was filing or order

Oregon legal holidays (ORS 187.010)

HolidayDate
New Year's DayJanuary 1
Martin Luther King, Jr. Day3rd Monday of January
Presidents' Day3rd Monday of February
Memorial DayLast Monday of May
JuneteenthJune 19
Independence DayJuly 4
Labor Day1st Monday of September
Veterans DayNovember 11
Thanksgiving Day4th Thursday of November
Christmas DayDecember 25

Observed-day rule (ORS 187.020):

  • Saturday holiday → observed on the preceding Friday
  • Sunday holiday → observed on the following Monday

Note: Oregon does NOT recognize the day after Thanksgiving as a statewide holiday (unlike Washington). Some Oregon counties may treat it as a courthouse closure day; verify locally.

Deterministic computation

Use the bundled scripts/case-calendar.py for date arithmetic:

# Compute the answer deadline — 30 calendar days from service
# on 2025-04-15
python3 plugins/or-court-docs/scripts/case-calendar.py \
  --from 2025-04-15 --rule answer-due

# Compute a custom deadline — 14 court days after a given date
python3 plugins/or-court-docs/scripts/case-calendar.py \
  --from 2025-04-15 --days 14 --mode court

# List all known rules
python3 plugins/or-court-docs/scripts/case-calendar.py --rules

The script encodes ORCP 10 A/B/C and ORS 187.010/.020 exactly, so the computation is deterministic.

Deadlines by procedural posture

Initial response (defendant)

TriggerDeadlineAuthority
Personal service in Oregon30 days from serviceORCP 7 C(2)
Service on Oregon resident outside Oregon30 daysORCP 7 C(2)
Service by publication30 days from completed publicationORCP 7 D(6)
Substituted service30 days from completed mailing (mailing follows the substituted delivery)ORCP 7 D(2)(b)
Motion under ORCP 21 in lieu of answer30 days; tolls answer until court rulesORCP 21 D

Motion practice timing

EventTimingAuthority
Motion to compel — meet-and-confer prerequisiteBefore filingORCP 46 A, local SLR
Motion to compel — response14 days (typical); check local SLRLocal SLR; default
Motion to dismiss — response14 daysLocal SLR; default
Motion to dismiss — reply7 daysLocal SLR; default
Summary judgment — motionAt least 60 days before trialORCP 47 C
Summary judgment — response20 days after service of motionORCP 47 C
Summary judgment — reply5 days after service of responseORCP 47 C
Summary judgment — hearingAt least 11 days after filing replyORCP 47 C
Motion to reconsider — filed"Reasonable time" — typically 10 daysORCP 64 / 71

Discovery

EventTimingAuthority
RFP response30 days (45 if served with summons)ORCP 43 B
RFA response30 days (45 if served with summons)ORCP 45 B
Deposition notice — party5 daysORCP 39 B
Deposition notice — non-party7 days (subpoena required)ORCP 39 B / 55
Discovery cutoff (typical)30 days before trial; case-schedule order may varyCase schedule

Post-judgment

EventTimingAuthority
Motion to set aside default"Reasonable time"; not exceeding 1 year for ORCP 71 B(1)–(3)ORCP 71 B
Motion to amend judgment10 days after entry of judgmentORCP 64
Notice of Appeal — circuit to Court of Appeals30 days from judgment entryORS 19.255 / ORAP 5.30
Garnishment Challenge / Exemption30 days from notice of writORS 18.700 et seq.
Bank levy challenge30 days from noticeORS 18.700+
Statement of attorney fees and costs14 days from judgmentORCP 68 C(2)
Cost bill14 days from judgmentORCP 68 C
Writ of garnishment issuanceAfter judgment is final and writ issuedORS 18.605

Arbitration

EventTimingAuthority
Arbitration hearingTypically 90 days from assignmentPer SLR / arbitrator
Trial de novo request20 days from arbitration awardORS 36.425
Trial de novo fee-shifting cutoffAt trial de novo conclusionORS 36.425(5)

Statutes of limitations — Oregon

Contract and debt

Claim typeSOLAuthority
Written contract6 yearsORS 12.080(1)
Open account / credit card6 yearsORS 12.080(2)–(4)
Oral contract6 yearsORS 12.080(1)
Statutory liability (UTPA, ORS 697, etc.)6 years (general)ORS 12.080(2)

Tort

Claim typeSOLAuthority
Personal injury (most)2 yearsORS 12.110
Fraud / mistake2 years from discovery; 10-year reposeORS 12.110(1)
Defamation1 yearORS 12.120(2)
Malicious prosecution1 yearORS 12.140

Real property

Claim typeSOLAuthority
Real property10 yearsORS 12.040
Quiet title10 yearsORS 12.040

Judgments

EventLimitAuthority
Judgment lifespan10 years from entry, renewableORS 18.182
Judgment renewalBefore original 10-year period expiresORS 18.182

Consumer protection

Claim typeSOLAuthority
UTPA private action1 year from discovery; 6-year reposeORS 646.638(6)
FDCPA private action1 year from violation15 USC § 1692k(d)
FCRA private action2 years from discovery; 5-year repose15 USC § 1681p
TILA private action1 year from violation (rescission: 3 years)15 USC § 1640(e); § 1635(f)

Collection agency / ORS 697

Claim typeSOLAuthority
ORS 697.058 prohibited practices6 years (statutory)ORS 12.080(2)
ORS 697.085 civil action6 yearsORS 12.080(2)

The 3-day mail rule, in practice

ORCP 10 C adds 3 days to any response period when service was by mail. This rule trips up many practitioners. Examples:

  • Discovery response served by mail on April 1: response due 30 + 3 = 33 days from April 1, i.e., May 4
  • Discovery response served by eService on April 1: response due 30 days, i.e., May 1 (no mail-rule addition; eService is electronic, not mail)
  • Motion served by mail on April 1: response due [local SLR period] + 3 days from April 1

eService through File and Serve does NOT trigger the 3-day mail rule. The 3-day rule applies only to actual paper mail under ORCP 9 B (USPS).

Computing examples

Example 1: Answer to complaint

Defendant is personally served on Wednesday, April 15, 2025.

ORCP 7 C(2) — 30 calendar days to answer.

Day 1 = April 16 (day after service). 30 days from April 15, counting day 1 = April 16, is May 15.

May 15 is a Thursday — a business day. Answer due May 15, 2025.

Example 2: Motion to compel with meet-and-confer

Discovery response served by eService on Friday, May 16, 2025. The response objects to RFPs 3, 5, 6.

ORCP 43 B — 30 days. No mail-rule addition (eService).

May 16 + 30 days = June 15. June 15 is a Sunday → next business day. Original response was timely; no extension to the requesting party.

Defendant decides to meet and confer. Meet-and-confer letter sent Monday, May 19, 2025. Reasonable response window of 14 days = Monday, June 2, 2025.

If opposing party fails to supplement by June 2, motion to compel can be filed.

Example 3: SJ schedule

Trial date: Monday, August 25, 2025.

ORCP 47 C — motion filed at least 60 days before trial.

60 days before August 25 = June 26 (Thursday). SJ motion must be filed by June 26, 2025.

Response due 20 days after service of motion. If motion was filed and served on June 26, response due July 16, 2025.

Reply due 5 days after service of response. If response was served on July 16, reply due July 21, 2025.

Hearing must be at least 11 days after filing of reply. If reply was filed July 21, hearing must be on or after August 1, 2025.

(Use the calendar script to verify and adjust for any intervening holidays.)

Example 4: Notice of Appeal

Judgment entered Tuesday, June 3, 2025.

ORS 19.255 — 30 days from entry of judgment to file Notice of Appeal.

June 3 + 30 days = July 3 (Thursday — Independence Day-1). July 3 is a business day; July 4 is a holiday.

Notice of Appeal due July 3, 2025. (If June 3 were a Friday, the deadline could fall on a weekend and extend.)

Common deadline-computation mistakes

MistakeConsequence
Including the day of the triggering eventOff-by-one; missed deadline
Forgetting the 3-day mail ruleShort-served response is treated as timely; surprise
Adding 3 days for eServiceNot required; can backfire if you over-rely
Counting weekends in periods < 7 daysOver-counts; ORCP 10 B excludes intermediate weekends for short periods
Forgetting to extend if last day is weekend/holidayOff-by-one; missed deadline
Confusing court days and calendar days"Days" in ORCP is calendar unless specified court
Confusing observe-day ruleSaturday Independence Day observed on prior Friday; Sunday observed on following Monday

When in doubt, file early

When the deadline is close, file early. Late filings can be fatal — ORCP 21 motions, Notice of Appeal, Motion to Vacate, etc., are all strict deadlines and missing them is not curable through the doctrine of substantial compliance.

For pro se filers: build a buffer. Aim for filings 5–7 days before the deadline; that leaves room for technology issues, clerk rejection, or last-minute corrections.

References

  • scripts/case-calendar.py — deterministic date arithmetic
  • or-law-references/references/civil-rules.md — ORCP 10 verbatim
  • or-law-references/references/or-ors-debt/ORS-12.md (when populated) — verbatim ORS 12 text on SOLs
  • or-law-references/references/or-ors-debt/ORS-187.md (when populated) — verbatim ORS 187 holiday list

Oregon Discovery — Procedural Reference

This skill covers the matter-neutral procedural framework for discovery in Oregon civil practice. The full ORCP text lives in or-law-references/references/civil-rules.md. For subject- matter-specific request banks (e.g., debt-buyer chain-of-title RFPs), compose with the relevant subject-matter skill.

NOT LEGAL ADVICE. Verify each rule and the local SLR before drafting.

Oregon's distinctive discovery model — no interrogatories

The single most important fact about Oregon civil discovery: Oregon does NOT have written interrogatories under the ORCP as a matter of right.

Available discovery tools:

  • Depositions — ORCP 39 (oral) and ORCP 40 (written questions; rare)
  • Requests for production — ORCP 43
  • Physical / mental examination — ORCP 44 (court order required)
  • Requests for admission — ORCP 45
  • Subpoenas for non-parties — ORCP 55

Why no interrogatories? Oregon's Council on Court Procedures historically rejected the FRCP 33 model on the theory that written interrogatories generate boilerplate disputes without producing meaningful information; depositions and RFPs are sufficient.

Practical implications:

  • A party in Oregon cannot serve written interrogatories to the opposing party as a matter of right
  • The court can order interrogatories by stipulation, in a mandatory arbitration proceeding (under the arbitrator's discretion), or by special order in unusual cases — but this is rare
  • Pro se filers porting from Washington or federal practice often mis-serve "First Interrogatories" — these are unenforce- able in Oregon and will be objected to. The right tools are RFPs and short-form deposition.

ORCP 36 — General scope of discovery

The scope test, identical to FRCP 26(b)(1):

  • Relevance: relevant to a claim or defense
  • Proportionality: proportional to the needs of the case, considering (1) importance of the issues, (2) amount in controversy, (3) party's relative access, (4) party's resources, (5) importance of the discovery in resolving issues, (6) burden / expense vs. likely benefit
  • Reasonably calculated to lead to admissible evidence

Beyond the scope test, ORCP 36 sets:

  • ORCP 36 B(1): scope statement
  • ORCP 36 B(2): protected materials — privilege, work product, expert disclosures
  • ORCP 36 C: protective orders — limiting discovery on motion

ORCP 43 — Requests for production

The workhorse rule in Oregon discovery.

Mechanics

  • ORCP 43 A: Party may serve RFPs on any other party
  • ORCP 43 B: Response within 30 days (45 days if served with summons)
  • Form: Each request states a specific category of documents; the response either produces, identifies responsive documents, or objects with specific grounds

Drafting good RFPs

A well-drafted RFP is:

  • Specific: targets a defined category of documents, not "all documents related to the case"
  • Tied to a claim or defense: cites the relevance under ORCP 36 B(1) in a preamble if helpful
  • Bounded by time: "documents dated between [date] and [date]"
  • Bounded by party: "documents created, sent, received, or maintained by [party or entity]"

Example (well-drafted):

Request for Production No. 3: All documents constituting, referencing, or summarizing the original cardholder agreement between Defendant John Doe and Bank of America for account number ending in XXXX, including signature pages, incorporated terms and conditions, and any electronic acceptance records.

Example (poorly drafted):

Request for Production No. 3: All documents related to the account.

Common RFP objections (and how to overcome)

ObjectionResponse
OverbroadNarrow the temporal or party scope; or stand on the request and let the court rule
BurdensomeQuantify the actual burden; ORCP 36 proportionality is a balancing test
PrivilegedRequest a privilege log per ORCP 36 B(2); the bare assertion is insufficient
RelevanceCite the specific claim or defense the request relates to
Not in possession, custody, or controlVerify; "possession" includes documents the party can access by ordinary means
Trade secretPropose a protective order under ORCP 36 C
PrematureMany objections labeled "premature" are actually relevance — push back

ORCP 39 — Depositions

When and how

  • After action is commenced, any party may take depositions on notice (5 days for parties, 7 for non-parties)
  • Stenographic, audio, or video recording acceptable
  • Subpoena required for non-party depositions (ORCP 55)
  • ORCP 39 D limits to 7 hours per deposition (typical practice; verify current rule)

Limits

  • 10 depositions per side without leave (per ORCP 36 / practice)
  • Leave required for repeat deposition of same witness, or to depose a person already deposed in a related action

Use of depositions

  • ORCP 39 I governs use of deposition testimony at trial: party admission, impeachment, unavailable witness, etc.
  • ORCP 39 C governs recording — written transcript required for use as evidence; audio/video supplements

Pro se deposition practice

Pro se litigants can take depositions, but the mechanics (reservation of court reporter, subpoena issuance, recording agreements) are complex. Many pro se litigants substitute the deposition by written questions under ORCP 40 for simple factual depositions — slower but procedurally simpler.

ORCP 45 — Requests for admission

Mechanics

  • Party serves written requests for admission of facts or application of law to facts
  • Response within 30 days (45 if served with summons)
  • Failure to respond → deemed admitted (ORCP 45 B)
  • Response options: admit, deny, or state inability to admit or deny with specifics

Strategic use

RFAs are powerful in Oregon because:

  • They narrow the issues for trial
  • They establish foundational facts (e.g., "Plaintiff is a Delaware LLC", "the account was opened on [date]") without needing live testimony
  • The 30-day default-admission risk creates pressure to respond

Each RFA should be a single, simple fact — compound RFAs get partial denials that are hard to use. Example:

Request for Admission No. 5: Admit that Plaintiff is a Delaware limited liability company.

NOT:

Request for Admission No. 5: Admit that Plaintiff is a Delaware LLC organized in 2017 with its principal place of business in New Jersey and that it filed a Foreign LLC Registration in Oregon on April 1, 2024.

The compound form invites the response "Admitted in part, denied in part" with no usable narrowing of issues.

Withdrawal of admissions (ORCP 45 C)

  • Court may permit withdrawal on motion if the presentation of the merits will be subserved and the requesting party is not prejudiced
  • High bar; planned admissions and considered denials are preferred to last-minute withdrawal motions

Meet and confer

Mandatory under ORCP 46 A — and under most local SLRs (e.g., Multnomah SLR 5.045 / Washington Co SLR 5.046).

The meet-and-confer:

  • Identifies the specific issue (e.g., "RFP No. 3 — Plaintiff's objection on grounds of burden")
  • Records the parties' positions
  • Documents the inability to resolve

Sample meet-and-confer email

To:      [opposing counsel]
Subject: Meet and Confer — Discovery Dispute, Case No. 25CV12345

Counsel:

I am writing to meet and confer under ORCP 46 A (and Multnomah
SLR 5.045) regarding the discovery responses you served on
[date]. Specifically:

1.  RFP No. 3 (cardholder agreement) — your objection on
    grounds of burden. We disagree because [reasons]. We
    request that you supplement the response within 14 days,
    by [date]. If you cannot, please let us know whether the
    burden can be addressed by [proposed alternative —
    sampling, time-limited subset, etc.].

2.  RFP No. 5 (assignment schedule) — your objection on
    grounds of relevance. We disagree because [reasons]. We
    request supplementation within 14 days.

3.  RFP No. 6 (account history) — your objection on grounds
    of privilege. The bare assertion is insufficient under
    ORCP 36 B(2). Please provide a privilege log identifying
    each document withheld within 14 days.

If we cannot resolve these by [date], we will move to compel
under ORCP 46 A.

I am available by phone at [number] to discuss before [date].
Please let me know a good time.

Best,
[Name][, pro se]

The follow-up email confirming the call (and stating the opposing party's position) is what the meet-and-confer certification recites.

Motion to compel (ORCP 46 A)

Prerequisites

  • A specific discovery request was served
  • The opposing party responded with objections OR failed to respond
  • The moving party met and conferred (or attempted to)
  • The conference did not resolve the dispute

Required content of the motion

  1. Identification of the specific request at issue
  2. The opposing party's response (or non-response)
  3. Statement of why the response is deficient
  4. Meet-and-confer certification (UTCR / local SLR)
  5. Statement of relief — order compelling response, fees under ORCP 46 A(4)(a)

Fee-shifting (ORCP 46 A(4)(a))

Mandatory if the motion is granted, unless the opposing party's failure was "substantially justified" or other circumstances make an award unjust.

The fee award is in addition to whatever sanctions (ORCP 46 B) the court may impose. Track time spent on the motion — a fee petition under ORCP 68 follows.

Drafting the meet-and-confer certification

In Multnomah / Washington County (and many other counties):

                CERTIFICATION OF MEET AND CONFER
                  (Multnomah SLR 5.045 / ORCP 46 A)

Pursuant to Multnomah SLR 5.045 and ORCP 46 A, counsel for
Defendant certifies that:

1.  On [date 1], Defendant served First Requests for Production
    Nos. 1–6 on Plaintiff.

2.  On [date 2], Plaintiff served Responses, objecting on
    grounds of [grounds] without producing responsive documents.

3.  On [date 3], Defendant sent a meet-and-confer letter to
    Plaintiff (Exhibit 3) identifying the specific objections,
    explaining Defendant's position, and requesting
    supplementation within 14 days.

4.  On [date 4], Plaintiff responded (Exhibit 4), declining to
    supplement.

5.  The parties have been unable to resolve the discovery
    dispute and are at impasse.

Defendant therefore respectfully requests an order compelling
production under ORCP 46 A.

Protective orders (ORCP 36 C)

A party from whom discovery is sought may move for a protective order to:

  • Forbid the discovery
  • Limit the scope
  • Require performance at a different time or place
  • Restrict who may attend
  • Seal the discovery materials

The standard: good cause. The court balances the burden against the need.

Discovery in mandatory arbitration

If the case is in ORS 36.400 mandatory arbitration, discovery is limited to what the arbitrator's rules permit. Some arbitrators allow interrogatories by stipulation; most rely on ORCP 43 RFPs and short depositions.

If discovery disputes arise in arbitration, motion to the arbitrator, not the circuit judge. The circuit judge hears disputes about the arbitration process (e.g., arbitrator disqualification), not substantive discovery.

Subject-matter request banks

This skill is matter-neutral. For pre-built request banks:

  • Debt-buyer chain of title: see or-consumer-debt/ references/rfp-debt-buyer.md and rfa-debt-buyer.md
  • Landlord-tenant (future): would live in or-landlord- tenant/references/
  • Personal injury (future): would live in or-personal- injury/references/

References

  • references/meet-and-confer.md — full meet-and-confer protocol with sample emails and call-log templates
  • references/objection-responses.md — drafting responses to RFPs, including objection libraries

Draft an Oregon Declaration

Scaffold a new declaration that complies with UTCR 2.010 and ORCP 1 E. The declaration should be ready to fill in, sign, and file in support of a motion or other filing.

NOT LEGAL ADVICE. This skill scaffolds a court document as a drafting aid. The user — not the skill — is the declarant, chooses what facts to swear to, and signs the declaration. Verify every rule, deadline, and citation against current law before filing. Pair with substantive review by counsel where stakes warrant.

What this skill produces

A declaration with:

  1. Caption (court header, parties, case number, document title: "DECLARATION OF [NAME] IN SUPPORT OF [MOTION TITLE]")
  2. Salutation: "I, [Full Name], declare under penalty of perjury under the laws of the State of Oregon that the following is true and correct:"
  3. Numbered paragraphs of substantive content
  4. Verification clause (ORCP 1 E form): "I declare under penalty of perjury under the laws of the State of Oregon that the foregoing is true and correct."
  5. Date and place of execution ("DATED this ... Executed at [city], Oregon")
  6. Signature block
  7. Exhibit List (if exhibits)
  8. Exhibit cover pages

Inputs to ask the user

  • Caption: court / county / parties / case number
  • Declarant name and role: who is signing? (party, witness, expert, etc.)
  • Supporting motion: what motion does this declaration support? (the document title incorporates this)
  • Personal-knowledge facts: what facts is the declarant swearing to?
  • Exhibits: list of documents that go with the declaration

Anatomy of a declaration

Salutation (top of body)

I, John Doe, declare under penalty of perjury under the laws
of the State of Oregon that the following is true and
correct:

This is the ORCP 1 E form. Some practitioners prefer the shorter:

I, John Doe, hereby declare under penalty of perjury the
following:

Either is acceptable. The ORCP 1 E form is cleaner.

Numbered paragraphs

Each paragraph contains one factual point. Number with bold Arabic numerals followed by a period and tab:

1.  Identity. I am the Defendant in the above-captioned
    action. I am 42 years old, an Oregon resident, and I make
    this Declaration in support of Defendant's Motion to
    Compel under ORCP 46 A.

2.  Personal knowledge. The facts stated in this Declaration
    are based on my personal knowledge, except where I
    explicitly state otherwise.

3.  Service of First Requests for Production. On April 1,
    2025, I served First Requests for Production Nos. 1–6 on
    Plaintiff's counsel via File and Serve. A true and
    correct copy of the Requests is attached as Exhibit 1.

4.  Plaintiff's Responses. On May 1, 2025, I received
    Plaintiff's Responses via File and Serve. Plaintiff
    objected on grounds of "relevance, burden, and
    possession" and did not produce documents responsive to
    Requests Nos. 3, 5, and 6. A true and correct copy of
    Plaintiff's Responses is attached as Exhibit 2.

5.  Meet-and-confer letter. On May 10, 2025, I sent
    Plaintiff's counsel a meet-and-confer letter identifying
    the objections and requesting supplementation. A true
    and correct copy is attached as Exhibit 3.

6.  Phone conference. On May 14, 2025, I spoke with
    Plaintiff's counsel by phone for approximately 30
    minutes. I memorialized the call by email the same day;
    a true and correct copy of that email is attached as
    Exhibit 4.

7.  Plaintiff's position. As of the date of this Declaration,
    Plaintiff has not supplemented as to Requests Nos. 3, 5,
    and 6. Plaintiff maintains its objections.

8.  Damages from non-production. Without these documents, I
    cannot evaluate whether Plaintiff has standing to bring
    this action.

Verification clause (end of body, before signature)

I declare under penalty of perjury under the laws of the
State of Oregon that the foregoing is true and correct.

Date and place

DATED this ____ day of ___________, 20__.

Executed at Portland, Oregon.

If executed outside Oregon, change to:

Executed at [City, State].

(28 USC § 1746 form requires identifying the state.)

Signature block

______________________________________
JOHN DOE
Defendant, pro se
[Address]
[Phone]
[Email]

ORCP 1 E — declarations in lieu of affidavits

ORCP 1 E: A "declaration under penalty of perjury" in the prescribed form may be used in lieu of a notarized affidavit. The acceptable form:

"I hereby declare that the above statement is true to the best of my knowledge and belief, and that I understand it is made for use as evidence in court and is subject to penalty for perjury."

OR the shorter:

"I declare under penalty of perjury under the laws of the State of Oregon that the foregoing is true and correct."

Either form is accepted statewide. Most pro se filers use the shorter form.

OEC 602 — Personal knowledge

Under OEC 602, the declarant must have personal knowledge of every stated fact, OR must specify the basis for belief.

If the declarant is testifying about facts they did not personally observe, say so:

9.  Reliance on records. The amounts and dates in
    paragraphs 3–6 are derived from my review of [source —
    bank statements, invoices, etc.]. I personally
    reviewed these records on [date]; true and correct
    copies are attached as Exhibits 5 and 6.

A declaration that includes facts beyond the declarant's personal knowledge, without specifying the basis, is subject to objection under OEC 602 and may be struck on motion under ORCP 47 D (for SJ practice) or its analog.

Exhibits

For declarations with exhibits, follow these conventions:

  • Number them (Exhibit 1, Exhibit 2, ...) — Oregon convention
  • Reference each exhibit by number in the paragraph introducing it
  • Authenticate each exhibit: "A true and correct copy is attached as Exhibit [N]"
  • List all exhibits on an Exhibit List page after the signature block
  • Each exhibit gets a cover page ("EXHIBIT [N]" centered, with a short italic caption)

See or-statewide-format/references/exhibit-handling.md for the full exhibit-handling guide.

Declarations vs. motions — drawing the line

Declarations contain sworn facts. Motions contain argument.

A common mistake: putting argument in the declaration.

❌ Wrong (in the declaration):

Plaintiff is clearly a debt buyer that doesn't have proper chain of title and is trying to mislead the Court.

This is argument. It belongs in the motion, not the declaration.

✅ Right (in the declaration):

  1. Plaintiff's status. Based on my review of the public filings of [Plaintiff entity name] with the Oregon Secretary of State (Exhibit 5), Plaintiff is a debt-buying entity that purchases charged-off accounts. Plaintiff's Complaint alleges it "acquired" my account through an "assignment" but has not produced any document evidencing that assignment in response to Requests for Production.

The facts are sworn; the characterization ("clearly trying to mislead") is omitted. The motion can argue the characterization based on these facts.

Declarations and the OEC 803(6) business-records pattern

For declarations supporting business records under OEC 803(6) (the analog to FRE 803(6)), the declarant should be a "custodian or other qualified witness" attesting to:

  1. The record was made at or near the time of the events
  2. The record was made by, or from information transmitted by, a person with knowledge
  3. The record was kept in the course of regularly conducted business activity
  4. It was the regular practice of the business to make such records

This is the foundation pattern for OEC 902(11) certified business records.

For a debt-buyer plaintiff's declaration attempting to authenticate the original creditor's records, the declaration typically fails because the declarant is the debt buyer's custodian, not the original creditor's. See or-consumer-debt/ references/evidence-debt-buyer.md for the foundational challenges.

Layered composition

This skill ALWAYS composes with:

  • or-statewide-format — caption, format, signature block, exhibits

It typically composes with:

  • or-pro-se — for pro se declarants
  • or-draft-motion — the declaration usually accompanies a motion
  • or-multcc / or-wccc / or-county-courts — the court header reflects the venue

Quality checks

Before filing:

  • or-quality-check — format pass
  • or-fact-check — verifies that the declaration's facts are consistent with the motion and any exhibits

Common pitfalls

PitfallConsequence
Missing the perjury clauseDeclaration is invalid; may need to re-execute
Argument mixed in with factsSubject to objection; weakens both motion and decl
Facts beyond personal knowledge without basisOEC 602 objection
Wrong jurisdiction in salutation ("California" / "Washington")Invalid form
Lettered exhibits (A, B, C)Wrong convention for Oregon
Static date in the bodyUse fill-in blanks for handwritten date
No exhibit listDisorganized record; judge can't navigate

Cross-references

  • or-statewide-format/references/templates/declaration.md — full template
  • or-statewide-format/references/exhibit-handling.md — exhibit conventions
  • or-pro-se/references/pro-se-drafting-framework.md — drafting principles
  • or-draft-motion — companion motion
  • or-law-references/references/evidence-rules.md — OEC references

Draft an Oregon Motion + Supporting Memorandum

Scaffold a motion and companion memorandum that complies with UTCR 2.010, ORCP / UTCR statewide motion practice, and the pro-se drafting framework.

NOT LEGAL ADVICE. This skill scaffolds a court document as a drafting aid. The user — not the skill — chooses the motion type, theory of relief, and strategy. Verify every rule, deadline, and citation against current law before filing. Pair with substantive review by counsel where stakes warrant.

What this skill produces

A motion with the following sections, ready for filling in:

  1. Caption (court header, parties, case number, document title)
  2. MOTION — short, declaratory: "Pursuant to ORCP [N], [party] respectfully moves the Court for an order [relief]."
  3. MEMORANDUM — sections I–VII (pro-se drafting framework):
    • I. Relief Requested
    • II. Statement of Facts
    • III. Statement of Issues
    • IV. Evidence Relied Upon
    • V. Authorities
    • VI. Argument
    • VII. Conclusion
  4. Signature block
  5. Certificate of Service

Inputs to ask the user

  • Court / county: Multnomah? Washington Co? Other?
  • Case number: e.g., 25CV12345
  • Caption: Plaintiff / Defendant party names
  • Motion type: dismiss (ORCP 21 A(?)), compel (ORCP 46), SJ (ORCP 47), vacate (ORCP 71), strike (ORCP 21 E), etc.
  • The procedural authority: which ORCP / ORS / UTCR / SLR section is being invoked
  • The relief requested: specifically, what should the court order?
  • Pro se or counsel?: affects signature block
  • Estimated argument time: 10, 15, 20, 30 minutes
  • Hearing mode: in-person, WebEx, telephone (per assigned court's standing order)

The pro-se drafting framework (in detail)

I. Relief Requested (one paragraph)

What specifically the court should order. Bullet or sub-letter the elements:

I.  RELIEF REQUESTED

    Defendant asks the Court to enter an order:
    (a) compelling Plaintiff to produce documents responsive
        to Requests Nos. 1–6 by [date certain];
    (b) overruling Plaintiff's objections; and
    (c) awarding Defendant reasonable expenses incurred in
        making this Motion under ORCP 46 A(4)(a).

II. Statement of Facts (numbered paragraphs)

Each fact is a short sentence. Each is cited to the supporting Declaration paragraph or Exhibit.

II. STATEMENT OF FACTS

    1.  Plaintiff filed the Complaint on January 14, 2025.
        (Decl. ¶ 1.)

    2.  On April 1, 2025, Defendant served First Requests
        for Production. (Decl. ¶ 2; Ex. 1.)

    3.  On May 1, 2025, Plaintiff served Responses,
        objecting on grounds of [grounds] without producing
        responsive documents. (Decl. ¶ 3; Ex. 2.)

    4.  ...

Keep facts to one short sentence each. Multi-clause sentences in fact statements are harder for the judge to follow.

III. Statement of Issues (yes-or-no questions)

1–3 yes-or-no questions the court must answer to rule on the motion:

III. STATEMENT OF ISSUES

     1. Whether documents proving the chain of title from
        the original creditor to a debt-buyer plaintiff are
        within ORCP 36 B(1) scope when the defendant denies
        the existence of the account.

     2. Whether Plaintiff's "possession" objection is valid
        when Plaintiff alleges it owns the account.

     3. Whether fee-shifting under ORCP 46 A(4)(a) is
        mandatory given Plaintiff's failure to produce was
        "without substantial justification".

Each issue should be answerable yes/no. Avoid open-ended "whether the Court should..." formulations.

IV. Evidence Relied Upon (list)

The supporting record:

IV. EVIDENCE RELIED UPON

    - Declaration of John Doe, filed herewith
    - Exhibit 1: First Requests for Production
    - Exhibit 2: Plaintiff's Responses and Objections
    - Exhibit 3: Meet-and-confer correspondence
    - Court file (Complaint, Answer)

V. Authorities (list)

Rules, statutes, cases:

V.  AUTHORITIES

    - ORCP 36 B(1) — scope of discovery
    - ORCP 43 — requests for production
    - ORCP 46 A — motion to compel
    - ORCP 46 A(4)(a) — mandatory fee-shifting
    - Multnomah SLR 5.045 — meet-and-confer
    - Phillips v. Beaverton Aluminum Co., 314 Or App 257,
      498 P3d 814 (2021)

VI. Argument (organized by issue)

Each issue gets its own subsection with a bold lead-in heading:

VI. ARGUMENT

    A.  The documents are within ORCP 36 B(1) scope.

        [2–3 paragraphs. Cite the rule, cite the facts, draw
         the conclusion.]

    B.  Plaintiff's "possession" objection contradicts its
        Complaint.

        [2–3 paragraphs.]

    C.  Fee-shifting is mandatory under ORCP 46 A(4)(a).

        [2–3 paragraphs.]

VII. Conclusion (one paragraph)

Restate the relief:

VII. CONCLUSION

     For the foregoing reasons, Defendant respectfully
     requests entry of the Proposed Order filed herewith.

Motion-type quick reference

Motion to dismiss

Sub-ruleUse when
ORCP 21 A(1)No subject-matter jurisdiction
ORCP 21 A(2)No personal jurisdiction
ORCP 21 A(3)Improper venue
ORCP 21 A(4)Insufficient summons
ORCP 21 A(5)Insufficient service
ORCP 21 A(6)Not real party in interest
ORCP 21 A(7)Failure to join party
ORCP 21 A(8)Failure to state ultimate facts
ORCP 21 A(9)Pendency of another action
ORCP 21 EMotion to strike

Motion to compel discovery

  • Authority: ORCP 46 A
  • Prerequisite: meet-and-confer certification (UTCR / local SLR)
  • Mandatory fee-shifting: ORCP 46 A(4)(a)

Motion for summary judgment

  • Authority: ORCP 47
  • Timing: 60 days before trial; 20 days response; 5 days reply; 11 days before hearing
  • Standard: no genuine issue of material fact + entitled to judgment as a matter of law

Motion to vacate

  • Authority: ORCP 71 B (grounds 1–6)
  • Deadline: reasonable time; 1 year for grounds (1)–(3)
  • Show: ground + diligence + meritorious defense + lack of prejudice

Motion for reconsideration

  • Authority: ORCP 64 (or analogous under recent rule development; verify current)
  • Deadline: 10 days from judgment

Motion for default

  • Authority: ORCP 69
  • For when defendant fails to answer in 30 days

Motion for continuance

  • Authority: UTCR 6.030
  • Show: good cause

Anti-SLAPP motion

  • Authority: ORS 31.150
  • Show: claim arises from protected expression; plaintiff fails to show probability of prevailing

Oregon-specific drafting notes

Cite the rule first in the Motion

The Oregon judge expects to see the procedural authority on the first line of the Motion:

Pursuant to ORCP 46 A, Defendant moves the Court for an
order compelling Plaintiff to produce ...

NOT: "This Court has the power to compel..."

Use exact ORCP subsection notation

ORCP 21 A(8), not ORCP 21(A)(8). Capital letters separated by spaces, with parenthesized lower-case sub-elements.

Oral argument designation

UTCR 5.050 requires noting whether oral argument is requested. Format on the document title:

DEFENDANT'S MOTION TO COMPEL UNDER ORCP 46 A
(ORAL ARGUMENT REQUESTED — 20 MINUTES)

Some local SLRs require the oral-argument request in a separate Notice of Hearing rather than the document title. Check or-multcc / or-wccc / or-county-courts.

Mandatory arbitration

If the case is in ORS 36.400 mandatory arbitration, motions go to the arbitrator, not the judge. Title accordingly:

DEFENDANT'S MOTION TO COMPEL UNDER ORCP 46 A
(IN ARBITRATION PROCEEDING UNDER ORS 36.400)

Meet-and-confer (discovery motions)

Multnomah SLR 5.045 / Washington Co SLR 5.046 / other county SLRs require a meet-and-confer certification. Include it in Section II (Facts) or as a separate Certification at the end.

Page count

Target 4–6 pages for the memorandum. Anything longer should split fact narrative into the declaration and keep the memo tight.

Layered composition

This skill ALWAYS composes with:

  • or-statewide-format — caption, fonts, margins, footer, exhibits
  • The relevant court skill — or-multcc, or-wccc, or or-county-courts — for local motion practice

It typically composes with:

  • or-pro-se — pro-se drafting framework details, pro se signature block, service protocol
  • or-draft-declaration — to draft the supporting declaration
  • or-draft-order — to draft the proposed order
  • or-draft-note — to draft the Notice of Hearing

For motion-type-specific guidance:

  • or-discovery — for motions to compel
  • or-post-judgment — for motions to vacate, garnishment- related motions
  • or-first-30-days — for ORCP 21 motions in initial response

Output

The skill produces a Markdown scaffold of the motion. The user fills in:

  • Specific facts (with declaration citations)
  • Specific issues
  • Specific argument
  • Cites the user has verified

Optionally, or-statewide-format/references/docx-generation.md shows how to convert the Markdown to .docx for filing.

Quality checks

After scaffolding, run:

  • or-quality-check — format pass (UTCR 2.010 compliance)
  • or-fact-check — citation and consistency pass

Before filing.

Cross-references

  • or-statewide-format — caption + UTCR 2.010
  • or-statewide-format/references/templates/motion-with-memo.md — full scaffold template
  • or-pro-se/references/pro-se-drafting-framework.md — Parker drafting principles
  • or-multcc / or-wccc / or-county-courts — local motion practice

Draft an Oregon Notice of Hearing

Scaffold the scheduling form that places a motion on the court's calendar. The Notice of Hearing is Oregon's analog to Washington's "Note for Motion Docket".

NOT LEGAL ADVICE. This skill scaffolds a scheduling form as a drafting aid. The user — not the skill — chooses the motion, the date requested, and the relief sought. Verify every rule, deadline, and local-rule requirement before filing. Pair with substantive review by counsel where stakes warrant.

Terminology: Oregon practice calls this a Notice of Hearing (or "Notice of Hearing on Motion"). Some practitioners coming from Washington may say "note for motion docket" — this skill responds to both but produces the Oregon-correct form.

When required

Most Oregon circuit courts require a Notice of Hearing to be filed and served before a motion can be heard. Some judges allow ex-parte requests to the judicial assistant in lieu of a formal Notice — check the assigned judge's standing order.

Local-rule timing:

  • Multnomah SLR 5.015: Notice filed within 3 business days of JA confirming the date
  • Washington Co (OR) SLR 5.045: Notice filed simultaneously with the motion
  • Other counties: per local SLR; usually filed simultaneously with or shortly after the motion

What this skill produces

A single-page Notice of Hearing with:

  1. Caption (court header, parties, case number, document title: "NOTICE OF HEARING ON [MOTION TITLE]")
  2. Hearing details panel in the right column of the caption: date, time, courtroom or WebEx, mode, judge
  3. Notice text identifying the motion, the date and time, the location, and the connection information for remote hearings
  4. Oral argument designation (if requested)
  5. Signature block
  6. Certificate of Service

Inputs to ask the user

  • Caption: court / county / parties / case number
  • Motion title: the title of the motion being noticed
  • Hearing date: confirmed by the JA / Civil Division
  • Hearing time: morning or afternoon block
  • Mode: in-person, WebEx, telephone
  • Courtroom / connection info: room number for in-person; WebEx URL / meeting ID for remote
  • Assigned judge: Hon. [Name]
  • Estimated argument time: e.g., 20 minutes

Template

            IN THE CIRCUIT COURT OF THE STATE OF OREGON
                  FOR THE COUNTY OF MULTNOMAH

VELOCITY INVESTMENTS, LLC,      │   Case No. 25CV12345
                                │
     Plaintiff,                 │   NOTICE OF HEARING ON
                                │   DEFENDANT'S MOTION TO
     v.                         │   COMPEL PRODUCTION OF
                                │   DOCUMENTS UNDER ORCP 46 A
JOHN DOE,                       │
                                │   HEARING: [Date] at [Time]
     Defendant.                 │   PLACE: Courtroom [#] /
                                │   WebEx (link below)
                                │   BEFORE: Hon. [Judge]
                                │   MODE: [In person / WebEx]
                                │   ORAL ARGUMENT: [time
                                │   estimate]
────────────────────────────────────────────────────────────

TO:  Plaintiff Velocity Investments, LLC and its counsel of
     record [Name, OSB #, Address, Email]

PLEASE TAKE NOTICE that Defendant's Motion to Compel
Production of Documents Under ORCP 46 A, filed [date], will
be heard before the Honorable [Judge Name], Department /
Courtroom [#] of the Circuit Court of the State of Oregon
for the County of Multnomah, on:

       [DAY OF WEEK], [MONTH DAY], 20[YY] at [TIME] [AM/PM]
       Hearing mode: [In person / WebEx]
       WebEx information: [URL or meeting ID and password]
       Estimated argument: [20 minutes]

The hearing was reserved with the Judicial Assistant to the
Hon. [Judge Name] on [date]; confirmation is attached as
Exhibit 1.

Defendant respectfully requests oral argument under UTCR
5.050.

DATED this ____ day of __________, 20__.

______________________________________
JOHN DOE
Defendant, pro se
[Address]
[Phone]
[Email]


                  CERTIFICATE OF SERVICE
[Per UTCR 1.090, served on Plaintiff and counsel via
File and Serve eService and by email to [opposing email]]

County-specific variations

Multnomah

Notice filed within 3 business days of JA confirmation. Filing through File and Serve, document code "Notice of Hearing".

The Multnomah courthouse is the Central Courthouse, 1200 SW 1st Avenue. Identify "Multnomah County Central Courthouse" in the Place line if helpful.

Washington Co (Oregon)

Notice filed simultaneously with the motion under WCCC SLR 5.045. The motion and Notice are uploaded together in File and Serve.

The courthouse is at 145 NE 2nd Avenue, Hillsboro.

Other counties

Per local SLR. The Notice typically:

  • Is filed simultaneously with or shortly after the motion
  • Identifies the assigned judge if one has been assigned
  • Reflects the mode confirmed by the court coordinator or Civil Division

Multiple motions noticed for the same hearing

If several motions are being argued together (e.g., a Motion to Compel and a Motion for Protective Order arising from the same discovery dispute), the Notice may list both. Format:

NOTICE OF HEARING ON DEFENDANT'S MOTION TO COMPEL UNDER
ORCP 46 A AND PLAINTIFF'S CROSS-MOTION FOR PROTECTIVE ORDER
UNDER ORCP 36 C

Stricken or continued hearings

If a previously noticed hearing is stricken or continued, file an amended Notice. Reference the prior Notice and explain the change:

NOTICE OF HEARING (AMENDED) ON DEFENDANT'S MOTION TO COMPEL

[Notice 1 of [date] is hereby AMENDED. The hearing
previously set for [old date] at [old time] is RESET as
follows:]

The same caption / signature / Certificate of Service apply.

Pro se notes

  • A pro se filer must use the same Notice format as counseled parties
  • The OSB# field is omitted on the signature block (pro se filers don't have an OSB#)
  • Email is acceptable for the contact email; use a stable email account that won't change during the litigation

Companion documents

A complete motion packet includes:

  1. Motion + Memorandum
  2. Supporting Declaration with exhibits
  3. Proposed Order ("[PROPOSED]" in title)
  4. Notice of Hearing (this skill)
  5. Certificate of Service

The Notice is the LAST document filed in time-sequence (after the JA has confirmed the date), unless the local SLR requires simultaneous filing.

Quality checks

Before filing the Notice:

  • or-fact-check — verify the hearing date, time, mode, courtroom, and connection info match the JA's confirmation
  • or-quality-check — UTCR 2.010 format pass

A Notice with the wrong date or wrong WebEx link is the most common pro se filing error and the most likely reason a hearing falls off the calendar.

Cross-references

  • or-statewide-format/references/templates/notice-of-hearing.md — full template
  • or-schedule-hearing — the email or call to reserve the date (precedes the Notice)
  • or-multcc/references/civil-motion-scheduling.md — Multnomah-specific
  • or-wccc/references/civil-motion-practice.md — Washington Co-specific
  • or-county-courts — other counties

Draft an Oregon Proposed Order

Scaffold a proposed order with findings and relief pre-filled, so the judge only needs to sign.

NOT LEGAL ADVICE. This skill scaffolds a court document as a drafting aid. The user — not the skill — chooses the findings, the relief, and the form of the order. Only a judge signs an order; this skill prepares the proposed form for the judge's consideration. Verify every rule, deadline, and citation against current law before filing. Pair with substantive review by counsel where stakes warrant.

What this skill produces

A proposed order with:

  1. Caption with [PROPOSED] bracket in the title
  2. Preamble identifying the motion and what the court has considered
  3. Findings (numbered, if appropriate)
  4. Order text ("IT IS HEREBY ORDERED")
  5. Numbered relief paragraphs (A, B, C, ...)
  6. Date and judge signature line
  7. Submitting attorney/party block
  8. Notice of Presentation or Approval as to Form

Inputs to ask the user

  • Caption: court / county / parties / case number
  • Motion being decided: title and filing date of the motion this order will resolve
  • Outcome: granted, denied, granted in part / denied in part, taken under advisement
  • Specific relief: the operative orders (produce by X, award fees of Y, vacate Z, etc.)
  • Findings: factual findings, if the order rests on factual determinations
  • Fee award: if a fee request, identify the statute and amount (or "to be determined by ORCP 68 C(2) Statement")
  • Submitting party: counsel or pro se

Template — Order Granting Motion

            IN THE CIRCUIT COURT OF THE STATE OF OREGON
                  FOR THE COUNTY OF MULTNOMAH

VELOCITY INVESTMENTS, LLC,      │   Case No. 25CV12345
                                │
     Plaintiff,                 │   [PROPOSED] ORDER GRANTING
                                │   DEFENDANT'S MOTION TO
     v.                         │   COMPEL PRODUCTION OF
                                │   DOCUMENTS UNDER ORCP 46 A
JOHN DOE,                       │
                                │
     Defendant.                 │
────────────────────────────────────────────────────────────

This matter came before the Court on Defendant's Motion to
Compel Production of Documents Under ORCP 46 A, filed
[date]. The Court has considered the Motion, the Memorandum
in support, the Declaration of John Doe and the Exhibits
thereto, Plaintiff's response (if any), and the records and
files of this action. The Court being fully advised in the
premises,

FINDS that:

1.  Defendant served First Requests for Production on April
    1, 2025.

2.  Plaintiff served Responses on May 1, 2025 objecting on
    grounds of "relevance, burden, and possession" without
    producing responsive documents to Requests Nos. 3, 5,
    and 6.

3.  Defendant met and conferred with Plaintiff on May 10
    and May 14, 2025 under ORCP 46 A and Multnomah SLR
    5.045. The parties were unable to resolve the discovery
    dispute.

4.  The documents requested in Requests Nos. 3, 5, and 6
    are within the scope of ORCP 36 B(1) — relevant to
    Plaintiff's claim and proportional to the needs of the
    case.

5.  Plaintiff's failure to produce was not substantially
    justified within the meaning of ORCP 46 A(4)(a).

THEREFORE, IT IS HEREBY ORDERED that:

A.  Defendant's Motion to Compel is GRANTED;

B.  Plaintiff shall produce all documents responsive to
    Requests for Production Nos. 3, 5, and 6 within 14
    calendar days of the date of this Order, or by
    ____________, 20__, whichever is sooner;

C.  Plaintiff's objections to Requests Nos. 3, 5, and 6 are
    OVERRULED;

D.  Defendant is awarded reasonable expenses, including
    attorney fees, incurred in making this Motion, pursuant
    to ORCP 46 A(4)(a). The amount of expenses and fees shall
    be determined upon Defendant's Statement of Attorney
    Fees and Costs filed under ORCP 68 C(2) within 14 days
    of this Order.

DATED this ____ day of __________, 20__.


                            _______________________________
                            CIRCUIT COURT JUDGE


Submitted by:
______________________________________
JOHN DOE
Defendant, pro se
[Address]
[Phone]
[Email]


Notice of Presentation:
This Order is being submitted to the Court without the
opportunity for opposing counsel to approve as to form,
pursuant to UTCR 5.100(2), because the Order tracks the
Court's [anticipated] ruling on this Motion.

— OR —

Approval as to Form:
______________________________________
[Plaintiff's Counsel Name, OSB # ______]
Attorney for Plaintiff Velocity Investments, LLC

Template — Order Denying Motion

[Caption with "[PROPOSED] ORDER DENYING DEFENDANT'S MOTION
TO COMPEL"]

This matter came before the Court on Defendant's Motion to
Compel...

FINDS that [findings supporting denial]:

THEREFORE, IT IS HEREBY ORDERED that:

A.  Defendant's Motion to Compel is DENIED;

B.  [Conditions, if any]

Template — Order Granting in Part / Denying in Part

A.  Defendant's Motion to Compel is GRANTED IN PART and
    DENIED IN PART as follows:

    1.  As to Requests Nos. 3 and 5, the Motion is GRANTED.
        Plaintiff shall produce within 14 days.

    2.  As to Request No. 6, the Motion is DENIED. Plaintiff's
        objection is sustained.

B.  ...

UTCR 5.100 — Order submission

UTCR 5.100 governs the mechanics of submitting orders:

  • (1) The party preparing the order must serve all parties at least 3 days before submission, unless service is excused
  • (2) The submitting party must state in a Notice of Presentation whether opposing parties have had the opportunity to approve as to form
  • (3) Opposing parties have 3 court days (in most courts) to object to the form
  • (4) After 3 court days without objection, the order may be signed
  • (5) Approval as to form is not required when the order tracks the court's ruling; the submitting party states this

Local SLRs (Multnomah SLR 5.100, Washington Co SLR 5.101) may modify the procedure.

Key drafting elements

"[PROPOSED]" bracket

Keep [PROPOSED] in the title until the judge signs. The clerk (or the prevailing party) strikes the bracket at signature time. Same convention for [STIPULATED] orders.

"IT IS HEREBY ORDERED"

The operative phrase. Without it, the document reads like a memorandum, not an order.

Numbered relief (A, B, C)

Each relief paragraph is one sentence. If a paragraph needs explanation, the explanation goes in the Findings section, not the ORDER section.

Date certain

Avoid open-ended deadlines:

❌ "Plaintiff shall produce promptly"

✅ "Plaintiff shall produce within 14 calendar days of the date of this Order, or by __________, 20, whichever is sooner"

The blank for the specific date is filled in when the judge signs (typically by adding 14 calendar days to the signature date).

Findings

If the order rests on factual determinations (default vacation, SJ, contempt, etc.), include findings. Findings let an appellate court understand the basis of the ruling.

If the order is purely procedural (e.g., compelling discovery), findings are optional but often helpful.

Fee award

When the order awards fees:

  • Reference the statute or rule (ORCP 46 A(4)(a), ORS 20.105, ORS 20.096, etc.)
  • State that the amount will be determined under ORCP 68 C(2) — the procedural mechanism for fee statements
  • Calendar the 14-day window for filing the Statement of Attorney Fees and Costs (ORCP 68 C(2))

Oregon-specific notes

OSB# on the submitting block

Counsel includes the OSB# (e.g., "OSB # 091234"). Pro se filers omit — they don't have an OSB#.

"v." between parties

In the caption. Not "vs."

Numbered exhibits

If the order references an exhibit, use the number (Exhibit 1, 2, 3 ...).

Pre-hearing vs. post-hearing orders

This skill drafts the pre-hearing proposed order — the one filed with the motion so the judge can sign on the bench.

For the post-hearing version (signed by the judge with bench modifications applied), see or-submit-order. The post-hearing workflow:

  1. Apply bench modifications to the proposed order (the agent strikes the [PROPOSED] bracket)
  2. Re-serve under UTCR 5.100 (3 days)
  3. Submit to chambers via the assigned judge's JA email

Composition

This skill ALWAYS composes with:

  • or-statewide-format — caption, format
  • The relevant court skill — for the court header and any local-rule particulars

It typically follows:

  • or-draft-motion — the motion this order would grant
  • or-draft-declaration — the supporting declaration

Quality checks

Before submitting:

  • or-fact-check — verifies the relief tracks what the motion requests; that dates, amounts, and party names are consistent
  • or-quality-check — UTCR 2.010 format pass

Common pitfalls

PitfallConsequence
Missing "[PROPOSED]" in titleOrder looks signed; clerk may reject
No "IT IS HEREBY ORDERED" phraseCourt treats as memorandum
Open-ended deadlinesInvites enforcement disputes
Inconsistent relief vs. motionCourt won't grant relief not requested
Missing fee authorityAward has no basis; may be reversed
Forgetting Notice of PresentationUTCR 5.100 violation; possible delay
Wrong judge's signature lineDifferent from the assigned judge

Cross-references

  • or-statewide-format/references/templates/proposed-order.md — full template
  • or-submit-order — post-hearing signed-order submission
  • or-draft-motion — companion motion
  • or-law-references/references/fees-and-costs.md — fee award statutes and ORCP 68 mechanics

Fact-Check Oregon Court Filings

Use this skill to verify Oregon court filings (or packets of filings) before filing. The agent runs four passes and outputs a report. The user reviews the report and accepts or rejects each suggested correction.

NOT LEGAL ADVICE. Fact-checking verifies the surface — it doesn't tell you whether the legal position is winning. Pair with substantive review by counsel where stakes warrant.

When to invoke

Before filing any of:

  • Motion (any type)
  • Memorandum in support
  • Declaration with exhibits
  • Proposed Order
  • Notice of Hearing
  • Answer with affirmative defenses and counterclaims
  • Brief on appeal

For a multi-document packet (motion + memo + decl + order + notice), invoke once and check the whole packet for cross- document consistency.

The four passes

Pass 1: Citation verification

Every cite in the filing resolves to a real source. The cite patterns:

  • Oregon cases: [Party] v. [Party], [vol] Or [page], [vol] P2d/P3d [page] ([year]) — verify against CourtListener
  • Court of Appeals: same pattern, Or App reporter
  • 9th Circuit / federal: F, F2d, F3d, F Supp, etc. — verify against CourtListener
  • Supreme Court: US, S Ct — verify against CourtListener
  • ORS: ORS [Ch].[section]([subsection]) — verify against oregonlegislature.gov
  • ORCP: ORCP [N] [Letter]([number]) — verify against counciloncourtprocedures.org
  • OEC: OEC [N]([number]) — verify against oregonlegislature.gov (ORS Ch. 40)
  • UTCR: UTCR [N].[NNN]([N]) — verify against courts.oregon.gov/rules/UTCR
  • Local SLR: [County] SLR [N].[NNN] — verify against the county's rules page
  • USC: [title] USC § [section]([sub]) — verify against uscode.house.gov
  • CFR: [title] CFR § [N].[NN] — verify against ecfr.gov

For each cite:

  1. Resolve: does the cite exist?
  2. Quote: if the filing quotes the source, does the quote match?
  3. Holding: if the filing relies on a case for a proposition, does the case actually stand for that proposition?
  4. Currency: has the case been overruled or distinguished? Has the statute been amended? Is the rule number still in use?

Use WebFetch against the canonical URLs in or-law-references/references/online-sources.md. Do not use other fetch mechanisms.

Common Oregon citation errors to flag
PatternError
Or. (with period)Oregon Style Manual uses Or without period
P.3d (with periods)Oregon style is P3d
U.S.C. (with periods)Oregon style is USC
vs.Oregon uses v.
Rule 12(b)(6) or CR 12(b)(6)Oregon uses ORCP 21 A(8)
Wn.2d or Wn. App.Washington reporter — wrong jurisdiction
CR 56Washington rule — Oregon is ORCP 47
KCDC or KCSCWashington courts — wrong jurisdiction
RCW [N.NN]Washington statutes — Oregon is ORS [N.NNN]
Lettered exhibits (A, B, C)Oregon convention is numbered
Exhibit A at page 5Should be Exhibit 1 at p. 5
Static "Page 5 of 12"Must use PAGE and NUMPAGES Word fields
Bluebook periods in federal citesOregon style omits

Pass 2: Internal consistency

Within a single document, do the following agree:

  • Caption case number = body case-number references
  • Caption party names = body party-name references
  • Document title in caption = document title at top of body = document title in footer
  • Hearing date in motion = hearing date in Notice of Hearing
  • Exhibit numbers referenced in body = exhibit numbers in Exhibit List
  • Dollar amounts consistent throughout (e.g., the judgment amount in caption matches the amount in the body and in the proposed order)
  • Date references consistent (e.g., "served on April 1, 2025" appears the same in every paragraph that references the service date)
  • Paragraph cross-references point to actual paragraphs (e.g., "see ¶ 4 above" verifies that ¶ 4 says what is implied)
  • Pin cites to exhibits and pages are accurate

Pass 3: Packet consistency

Across multiple documents in a single filing packet:

  • All captions are identical (same court header, same parties in same order, same case number)
  • All document titles match what the body actually contains (the Memorandum's title shouldn't say "Motion to Compel" if it accompanies a "Motion to Vacate")
  • Hearing date / location / mode identical across Motion, Memorandum, Notice of Hearing, Proposed Order
  • Exhibit numbers cross-referenced across documents (Motion ¶ 4 says "Decl. Ex. 2"; Declaration's Exhibit List must include Exhibit 2)
  • Signature blocks identical (name, role, address, phone, email all match across documents in the packet)
  • Service lists include the same parties in the same order

Pass 4: Sworn-vs.-argued consistency

The single most damaging fact-check failure: a motion argues a fact that contradicts what a declaration (sworn under penalty of perjury) says.

Example:

  • Declaration ¶ 4: "I received the validation notice on April 3, 2025."
  • Motion at p. 4: "Defendant received the validation notice on March 28, 2025."

These cannot both be true. Either the declaration is wrong (and the declarant has committed perjury) or the motion mis-states the record. Either way, opposing counsel will catch it and exploit it.

The fact-check pass identifies every assertion in the motion that purports to recite a fact, and locates the supporting paragraph in the declaration. Each pair is then compared.

Discrepancies are flagged with:

  • The motion language
  • The declaration language
  • A proposed correction (typically updating the motion to conform to the declaration, since the declaration is sworn)

Output format

The agent produces a report:

=== Fact-Check Report ===
Packet: [Motion to Compel + Memorandum + Declaration + Order +
         Notice of Hearing]
Date: [today]

Pass 1: Citation Verification
  [PASS] Buchler v. Oregon Corrections Div., 316 Or 499 (1993)
  [PASS] ORCP 46 A(4)(a)
  [WARN] State v. Smith, 250 Or App 1, 280 P3d 1 (2012)
         — Year verified; check that opinion is for the
         proposition cited (current cite supports holding on
         relevance; brief cites it for proportionality —
         consider Phillips v. Beaverton instead)
  [FAIL] Mattiza v. Foster, 311 Or 1, 803 P3d 723 (1990)
         — Parallel cite is P2d, not P3d (1990 case predates
         P3d series). Correct to "803 P2d 723"

Pass 2: Internal Consistency
  [PASS] Caption case number matches body
  [PASS] Document titles match
  [WARN] Motion ¶ 5 references Exhibit 3; Exhibit List
         only includes Exhibits 1 and 2. Either add Exhibit 3
         to the list, or correct the reference to Exhibit 2.

Pass 3: Packet Consistency
  [PASS] All captions identical
  [FAIL] Motion identifies hearing as "June 15 at 9:30 AM
         WebEx"; Notice of Hearing says "June 17 at 9:00 AM
         in person". Reconcile.

Pass 4: Sworn-vs.-Argued Consistency
  [FAIL] Motion p. 4 states "Defendant received the
         validation notice on March 28, 2025."
         Declaration ¶ 4 states "I received the validation
         notice on April 3, 2025." Reconcile (typically
         conform the motion to the declaration).

Summary: 2 PASS, 2 WARN, 3 FAIL — review and correct before
filing.

What this skill does NOT do

  • It does NOT silently rewrite the filing. All flags require user review.
  • It does NOT verify the legal soundness of the argument — whether the citations support the proposition is for the user (and ideally an attorney).
  • It does NOT check the substantive law applies — e.g., if the filing relies on ORCP 36 B(1) for a discovery dispute in arbitration, this skill won't tell you that ORCP 36 may not apply in the arbitration proceeding.
  • It does NOT check timing — that's or-deadlines.
  • It does NOT check format — that's or-quality-check.

How to invoke

User: Fact-check the motion-to-compel packet I just drafted.
Agent: [Runs the four passes, produces the report]
User: For the FAIL on the parallel cite, fix it. For the
       hearing-date discrepancy, the correct date is June 15
       — update the Notice of Hearing.
Agent: [Applies the two fixes; re-runs Pass 2/3 to verify;
       reports]

The user remains in control of every change.

Citation verification — WebFetch templates

Oregon case

WebFetch:
  url: https://www.courtlistener.com/?q=%22[case name]%22+%22[volume]+Or+[page]%22&type=o&court=or
  prompt: Verify this Oregon Supreme Court citation: [Party]
          v. [Party], [vol] Or [page], [parallel] P2d/P3d
          [page] ([year]). Confirm (1) the case exists at the
          cited reporter and page, (2) the parallel cite, (3)
          the year, and (4) the case is still good law.
          If the case has been overruled, distinguished, or
          superseded by a later Oregon decision, identify
          the later case.

Oregon Court of Appeals

Same pattern, court=orctapp.

9th Circuit

WebFetch:
  url: https://www.courtlistener.com/?q=%22[case name]%22&type=o&court=ca9
  prompt: Verify this 9th Circuit citation: [Party] v.
          [Party], [vol] F3d/F2d [page] (9th Cir [year]).
          Confirm the citation and that the case is still
          good law.

ORS section

WebFetch:
  url: https://www.oregonlegislature.gov/bills_laws/ors/ors[CHAPTER].html
  prompt: Locate ORS [chapter].[section]([subsection]).
          Quote the verbatim text. Identify the most recent
          legislative amendment.

ORCP rule

WebFetch:
  url: https://counciloncourtprocedures.org/
  prompt: Locate the current ORCP PDF. Quote the verbatim
          text of ORCP [N] [Letter]([number]). Identify the
          effective date of the current version.

UTCR rule

WebFetch:
  url: https://www.courts.oregon.gov/rules/UTCR/Pages/default.aspx
  prompt: Locate the current UTCR PDF. Quote the verbatim
          text of UTCR [N].[NNN]([N]). Identify the effective
          date.

Federal statute

WebFetch:
  url: https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title[N]-section[NNNN]&num=0&edition=prelim
  prompt: Locate [title] USC § [section]([subsection]).
          Quote the verbatim text. Identify the release
          point of the current version.

Federal regulation

WebFetch:
  url: https://www.ecfr.gov/current/title-[N]/chapter-[N]/subchapter-[N]/part-[NNNN]/section-[NNNN].[NN]
  prompt: Locate [title] CFR § [N].[NN]. Quote the verbatim
          text as currently in effect. If a relevant date
          was specified, also identify the version in effect
          on that date.

Pre-fact-check checklist (for the user)

Before invoking the skill, ensure:

  • Draft is reasonably complete (don't fact-check a half-written motion)
  • All exhibits referenced are listed
  • All key dates are filled in (no "[date]" placeholders)
  • Citations are inserted (no "TBD" or "[case here]" placeholders)
  • Spell-check and grammar-check have been run

Cross-references

  • or-law-references/references/online-sources.md — canonical fetch URLs
  • or-law-references/references/citation-format.md — Oregon Style Manual conventions
  • or-quality-check — format-pass (paper, margins, fonts, footer)
  • or-file-packet — final-packet preflight
  • All draft-* skills — the documents that get fact-checked

Assemble an Oregon Court Filing Packet

Gather and organize all documents required for a complete Oregon civil filing: motion, supporting declaration, exhibits, proposed order, Notice of Hearing, and Certificate of Service.

NOT LEGAL ADVICE. This skill is a procedural and drafting aid, not legal advice. Verify current rules, deadlines, and venue-specific practices before filing. Pair with substantive review by counsel where stakes warrant.

Standard packet for a noted civil motion

#DocumentSkill
1Motion + Memorandumor-draft-motion
2Supporting Declaration(s) with exhibitsor-draft-declaration
3Proposed Order ("[PROPOSED]" in title)or-draft-order
4Notice of Hearingor-draft-note
5Certificate of ServiceUTCR 1.090

Optionally:

  • Working copies (Multnomah SLR 5.100, Washington Co SLR 5.100 — over threshold pages) — paper packet delivered to chambers
  • Application for Fee Waiver (ORS 21.682) if filing fees cannot be paid

Step-by-step

Step 1: Reserve the hearing date

Per the court's procedure (see or-schedule-hearing).

Step 2: Draft each document

For each document, use the relevant draft-* skill:

  • Motion + Memorandum → or-draft-motion
  • Declaration → or-draft-declaration
  • Proposed Order → or-draft-order
  • Notice of Hearing → or-draft-note

Step 3: Run Quality Check

Run or-quality-check against each document:

  • UTCR 2.010 format compliance
  • pro-se drafting framework content checks
  • Citation format

Fix any FAILs before proceeding.

Step 4: Run Fact Check

Run or-fact-check against the entire packet:

  • Citation verification
  • Internal consistency (within each document)
  • Packet consistency (across documents)
  • Sworn-vs.-argued consistency

Fix any FAILs before proceeding.

Step 5: Preflight checklist

Before filing, verify:

Captions
  • All five documents use identical court header
  • All five documents have the same case number
  • All five documents have the same party names in the same order
  • Document titles match what's actually in the body
Hearing details (across motion, Notice of Hearing,

proposed order)

  • Date matches
  • Time matches
  • Mode (in-person / WebEx) matches
  • Courtroom or connection info matches
  • Assigned judge matches
Service
  • Certificate of Service in each document (or as a separate document)
  • All parties identified by full name and address (or email)
  • Method of service identified
Exhibits
  • All exhibits referenced in the motion or declaration are present
  • Exhibit numbering is sequential and consistent
  • Cover pages and Exhibit List present in the declaration
File and Serve readiness
  • Each document is in PDF format
  • Each document is under 25 MB (or split if larger)
  • Document codes selected matching UTCR 2.110 titles
  • Filing fees identified (or fee-waiver application attached)
Signature
  • Signature block on each document
  • Date is filled in (or fill-in blanks for handwritten date)
  • OSB# if counsel; omitted if pro se
Confidential information (UTCR 2.120)
  • SSN redacted (last 4 only)
  • Account numbers redacted (last 4 only)
  • Minor children referenced by initials
  • DOB redacted (year only for adults)

Step 6: File via File and Serve

Sequence

In Multnomah, file each document separately with its own document code. The order:

  1. Motion + Memorandum — "Motion (Other)" or specific code
  2. Supporting Declaration — "Declaration of [Name]"
  3. Proposed Order — "Order — Proposed"
  4. Notice of Hearing — "Notice of Hearing"
  5. Certificate of Service — "Certificate of Service" (or included as page of each filed document)
Document codes

Pick from the File and Serve dropdown matching the UTCR 2.110 title. If no exact match, use the closest available; some codes are:

  • Motion (Other)
  • Motion to Compel
  • Motion to Dismiss
  • Motion for Summary Judgment
  • Motion to Vacate
  • Memorandum in Support of Motion
  • Declaration of [Name]
  • Order — Proposed
  • Notice of Hearing
  • Certificate of Service
Fees

Pay or apply for waiver at submission. Filing fees:

FilingFee (approximate)
Motion (most types)~$11
Order — Proposed$0 (no fee for proposed order)
Notice of Hearing$0
Declaration$0

Verify against https://www.courts.oregon.gov/services/fees/.

Step 7: Working copies (if required)

For Multnomah (over 25 pages total) or Washington Co (over 15 pages total):

  • Print one complete packet (motion + memo + decl + exhibits + proposed order)
  • Tab each document on its own tab
  • Bind (binder clip, staple, or perfect bind)
  • Add a cover with case caption, hearing date, judge name, and a short index of what's enclosed

Deliver:

  • Multnomah: Mail room (loading dock) at 1200 SW 1st Ave, Portland; addressed to "Hon. [Judge Name], c/o [JA Name]"
  • Washington Co: Civil Division counter, 2nd floor, 145 NE 2nd Ave, Hillsboro
  • Verify per-judge variations from the standing order

Step 8: Serve under ORCP 9 / UTCR 21.100

  • eService through File and Serve: for registered parties, service is automatic upon filing
  • Email: for parties consenting in writing
  • Mail: USPS first-class for non-registered parties
  • Hand delivery: optional

Certificate of Service (UTCR 1.090) documents the service.

Step 9: Calendar deadlines and hearing date

  • Hearing date — calendar with reminders at 7, 3, and 1 day out (see or-hearings/references/hearing-day-checklist.md)
  • Response deadline (if waiting for opposing party's response)
  • Reply deadline (if you'll reply to opposing's response)

Common packet errors

ErrorConsequence
Caption discrepancy between motion and proposed orderCourt rejects; refile
Hearing date mismatch between Notice and motionHearing falls off calendar
Missing Certificate of ServiceUTCR 1.090 violation; clerk rejects
Exhibit numbering mismatchConfused record; sanctions risk
Notice of Hearing filed before JA confirms dateHearing date may be rejected
Filing fee not paid (and no fee-waiver applied)Filing not accepted
Document over 25 MBUpload fails
Wrong document code in File and ServeFiling mis-indexed; may delay
Working copies not delivered when requiredJudge sees incomplete record
Caption uses "vs." instead of "v."Cosmetic but unprofessional

After filing

  • Confirm acceptance within 1–2 business days (File and Serve sends email)
  • If rejected, fix and re-file before any deadline
  • Update the calendar with the hearing date and any intermediate deadlines
  • Track opposing's response — if no response by the deadline, the motion is unopposed (judges may rule on the papers)
  • Prepare for the hearing (see or-hearings)

Pro se packet considerations

A pro se filer's packet is judged by the same standard as counsel's. Common pro se shortcuts to avoid:

  • Combining motion + declaration into one document (file separately)
  • Skipping the Notice of Hearing (most courts require it)
  • Lettered exhibits (use numbers in Oregon)
  • Static page numbers in the footer (use PAGE / NUMPAGES Word fields)
  • Forgetting the proposed order (judges expect one)
  • No working copies for Multnomah over-25-page motions

Companion skills

Run before assembling packet:

  • or-statewide-format — formatting baseline
  • or-pro-se — pro-se drafting framework
  • The relevant draft-* skills

Run during packet assembly:

  • or-quality-check — format pass
  • or-fact-check — substantive pass

Run after filing:

  • or-hearings — prep for the hearing

Cross-references

  • All draft-* skills — the individual documents
  • or-quality-check — format pass
  • or-fact-check — substantive pass
  • or-schedule-hearing — reserving the date (prerequisite)
  • or-hearings — preparing for the hearing (next step)
  • or-statewide-format/references/templates/ — the four primary templates

Oregon — First 30 Days After Service

When a defendant in an Oregon civil case is served with a summons and complaint, ORCP 7 C(2) gives them 30 calendar days to respond. This skill covers the matter-neutral workflow for that window — what to do, in what order, to preserve all rights and put the defendant in the strongest position before answering.

NOT LEGAL ADVICE. This is a procedural framework, not a case strategy. The strategic decisions (defend on the merits? attack jurisdiction? negotiate? settle?) depend on the specific facts and law.

The 30-day clock

The 30-day clock starts on the day after service and runs 30 calendar days under ORCP 10 A. If day 30 falls on a weekend or legal holiday (ORS 187.010), the deadline extends to the next business day.

For service by mail (rare for initial process, but happens with ORCP 7 D(2)(d) consensual mail service), add 3 days under ORCP 10 C.

For service by publication (ORCP 7 D(6)), the 30 days starts from the date of last publication.

Use or-deadlines and scripts/case-calendar.py to compute the precise deadline.

Three response options

The defendant must do one of three things within 30 days:

  1. File an Answer (the merits response)
  2. File an ORCP 21 motion to dismiss (or other ORCP 21 defense raised as a motion) — this tolls the answer deadline
  3. Reach an agreed extension with plaintiff (typically a written stipulation filed with the court)

Failure to do one of these results in default under ORCP 69. The defendant's defenses on the merits are lost; only ORCP 71 vacation can re-open the case.

Step-by-step workflow

Day 1 — Triage

Same day or next day after service.

  • Photograph the summons, complaint, and any envelope — preserve the postmark and method of service
  • Note the date and method of service — these affect the deadline computation
  • Calendar the 30-day deadline using or-deadlines
  • Calendar a working buffer at day 23 — file by then if possible
  • Identify the court — circuit court, county, case number
  • Read the complaint carefully — what claims, what damages, what relief?

Days 2–5 — Defenses inventory

Make a checklist of potential defenses. The ORCP 21 defenses are jurisdictional or procedural and must be raised first (via ORCP 21 motion OR in the answer) or they are waived (ORCP 21 G):

DefenseORCPWhen waived
Lack of subject-matter jurisdiction21 A(1)Never
Lack of personal jurisdiction21 A(2)If not raised by motion or in first responsive pleading
Improper venue21 A(3)Same
Insufficient service of summons21 A(4)Same
Insufficient service of process21 A(5)Same
Not the real party in interest21 A(6)If not raised by motion or in first responsive pleading
Failure to join party21 A(7)At any time
Failure to state ultimate facts21 A(8)At any time (but raised promptly)
Pendency of another action21 A(9)If not raised by motion or in first responsive pleading
More definite statement21 BIf not raised by motion before responsive pleading
Motion to strike21 EIf not raised by motion before responsive pleading

Also consider substantive affirmative defenses (these go in the answer, not the ORCP 21 motion):

  • Statute of limitations (ORS 12 — verify SOL for each claim)
  • Statute of frauds (ORS 41.580)
  • Lack of capacity / standing
  • Failure of consideration
  • Accord and satisfaction
  • Estoppel / waiver / laches
  • Comparative fault (ORS 31.600)
  • Set-off
  • Discharge in bankruptcy (11 USC § 727)
  • Federal preemption
  • Anti-SLAPP (ORS 31.150)
  • Subject-matter-specific defenses (see relevant subject-matter skill)

Days 5–10 — Counterclaims inventory

ORCP 22 governs counterclaims:

  • Compulsory counterclaim (ORCP 22 A): any claim arising out of the same transaction or occurrence. Must be raised in the answer or it's waived for future actions.
  • Permissive counterclaim (ORCP 22 B): any other claim against the plaintiff. Can be raised in the answer or in a separate action.

For a debt-collection defendant, potential counterclaims often include:

  • FDCPA (15 USC § 1692k) — if a debt collector or collection attorney is the plaintiff
  • Oregon UTPA (ORS 646.605) — broader than FDCPA
  • ORS 697 (Collection Agency) — if plaintiff is not registered
  • Defamation, intentional interference, etc. — fact-specific

See or-consumer-debt for the full debt-defense counterclaim menu. For other case types, consult the relevant subject- matter skill or general civil-defense practice.

Days 10–15 — Discovery planning

While the answer is being drafted, plan initial discovery:

  • First RFPs: target the plaintiff's foundational evidence — contract, chain of title, accounting, authorization to sue, registration to do business
  • First RFAs: lock in basic facts that should be uncontroverted (corporate form, identity, dates)
  • Depositions: typically not until after answer; identify potential deponents (plaintiff's PMK, document custodian)
  • Subpoenas to non-parties (original creditor, banks): plan but don't issue until after answer

Serve discovery with the answer or shortly thereafter — discovery is often the bottleneck and starting early creates leverage.

Days 15–23 — Draft the response

Choose the path:

Path A: Answer with affirmative defenses + counterclaims

Use this when:

  • The defenses are substantive (SOL, lack of standing, etc.)
  • You want to start discovery immediately
  • Counterclaims should be pled now

Structure:

  1. Caption (court header, parties, case number, title: "DEFENDANT'S ANSWER, AFFIRMATIVE DEFENSES, AND COUNTERCLAIMS")
  2. Admissions and denials — paragraph-by-paragraph response to the complaint
  3. Affirmative defenses — numbered, each with the legal basis and a brief factual showing
  4. Counterclaims — numbered, each with elements and prayer for relief
  5. Prayer for relief on counterclaims
  6. Signature block (with "Defendant, pro se" if applicable)
  7. Certificate of Service
Path B: ORCP 21 motion to dismiss

Use this when:

  • A jurisdictional or service defect could end the case
  • Failure to state ultimate facts (ORCP 21 A(8)) — the complaint, accepting allegations as true, doesn't entitle plaintiff to relief
  • You want to delay the merits while pursuing the procedural issue

Structure (see or-draft-motion):

  1. Caption ("DEFENDANT'S MOTION TO DISMISS UNDER ORCP 21 A(8)")
  2. Motion
  3. Memorandum — facts, issues, evidence, authorities, argument
  4. Conclusion

ORCP 21 motions toll the answer deadline. If denied, the defendant has 10 days to file the answer (ORCP 21 D — verify current rule).

Path C: Stipulated extension

If the parties agree, file a Stipulation for Extension of Time signed by all counsel/parties. The court routinely grants modest extensions (14–30 days) on stipulation.

Some Oregon judges have specific extension protocols in their standing orders — check first.

Day 23–25 — QC and filing

  • Run or-quality-check against the draft
  • Run or-fact-check to verify citations and dates
  • Verify deadlines with or-deadlines
  • eFile via File and Serve with the correct UTCR 2.110 document code
  • Serve all parties under ORCP 9 / UTCR 21.100
  • File a Notice of Hearing if the response is an ORCP 21 motion that needs a hearing date

Pre-answer evidence preservation

Before, during, and after the 30-day window, the defendant should:

  • Preserve all communications with plaintiff (emails, letters, voicemails) — these may be FDCPA or UTPA evidence
  • Preserve relevant business records — bank statements, cardholder agreement, monthly statements (if not destroyed in the ordinary course)
  • Photograph any physical evidence that may degrade
  • Issue a litigation-hold notice to anyone in custody of potentially relevant documents (in a pro se context, this is often informal — "please don't destroy the email archive")

Pre-answer settlement

Consider whether to attempt settlement before answering:

  • Pro: avoids the cost of litigation; some plaintiffs settle for pennies on the dollar before discovery
  • Con: the defendant gives up the leverage of an answer with counterclaims; the plaintiff may interpret a pre- answer settlement offer as weakness

For debt cases, sending a debt-validation request (ORS 697 / FDCPA) during the 30-day window is often a procedurally parallel move — it forces the plaintiff to produce authentication documents while the answer is being drafted.

Default avoidance

The single biggest pro se failure mode is missing the 30-day deadline. Tools to prevent it:

  • Calendar the deadline immediately upon service
  • Calendar a buffer at day 23 so a late file is still on time
  • eFile, not paper — paper risks clerk rejection
  • Confirm filing acceptance within 2 business days; if rejected, re-file before day 30

If default has already been entered, the defendant must move to vacate under ORCP 71 B — see or-post-judgment.

Pro se considerations

A pro se defendant in the first 30 days should:

  • Save every paper document the plaintiff has sent
  • Save every email and voicemail — even spam-folder ones from the plaintiff
  • Photograph the envelope of the summons before opening (to preserve postmark)
  • Sleep on the response before filing — initial drafts are often emotionally loaded
  • Consider getting an attorney consultation even for pro se cases — many Oregon attorneys offer flat-fee consultations under the OSB Modest Means program

Step summary

  1. Day 1: triage, photograph, calendar
  2. Days 2–5: defenses inventory
  3. Days 5–10: counterclaims inventory
  4. Days 10–15: discovery planning
  5. Days 15–23: draft answer + counterclaims OR ORCP 21 motion
  6. Days 23–25: QC, fact-check, eFile, serve

Build the buffer at day 23. Aim for day 25 filing, with day 30 as the absolute deadline. Anything later is a default-risk race.

Cross-references

  • or-deadlines — exact date computation
  • or-draft-motion — ORCP 21 motion structure
  • or-draft-declaration — supporting declaration form
  • or-discovery — first RFPs / RFAs
  • or-law-references/references/civil-rules.md — ORCP 7, 10, 21, 22 verbatim
  • or-consumer-debt — debt-defense-specific affirmative defenses and counterclaims
  • or-pro-se — pro-se drafting framework for the response
  • or-post-judgment — if default has already been entered, motion to vacate under ORCP 71

Oregon Hearings — Preparation and Conduct

A hearing is where a well-prepared pro se litigant wins or loses the motion. The judge has usually read the briefs but has questions. The hearing is your chance to answer them directly.

This skill covers both in-person and remote (WebEx / phone) hearings in Oregon circuit courts, with specific guidance for Multnomah, Washington, and the other high-volume counties.

NOT LEGAL ADVICE. Court rules, etiquette, and remote- hearing details change. Verify against your court's standing orders before any hearing.

Core principles

  1. The judge has read the briefs — do not recite them. Focus on the two or three points the judge needs clarified, and on any questions the court will plausibly have.
  2. Answer questions directly — when the judge asks a question, answer it first, then explain. Never dodge.
  3. Concede what must be conceded — acknowledge weak points; argue the stronger points. A pro se litigant who concedes nothing loses credibility.
  4. Keep it short — Oregon judges tend to limit civil motion argument to 10–20 minutes per side. If you have 15 minutes, make 2–3 points well, not 8 points lightly.

Before the hearing

24 hours before

  • Confirm date, time, courtroom, and mode. WebEx link or in-person address. Check the assigned judge's standing order for any last-minute changes.
  • Review the file — your motion, opposing response, your reply (if any), the exhibits.
  • Outline 2–3 main points you must make. Write them down.
  • Outline 2–3 likely judge questions and how you would answer.
  • Prepare your closing line — typically a 30-second summary of the relief you want.

Day of

  • For in-person: arrive 30 minutes early. Allow 15–20 minutes for security at major courthouses (Multnomah Central, Washington Co Hillsboro).
  • For WebEx: log in 10–15 minutes early. Test audio and video. Have a backup phone connection ready.
  • For phone: have the call-in number and meeting ID handy. Find a quiet location.

What to wear

In-person hearings:

  • Court dress — business or business-casual. A button-up shirt and slacks for men; a similar level of dress for women. Suit is rarely required but never wrong.
  • No t-shirts, jeans, hats, even for routine motion practice. Oregon judges are generally informal but expect basic professional dress.
  • No hats inside the courtroom (except for religious head coverings, which are always allowed).

WebEx hearings:

  • Same standard, top-half only — you're on camera from the shoulders up. Wear a collared shirt or its equivalent. Even for a 10-minute motion hearing, looking professional matters.
  • Plain background — no clutter or visible household items. A blurred background is acceptable; a virtual background that is conservative is fine.

Phone hearings:

  • Pajamas are OK. The judge can't see you. But sit upright at a desk — your voice carries your posture.

Addressing the court

  • "Your Honor" is the standard form of address for any judge.
  • "The Court" in argument when referring to the judge in the third person: "The Court will recall from the briefs..."
  • Never "Judge" without their last name, and never their first name.
  • "Counsel" when addressing opposing attorney; "Plaintiff" or "Defendant" when referring to their client (or use the party name if multiple parties).
  • For pro se opposing party: "Plaintiff" or their last name — "Mr./Ms. Smith".

Courtroom etiquette

  • Stand when the judge enters the courtroom. Remain standing until the judge says "Be seated" or sits down.
  • Stand when speaking to the court — at counsel table or at the lectern. Sit when the judge is asking the other side questions.
  • One person speaks at a time. No interrupting opposing counsel or the judge.
  • Address the court, not opposing counsel. Even when arguing against opposing counsel's point, speak to the judge.
  • Wait for the judge to call your matter before approaching the lectern.
  • Be brief. If you have nothing new to add to the briefs, say so: "Your Honor, I will rest on the briefs unless the Court has questions."

Presenting argument

Standard structure

  1. Opening (15 seconds): Identify yourself, the case, and the relief you seek.

    "Good morning, Your Honor. John Doe, pro se defendant, in Case No. 25CV12345. The Court has Defendant's Motion to Compel before it; I am asking the Court to grant the motion and order production within 14 days."

  2. The strongest point (2–3 minutes): your best argument, one clear point.

  3. Anticipate the opposing argument (1–2 minutes): what would the other side say, and why is it wrong?

  4. Brief answer to likely judge questions (varies).

  5. Closing (30 seconds): restate the relief.

Answering judge questions

The judge will interrupt with questions. When that happens:

  • Stop talking the moment the judge starts
  • Answer the question first — yes, no, or "the answer is X"
  • Then briefly explain why
  • Do not deflect — if you don't know, say "Your Honor, I don't have that information at hand, but it appears in the declaration at paragraph 4" or "Your Honor, I'd need to check the record on that"

Concessions

A well-placed concession often wins the case:

"Your Honor, opposing counsel is right that the Court has discretion to deny this motion under ORCP 46. But the question for the Court is whether that discretion should be exercised here, and we submit it should not because [strong reason]."

A litigant who concedes nothing — including obvious points the judge clearly believes — loses credibility on every point.

Remote (WebEx) hearings

Technical setup

  • Use a laptop or desktop rather than a phone for video. Camera quality and audio matter.
  • Plug into ethernet if available; Wi-Fi can drop.
  • Have backup: a phone call-in option in case the video fails.
  • Headphones with microphone are best — reduce echo and background noise.

Conduct on video

  • Look at the camera (not the screen) when speaking — this is the eye contact equivalent on video.
  • Mute when not speaking to suppress background noise.
  • Don't read from your screen while looking down — your notes should be either to the side of the camera or on the same screen as the WebEx window so your eyes stay close to camera-level.
  • Show what you're holding if it's relevant: "Your Honor, I am holding Exhibit 3, the bill of sale, which..."

Technical-failure protocol

If your audio or video fails during the hearing:

  1. Stay on the line; mute if you can't speak
  2. Text or call the court's tech support line (often listed on the courthouse website)
  3. If you need to drop and re-join, do so calmly; the judge will wait
  4. If technical issues are recurring, ask to continue the hearing

Working copies and exhibits at hearing

  • Bring your packet to in-person hearings even if you've delivered working copies — the judge may want to refer to a specific page
  • Have a digital copy for WebEx — share-screen capability for exhibits, though Oregon judges generally do not encourage screen-sharing of exhibits at routine motion hearings (the briefs and working copies should cover it)
  • Witnesses at non-evidentiary hearings are unusual; if a declaration is in the record, that's typically enough

County-specific details

Multnomah Circuit Court

  • WebEx is default for routine civil motions
  • Judge standing orders linked from the judge's page (each judge has different preferences)
  • Connection info from the assigned JA when the date is set
  • In-person hearings at the Central Courthouse, 1200 SW 1st Avenue, Portland

Washington County Circuit Court (OR)

  • Mode is judge-specific; check the Civil Division confirmation
  • In-person at 145 NE 2nd Avenue, Hillsboro

Other counties

  • WebEx is increasingly common, but judges in some smaller counties prefer in-person
  • The local SLR Chapter 7 governs remote hearings (parallels UTCR 7.010)

Hearing-day checklist

  • Confirm date, time, courtroom/WebEx link 24 hours before
  • Print the motion, response, reply, and key exhibits
  • Bring working copies if not previously delivered
  • Outline 2–3 main points
  • Outline 2–3 anticipated judge questions
  • For in-person: arrive 30 minutes early
  • For WebEx: log in 10–15 minutes early; test audio/video
  • Dress appropriately
  • Have backup contact (phone) for tech issues
  • Bring a notepad to take notes during the hearing
  • After: send a follow-up email to the JA if working copies were used and need return

After the hearing

  • If the court rules from the bench, the prevailing party submits the proposed order with any bench modifications. See or-submit-order.
  • If the court takes the matter under advisement, the ruling comes by written order, typically 2–6 weeks. The prevailing party then submits the order if not already done.
  • If a hearing was for evidentiary purposes, transcripts must be ordered separately (the court does not provide transcripts for free).

Common pro se hearing mistakes

MistakeConsequence
Reading from the briefWastes time; judge can read
Dodging judge questionsLoses credibility
Arguing with opposing counselJudge cuts you off
Failing to concede obvious pointsLoses every argument
Being lateAdverse inference; possible dismissal
Dressing too casuallyFirst impression matters
Talking over the judgeAlways lose this fight
Bringing irrelevant materialsCluttered argument
No closingLoses the chance to restate relief

References

  • references/oral-argument.md — extended guide to making arguments and fielding questions
  • references/courtroom-etiquette.md — full etiquette guide by county and by judge type
  • references/zoom-hearings.md — WebEx / Zoom-specific techniques (Oregon courts have moved to WebEx; many practitioners still call them "Zoom hearings")
  • references/hearing-day-checklist.md — printable single-page checklist

Oregon Law References — General Civil Practice

Federal corpora. or-law-references/references/federal-debt-laws/, federal-bankruptcy/, and ucc-model/ are links into the claude-legal-federal-laws dependency. If one is missing or a dangling link (some install methods copy only this plugin's folder), read the same file from claude-legal-federal-laws via its federal-law-references skill; file names are identical.

This skill is a matter-neutral reference index — a pointer to the statutes, rules, and doctrines most often invoked in Oregon civil practice across any subject matter. The body below summarizes each source. Detailed sections, elements, and citation examples live in references/.

NOT LEGAL ADVICE. These notes are drafting aids, not legal advice. Every citation should be verified against the current ORS, current court rule, or current case law before it goes into a filing. Use or-fact-check before any packet is filed.

How to use this skill

Ask: what is the user trying to establish procedurally?

  • A procedural motion (compel, dismiss, strike, default, SJ, vacate) → start with references/civil-rules.md
  • An evidentiary objection (hearsay, authentication, best evidence, foundation) → start with references/evidence-rules.md
  • A fee-and-cost request or objection → start with references/fees-and-costs.md
  • A local-rule question (Multnomah SLR; Washington Co SLR) → start with references/local-rules.md
  • Citation format → references/citation-format.md
  • Canonical URL or citation verification → start with references/online-sources.md and hand off to or-fact-check for per-filing verification
  • Programmatic / structured lookup (ORS XML, USC XML, eCFR API, CourtListener for cite-checking, bulk extraction, change detection) → references/legal-data-apis.md. Prefer the APIs listed there over HTML scraping when the result will be parsed
  • A general civil case (SJ standard, lodestar, default- vacation) → start with references/key-cases.md
  • Subject-matter law (FDCPA, Reg F, consumer protection under UTPA, landlord-tenant, family, PI, criminal) → use the relevant subject-matter skill (e.g., or-consumer-debt for debt collection)

Oregon civil rules

A single set of rules — there is no Oregon analog to Washington's CR / CRLJ split, because Oregon consolidated its trial courts in 1998.

  • ORCP — Oregon Rules of Civil Procedure (adopted by the Council on Court Procedures under ORS 1.735, with legislative approval / non-disapproval)

Key rules:

  • ORCP 1 — applicability; ORCP 1 E permits declarations "under penalty of perjury" in lieu of notarized affidavits
  • ORCP 7 — service of summons and complaint; 63-day deadline for Return of Service (ORCP 7 D(3))
  • ORCP 9 — service of subsequent papers; ORCP 9 C: 3-day mail rule; ORCP 9 G: Certificate of Service
  • ORCP 10 — time computation; defines court days vs. calendar days
  • ORCP 15 — pleadings allowed; 30 days to answer (ORCP 7 C(2))
  • ORCP 17 — signing of pleadings; sanctions for unfounded filings
  • ORCP 21 — motions to dismiss / defenses asserted as motions; ORCP 21 A(8) = failure to state ultimate facts (the Oregon analog to FRCP 12(b)(6))
  • ORCP 23 — amendment of pleadings; "leave shall be freely given"
  • ORCP 36 — general scope of discovery; ORCP 36 B(1) = relevance + proportionality
  • ORCP 39 — depositions
  • ORCP 43 — requests for production
  • ORCP 44 — physical/mental examination
  • ORCP 45 — requests for admission
  • ORCP 46 — motion to compel; ORCP 46 A(4)(a) = mandatory fee-shifting on a successful motion to compel
  • ORCP 47 — summary judgment; ORCP 47 C governs filing / response / reply schedule
  • ORCP 54 — dismissal; ORCP 54 B = failure to prosecute
  • ORCP 67 — judgments
  • ORCP 68 — costs; ORCP 68 C(2)–(4) = statement of costs and fees procedure
  • ORCP 69 — default
  • ORCP 71 — relief from judgment or order; the Oregon analog to FRCP 60(b)
  • ORCP 81 — interpretation

Note: Oregon does NOT have written interrogatories under ORCP as a matter of right. Discovery tools available are: depositions (ORCP 39), requests for production (ORCP 43), physical/mental exams (ORCP 44), and requests for admission (ORCP 45). Some court-annexed arbitration programs allow interrogatories under arbitrator's discretion. This is a major distinction from Washington (which has CR 33 interrogatories) and from the FRCP (which has FRCP 33).

See references/civil-rules.md for rule-by-rule coverage.

Oregon Evidence Code (OEC)

The OEC is codified in ORS 40.010–40.585. Numbering parallels the Federal Rules of Evidence (FRE) at the section level (OEC 401 = relevance; OEC 801 = hearsay definition; OEC 901 = authentication), but the substantive rules sometimes diverge.

Key sections for civil practice:

  • OEC 401 — relevance
  • OEC 403 — exclusion for prejudice / confusion
  • OEC 602 — personal knowledge
  • OEC 801–803 — hearsay; OEC 803(6) = business records
  • OEC 901–902 — authentication; OEC 902 = self-authentication
  • OEC 1001–1008 — best evidence; OEC 1002 = original document rule

See references/evidence-rules.md for rule-by-rule coverage and the business-records / authentication patterns most common in civil practice.

Fees and costs

ORS Ch. 20 — the costs and fees chapter. Recovery mechanisms:

  • ORS 20.075 — factors considered in awarding fees (when fees are authorized by statute or contract)
  • ORS 20.077 — fees on a per-claim basis
  • ORS 20.082 — small claims fees
  • ORS 20.083 — fees as costs vs. as part of judgment
  • ORS 20.096 — reciprocal fee-shifting in contract cases (when contract has one-sided fee clause, prevailing party of either side recovers)
  • ORS 20.105 — fee award against party for objectively unreasonable position (rough analog to CR 11 in Washington / Rule 11 federal — but distinct standard)
  • ORS 20.140 — in forma pauperis status
  • ORS 20.180 — costs as taxed
  • ORS 20.190 — prevailing-party fees (mandatory $200–$590 depending on case type)

ORCP-based fee-shifting:

  • ORCP 46 A(4)(a) — mandatory fee-shifting to the prevailing party on a motion to compel, unless the opposing party's failure was "substantially justified"
  • ORCP 17 — sanctions for unsigned or unfounded pleadings
  • ORCP 32 — class action attorney fees
  • ORCP 54 E — fees on dismissed claims

Statutory fee-shifting (subject-matter-specific):

  • ORS 646.638(3) — UTPA: prevailing-party fees mandatory
  • 15 USC § 1692k — FDCPA: prevailing-consumer fees mandatory
  • ORS 90.255 — landlord-tenant: prevailing-party fees available

See references/fees-and-costs.md for full coverage, the lodestar method, pro-se recovery limits, and pleading templates.

Local rules

Each Oregon circuit court maintains Supplemental Local Rules (SLR) layered on top of the statewide UTCR and ORCP:

  • Multnomah SLR — Civil Department: motion practice through assigned JA (SLR 5.025), meet-and-confer certification (SLR 5.045), working copies over 25 pages (SLR 5.100), order submission (SLR 5.101)
  • Washington County SLR (Oregon) — Civil Division scheduling (SLR 5.025), simultaneous Notice of Hearing (SLR 5.045), meet-and-confer (SLR 5.046), working copies over 15 pages (SLR 5.100)
  • Other counties' SLR — Lane, Marion, Jackson, Deschutes, Clackamas, etc.

See references/local-rules.md for the full coverage, inter-county variation, and the interaction with UTCR statewide formatting.

Citation format

Oregon uses the Oregon Appellate Courts Style Manual (OACSM, also called the "Oregon Style Manual") published by the OJD. Form for an Oregon case citation:

Smith v. Jones, 350 Or 1, 250 P3d 100 (2010)

Federal citations are non-Bluebook in Oregon style: 15 USC § 1692k(a)(1) (no periods in "USC"). See references/citation-format.md for patterns for Oregon and federal citations, parallel cites, short-form references, and UTCR / Style-Manual compliance.

Canonical online sources

references/online-sources.md is the AI-agent-friendly catalog of canonical URLs for:

  • Oregon court rules (UTCR, ORCP, OEC, ORAP) — courts.oregon.gov and the Council on Court Procedures site
  • ORS text — oregonlegislature.gov
  • eCFR (for federal regulations)
  • Cornell LII (for U.S.C. sections)
  • CourtListener and Google Scholar (for case law)
  • Multnomah and Washington County SLRs
  • OJD eCourt File and Serve (for filing mechanics)

The catalog is the only approved fetch source for verification work. Per the plugin's safety policy, WebFetch is the only mechanism used — no curl, wget, Python requests, or other bypasses are permitted. See or-fact-check for the per-filing verification workflow.

Key general-civil cases

references/key-cases.md catalogs the general-civil cases this plugin relies on most:

  • SJ burden: Two Two v. Fujitec America, Inc., 355 Or 319, 325 P3d 707 (2014) (no genuine issue of material fact; light shifts to non-movant after movant's prima facie showing)
  • SJ inferences favorable to non-movant: Jones v. General Motors Corp., 325 Or 404, 939 P2d 608 (1997)
  • Reciprocal fee-shifting: Lemargie v. Johnson, 212 Or App 451, 157 P3d 1284 (2007) (ORS 20.096 scope)
  • Lodestar method: Strawn v. Farmers Ins. Co. of Oregon, 353 Or 210, 297 P3d 439 (2013)
  • American rule baseline / no-fees-without-authority: Domingo v. Anderson, 325 Or 385, 938 P2d 206 (1997)
  • ORCP 71 default-vacation: Wagar v. Prudential Ins. Co. of America, 276 Or 827, 556 P2d 658 (1976) (excusable neglect standard; also discussed in Or App opinions on ORCP 71 B(1))

Subject-matter cases — FDCPA, UTPA, business-records foundation in debt cases, chain-of-title — live alongside their subject-matter bundle (e.g., or-consumer-debt/references/ key-cases.md).

Notes

  • These references are neutral summaries. They do not tell the user whether they win or lose.
  • Always verify a case before citing — Oregon case law has evolved on several doctrines (business-records foundation, ORCP 71 grounds, fee-shifting scope, ORCP 47 inferences).
  • For federal law, check the most recent Ninth Circuit opinion where controlling in federal court; Oregon state courts treat Ninth Circuit federal-statute interpretations as persuasive.
  • Before filing, run or-fact-check against the packet to catch fabricated, misquoted, or superseded citations.

Multnomah County Circuit Court

Use this skill in addition to or-statewide-format when the case is in the Multnomah County Circuit Court (MCCC). Multnomah is the largest trial court in Oregon (~25–30% of all civil filings statewide) and has the most developed local-rule and motion- practice ecosystem.

NOT LEGAL ADVICE. These notes describe the venue's procedural mechanics as a drafting aid, not legal advice. Local rules and judge-specific practices change; verify with the clerk and the current SLR before relying on anything here.

Court locations and divisions

Multnomah Circuit Court has three principal facilities:

  • Central Courthouse (the new flagship), 1200 SW 1st Ave, Portland OR 97204 — civil, criminal felony, family law, probate, mandatory arbitration. Opened 2020, replaced the old Multnomah County Courthouse.
  • Justice Center, 1120 SW 3rd Ave, Portland OR 97204 — criminal misdemeanor, in-custody criminal arraignments, violations
  • Donald E. Long Juvenile Justice Complex (the "JJC"), 1401 NE 68th Ave, Portland OR 97213 — juvenile delinquency and juvenile dependency

For civil pleadings, the venue is the Central Courthouse. The caption identifies "FOR THE COUNTY OF MULTNOMAH" — there is no sub-division reference in the caption (unlike KCDC's East/South/West divisions in Washington).

Caption — Multnomah variant

            IN THE CIRCUIT COURT OF THE STATE OF OREGON
                  FOR THE COUNTY OF MULTNOMAH

Case numbers follow YYCVNNNNN for civil cases (e.g., 25CV12345). The first two digits are the year; "CV" is the case type (civil); the remaining digits are the sequential filing number for the year.

Civil motion scheduling — chambers contact, not a calendar clerk

Multnomah does not use a centralized motions docket. Each civil case is assigned to a specific judge at filing (via the Multnomah civil case-assignment system). Motions are heard on that judge's individual calendar. To set a motion:

Step 1 — Identify the assigned judge

The assigned judge appears on the OJD Case Information screen for the case (visible to the parties and in File and Serve once the case is filed). For a newly filed case where assignment has not yet posted, check with Civil Division at (503) 988-3022.

Step 2 — Contact the judge's judicial assistant (JA)

Email or call the assigned judge's JA to request a hearing date. The JA roster is published on the Multnomah Circuit Court website (courts.oregon.gov/multnomah, "Judges and Staff"):

In the email, identify:

  • Case caption and number
  • Motion type (e.g., "Motion to Compel under ORCP 46")
  • Estimated argument time
  • Whether other parties have been consulted on dates
  • Two or three proposed dates that work for the moving party

Step 3 — JA confirms the date

The JA will reply confirming the date, courtroom, and mode (in-person, WebEx, or telephone). Some judges hold all civil motions on WebEx by default; others prefer in-person. Take what the JA offers.

Step 4 — File the Notice of Hearing

After the JA confirms, file a Notice of Hearing through File and Serve, identifying the date, courtroom, mode, and assigned judge. The Notice of Hearing is what gives the record notice of the setting (the JA's email is internal scheduling, not part of the court record).

Step 5 — Working copies to chambers

For motions over 5 pages (memorandum + exhibits combined), or for motions where the judge has specifically requested it, deliver working copies to chambers:

  • Multnomah SLR 5.100 governs working copies
  • Deliver to the judge's courtroom or chambers via the Central Courthouse mail room
  • The working copy is a tabbed, bound paper copy of the entire packet — motion, memorandum, declaration, exhibits, proposed order
  • For pro se filers, mailing the working copy to the courtroom (addressed to the judicial assistant) is acceptable
  • Some judges accept email-only working copies for short motions; always confirm with the JA when you request the date

Authoritative source — pull the current judge roster every time

The Multnomah Circuit Court website is the canonical source for judges, judicial assistants, courtrooms, and standing orders:

https://www.courts.oregon.gov/courts/multnomah/Pages/default.aspx

Agent behavior: when drafting a Notice of Hearing or working- copy cover note, fetch the current JA contact info from that page. Judge rotations occur in January each year (and sometimes mid-year); do not cache assignments across sessions.

Multnomah SLR — Supplemental Local Rules

Multnomah's SLR adds detail on top of the statewide UTCR. Key sections for civil motion practice:

SLRSubject
1.001Effective date and scope
5.015Notice of Hearing on Motion
5.025Setting motions (chambers-based, by JA)
5.045Meet-and-confer certification for discovery motions
5.100Working copies — when, how, and where
5.101Submission of orders to chambers
7.010Telephonic and remote hearings
8.010Mandatory arbitration program (under ORS 36.400)
12.010Pretrial conferences and trial readiness
14.010Mediation referrals

The current Multnomah SLR PDF lives at https://www.courts.oregon.gov/courts/multnomah/rules — pull it when a specific SLR section is invoked, because Multnomah updates its SLRs more frequently than other counties.

Mandatory arbitration

ORS 36.400 et seq. requires arbitration for civil cases where the amount in controversy is between $10,000 and $50,000 (the ceiling is set by ORS 36.405 and is currently $50,000 statewide; Multnomah elects the statutory ceiling). Multnomah SLR 8.010 implements this.

If the case is in arbitration:

  • Discovery is limited (see arbitration program rules)
  • Motions go to the arbitrator, not the judge — caption the motion accordingly: "MOTION TO COMPEL... (IN ARBITRATION PROCEEDING UNDER ORS 36.400)"
  • A trial de novo can be requested after the arbitration award per ORS 36.425, but only after fees are paid

eFiling and service

Multnomah requires eFiling for all civil matters through File and Serve (https://oregon.tylertech.cloud). Document codes are specific:

  • Motion → "Motion (Other)" or "Motion to [Type]" if listed
  • Memorandum → "Memorandum in Support of Motion"
  • Declaration → "Declaration of [Name]"
  • Notice of Hearing → "Notice of Hearing"
  • Proposed Order → "Order — Proposed"

Service through eService (File and Serve) counts as service for registered parties (UTCR 21.100, ORCP 9 G(1)(d)). Self- represented parties not registered must be served by mail or hand delivery — see or-pro-se for the protocol.

Filing fees

Multnomah civil filing fees track the OJD statewide schedule under ORS 21.135-21.170:

  • Complaint or counterclaim over $10,000: $281 (subject to legislative update — pull current fee from https://www.courts.oregon.gov/services/fees/Pages/default.aspx)
  • Motion: $11 per side per motion (some motion types are free — see ORS 21.260)
  • Fee waiver: ORS 21.682 (filing-fee deferral); ORS 20.140 (in forma pauperis status)

Fee-waiver applications are filed simultaneously with the underlying pleading on File and Serve; the fee is deferred pending the court's order on the application.

Document set for a noted motion in Multnomah

  1. Motion (primary relief sought)
  2. Memorandum in Support (if argument is more than 1 page)
  3. Supporting Declaration(s) with exhibits
  4. Proposed Order ("[PROPOSED]" bracket in title)
  5. Notice of Hearing (filed separately after JA confirms date)
  6. Certificate of Service (separately or as a page in each document)
  7. Working copies to chambers (for motions over 5 pages or where the judge requests)

eFile each as a separate PDF through File and Serve. Working copies are delivered separately (paper or email per the JA's preference).

Scheduling email — recommended template

To:      [Assigned Judge's JA email]
Subject: Hearing Date Request — [Case Short Title],
         Case No. [Cause Number]

Dear [Judicial Assistant Name]:

I am [Counsel of record / Defendant, pro se] in [case short
title], Case No. [cause number], assigned to the Hon. [Judge
Name].

I am requesting to reserve a date for hearing on Defendant's
[motion title], filed (or to be filed) on [date]. I estimate
[20 minutes / 30 minutes] of argument.

I propose the following dates:
   [Option 1]
   [Option 2]
   [Option 3]

I have [contacted / not yet contacted] opposing counsel about
these dates. [If contacted: opposing counsel [agrees / objects
to / has not responded re] dates as follows: ...]

If WebEx is the preferred mode for the Court, please advise so
I can include the connection details on the Notice of Hearing.

Thank you,
[Name][, pro se designation if applicable] [, OSB # ___ if
counsel]
[Address]
[Phone]
[Email]

References

  • references/central-courthouse.md — Central Courthouse venue info, courtrooms, judges, mail-room directions
  • references/civil-motion-scheduling.md — JA contact protocol, working copies, courtesy copies
  • references/multnomah-slr.md — local rules summary, frequent references

Oregon Post-Judgment Procedure

When a judgment has been entered — against the defendant or for the defendant — a separate body of rules governs what happens next. Pro se defendants most often face post-judgment procedure in two situations:

  1. A default judgment was entered against them and they want to vacate it under ORCP 71
  2. A judgment creditor is collecting — garnishment, bank levy, supplemental proceedings — and the debtor needs to know their rights and exemptions

This skill covers both angles.

NOT LEGAL ADVICE. Post-judgment timing is unforgiving. Verify each deadline and consult a licensed attorney where the stakes are significant.

Core principles

  1. Vacation is about cause plus diligence — ORCP 71 requires a specific ground (mistake, excusable neglect, void judgment, etc.) AND that the motion be brought within a "reasonable time" (and no more than 1 year for grounds (1)– (3))
  2. Exemptions are claimed promptly or lost — most exemptions under ORS 18.345–18.385 must be claimed within 30 days of the garnishment notice
  3. Debtor exam responses are mandatory — a writ of debtor exam (supplemental proceedings) is a court order; failure to respond can lead to contempt
  4. A judgment lives 10 years (ORS 18.182) and can be renewed for another 10. The judgment is collectible throughout this period.

Motion to vacate under ORCP 71

When applicable

A defendant against whom default judgment was entered, who believes the entry was wrongful or excusable. Grounds under ORCP 71 B:

  1. Mistake, inadvertence, surprise, or excusable neglect — most common ground; classic example: defendant did not see the summons because it was served while they were hospitalized
  2. Newly discovered evidence — that, with reasonable diligence, could not have been discovered before the judgment
  3. Fraud, misrepresentation, or other misconduct of an adverse party — including service fraud (false return of service)
  4. Judgment is void — e.g., no personal jurisdiction, defective service
  5. Judgment satisfied, released, or discharged — or no longer equitable
  6. Any other reason justifying relief

Deadline

  • Grounds (1)–(3): "reasonable time", and not more than 1 year after entry of judgment
  • Grounds (4)–(6): "reasonable time" — no fixed cap

The 1-year cap is hard for grounds (1)–(3). Beyond 1 year, only the open-ended grounds (4)–(6) are available, and they're harder to win.

What the motion must show

The motion must establish:

  1. A specific ground under ORCP 71 B
  2. Diligence — the defendant moved promptly upon learning of the judgment
  3. A meritorious defense — if the judgment is vacated, the defendant has a real defense to advance (not just a wish to re-litigate)
  4. Lack of prejudice to the plaintiff — vacating the judgment doesn't unfairly harm plaintiff

See Wagar v. Prudential Ins. Co. of America, 276 Or 827, 556 P2d 658 (1976), and the recent ORCP 71 line of cases.

Procedural mechanics

  • File the motion with a supporting declaration under ORCP 1 E
  • Attach the proposed answer as an exhibit (showing the meritorious defense)
  • File a Notice of Hearing (or follow local SLR for motion scheduling)
  • The motion is typically set on the assigned judge's calendar; in Multnomah, contact the JA
  • Be prepared for the judge to want oral argument — see or-hearings

Stay of execution pending vacate motion

Filing the motion to vacate does NOT automatically stay execution (garnishment, levy). To stop collection while the motion is pending, file a separate motion for stay with a showing of:

  • Likely success on the vacate motion
  • Irreparable harm without stay
  • Balance of equities
  • Public interest (if applicable)

See references/motion-to-vacate.md for the full template and checklist.

Garnishment response

How Oregon garnishment works

Once a judgment is entered and the time for appeal has passed, the judgment creditor can issue a Writ of Garnishment (ORS 18.605):

  • Wage garnishment: served on the debtor's employer; the employer withholds a portion of wages (typically 25% under ORS 18.385) and pays it to the court
  • Bank levy: served on the debtor's bank; the bank freezes funds in the account and (after a waiting period) pays them to the court
  • Account-receivable garnishment: served on any third party who owes money to the debtor

Exemption claim procedure

Within 30 days of being notified of the writ, the debtor can file a Challenge to Writ of Garnishment (ORS 18.700+) claiming exemptions:

  • Wage exemption (ORS 18.385): only 25% of disposable earnings is garnishable; if disposable earnings are below the statutory minimum (around 40× federal minimum wage), garnishment is zero
  • Head of household / family support (ORS 18.385): if the debtor supports a family, additional protection
  • Federal benefits (Social Security, SSI, VA, federal retirement) — fully exempt under federal and state law
  • State benefits (TANF, OHP, unemployment) — exempt under ORS 18.345+
  • Homestead exemption (ORS 18.395+): up to $40,000 of equity ($50,000 for joint owners) in primary residence
  • Personal property exemptions (ORS 18.345): tools of trade ($5,000), motor vehicle ($3,000), personal property ($3,000), etc.

What to do on receipt of garnishment notice

  1. Calendar the 30-day deadline for filing the Challenge
  2. Photograph the notice and the postmarked envelope
  3. Identify what's being garnished (wages vs. bank account)
  4. Compute exemptions — which categories apply and how much
  5. File the Challenge on the OJD form (Exemption Claim Form) via File and Serve
  6. Serve the creditor under ORCP 9
  7. Attend the hearing (typically held within 21 days of filing) — see or-hearings

See references/garnishment-response.md for the full checklist and form templates.

Supplemental proceedings (debtor exam)

After judgment, the creditor may serve a Notice of Debtor's Examination (ORS 18.265+) requiring the debtor to appear and answer questions about assets, income, and ability to pay.

Mechanics

  • Service: ORCP 7 or under ORS 18.265 — typically personal service
  • Location: courthouse, before the judge or a court reporter
  • Topics: any assets that could be subject to execution; the debtor must answer truthfully
  • Documents: the creditor can subpoena financial records (bank statements, pay stubs, etc.)

Exemptions during exam

The debtor can refuse to answer questions about exempt property — but must affirmatively claim the exemption on the record. Silent refusal is treated as evasion and risks contempt.

Pro se considerations

  • Bring documents requested in the subpoena — failure to produce is sanctionable
  • Answer truthfully — perjury is a felony
  • Claim exemptions on the record — name the property and the statutory ground
  • Take notes — what assets the creditor seems interested in; this informs future planning

See references/supplemental-proceedings.md for the full guide.

Exemption catalog (ORS 18.345–18.385)

Real property

  • Homestead: $40,000 single / $50,000 joint owners of principal residence (ORS 18.395+)
  • Mobile home as principal residence: same

Personal property

  • Motor vehicle: $3,000 equity
  • Tools of trade: $5,000
  • Books, musical instruments, family photos: $600 each
  • Household goods, furnishings, appliances: $3,000 aggregate
  • Wearing apparel, jewelry, personal items: $1,800 + $600 watch
  • Pets: not specifically protected but courts won't generally seize

Earnings

  • Wages: 75% of disposable earnings exempt; lower limit at ~40× federal minimum wage
  • Pensions, retirement, IRAs: exempt (ORS 18.358)
  • Federal benefits (Social Security, SSI, VA, federal retirement): fully exempt under federal preemption

Benefits

  • Unemployment compensation: exempt
  • Workers' compensation: exempt
  • Public assistance (TANF, OHP): exempt
  • Tax refunds / EITC: federal portion exempt; Oregon state EITC also exempt under recent decisions

Bank account safe harbor

When wages or federal benefits are deposited directly into a bank account, those funds retain their exempt character. Under 31 CFR 212, banks must protect 2 months of direct-deposited federal benefits from garnishment. State law (ORS 18.345) similarly protects identified federal benefits.

If garnished, the debtor files a Challenge identifying the funds as exempt federal benefits with bank records showing the deposits.

See references/exemptions.md for the full annotated list with ORS citations.

Satisfaction of judgment

When a judgment has been paid in full, the creditor must file a Satisfaction of Judgment (ORS 18.235 / ORCP 67):

  • Within 60 days of full payment
  • On the OJD form, identifying the case and the amount paid
  • Filed with the court that entered the judgment

If the creditor fails to file a satisfaction, the debtor may move the court for an order declaring the judgment satisfied (ORS 18.235+ procedure).

See references/satisfaction-of-judgment.md for the full mechanism and template.

Judgment renewal

A judgment lives 10 years from entry (ORS 18.182). The creditor may renew once for another 10 years by filing a Motion to Renew Judgment (ORS 18.182(2)) before the original 10-year period expires.

For a debtor, the practical implication: a creditor cannot collect after 20 years (10 original + 10 renewed) unless they manage another renewal — which is procedurally hard. The 10- year clock is a defense to long-stale judgments.

Pro se post-judgment checklist

After receiving any post-judgment paper:

  • Identify the type (garnishment notice, debtor exam notice, satisfaction request, etc.)
  • Photograph the paper and the envelope
  • Calendar all deadlines (30 days for exemption claim; 30 days for vacate; debtor exam date; etc.)
  • Identify which skill applies — vacate? garnishment? exam? satisfaction?
  • Pull the relevant exemption analysis from references
  • Draft the response using the corresponding reference template
  • eFile via File and Serve with the correct UTCR 2.110 code
  • Serve the creditor under ORCP 9 / UTCR 21.100
  • Attend any scheduled hearing — see or-hearings

References

  • references/motion-to-vacate.md — ORCP 71 motion to vacate, full template and checklist
  • references/garnishment-response.md — Challenge to Writ of Garnishment under ORS 18.700+, exemption-claim form, hearing prep
  • references/exemptions.md — full annotated exemption catalog (ORS 18.345–18.385)
  • references/supplemental-proceedings.md — debtor exam preparation and conduct
  • references/satisfaction-of-judgment.md — Satisfaction of Judgment under ORS 18.235; motion to compel satisfaction if creditor refuses

Pro Se Drafting for Oregon Courts

Use this skill when drafting court documents for a pro se litigant in an Oregon circuit court. It encodes the drafting framework adapted to Oregon procedural conventions and the practical service and filing protocols pro se filers need.

NOT LEGAL ADVICE. This skill is a drafting aid for self-represented litigants, not legal advice and not a substitute for counsel. For complex matters, or matters with substantial sums at stake, consider consulting a licensed attorney in your jurisdiction. Verify every rule, deadline, and citation against current law before filing.

The pro-se drafting framework

Every motion and declaration follows four principles:

  1. Front-load the strongest facts. The judge should know the best fact in the case within the first paragraph. Do not bury it under procedural history.
  2. Keep motions concise. Target 4–6 pages for a motion + memorandum. Use bold lead-ins to let the judge skim. Every sentence earns its place.
  3. Write to the judge, not to opposing counsel. Avoid ad hominem. Let the record speak. State facts; let the judge draw the characterizations.
  4. Let the record speak. Attach the documents that prove the point and cite to them by exhibit number and page. A well- indexed record is worth more than rhetoric.

Signature block for pro se (Oregon)

____________________________________
[Full Name]
Defendant, pro se
[Street Address]
[City, OR ZIP]
[Phone]
[Email]
  • Use "pro se" (Oregon convention, same as Washington)
  • Omit OSB number — that's for licensed Oregon attorneys. Including a fake OSB# is grounds for sanctions and could qualify as unauthorized practice of law (ORS 9.160).
  • Include phone (required for chambers contact)
  • Include email (most courts and opposing counsel serve electronically by default)
  • For declarations, also include the perjury clause (ORCP 1 E) above the signature

Service protocol — Oregon

Initial summons and complaint (ORCP 7)

If you (as plaintiff) are filing a new case, the summons and complaint must be served per ORCP 7 — File and Serve cannot serve initial process. Hire a process server or sheriff for personal service unless the defendant has agreed in writing to accept service by mail.

Subsequent filings (ORCP 9, UTCR 21.100)

After the initial complaint, all subsequent filings are served under ORCP 9. Acceptable methods:

  • eService through File and Serve — for parties registered for eService (most attorneys, some pro se litigants)
  • Email — if the parties agreed in writing or the receiving party has eService registered
  • Mail (USPS first-class) — universally acceptable
  • Hand delivery — universally acceptable

Pro se filers without eService access should serve by both email and certified mail (USPS Certified with Return Receipt, or Priority Mail with tracking) — belt and suspenders.

Service best practices for pro se

  1. Photograph postmarked envelopes before opening any incoming mail from the court or opposing counsel — date of postmark is sometimes important
  2. Memorialize every oral or phone interaction with opposing counsel in writing immediately after it happens (a short email "to confirm our call today" is a contemporaneous record)
  3. Keep a complete filing log — date, filing, service method, recipient
  4. Use certified mail whenever opposing counsel has a documented history of false Certificates of Service
  5. Include a Certificate of Service (UTCR 1.090) with every filing, signed and dated

Common pro se pitfalls — Oregon-specific

PitfallFix
Overlong motionsCap at 6 pages; move narrative to declarations
Emotional toneRewrite as neutral fact statements; let the judge characterize
Missing relief clauseEvery motion ends with a clear "RELIEF REQUESTED" section
Citing exhibits without attachingAlways attach, index, and label with exhibit numbers (NOT letters — Oregon convention)
Forgetting the ORCP 1 E perjury clauseEvery declaration needs the "I declare under penalty of perjury under the laws of the State of Oregon..." clause
Colored or highlighted textViolates UTCR 2.010 — use bold/italic for emphasis
Missing Notice of HearingMost counties require a Notice of Hearing to set the motion on calendar
Ambiguous signature blockAlways include name, "pro se" designation, address, phone, email — NO OSB#
Trying to serve interrogatoriesOregon does not permit interrogatories under ORCP without a court order. Use RFPs (ORCP 43) and depositions instead. See or-discovery.
Citing "CR 12(b)(6)"Use ORCP 21 A(8) — Oregon's analog to FRCP 12(b)(6)
Citing "RCW" or Washington rulesOregon uses ORS (Oregon Revised Statutes), not RCW
Using "vs."Oregon uses "v." (with period) — not "vs."
Lettered exhibits (A, B, C)Oregon convention is numbered (1, 2, 3)
Filing federal-style citationsOregon Style Manual uses no periods in "Or", "Or App", "P3d", "USC", "CFR"

Drafting checklist (run before filing)

  • Caption is complete and matches the case number exactly
  • Court header uses "IN THE CIRCUIT COURT OF THE STATE OF OREGON" + "FOR THE COUNTY OF [COUNTY]"
  • Parties separator is "v." (with period), not "vs."
  • First paragraph states the single most important fact
  • Every factual assertion is supported by an exhibit or sworn statement
  • Motion ≤ 6 pages; longer content moved to declaration
  • Relief requested is spelled out at the end
  • Perjury clause (ORCP 1 E form) present on all declarations
  • Signature block includes name, pro se designation, address, phone, email — NO OSB#
  • Footer shows document title and "Page X of Y" on every page
  • UTCR 2.010 compliant (3″ top margin page 1, 1″ elsewhere, no color)
  • Certificate of Service attached with date and method
  • All exhibits listed, cover-paged, and referenced in the body by number (not letter)
  • Confidential personal info redacted per UTCR 2.120 (SSN last 4 only, etc.)

Oregon-specific pro se resources

Statewide

Legal aid

County-specific

  • Multnomah Civil Self-Help: Floor 3, Central Courthouse
  • Washington Co Civil Self-Help: limited; Civil Division counter answers procedural questions
  • Lane: Eugene Justice Center has a Civil Self-Help counter
  • Marion: Salem courthouse has a self-help kiosk

Companion skills

  • Use or-statewide-format for the actual document templates, caption structure, and UTCR 2.010 formatting
  • If the case is in Multnomah Circuit Court, use or-multcc for chambers / JA / SLR specifics
  • If the case is in Washington County, use or-wccc for Civil Division / SLR specifics
  • For any other Oregon county, use or-county-courts

References

  • references/pro-se-drafting-framework.md — full drafting guide with Oregon-flavored examples
  • references/service-protocol.md — service, postmark preservation, Certificate of Service templates per UTCR 1.090
  • references/pro-se-toolkit.md — common motion types and how to draft them without counsel

Quality Check — Format + Content

Run a two-pass quality check on an Oregon court document before filing.

NOT LEGAL ADVICE. Formatting and quality checks verify the surface — they don't tell the user whether the underlying legal position is sound. Verify current rules before filing; pair with substantive review by counsel where stakes warrant.

Arguments

If the user names a file path, use it. Otherwise, glob the workspace for recent .docx files and ask which one to check.

Pass 1 — Format check (UTCR 2.010)

  1. Run the checker:

    python3 "${CLAUDE_PLUGIN_ROOT}/scripts/format-check.py" "<path>"
    
  2. Parse output and summarize:

    • ✅ PASS: item complies
    • ⚠️ WARN: item may deviate; user should verify manually
    • ❌ FAIL: item does not comply; must be fixed
  3. What is checked:

    • Paper size (Letter: 8.5" × 11")
    • Margins (1" on all sides at minimum; 3" top on page 1 is a strong recommendation per UTCR 2.010(2))
    • Line spacing (≥ 1.5 for body)
    • Font family (Times New Roman or similar proportional serif)
    • Font size (≥ 12pt in body)
    • No color text, no highlighting (UTCR 2.010 "black or blue-black ink only")
    • Footer contains PAGE and NUMPAGES fields (per the plugin's footer convention)
    • Numbered paragraphs (if declaration)
  4. For each failure, explain:

    • What UTCR 2.010 requires
    • Where the deviation is
    • How to fix it (in Word or by regenerating with the docx-js template)

Pass 2 — Content check

Caption and header

  • Court header is correct: "IN THE CIRCUIT COURT OF THE STATE OF OREGON" + "FOR THE COUNTY OF [COUNTY]"
  • Cause number present and correctly formatted (e.g., 25CV12345 for civil; 25SC##### for small claims; 25DR##### for domestic relations)
  • Parties correctly styled (Plaintiff, Defendant — not "Plaintiff(s)" unless multiple, not "the parties")
  • Document title on page 1 matches body and footer
  • Use "v." between parties (not "vs.")
  • "pro se" notation on signature block if applicable
  • OSB# present if counsel; omitted if pro se
  • UTCR 2.120 — confidential personal data redacted (SSN last 4 only; account numbers last 4; minor children initials; etc.)

Structure (pro-se drafting framework, for motions)

  • MOTION section is short and declarative
  • I. Relief Requested — one paragraph, specific
  • II. Statement of Facts — numbered, each with record citation
  • III. Statement of Issues — 1 to 3 yes/no questions
  • IV. Evidence Relied Upon — list with exhibit numbers (NOT letters)
  • V. Authorities — rules and cases
  • VI. Argument — organized by issue, with bold lead-in headings
  • VII. Conclusion — one paragraph, restate relief
  • Length ≤ 6 pages for memorandum

Citations (Oregon Style Manual)

  • Oregon cases cite Or / Or App (no periods)
  • Parallel cites use P2d / P3d (no periods)
  • Federal cases use F / F2d / F3d (no periods); 9th Cir (no periods); US / S Ct (no periods)
  • ORS cited as ORS 12.080(1) (no section symbol; lowercase letters in parens for sub-subs)
  • ORCP cited as ORCP 21 A(8) (capital letter separated by space; parens for lower)
  • OEC cited as OEC 803(6)
  • UTCR cited as UTCR 2.010(1)
  • USC cited as 15 USC § 1692k(a)(1) (no periods in "USC"; section symbol)
  • CFR cited as 12 CFR § 1006.30 (no periods)
  • No Rule 12(b)(6) or CR 12(b)(6) (Federal / Washington — Oregon is ORCP 21 A(8))
  • No RCW cites (Washington — Oregon is ORS)

Exhibits (if applicable)

  • Exhibits numbered, not lettered (Oregon convention)
  • Each exhibit referenced in the body by number
  • Exhibit List present at end of declaration
  • Cover page for each exhibit
  • Pagination continuous through exhibits

Declarations (if applicable)

  • ORCP 1 E perjury clause present: "I declare under penalty of perjury under the laws of the State of Oregon that the foregoing is true and correct."
  • Salutation at top: "I, [Name], declare under penalty of perjury..."
  • Numbered paragraphs of substantive facts
  • Date and place ("Executed at [City], Oregon")
  • Signature block with name, role, address, phone, email
  • No argument mixed with facts

Motion-specific checks

Motion to dismiss (ORCP 21):

  • Specific sub-letter cited (A(1), A(2), ..., A(8), B, E)
  • If A(8) "failure to state ultimate facts": brief identifies which element of which claim fails

Motion to compel (ORCP 46 A):

  • Meet-and-confer certification present and detailed (Multnomah SLR 5.045 / Washington Co SLR 5.046)
  • Specific RFPs at issue identified
  • ORCP 46 A(4)(a) fee-shifting requested

Motion for summary judgment (ORCP 47):

  • Filed at least 60 days before trial (verify against case schedule)
  • Statement of undisputed material facts (with record citations)
  • Each element of claim/defense analyzed
  • Affidavits/declarations comply with ORCP 47 D (personal knowledge, admissible facts)

Motion to vacate (ORCP 71):

  • Specific ground identified (B(1)–B(6))
  • If grounds (1)–(3): within 1 year of judgment
  • Diligence narrative (when discovered, when filing)
  • Meritorious defense (proposed answer attached)
  • Lack of prejudice to opposing party

Signature block

  • Name in ALL CAPS or bold
  • Role identified (Plaintiff/Defendant, pro se OR counsel of record + OSB#)
  • Street address (Oregon city + ZIP)
  • Phone
  • Email
  • No OSB# if pro se (and conversely OSB# IS present if counsel)

Certificate of Service (UTCR 1.090)

  • Present at the end of every served document
  • Date of service
  • Method (eService, email, mail, hand)
  • Name and address (or email) of each party served
  • Signature of the server

Pass 2 output

The agent produces a report like Pass 1:

=== Content Check ===
Document: motion-to-compel.docx
Date: [today]

Caption: [PASS]
  - Court header correct
  - Case number 25CV12345 valid
  - Parties Plaintiff/Defendant
  - "v." used (not "vs.")
  - pro se on signature; no OSB#

Structure: [WARN]
  - PASS: All seven sections (I–VII) present
  - WARN: Memorandum is 7 pages — slightly over the 6-page
    Parker target; consider moving paragraph 5–6 of facts
    to the declaration

Citations: [FAIL]
  - PASS: ORCP cites use Oregon Style Manual format
  - FAIL: Two cases use Bluebook format ("Or." and "P.3d")
    instead of Oregon style ("Or" and "P3d"). Specifically:
      Mattiza v. Foster, 311 Or. 1, 803 P.3d 723 (1990)
      → Mattiza v. Foster, 311 Or 1, 803 P2d 723 (1990)

Exhibits: [PASS]
  - Numbered 1–4
  - Exhibit List present
  - Cover pages present

Summary: 4 PASS, 1 WARN, 1 FAIL

Composition

This skill ALWAYS composes with:

  • or-statewide-format — for the UTCR 2.010 requirements
  • The relevant court skill — for local-rule particulars

It typically follows the draft-* skills (which produce the document) and precedes or-fact-check (which verifies the substantive content).

Cross-references

  • scripts/format-check.py — the Pass 1 checker
  • or-statewide-format — UTCR 2.010 baseline
  • or-pro-se — pro-se drafting framework
  • or-fact-check — substantive verification pass
  • or-law-references/references/citation-format.md — Oregon Style Manual rules

Reserve a Hearing Date in an Oregon Circuit Court

In most Oregon circuit courts, a civil motion cannot simply be self-noticed for a date. The moving party must request a date from the court (the assigned judge's judicial assistant, the Civil Division, or the Court Administrator, depending on the county). After confirmation, the Notice of Hearing is filed.

This skill drafts the date-request email (or call log) — the necessary precursor step.

NOT LEGAL ADVICE. This skill drafts a scheduling communication as a procedural aid, not legal advice. Verify current per-court protocols and local-rule requirements before sending. Pair with substantive review by counsel where stakes warrant.

Per-county routing

Different Oregon counties route hearing requests through different intermediaries:

CourtContact route
MultnomahAssigned judge's JA (email)
Washington CoCivil Division (email or phone)
ClackamasCivil counter at 807 Main Street
LaneJA for most civil judges; Court Administrator otherwise
MarionCivil Department on Floor 2
JacksonCivil Division clerk
DeschutesCourt coordinator
Most rural countiesCourt coordinator or centralized motion docket clerk

Confirm the routing from the assigned court's website before drafting. The Multnomah / Washington / Lane / Marion judge pages list JA contacts; smaller counties' clerk's offices typically have a single Civil contact line.

Inputs to ask the user

  • County: Multnomah, Washington, Lane, etc.
  • Assigned judge: name and (if Multnomah/Lane) JA email
  • Case caption and number
  • Motion type: the title of the motion (e.g., "Motion to Compel Production of Documents Under ORCP 46 A")
  • Filing status: motion already filed? Or to be filed after date is confirmed?
  • Estimated argument time: 10, 15, 20, 30 minutes
  • Date preferences: 2–3 proposed dates
  • Opposing party: have they been consulted on dates? What's their position?

Email template — Multnomah (JA-based)

To:      [Assigned Judge's JA email]
Subject: Hearing Date Request — [Case Short Title],
         Case No. [Cause Number]

Dear [Judicial Assistant Name]:

I am [Counsel of record / Defendant, pro se] in the above-
captioned matter, assigned to the Hon. [Judge Name].

I am requesting a hearing date for [Motion Title], filed
[date] (or to be filed [date]). Estimated argument time:
[20 minutes].

Proposed dates:
   [Date 1]
   [Date 2]
   [Date 3]

I have [conferred / not yet conferred] with opposing
counsel on these dates. [Opposing counsel [agrees / objects
to / has not responded re] each / specific dates.]

If WebEx is the Court's preferred mode for this motion,
please confirm and I will include the connection details on
the Notice of Hearing.

Thank you,
[Name][, pro se / OSB # ____ if counsel]
[Address]
[Phone]
[Email]

Email template — Washington County (Civil Division)

To:      WCCCCivilCT@ojd.state.or.us
Subject: Hearing Date Request — [Case Short Title],
         Case No. [Cause Number]

Civil Division:

I am [Counsel of record / Defendant, pro se] in the above-
captioned matter, assigned to the Hon. [Judge Name].

I am requesting a hearing date for [Motion Title], to be
filed [date]. Estimated argument time: [X minutes].

Proposed dates:
   [Date 1]
   [Date 2]
   [Date 3]

I have / have not conferred with opposing counsel on these
dates.

If the Court prefers WebEx or telephone, please advise so I
can include the connection details on the Notice of Hearing.

Thank you,
[Name][, pro se / OSB # ____]
[Contact info]

Email template — other counties

To:      [Civil Division / court coordinator / JA email]
Subject: Hearing Date Request — [Case Short Title],
         Case No. [Cause Number]

[Salutation appropriate to the contact]

I am [role] in [case short title], Case No. [cause number],
assigned to [Judge Name if known].

I am requesting a hearing date for [Motion Title], to be
filed [date]. Estimated argument time: [X minutes].

Proposed dates:
   [Date 1]
   [Date 2]
   [Date 3]

If the Court prefers WebEx or telephone, please advise so I
can include the connection details on the Notice of Hearing.

Thank you,
[Name][, pro se / OSB # ____]
[Contact info]

Phone log template

For counties where date reservation is by phone (some rural counties), document the call:

Call log — [Date]

To:    [Contact name and number]
From:  [Your name and number]
Re:    Hearing date request, Case No. [cause number]

Notes:
- Identified myself and the case
- Stated motion type and estimated time
- Proposed [Date 1], [Date 2], [Date 3]
- [Court contact] confirmed [Date X] at [Time] in
  [Courtroom / WebEx]
- [Court contact] noted [any standing orders or working-copy
  requirements]
- Confirmed by email at [time]

Follow up the call with an email confirming the reservation ("To confirm our call today, the hearing on Defendant's Motion to Compel is set for [Date] at [Time] in [Mode] before the Hon. [Judge]. I will file the Notice of Hearing within [period].").

Information needed in the date-request

The court contact needs to know:

  1. Case identification — caption short title and number
  2. Motion identification — title, ORCP/UTCR authority
  3. Argument time estimate — affects calendar slot
  4. Mode preferences (or simply asking what's available)
  5. Proposed dates — give 2–3 options
  6. Opposing party status — conferred? agreed? objecting?

After confirmation

Once the court confirms the date:

  1. Calendar it — date, time, mode, courtroom, judge
  2. Save the confirmation email as evidence of reservation
  3. Draft the Notice of Hearing (use or-draft-note)
  4. File the Notice within the local SLR window (Multnomah: 3 business days; Washington Co: simultaneous with motion)
  5. Serve the Notice on all parties
  6. Set hearing-prep reminders at 7, 3, 1 day(s) out

Common pitfalls

PitfallConsequence
Going to the wrong contact (JA when it's Civil Division, or vice versa)Wasted email; delay
Not identifying the assigned judgeCivil Division may not know which calendar
Proposing dates too close to trialCourt may decline if motion can't be heard before relevant cutoff
Forgetting estimated timeCourt may set a too-short slot
Failing to consult opposing counselCourt may strike or reschedule; bad first impression
Not following up the call with an emailNo paper record; disputes about the reservation
Filing the Notice before the JA confirmsConfusion; possible rejection

Pro se considerations

  • Email is generally fine; phone is fine too
  • Be professional; the JA / Civil Division clerk is doing you a favor by scheduling
  • Don't follow up too aggressively; allow 1–2 business days before re-contacting
  • Save every email — court contacts are part of the record

Cross-references

  • or-draft-note — drafts the Notice of Hearing (the follow-up document)
  • or-multcc/references/civil-motion-scheduling.md — Multnomah JA process
  • or-wccc/references/civil-motion-practice.md — Washington Co Civil Division process
  • or-county-courts — other counties
  • or-file-packet — final packet assembly

Oregon Statewide Court Document Formatting

Use these rules whenever drafting a paper to be filed in an Oregon circuit court. They derive from the Uniform Trial Court Rules (UTCR) Chapter 2 (Form of Documents) and common statewide drafting conventions used by the Oregon Judicial Department (OJD).

Oregon consolidated its trial courts in 1998 — there is no separate district court system. All civil matters file in Circuit Court regardless of amount in controversy. Small claims (≤ $10,000) and court-annexed mandatory arbitration ($10,000–$50,000) are sub-procedures within Circuit Court (ORS Ch. 46 and ORS 36.400 et seq., respectively).

NOT LEGAL ADVICE. Generated content is a drafting aid; verify against current UTCR, ORCP, and the local Supplemental Local Rules (SLR) for the specific circuit before filing.

UTCR 2.010 format requirements (mandatory)

ItemRule
Paper sizeUS Letter, 8½ × 11 inches
SidesSingle-sided only
Top margin, page 1At least 3 inches to leave room for the clerk's filing stamp
All other marginsAt least 1 inch (top of subsequent pages, bottom, left, right)
ColorBlack or blue-black ink only; no colored or highlighted text in the body
Attachments / exhibitsSame rule applies unless the nature of the attachment makes compliance impractical (color photo as evidence, native screenshots)
CitationsConform to the Oregon Appellate Courts Style Manual (latest edition, OJD)
eFilingMandatory in every circuit court through File and Serve (Tyler) — accept PDFs only

When producing a .docx programmatically for upload to File and Serve, apply a 1-inch top margin to the whole section and add ~2 inches of leading space before the caption on page 1 so the effective top margin for page 1 is 3 inches. Subsequent pages then fall at 1 inch automatically.

Do not use colored highlighting or colored text anywhere in the pleading body. Color is permitted in attachments only when the nature of the attachment makes B&W impractical (for example, a native phone screenshot).

Default typography

  • Font: Times New Roman 12 pt (Arial 12 pt is also accepted)
  • Line spacing: 1.5 or double-spaced for body text; single-spaced for block quotations, signature blocks, and tables
  • Paragraph numbering: Bold Arabic numeral followed by a period and tab, e.g. 1.\tI am the Defendant...
  • Bold lead-ins for labeled paragraphs: **Background.** at the start of a paragraph, then regular text

Required footer (mandatory on every generated document)

Every generated document MUST carry a running footer on every page with:

  • Left: a short document identifier — typically [Document title] — Case No. [case number] (e.g., Motion to Compel — Case No. 25CV12345). Keep it to a single line so it never wraps.
  • Right: Page X of Y, where X is the current page and Y is the total page count. Use Word's PAGE and NUMPAGES fields — never a static number.
  • Font: 10 pt Times New Roman (matches body font family; smaller for visual hierarchy).
  • Alignment: a right-aligned tab stop at 9,360 DXA (6.5″) places the page counter flush right while the title stays flush left.

The footer runs continuously from page 1 through the last exhibit page — do not restart or suppress pagination anywhere. scripts/format-check.py validates the footer and will FAIL on a document missing the NUMPAGES field, the PAGE field, or a non-pagination title on the left.

See references/docx-generation.md for the exact docx-js recipe.

Line numbering (pleading paper)

Apply continuous line numbering down the left margin of every generated pleading — the classic "pleading paper" convention. Line numbers count every line of the body and restart on each page.

UTCR 2.010 does not itself require line numbering, and an Oregon filing without it is rule-compliant. But line-numbered pleading paper is common across Oregon civil practice and lets the court and opposing counsel cite to an exact location ("page 4, lines 12–15"). Apply it by default to every motion, memorandum, declaration, notice of hearing, and proposed order. Exhibits and attachments are exempt.

Set line numbering on the section properties — count every line, restart each page. The numbers sit in the left margin and do not change the 1-inch text margin. See references/docx-generation.md for the exact docx-js recipe, including the start-attribute caveat (pass no start value — an explicit start: 1 renders off by one in LibreOffice).

Margin rule (double vertical line)

Draw a double vertical rule — two thin parallel lines (~0.75 pt each, with a ~7 pt gap between them) — down the left margin between the line numbers and the body text. It is the standard companion to line-numbered pleading paper. Like line numbering, UTCR 2.010 does not require it, but it is common convention. Apply it by default to every line-numbered pleading; exhibits and attachments are exempt.

Implement it as two independent full-height line shapes anchored in the page header, so they repeat on every page — not as an OOXML double page border, whose style couples the inter-line gap to the line weight (widening the gap thickens both lines into heavy bars). See references/docx-generation.md for the exact recipe.

Caption structure (UTCR 2.100)

Two columns separated by a vertical rule:

            IN THE CIRCUIT COURT OF THE STATE OF OREGON
                  FOR THE COUNTY OF MULTNOMAH

VELOCITY INVESTMENTS, LLC,         │  Case No. 25CV12345
                                   │
        Plaintiff,                 │  [DOCUMENT TITLE IN ALL CAPS,
                                   │   BOLD, WRAPPED TO 4–6 LINES]
        v.                         │
                                   │
JOHN DOE,                          │
                                   │
        Defendant.                 │

UTCR 2.100 requirements:

  • Court header (top, centered, bold): "IN THE CIRCUIT COURT OF THE STATE OF OREGON" on line 1, "FOR THE COUNTY OF [COUNTY]" on line 2
  • Party block (left): parties in ALL CAPS, bold; role (Plaintiff, Defendant, Petitioner, Respondent) in normal case, indented under the party name
  • Case number (top right, bold): 25CV12345 (year-CV-sequence, no spaces or dashes) for civil cases; small claims 25SC12345; domestic relations 25DR12345
  • Document title (right, all caps, bold, wrapped): the full UTCR 2.110 title — every required descriptor in capitals
  • Vertical rule: one line, on the right edge of the left cell OR the left edge of the right cell (not both — avoids double rules). This caption-internal column divider is distinct from the left-margin double rule above; do not conflate the two.
  • Horizontal rule below the caption separating it from the body

Build the caption as a two-cell borderless table; add the vertical border as above. Cell widths 4,680 DXA each on a 9,360 DXA (6.5-inch) content area.

Use "v." (lowercase, with period) between parties — Oregon convention. Not "vs."

UTCR 2.110 — Document titles

The title at the top of the document (and in the caption) must:

  • Be in ALL CAPS, bold
  • State the party making the filing (e.g., "DEFENDANT'S MOTION TO COMPEL")
  • State the nature of the document with enough specificity that the clerk can index it correctly (e.g., "MOTION TO COMPEL PRODUCTION OF DOCUMENTS UNDER ORCP 46")
  • Identify whether the matter is on the merits or part of a subsidiary proceeding (small claims, mandatory arbitration, etc.)
  • For motions: state whether oral argument is requested and the type of hearing (e.g., "ORAL ARGUMENT REQUESTED — 20 MINUTES")

The title appears in three places: the caption right column, again at the top of the body on page 1, and in the document filename when uploaded to File and Serve.

UTCR 2.120 — Confidential information

Redact before filing. UTCR 2.100(7) and 2.120 require that the following be omitted from publicly filed documents:

  • Social Security numbers (use last four digits only)
  • Bank account numbers, credit-card numbers (last four only)
  • Dates of birth (year only, except for minor parties in family cases)
  • Names of minor children (use initials)
  • Home addresses of victims, witnesses (where applicable)

Confidential personal information is filed on a separate Confidential Information Form (CIF) under UTCR 2.130 and is sealed by the clerk.

Required body elements

Every declaration needs (under ORCP 1 E and ORS 9.320, declarations "under penalty of perjury" are accepted in place of notarized affidavits for most filings — see ORCP 1 E and 28 USC § 1746 language):

  1. Salutation clause at the top of the body: "I, [Name], declare under penalty of perjury under the laws of the State of Oregon that the following is true and correct:"
  2. Numbered paragraphs with substantive content
  3. Verification clause at the end (Oregon form): "I hereby declare that the above statements are true to the best of my knowledge and belief, and I understand they are made for use as evidence in court and are subject to penalty for perjury." (Or the shorter ORCP 1 E form: "I declare under penalty of perjury under the laws of the State of Oregon that the foregoing is true and correct.")
  4. Date and place of execution: "DATED this ____ day of ________, 20." "Executed at [city], Oregon."
  5. Signature block with signer name, role, address, phone, email

Motions and memoranda do not need a perjury clause but do need a signature block with name, role, address, phone, and email, plus a Certificate of Service (UTCR 1.090 / ORCP 9 G) if served with the filing.

Exhibits

Embed exhibits at the end of the paper, after the signature block, in this order:

  1. Exhibit List page, centered title, each entry like: Exhibit 1: [one-line description]
  2. One cover page per exhibit: EXHIBIT 1 centered and bold at the top of the page, followed by an italic caption describing the exhibit, then the exhibit image or text
  3. Footer pagination continues through the exhibits — do not restart the page counter

Oregon convention is numbered exhibits ("Exhibit 1, Exhibit 2, ...") not lettered. This differs from Washington (lettered, "Exhibit A, Exhibit B, ..."). Reference exhibits in the body by number: "True and correct screenshots are attached as Exhibits 1 through 4."

The four document templates

See the references/templates/ directory for complete scaffolds:

  • declaration.md — declaration with numbered paragraphs and exhibits
  • motion-with-memo.md — motion with companion memorandum
  • notice-of-hearing.md — Oregon-standard notice form (analogous to a "Note for Motion Docket")
  • proposed-order.md — findings and order for judge signature

Each template includes the caption, body skeleton, signature block, and (for declarations) exhibit list scaffolding.

Citation format (Oregon Appellate Courts Style Manual)

Follow the Oregon Appellate Courts Style Manual (the "OACSM" or "Oregon Style Manual") published by the OJD. Common forms:

  • Oregon Supreme Court: Buchler v. Oregon Corrections Div., 316 Or 499, 853 P2d 798 (1993)
  • Oregon Court of Appeals: State v. Smith, 250 Or App 1, 280 P3d 1 (2012)
  • 9th Circuit: Mansor v. Or. Inv. Co., 819 F3d 1119 (9th Cir 2016)
  • ORS: ORS 12.080(1) (no section symbol for ORS in Oregon style)
  • ORCP: ORCP 47 C (subsections by upper-case letter, separated by spaces, no parentheses)
  • OEC: OEC 803(6) (subsections in parentheses, by number)
  • UTCR: UTCR 2.010(1)
  • Federal statutes: 15 USC § 1692k(a)(1) (no periods in "USC" in Oregon style; Bluebook would use "U.S.C.")
  • Federal regulations: 12 CFR § 1006.30 (Oregon style; no periods in "CFR")

Distinctive Oregon style choices:

  • No periods after Or, Or App, P2d, P3d, F2d, F3d, US, USC, CFR (Bluebook puts periods after all)
  • Use v. (with period) between parties; italicize case names including the v.
  • Spaces, not parentheses, separate ORCP subsection letters: ORCP 21 A not ORCP 21(A)
  • OEC subsections use parentheses with numerals: OEC 803(6)
  • No "&" or "et seq." within citations — use page pins

Italicize case names (including v.). Use the regional reporter (P2d / P3d) — Oregon does not have its own state reporter for the Supreme Court, only the Oregon Reports (Or, Or App), which are parallel-cited.

Producing documents programmatically

For .docx generation, use the docx npm package and follow the patterns in references/docx-generation.md. Key points:

  • Set page size explicitly to US Letter (12,240 × 15,840 DXA) — docx-js defaults to A4
  • Use Times New Roman at size: 24 (half-points = 12 pt)
  • Add a leading paragraph with spacing: { before: 2880 } (2 inches) on page 1 to yield the 3-inch effective top margin
  • Use LevelFormat.BULLET with a numbering config for bullets — never unicode bullet characters
  • Build the footer with a right-aligned tab stop at 9,360 DXA and use PageNumber.CURRENT / PageNumber.TOTAL_PAGES for "Page X of Y"

For format validation, use the bundled scripts/format-check.py on a generated .docx.

eFiling — OJD File and Serve

Every Oregon circuit court accepts (and requires) electronic filing through File and Serve (Tyler Tech), the OJD's statewide eFiling portal:

Service through File and Serve counts as service for parties who have registered for eService (ORCP 9 G(1)(d), UTCR 21.100). For parties who have not registered, follow ORCP 9 D (mail, hand delivery, or any of the other approved methods).

Compose with court-specific skills

This skill is always layered with:

  • or-multcc — if the case is in Multnomah County Circuit Court
  • or-wccc — if the case is in Washington County Circuit Court
  • or-county-courts — for any other county
  • or-pro-se — if the litigant is self-represented

The court-specific skill adds the local SLR variations, motion scheduling, working-copy practice, and the venue-specific filing quirks.

References

  • references/utcr-2-010-full-text.md — the full rule text for quick citation
  • references/caption-format.md — caption structure with full docx-js example
  • references/exhibit-handling.md — exhibit list, cover page, and pagination
  • references/docx-generation.md — docx npm library patterns for Oregon pleadings
  • references/templates/ — the four document templates

Post-Hearing Order Submission — Oregon

After the judge rules from the bench (or by written order), the prevailing party typically submits the proposed order for signature — with any modifications the court ordered at the hearing. This skill handles the post-hearing workflow.

NOT LEGAL ADVICE. This skill is a procedural and drafting aid, not legal advice. Verify the bench ruling against the court's order or recording, and verify current rules and deadlines before transmitting. Pair with substantive review by counsel where stakes warrant.

Three post-hearing scenarios

Scenario 1: Judge rules from the bench

The judge announces the ruling during the hearing, sometimes with specific modifications to the proposed order ("I'm granting this, but I want the production deadline at 21 days, not 14"). The prevailing party:

  1. Notes the bench modifications carefully
  2. Applies them to the proposed order (tracked changes if sharing with opposing for approval as to form)
  3. Removes the "[PROPOSED]" bracket from the title
  4. Re-serves the modified order on opposing under UTCR 5.100
  5. After 3 court days without objection, submits to chambers for signature

Scenario 2: Court takes under advisement

The court will rule by written order, typically 2–6 weeks later. The prevailing party (once the ruling issues):

  1. Reviews the court's written order
  2. If the order is fully self-executing (the court drafted it), no further submission required
  3. If the order directs the prevailing party to submit a proposed order, drafts the order matching the court's reasoning and submits

Scenario 3: Stipulated outcome

The parties stipulated before or during the hearing. The prevailing party (or the parties jointly):

  1. Drafts the order reflecting the stipulation
  2. Title: "[STIPULATED] ORDER..." (the bracket comes off when the judge signs)
  3. Both parties sign in the "Approved as to Form" line
  4. Submitted to chambers

Step-by-step (Scenario 1 — most common)

Step 1: Capture bench modifications

During the hearing, write down the specific modifications the court directed. Examples:

  • "Production deadline extended to 21 days, not 14"
  • "Plaintiff's objection to RFP 6 sustained; production required only for RFPs 3 and 5"
  • "Fee award reduced to $1,500 from the requested $2,400"
  • "Defendant's request for protective order denied without prejudice"

If unclear, ask the court for clarification before leaving the hearing.

Step 2: Apply modifications

Edit the proposed order:

  • Update the relevant relief paragraphs (A, B, C ...)
  • Remove the [PROPOSED] bracket from the title
  • Update the date line — leave blank for the judge's signature date (the judge writes in the date when signing)
  • Update the findings if the court's reasoning was different from the original draft

Step 3: Re-serve under UTCR 5.100

UTCR 5.100 requires that opposing parties have 3 court days to object to the form of the order before submission to the court.

Send the modified order:

To:      [Opposing counsel]
Subject: Proposed Order — Case No. 25CV12345, Motion to
         Compel

Counsel:

Attached is the proposed Order on Defendant's Motion to
Compel, modified to reflect the Court's rulings from the
[date] hearing:

  - [List the specific modifications applied]

If you have objections to the form, please respond within 3
court days. If we do not hear from you by [date], we will
submit the Order to chambers as drafted.

Best,
[Name][, pro se]

If opposing objects to the form (not the substance), negotiate the language; if no agreement, submit with a Notice of Presentation explaining the dispute.

Step 4: Submit to chambers

After the 3-court-day window:

Multnomah / Lane / counties with JA email

Email the assigned judge's JA:

To:      [JA email]
Subject: Order for Signature — Case No. 25CV12345

Dear [JA Name]:

Attached is the proposed Order on Defendant's Motion to
Compel, heard on [date]. The Order has been served on
opposing counsel for 3 court days under UTCR 5.100; no
objections to form were raised (or: objections noted in the
attached Notice of Presentation).

Please present to Judge [Name] for signature at the Court's
convenience.

Both the .docx and PDF formats are attached. Once signed,
please file in the case.

Thank you,
[Name][, pro se]
File and Serve (alternative)

In some counties, the order is filed in File and Serve under "Order — Proposed" rather than emailed to chambers. Check the assigned judge's standing order and the local SLR.

Washington Co (Civil Division)

For Washington Co (Oregon), submit through Civil Division either via email (per the assigned judge's standing order) or File and Serve.

Step 5: Track compliance with the signed order

Once the judge signs and the order is filed:

  • Calendar all deadlines the order sets (production deadlines, payment deadlines, etc.)
  • Calendar the 14-day ORCP 68 C(2) Statement of Attorney Fees deadline if fees were awarded
  • Calendar follow-up dates — e.g., status conference, next motion deadline

The signed order is the operative judgment for the issue ruled upon. Comply with the deadlines; failure to comply exposes the non-complying party to contempt or further motions.

Template — modified post-hearing order

            IN THE CIRCUIT COURT OF THE STATE OF OREGON
                  FOR THE COUNTY OF MULTNOMAH

VELOCITY INVESTMENTS, LLC,      │   Case No. 25CV12345
                                │
     Plaintiff,                 │   ORDER GRANTING DEFENDANT'S
                                │   MOTION TO COMPEL
     v.                         │   PRODUCTION OF DOCUMENTS
                                │   UNDER ORCP 46 A
JOHN DOE,                       │
                                │
     Defendant.                 │
────────────────────────────────────────────────────────────

This matter came before the Court on Defendant's Motion to
Compel Production of Documents Under ORCP 46 A, filed
[date]. A hearing was held on [date] before the Hon.
[Judge Name]. The Court [granted / denied / granted in
part] the Motion.

THEREFORE, IT IS HEREBY ORDERED that:

A.  Defendant's Motion to Compel is GRANTED;

B.  Plaintiff shall produce all documents responsive to
    Requests for Production Nos. 3 and 5 within **21**
    calendar days of the date of this Order, or by
    ____________, 20__, whichever is sooner; [modified
    from the original 14-day proposal per the Court's
    ruling from the bench on [date]]

C.  Plaintiff's objection to Request No. 6 is sustained;

D.  Defendant is awarded reasonable expenses, including
    attorney fees, in the amount of **$1,500** [modified
    from the original $2,400 request per the Court's
    ruling]; payable within 30 days of the date of this
    Order;

E.  Defendant's Statement of Attorney Fees and Costs
    requirement under ORCP 68 C(2) is waived in light of
    the Court's specific award above.

DATED this ____ day of __________, 20__.


                            _______________________________
                            CIRCUIT COURT JUDGE


Presented by:
______________________________________
JOHN DOE
Defendant, pro se
[Address]
[Phone]
[Email]


Notice of Presentation:
This Order tracks the Court's ruling at the [date] hearing.
A copy was served on Plaintiff's counsel on [date]; the 3
court days under UTCR 5.100 have elapsed without form
objection [or: objections received and addressed as
follows: ...].

The key changes from the pre-hearing version:

  • [PROPOSED] bracket removed from the title
  • 14-day deadline changed to 21 (and noted as modified)
  • $2,400 fee request reduced to $1,500 (and noted)
  • Fee award is now specific, so ORCP 68 C(2) waived
  • Notice of Presentation reflects the 3-court-day service

Working with opposing counsel on form

For cooperative opposing counsel, "Approval as to Form" is the clean alternative to a Notice of Presentation:

Approval as to Form:
______________________________________
[Plaintiff's Counsel Name, OSB # ______]
Attorney for Plaintiff Velocity Investments, LLC

Plaintiff's counsel signs in the "Approval as to Form" line before submission. This eliminates any form objections and speeds chambers' processing.

UTCR 5.100 — Order submission timing

StepTiming
Re-serve modified order on opposingDay 0
Opposing has 3 court days to objectDays 1–3
Submit to chambers (if no objection)Day 4+
Judge signsVariable (1 day to several weeks)
Signed order entered on docketSame day as signing

Common post-hearing mistakes

MistakeConsequence
Forgetting to remove [PROPOSED] from titleOrder looks pre-hearing; clerk may reject
Not applying bench modificationsOrder doesn't match ruling; judge may reject
Skipping the 3-court-day re-serveUTCR 5.100 violation; opposing can move to set aside
Submitting via wrong route (clerk vs. chambers)Delay; possible loss in the system
No Notice of Presentation when there's no Approval as to FormUTCR 5.100(2) violation
Missing deadlines set by the signed orderContempt; further motions
Forgetting to file the ORCP 68 C(2) StatementWaives fee claim

Pro se considerations

  • Drafting tone in the modified order should match the pre-hearing draft — clear, precise, neutral
  • Be conservative in applying bench modifications — when in doubt, capture what the judge said and stop
  • The judge's signature is on the date they signed; the effective date of the order is the date of entry
  • Read the signed order when it's filed — if the judge made further modifications on the bench at signing, those bind

Cross-references

  • or-draft-order — pre-hearing proposed order (predecessor)
  • or-statewide-format — caption / format
  • or-hearings — the hearing itself
  • or-deadlines — calendaring post-hearing deadlines
  • or-law-references/references/civil-rules.md — UTCR 5.100 text

Washington County Circuit Court (Oregon)

Use this skill in addition to or-statewide-format when the case is in the Washington County Circuit Court (Oregon). This is Oregon's second-busiest circuit court (Multnomah is first; Clackamas and Lane are usually close behind).

NOT LEGAL ADVICE. These notes describe the venue's procedural mechanics as a drafting aid, not legal advice. Local rules and judge-specific practices change; verify with the clerk and the current SLR before relying on anything here.

⚠ Naming caution: "Washington County" in Oregon is the suburban Portland county whose seat is Hillsboro. It is distinct from the state of Washington. For courts in the state of Washington (King County, Pierce County, etc.), use the wa-court-docs plugin.

Court location

Washington County Circuit Court sits at the Washington County Public Services Building / Courthouse complex in Hillsboro:

Civil and family-law courtrooms are in the main courthouse building. Juvenile is in the Juvenile Services Center, 222 SW 1st Avenue. Probate and small claims are in the Civil Department within the main courthouse.

Caption — Washington County variant

            IN THE CIRCUIT COURT OF THE STATE OF OREGON
                  FOR THE COUNTY OF WASHINGTON

Case numbers follow YYCVNNNNN for civil cases (e.g., 25CV12345). Same statewide format as Multnomah; the venue is identified by the "FOR THE COUNTY OF WASHINGTON" header line and the assigned department.

Civil motion scheduling — Civil Division contact

Unlike Multnomah's individual-calendar model, Washington County uses a lightly centralized scheduling approach: motions are heard on the assigned judge's calendar, but date reservations flow through the Civil Division at the courthouse rather than individual JAs. This is faster for routine motions but means less individual-judge customization.

Step 1 — Identify the assigned judge

The assigned judge appears on the OJD Case Information page and in File and Serve. New civil cases are assigned at filing.

Step 2 — Contact the Civil Division to request a date

Email or call the Civil Division to request a date on the assigned judge's calendar:

Specify:

  • Case caption and number
  • Assigned judge
  • Motion type and estimated argument time
  • Two or three proposed dates

Step 3 — Civil Division confirms

The Civil Division replies with the confirmed date, courtroom, and mode. For some judges, the JA confirms separately; for others, the Civil Division clerk has full authority.

Step 4 — File the Notice of Hearing

File the Notice of Hearing on File and Serve. Washington County SLR 5.045 requires the Notice to be filed simultaneously with the motion for non-arbitration cases (this is stricter than Multnomah's 3-day window).

Step 5 — Working copies

Washington County SLR 5.100 requires working copies for motions over 15 pages total. Deliver to the Civil Department clerk's counter or to chambers (the Civil Division will route).

Authoritative source — pull current judge roster

The Washington County Circuit Court website is the canonical source for judges, courtrooms, and standing orders:

https://www.courts.oregon.gov/courts/washington/Pages/default.aspx

Judges rotate dockets every two years (January 1 cycle, typical). Pull the current roster each session.

Washington County SLR — Supplemental Local Rules

Key civil sections:

SLRSubject
1.001Effective date and scope
5.025Setting motions through the Civil Division
5.045Notice of Hearing filed with motion
5.046Meet-and-confer certification for discovery motions
5.100Working copies (over 15 pages)
5.101Submission of orders
7.010Telephonic / WebEx hearings
8.010Mandatory arbitration (ORS 36.400)
12.010Pretrial conference

Pull the current SLR PDF from https://www.courts.oregon.gov/courts/washington/rules.

Mandatory arbitration

Washington County implements ORS 36.400 mandatory arbitration identically to Multnomah: cases between $10,000 and $50,000 go to arbitration. The Arbitration Commissioner's office at the courthouse handles assignments to the OJD arbitrator panel.

If your case is in arbitration:

  • File motions in the arbitration proceeding, not before the circuit judge
  • Title: "(IN ARBITRATION PROCEEDING UNDER ORS 36.400)"
  • The arbitrator's decisions are appealable to the circuit judge via trial de novo under ORS 36.425

eFiling and service

Washington County uses File and Serve like all OJD circuits. Document codes and service mechanics are identical to Multnomah (UTCR 21.100).

Self-represented parties not registered for eService must be served by mail or hand delivery under ORCP 9 D — see or-pro-se.

Filing fees

Same statewide schedule under ORS 21.135-21.170. Verify at https://www.courts.oregon.gov/services/fees/Pages/default.aspx.

Document set for a motion in Washington County

  1. Motion
  2. Memorandum in Support
  3. Supporting Declaration(s) with exhibits
  4. Proposed Order ("[PROPOSED]" in title)
  5. Notice of Hearing — filed simultaneously with the motion under WCCC SLR 5.045
  6. Certificate of Service
  7. Working copies if total packet exceeds 15 pages

Scheduling email — recommended template

To:      WCCCCivilCT@ojd.state.or.us
Subject: Hearing Date Request — [Case Short Title],
         Case No. [Cause Number]

Civil Division:

I am [Counsel of record / Defendant, pro se] in [case short
title], Case No. [cause number], assigned to the Hon. [Judge
Name].

I am requesting a hearing date for [Motion Title], to be filed
[date]. Estimated argument time: [X minutes].

Proposed dates:
   [Date 1]
   [Date 2]
   [Date 3]

I have / have not conferred with opposing counsel on these
dates.

If the Court prefers WebEx, please advise so I can include the
connection details on the Notice of Hearing.

Thank you,
[Name][, pro se / OSB #]
[Contact info]

Comparison to Multnomah

AspectMultnomahWashington Co
SchedulingThrough assigned judge's JAThrough Civil Division
Working-copy threshold25 pages15 pages
Notice of Hearing timingWithin 3 business days of JA confirmFiled simultaneously with motion
Meet-and-confer requirementSLR 5.045SLR 5.046
Default hearing modeWebEx for routine motionsMix — judge-dependent
Ex parte hoursM–F 8:30–12:00 in dedicated deptCivil Division counter, mornings

References

  • references/hillsboro-courthouse.md — venue info, courtrooms, judges, working-copy delivery
  • references/civil-motion-practice.md — full motion practice walkthrough
  • references/washington-county-slr.md — local rules summary

Sponsors

Details

Marketplace
codearranger/claude-legal
Source
plugins/or-court-docs
Category
Legal
Keywords
oregon, legal, pleadings, pro-se, utcr, orcp, oec, multnomah-county, washington-county-oregon, circuit-court, county-courts, civil-rules, evidence-rules, discovery, hearings, post-judgment, fact-check, fdcpa, reg-f, utpa, consumer-protection, debt-collection, ojd-ecourt, ors-697

More from codearranger/claude-legal

All 15