Translating legal language to plain Nepali for clients

Pure translation is not enough

A literal Nepali rendering of a complex contractual clause, or a translated extract from the Muluki Civil Code, or a translated paragraph from a Supreme Court decision, is rarely useful to a client on its own. The client reads it and arrives at the question every monolingual reader of dense legal prose arrives at, in any language: and? What does this mean I have to do, or stop doing, or sign, or refuse to sign, today? Pure translation does not answer that question. It only moves the same dense paragraph from one language into another.

The pattern that works is translation paired with a one-sentence consequence. Whenever you ask the model to translate a clause, a section, or an authority for a client, you ask it for two things in the same response: a clean Nepali version, and a single sentence — in plainer Nepali still — restating what this means for the client to do, decide, or watch out for. The first satisfies your professional duty to give the client the actual text. The second is what the client will actually read and act on.

The prompt pattern

A working prompt for client-facing translation looks like this. The example uses a force-majeure clause from an English-language construction contract, but the shape adapts to any clause, statute, or judgment passage:

Below is one clause from an English-language construction contract. Do two things, in this order.

First, translate the clause into clear, formal Nepali suitable for a written advisory note. Preserve the legal meaning. Where a term has a specific Nepali legal equivalent (for example contract-related terms in the Muluki Civil Code), use it.

Second, on a new line beginning “ग्राहकका लागि अर्थ —”, write one sentence in plainer Nepali stating what this clause means the client must do, decide, or watch out for. Use the second person. Do not add new legal claims beyond what the clause itself says.

Clause: [paste the clause]

You read the output. You confirm that the Nepali translation matches the English original. You confirm that the consequence sentence does not over-promise or invent a duty the clause does not impose. You hand the result to the client. The client reads two short paragraphs in Nepali — a faithful version of the clause, and one sentence telling them what to do — and the conversation that follows is about a decision, not a translation.

Vocabulary discipline and the personal glossary

A second mistake, easy to miss, is letting the model translate the same English term three different ways across three different documents for the same client. “Indemnity” becomes क्षतिपूर्ति in one note and हानि-नोक्सानीको क्षतिपूर्ति in the next and क्षति बेहोर्ने प्रतिज्ञा in the third. The client, who is not a lawyer, now thinks there are three different obligations. There is one.

The fix is a personal glossary you build over the first few months and feed into every translation prompt. For each English term of art you regularly encounter, fix one Nepali rendering and stick to it. Paste the glossary at the top of the prompt — “Use these renderings consistently: indemnity = क्षतिपूर्ति; warranty = प्रत्याभूति; arbitration = मध्यस्थता; force majeure = दैवी प्रकोप / अप्रत्याशित परिस्थिति; jurisdiction = क्षेत्राधिकार” — and the model will hold the line. After a year the glossary is short, opinionated, yours, and the client sees a single consistent term wherever the same concept appears.

Where the model quietly mistranslates

The model is most likely to mistranslate exactly the terms that matter most in Nepali legal practice — the terms of art that have specific meaning under domestic statute or long-standing usage. कब्जा is not just “possession” in the casual English sense; it has a specific evidentiary and procedural weight in property litigation. हकभोग is not interchangeable with “ownership.” जग्गा-धनी-प्रमाण-पूर्जा is not a synonym for “land title certificate” in general — it is a specific document with a specific issuing authority. मुद्दा-दर्ता is not the same as “filing a case” in the loose sense; it refers to a registration step with consequences for limitation and fee. A model trained mostly on English text, with a thin understanding of Nepali legal usage, will smooth all of these into approximate English translations and then back-translate into Nepali that sounds plausible but loses the legal precision.

The verification discipline is the same one the previous chapter applied to citations. Where the model translates a term of art that carries domestic legal weight, you check the rendering against an authoritative source — the relevant statute in the gazette version, the standard usage in NKP, a recognised Nepali legal glossary, the textbook your faculty members rely on. You do not advise the client on the model’s rendering of a term-of-art until you have confirmed it. For most ordinary contract language the model is fine. For the dozen or so terms in every matter that actually carry the legal weight, you check.

The four real failures, and how to catch them

In ordinary Nepali practice, four failure modes account for almost every translation problem worth catching.

One: the over-confident term of art. The model produces Nepali that reads correctly and is wrong on a specific legal phrase. The catch: keep the English original next to the Nepali draft and check each term of art line by line.

Two: the dropped condition. A clause says “the Contractor shall, within fourteen days of becoming aware, notify the Engineer in writing, failing which the claim shall be deemed waived.” A careless translation preserves the notify-in-writing part and loses the failing-which clause. The deadline survives but the consequence does not, and the client thinks the consequence is softer than it is. The catch: every conditional clause in the English original must have a conditional clause in the Nepali version.

Three: the wrong register. A demand-letter translation that should sound firm comes out apologetic, because the model’s default Nepali for client-facing text is soft. Or a translation for an elderly trustee comes out in legalistic Nepali that no human speaks. The catch: specify the register in the prompt — “formal but accessible, for a sixty-five-year-old trustee who is not a lawyer” or “firm and unambiguous, this is a demand letter to opposing counsel”.

Four: the cultural mis-calibration. Nepali clients, particularly older clients and clients from family businesses, sometimes prefer bad news to be delivered indirectly — with framing, with a softening, with an acknowledgement of the relationship before the warning. The model’s default Nepali, especially when asked to be “clear” or “direct”, lands flatter and bluntar than would feel right in the room. The catch: when you know a particular client will receive direct framing badly, add one line to the prompt — “frame the consequence respectfully, with an acknowledgement of the relationship before the warning, this is a long-standing family client” — and the output adjusts immediately.

What the client actually sees

When you have done this well, the client opens an envelope or a WhatsApp message and sees three short Nepali paragraphs. The first is a faithful translation of the clause or section. The second begins with “ग्राहकका लागि अर्थ —” and tells them in one sentence what they must do. The third, optional, lists by what date and to whom. They do not see the English original. They do not see the model. They do not see your glossary. They see a Nepali document they can act on, and they act on it.

That is what translation in a Nepali practice is for. Not to produce a parallel Nepali text. To produce a Nepali document the client uses to decide.

Check your understanding

Quick check

—

An advocate is preparing a Nepali version of a force-majeure clause for a monolingual SME contractor in Birgunj. Which approach is most likely to actually help the client?

1. AAsk the model for a clean Nepali translation of the clause and send only that to the client, since the clause itself is what governs.
2. BAsk the model for a Nepali translation paired with one sentence in plainer Nepali — beginning “ग्राहकका लागि अर्थ —” — restating what the clause means the client must do, decide, or watch out for.
3. CAsk the model to rewrite the clause into something simpler in English first, then send only the English to the client.
4. DAsk the model to summarise the entire contract in three lines and send that, skipping the clause itself.

Check answer→

What comes next

The same fact-first, register-aware discipline that powers good intake memos and good client-facing translation also powers the largest volume of work a small Nepali practice produces — the steady stream of letters. The next section is about using AI for demand letters, notices, and correspondence, and the single highest-leverage instruction you can give the model when drafting any client letter.