The two ways a freelance gig in Nepal goes wrong are almost always the same: the scope that quietly grew, and the payment that landed only at the very end, if it landed at all. A short, honest agreement prevents both. This guide is the terms that matter and the one-page structure that keeps the gig clean.
This is practical guidance, not legal advice; for a large or unusual deal, get a lawyer's eyes on it.
The five terms that matter
| Term | What to write | The failure it prevents |
|---|---|---|
| Scope | What is in, and a named list of what is not | The quiet scope growth |
| Price | The number, and what moves it | The "this is more than I thought" |
| Schedule | Portions tied to deliverables, not to the end | The one-shot payment at the end |
| Acceptance | What "done" looks like, in one line | The "it is not done yet" loop |
| Ownership | Yours until the final payment, then handed over | The free trial that never clears |
That table is the whole contract, and it fits on one page, which is why a client is more willing to sign it than a ten-page document.
The payment split that protects you
The structure is: something to start, a portion on a named deliverable, and the rest on acceptance. The reason for the split is not trust; it is that the risk is concentrated at the end, and the split moves it out. If the client wants it all at the end, that is a signal, and the honest response is to either price the risk into the number or to not take the shape, not to hope the end payment arrives.
The ownership line, and why it is non-negotiable
The work is yours until the final payment clears, and you hand it over on acceptance. That one clause is what stops a project from becoming a free trial the client keeps refining without paying. It is also the clause that keeps the code, the files and the account credentials in your control until the money has moved, which is exactly the leverage a freelancer should have.
The two habits around it
Keep a one-page record per job: the scope, the price, the schedule and the acceptance line, signed or emailed-back. And keep the getting-paid side clean, because a contract you cannot collect on is just paper; the move is covered in how freelancers in Nepal get paid. The pricing that goes in the number is the subject of how to price your freelance work in Nepal and abroad.
A sensible default
One page: scope with a named out-of-scope list, the price, a split schedule tied to deliverables, a one-line acceptance, and the ownership line. Get it signed or emailed-back before the work, and keep the record. Do that and the two classic failures, the grown scope and the unpaid end, are the ones you did not have.
Bottom line: a Nepali freelancer's protection is a one-page agreement with the scope, a split schedule, an acceptance line and the ownership clause, plus a clean way to collect it. Write the five terms, get it before the work, and the gig stays a transaction instead of a slow argument.
FAQ
Do I need a written contract for a small job?
The bigger the job, the more you do, but even a small one needs a one-page agreement that says what is in scope, the price, and the payment schedule. The cost of the one-pager is an hour; the cost of not having it is the argument.
How should I structure the payments?
Split it: a portion to start, tied to a deliverable, and the rest on acceptance. Never put the whole project on one payment at the very end, because that is the entire risk in one moment, and it is the single biggest reason freelancers get stiffed.
Who owns the work when it is done?
You should own it until the final payment clears, and hand it over on acceptance. That one clause, the work is yours until paid, is the difference between a relationship and a free trial.
Sources and how to verify
Platform policies, payout routes and NRB rules for moving money home change; confirm the current receiving method and fee with the platform and your bank. General guidance, not financial advice.