Tarikh and Peshi: how OrdoMetric models court dates

Terminology on this page is tagged [verify with a Nepali practitioner] until the pilot firm reviews it. Corrections are data changes in the label pack, not code.

Two kinds of court date

A Tarikh [verify] is the date on which a party or counsel must appear to receive the next date or a procedural order. A Peshi [verify] is a hearing on the cause list where the bench takes the matter up. Both are calendar dates in the court's timezone, not clock times; the order of the day is the cause-list serial number.

OrdoMetric therefore stores a hearing as:

Field	Meaning
kind	tarikh, peshi or other
hearing_date	a calendar date (AD is canonical, BS is stored as typed)
cause_list_serial	the serial on that day's list, when known
bench	single, division, full or constitutional bench [verify], judges nullable
outcome	from the firm's outcome list, recorded from midnight on the day
next date	creates the next hearing record when recorded

Why no clock time by default

District-court practice does not promise a time; the serial number is what the clerk watches. Forcing a time into the record would make the diary look more precise than the court is. An optional time field exists for the courts and tribunals that do fix one.

BS and AD

Bikram Sambat is the calendar people speak in; Gregorian is what every integration expects. OrdoMetric shows both (2083-05-24 BS · 9 Sep 2026), lets you type in either, and converts with a table-driven routine validated for 2000–2100 BS. Dates outside the table are flagged approximate [verify table coverage].

What the firm sees

On the home page, today's hearings appear by court, each with its kind chip (Peshi or Tarikh), the case, the bench, the purpose and a Record outcome button. Recording an outcome with a next date creates the next record and posts to the case's message board; the client update, if the firm sends one, carries only the stage and the next date.