This editorial policy explains how Film Permits Nepal researches, writes, reviews, and maintains the information published across this website. We are an independent private production-support service based in Kathmandu. We are not a government office, we do not issue permits, and we are not the authority that approves filming in Nepal. Because the words on this site influence how foreign productions plan their budgets, schedules, and paperwork, we hold our content to a documentary standard: clear, conservative, and honest about what is settled fact and what depends on your specific circumstances.
The guiding principle is simple. We would rather tell you that a fee or timeline must be confirmed against a current official source than print a confident number that turns out to be wrong. Regulatory details in Nepal can change, vary by location and activity, and depend on decisions made by authorities we do not control. So our pages are written to help you prepare well and ask the right questions, not to pose as a final legal ruling on your production.
This policy sets out who writes and reviews our material, how we treat sources, when and how we use software assistance in drafting, how we handle conflicts of interest, and the claims we will never make. It also describes how we correct mistakes and how you can flag one. We publish these standards openly so that producers, line producers, fixers, and legal teams can judge the reliability of what they read here and hold us to it. If anything on this site ever reads as a guarantee of approval, timing, access, or clearance, treat that as an error and tell us, because it would contradict the standards described below.
Purpose and scope of this policy
This policy applies to every page on this website: service descriptions, planning guides, production-type pages, location pages, frequently asked questions, and trust pages like this one. It governs the standards behind the text you read, the way we handle facts, and the accountability we accept for errors. It does not govern the private advisory work we do inside a paid engagement, which is documented separately in our engagement terms, although the same commitment to accuracy and honesty carries through both.
Our audience is international. Most readers are producers, line producers, production managers, fixers, journalists, and the legal or insurance teams who support them. Many are planning a first project in Nepal and are trying to understand what preparation looks like before they commit a budget. Some are experienced in the region and are checking a specific detail. We write for both, which means we explain context without assuming prior knowledge, and we avoid jargon where plain language will do.
The scope has clear edges. We describe what our service does, how foreign productions typically prepare, what categories of documents are usually involved, and how planning and review work in practice. We do not describe ourselves as the issuing authority, and we do not present our summaries as the current legal position of any government body. Where a fact is regulatory in nature, such as a fee, a processing time, or which office applies to a given activity, we frame it conditionally and point you toward confirmation against current official sources during your review.
This policy is a living document. We revisit it when our practices change, when we adopt new tools, or when a reader raises a fair concern about how we handle information. The version you are reading reflects our current standards. If you are relying on this page for a formal assessment of our editorial conduct, contact us and we will confirm the version that was in effect on the date that matters to you.
People-first content
We write for the person planning a production, not for a search engine and not to fill space. Every page should answer a real question that a producer or coordinator actually asks, and it should answer the most important part first. If you land on a page about documents, the opening lines should tell you what documents typically matter and why, before any longer explanation. We treat the reader's time as the scarcest resource in the exchange.
People-first means we prioritise usefulness over completeness for its own sake. A page does not need to list every conceivable edge case to be valuable; it needs to give an honest, well-organised picture of the common path and flag where individual circumstances change things. We would rather write four hundred clear words that help you prepare than a thousand words that hedge every sentence into uselessness. Clarity is a form of respect.
We also write for people who are under pressure. Productions run on tight schedules, and readers often arrive stressed, mid-planning, or troubleshooting a problem that has already appeared. So we lead with direct answers, use short paragraphs, and structure pages so a skim reader and a close reader both come away informed. We avoid manipulative urgency, fake scarcity, and pressure tactics. If something genuinely depends on timing, we say so plainly and explain the dependency rather than dramatising it.
This principle has a hard limit that protects you: usefulness never justifies inventing certainty. It would be easy to make a page feel more helpful by stating a precise fee or a guaranteed turnaround, and it would be dishonest. When the most useful truthful answer is that a detail must be confirmed for your specific case, that is what we write. A page that sends you into a planning meeting with accurate expectations has done its job better than one that sounds authoritative and misleads you. People-first content, for us, is content that leaves the reader better prepared and never falsely reassured.
First-hand experience
Our content is grounded in the practical experience of coordinating production-support work in Nepal: assembling document sets for foreign productions, reviewing paperwork against what applications typically require, liaising with local contacts, and helping crews plan realistic schedules around preparation and clarification cycles. When we describe a workflow, we are describing work we do, not a process copied from elsewhere. That lived familiarity is what lets us tell you which mistakes recur, which documents are commonly missed, and where productions tend to underestimate the time preparation takes.
Experience shows up in the texture of the writing. When we say that a scope change midway through a project can ripple into new permissions and new preparation, that comes from watching it happen. When we explain why a clear equipment list saves trouble later, or why translations and signatures deserve attention early, we are passing on patterns we have seen repeatedly. This is the part of our knowledge that no public document can fully capture, and it is where we add the most value to a planning reader.
We are equally disciplined about the limits of experience. Having coordinated many productions does not make us the authority that approves them, and it does not freeze the rules in place. What we observed on past projects informs how we help you prepare, but it never becomes a promise about how your project will be treated. Precedent is a planning aid, not a guarantee, and we present it that way.
Where we use scenarios or examples to illustrate a point, they are framed as illustrations drawn from the kinds of situations productions encounter, not as named case studies with real client identities. We do not attach real production names, real budgets, or real approval outcomes to these examples, both to protect client confidentiality and to avoid implying that one project's path predicts another's. The value of an illustration is that it makes a general pattern concrete, and we keep it honestly general.
How we research a topic
Research for a page starts by defining the reader's actual question and the decision behind it. A producer reading about equipment records is usually trying to decide what to prepare and when, so the research targets that decision rather than an abstract survey of the subject. We map the question into the parts a reader must understand, then work out which parts are stable general knowledge, which are procedural, and which are regulatory details that depend on current official sources or on the specifics of a project.
We separate three kinds of statements as we research. The first is durable practice: how foreign productions typically prepare, what document categories usually appear, and how review and planning generally work. These we can write with confidence because they change slowly and reflect our own work. The second is conditional and situational: which office applies, what a particular location requires, or how an activity like drone work or protected-area access is treated. These we write with explicit conditionality. The third is hard regulatory specifics such as exact fees, precise processing times, and named current issuing authorities. These we do not assert as verified fact unless they are confirmed against a current official source at the time of your review.
When research reaches a regulatory specific we cannot responsibly state, we do not guess and we do not paper over the gap with vague authority. We write the honest version: that the exact figure or the applicable office depends on current official sources and on your locations and activities, and that it is confirmed during your review. This is a deliberate editorial choice. A confident wrong number is more harmful to a budget than a clearly flagged unknown, because the reader plans around it.
Research also considers what a reader might do next. If understanding a topic properly requires knowing that a related permission could be triggered, we surface that link rather than leaving the reader to discover it late. Good research anticipates the follow-on question and answers it, or at least names it clearly so nothing important stays hidden until it becomes a scheduling problem.
Source use and citation
For anything regulatory, official primary sources take priority over secondary commentary, and current sources take priority over older ones. Rules, fees, and the allocation of responsibilities among offices can change, and a detail that was correct a year ago may not be correct today. We treat undated third-party summaries with caution and we do not elevate them above the official position simply because they are convenient to quote.
We deliberately avoid printing specific regulatory figures and named current issuing authorities as settled fact on general pages. This is not evasiveness; it is accuracy discipline. Because these specifics vary by activity and location and can change, stating them as fixed facts risks misleading a reader who plans around them. Instead we describe the shape of what to expect and commit to confirming the specifics against current official sources during your review, when we can tie the answer to your actual project.
We do not reproduce large portions of copyrighted material, and we do not present another organisation's text as our own. When a point genuinely rests on an external source, we characterise it in our own words and can point you to the underlying source on request. If you are relying on a particular claim for a formal decision, ask us and we will tell you what the claim is based on and how current that basis is. We would rather be asked than assumed.
Citation for us is also about traceability. Every substantive regulatory statement on the site should be answerable to a question of the form: what is this based on, and as of when. If we cannot give a good answer to that question, the statement should be softened, dated, or removed. This standard is what keeps the site from drifting into confident folklore, which is a real hazard in a field where rumours and outdated advice circulate freely among crews.
Conditional wording for regulatory topics
Regulatory topics on this site are written conditionally on purpose, and it helps to understand the wording so you can read it accurately. When we write that something depends on your locations and activities, or that a fee is confirmed against current official sources during your review, or that which office applies depends on the specifics of your project, these are not throat-clearing phrases. They are precise signals that the detail is genuinely variable and that a responsible answer requires your particulars or a fresh check.
There is a meaningful difference between our confident statements and our conditional ones. When we describe how a foreign production typically prepares a document set, we are stating durable practice and you can rely on the general shape. When we describe a fee, a timeline, or a named current authority, we use conditional language because those specifics are exactly the things that change and that we will not assert as verified fact. Reading the difference lets you sort what you can plan around now from what needs confirmation.
Conditional wording protects you as much as it protects us. If we wrote a single flat number for a cost or a fixed number of days for a process, a reader might build a budget or a shoot schedule around it and then be caught out when reality differed by location, activity, or timing. By flagging the variable clearly, we prompt the right question at the right moment, which is more useful than false precision. The goal is a reader who walks into a planning meeting knowing what is settled and what must still be checked.
We try never to let conditionality collapse into vagueness that helps no one. A well-written conditional statement still tells you what the variable is, why it varies, and how it gets resolved. So rather than a bare it depends, we aim for it depends on these specific factors, and here is how it is confirmed for your project. That is the standard we hold our regulatory writing to.
Authorship and review
Content on this site is produced by our editorial and coordination staff and reviewed before publication. Writing and review are treated as separate responsibilities: the person shaping a page is not the sole judge of whether it meets our standards. A reviewer checks that claims are appropriately sourced or appropriately conditioned, that nothing reads as a guarantee, that no prohibited claim has slipped in, and that the page actually answers the reader's question at the altitude a planning reader needs.
Review pays special attention to regulatory sensitivity. Pages that touch fees, timelines, drone operations, protected or heritage areas, restricted areas, and customs get closer scrutiny, because these are the topics where an overconfident sentence does the most damage and where the underlying details are most likely to shift. On these pages the reviewer specifically looks for any figure or authority named as settled fact and questions whether it should instead be framed as confirmed during review.
We maintain accountability for what we publish as an organisation. A page carries our editorial standards whether or not an individual byline is attached, and the same review discipline applies across the site. If you need to understand who was responsible for a particular page or when it was last reviewed, you can ask us and we will tell you what we can, consistent with our team's privacy.
Review does not end at publication. Because the subject matter changes, pages are revisited on an ongoing basis, and higher-risk topics are revisited more often. When a review finds that something has changed or that a statement was too confident, we update the page and, where the change is material, note that it was updated. The point of ongoing review is to keep the site honest over time, not only at the moment a page first goes live.
AI-assisted drafting policy
We use software tools, including AI writing assistants, to help with parts of the content process such as drafting, restructuring, tightening language, and checking consistency. We are open about this because readers deserve to know how content is made. What matters is not whether a tool touched a draft but whether the published result meets our standards for accuracy, honesty, and usefulness. Those standards are set and enforced by people.
AI assistance never sets the facts. We do not let a tool invent fees, timelines, statistics, legal provisions, authority names, awards, client names, or testimonials, and we treat any such specifics that surface in a draft as unverified until a person checks them against our sourcing rules. Because general-purpose models can produce fluent, confident text that is wrong, our review process is specifically alert to plausible-sounding regulatory specifics that have no verified basis. Anything of that kind is removed or reframed conditionally before publication.
Every page that involves AI assistance passes through human editorial judgement before it is published. A person is responsible for the final text, for its adherence to this policy, and for the commitments it makes to readers. The tool is an aid to expression and organisation, not a source of authority and not a substitute for the coordination experience that makes our content trustworthy. If a draft and our real-world understanding disagree, our understanding wins and the draft is corrected.
We also use human judgement to keep the writing genuinely useful rather than generically padded. AI tools can fill a page with confident-sounding filler, and part of the editor's job is to cut anything that does not help a planning reader. The result we aim for reads as though a knowledgeable colleague wrote it: direct, specific where it can be, honest where it cannot, and free of the hollow certainty that unedited machine text tends to produce.
Accuracy, verification, and the no-fabrication rule
The single most important rule on this site is that we do not fabricate. We do not invent specific government fees or amounts, we do not invent processing times or exact timelines, we do not name a specific authority as the current issuer when that is not something we can verify, and we do not invent legal provisions, statistics, awards, client names, or testimonials. If a specific regulatory fact is not something we can stand behind, we defer to confirmation against current official sources rather than filling the gap with a plausible guess.
This rule shapes how we write about the very things readers most want pinned down. On cost, we describe the kinds of factors that drive a production's spending and how those are assessed for a real project, without printing invented figures. On timing, we describe the stages of preparation and the dependencies that lengthen or shorten them, without promising a number of days. On authority, we explain that which office applies depends on your locations and activities, rather than asserting a single named issuer as verified fact. Each of these is a deliberate substitution of an honest structure for a dishonest specific.
Verification is the companion to the no-fabrication rule. Where we do state something, it should be answerable to a source or to our own direct practice. Durable practice about how productions prepare is verified by experience. Regulatory specifics are only stated when confirmed against a current official source, and on general pages we usually decline to state them at all, preferring to confirm them inside a real review tied to your project. This keeps the confident parts of the site genuinely reliable.
We also never dress up a guess as certainty through tone. Confident phrasing is not evidence, and we are careful that the way a sentence sounds matches how solid the underlying fact is. If our confidence in a detail is low, the wording reflects that. Readers should be able to trust that a firmly stated sentence on this site is firmly grounded, and that anything genuinely uncertain is flagged rather than smoothed over.
Conflicts of interest
We are a private, independent service, and we are transparent about the obvious commercial fact: we hope readers who need support will engage us. That commercial interest never entitles us to distort information to make our service look more necessary than it is. We do not exaggerate difficulty, invent obstacles, or imply that a production cannot proceed without us in order to drive engagements. Where a task is genuinely straightforward, we say so, even if that means a reader decides they do not need help with it.
We keep a clear line between editorial content and commercial promotion. Our planning guides are written to inform, and they are held to the accuracy standards in this policy regardless of whether the reader ever becomes a client. When a page does describe our services, it should be recognisable as a description of what we offer, not disguised as neutral guidance. Readers should always be able to tell when they are reading information and when they are reading an offer.
We are equally careful about our independence from the bodies that actually regulate and approve filming. We are not affiliated with, endorsed by, or acting on behalf of any government office, and we do not present ourselves as speaking for one. Our commercial relationship is with the productions we help, and our content does not carry undisclosed promotion of third parties dressed up as advice. If we ever reference an external provider, it is on the merits and disclosed as such.
Where a genuine conflict could affect how a reader weighs our words, the remedy is disclosure and restraint. We would rather lose a possible engagement by telling you honestly that something is simple than win one by making it sound harder than it is. Our long-term credibility with producers depends on being the source that does not cry wolf, and we manage conflicts with that priority in mind.
Corrections and updates
We treat corrections as a normal and necessary part of publishing about a changing subject, not as an embarrassment to be hidden. If we get something wrong, or if a detail that was once accurate stops being accurate, we want to fix it quickly and cleanly. Readers and clients are actively invited to flag anything that looks incorrect, out of date, or misleading, and we take those reports seriously regardless of who sends them.
When a possible error is raised, we review it against our sourcing and practice standards rather than defaulting to defend the existing text. If the report is right, we correct the page. For material changes, especially those affecting regulatory topics like fees, timelines, drone rules, or protected-area handling, we update the content and note that it has been updated so the change is visible rather than silent. Minor wording fixes may be made without a note, but substantive corrections are acknowledged.
Speed is prioritised by risk. A statement that could cause a production to make a costly planning decision on wrong information is corrected with more urgency than a small stylistic slip. If an error is serious enough that people may already have acted on it, we address it promptly and, where appropriate, make the correction prominent rather than burying it. The aim is to limit harm, not just to tidy the record.
Because the underlying rules and details shift over time, updating is continuous rather than occasional. Higher-risk pages are revisited more frequently, and any page can be revised when we learn something has changed. A correction is not an admission that the site is unreliable; it is evidence that the site is maintained. We would rather run a visible, well-managed corrections practice than pretend our content is permanently perfect.
Prohibited claims
Certain claims are simply never permitted on this site, and this list is a commitment to readers. We never claim to be an official or government service, and we never imply that engaging us is the same as obtaining an approval. We never guarantee that a permit or any permission will be granted, because that decision does not belong to us. We never promise a specific approval timeline, a guaranteed drone permission, guaranteed location access, or guaranteed customs clearance. Any sentence that reads as such a guarantee is an error under this policy and should be reported.
We also never fabricate the specifics that give false confidence. That means no invented government fees or amounts, no invented processing times, no naming of a specific current issuing authority as verified fact when it is not, and no invented legal provisions. It also means no invented statistics, awards, client names, or testimonials. If any of these appears on the site, it has escaped our controls and we want to know so we can remove it.
The reason these prohibitions exist is that each corresponds to a way productions get hurt. A guaranteed timeline invites an unbuildable schedule. A promised approval invites a commitment that may not hold. An invented fee invites a wrong budget. A false claim of official status invites misplaced legal reliance. By refusing all of them, we keep the site on the right side of the line between helping you prepare and misrepresenting what we or anyone can promise.
Within these limits there is still a great deal we will say confidently and at length, because honest usefulness does not require overreach. We will describe in detail what our service does, how preparation works, what documents typically matter, how planning and review proceed, what commonly goes wrong, and what to consider by production type and location. The prohibited-claims list narrows only the dishonest options; it leaves the genuinely helpful ones wide open, which is exactly where we want our content to live.
Confidentiality in what we publish
Our editorial standards intersect with our duty of confidentiality to the productions we support. Client projects are often sensitive: a concept, a location plan, a shoot date, or the mere fact that a particular production is coming to Nepal can be commercially or editorially confidential. So our public content never reveals identifiable details of the productions we work with, and our illustrative examples are kept general rather than tied to real clients.
When we describe scenarios to make a point concrete, we construct them as representative illustrations of the kinds of situations productions face. We do not attach real names, real budgets, real dates, or real approval outcomes. This protects clients and also keeps us honest, because a disguised real case could imply that one production's experience predicts another's, which it does not. A general illustration teaches the pattern without pretending to be a case study with a guaranteed moral.
This restraint is a deliberate trade-off against a certain kind of marketing polish. Named case studies and glowing testimonials can make a service look impressive, but presenting invented or embellished versions of them would violate both our confidentiality duty and our no-fabrication rule. We would rather publish an honest general example than an invented specific one, even though the specific one might read as more persuasive.
The handling of the actual documents and data clients share with us is governed in detail by our separate confidentiality and document-security materials. This editorial policy covers the narrower point: what we will and will not say publicly. The short version is that nothing a client entrusts to us becomes public content, and nothing on our public pages should ever expose a real production's plans. If you spot anything that appears to do so, treat it as a serious error and tell us immediately.
How to read and rely on this site
Read this site as well-informed preparation material, not as a substitute for confirmation against current official sources or for professional advice tied to your specific project. The pages are built to get you ready: to help you understand the shape of the process, assemble the right kinds of documents, plan a realistic schedule, and ask the right questions. They are not built to serve as the final legal word on your production, because that word depends on authorities and specifics beyond our content.
A practical way to use the site is to sort what you read into two buckets. The first bucket is durable guidance you can act on now: how foreign productions typically prepare, what document categories usually matter, what commonly goes wrong, and how review and planning work. The second bucket is anything specific and regulatory, such as a fee, a timeline, or which office applies, which you should treat as something to confirm for your actual project rather than a fixed value to plan around. Our conditional wording is there to help you sort correctly.
When a decision carries real cost or risk, confirm the specifics before you commit. If a budget line, a shoot date, or a location choice hinges on a regulatory detail, that is precisely the moment to have the detail confirmed against current sources and against your particulars, rather than relying on a general page. We would always rather you check twice on something that matters than proceed on an assumption drawn from general reading.
If anything on the site is unclear, appears inconsistent, or seems to promise more than we say we can promise, contact us. We would rather answer a question directly, tied to your project, than have you rely on a general page for a decision it was never meant to carry. The site is a strong starting point and a poor substitute for a real review, and using it as the former is how you get the most value from it while staying protected.
| Claim type | How we treat it | Why | What you should do |
|---|---|---|---|
| Durable practice (how productions prepare) | Stated confidently in plain language | Reflects our direct coordination experience and changes slowly | Rely on the general shape while planning |
| Document categories a production typically prepares | Described in detail as usual patterns | Broadly stable across projects and well understood from practice | Use as a preparation checklist, adjusted to your project |
| Which authority or office applies | Framed conditionally on your locations and activities | Allocation of responsibility varies and can change | Have it confirmed for your specific project during review |
| Specific fees or amounts | Not asserted as fixed facts; drivers described instead | Figures vary by activity and location and can change | Confirm against current official sources before budgeting |
| Processing times or exact timelines | Described as stages and dependencies, not fixed durations | Timing depends on many factors outside our control | Plan buffers; confirm expectations for your case |
| Approval, drone permission, access, or clearance | Never guaranteed | These decisions belong to authorities, not to us | Prepare thoroughly; treat any guarantee as an error |
| Statistics, awards, client names, testimonials | Never fabricated; omitted if not genuinely verifiable | Invented proof misleads and breaches our standards | Ask us what any stated claim is based on |
| Illustrative scenarios | Presented as general, not real named cases | Protects client confidentiality and avoids implying precedent | Read as a pattern, not a promise about your outcome |
How to read our content by claim type: what we state confidently, what we condition, and what we never assert
What this includes
- Clear standards for how we research, write, and review every page
- A stated priority of official and current sources for regulatory topics
- Conditional wording that flags what depends on your project or current sources
- Separation of writing and review, with closer scrutiny of high-risk topics
- Open disclosure of AI-assisted drafting under human editorial control
- A strict no-fabrication rule covering fees, timelines, authorities, and proof
- A published list of claims we will never make
- An active, risk-prioritised corrections and update practice
- Confidentiality protection for client productions in all public content
- A route to ask what any specific claim is based on and how current it is
What this does not include
- Official status: we are not a government office and do not issue permits
- Guarantees of approval, timing, drone permission, access, or customs clearance
- Invented government fees, amounts, or exact processing times
- A named current issuing authority asserted as verified fact on general pages
- Fabricated statistics, awards, client names, or testimonials
- Named real case studies with identifiable production details
- Legal, tax, or immigration advice tailored to your specific circumstances
- A substitute for confirmation against current official sources
- Reproduction of copyrighted material beyond brief attributed quotation
- Any promise that engaging us is equivalent to obtaining an approval
Frequently asked questions
No. We are an independent private production-support service based in Kathmandu, and we are not a government office. We do not issue permits and we are not the authority that approves filming in Nepal. Our role is to help foreign productions prepare well: to understand the process, assemble the right kinds of documents, and plan realistic schedules. Any page that reads as though we grant approvals is an error under this policy, and we would want you to report it.
Because those specifics genuinely vary by activity and location and can change over time, and stating them as fixed facts would risk misleading you. A confident wrong number is more damaging to a budget or schedule than a clearly flagged unknown, since you plan around it. Instead of inventing figures, we describe the factors that drive cost and the stages and dependencies that affect timing. The specifics are then confirmed against current official sources and tied to your actual project during a review.
We do use software tools, including AI writing assistants, to help draft, restructure, and tighten text, and we disclose this openly. What matters is that the published result meets our standards, which are set and enforced by people. AI never establishes facts on this site: it does not invent fees, timelines, authorities, statistics, or testimonials, and any such specifics in a draft are treated as unverified until a person checks them. Every AI-assisted page passes through human editorial judgement, and a person is responsible for the final text.
We never claim to be an official or government service, and we never guarantee that a permit or permission will be granted. We never promise a specific approval timeline, guaranteed drone permission, guaranteed location access, or guaranteed customs clearance. We also never fabricate specifics such as government fees, processing times, a named current issuing authority asserted as fact, legal provisions, statistics, awards, client names, or testimonials. If any of these appears on the site, it has escaped our controls and we want to know so we can remove it.
For regulatory topics we prioritise official primary sources over secondary commentary, and current sources over older ones, because rules and responsibilities can change. We deliberately avoid printing specific figures and named current authorities as settled fact on general pages, preferring to confirm them against current official sources inside a real review. We do not reproduce copyrighted material or present another organisation's text as our own. If you are relying on a particular claim for a decision, ask us what it is based on and how current that basis is.
No. The site is well-informed preparation material, not legal, tax, or immigration advice tailored to your circumstances, and not a substitute for confirmation against current official sources. It helps you understand the shape of the process, prepare the right documents, and plan a realistic schedule. When a decision carries real cost or risk, confirm the specifics for your actual project before committing. If a budget line, shoot date, or location choice depends on a regulatory detail, that is exactly the moment to have it checked rather than relying on a general page.
Writing and review are separate responsibilities, so the person who drafts a page is not the sole judge of whether it meets our standards. A reviewer checks that claims are properly sourced or properly conditioned, that nothing reads as a guarantee, that no prohibited claim has slipped in, and that the page answers the reader's real question. Pages touching fees, timelines, drone operations, protected or heritage areas, restricted areas, and customs receive closer scrutiny. Review continues after publication, with higher-risk topics revisited more often.
Phrases like depends on your locations and activities, confirmed against current official sources during your review, or which office applies depends on the specifics of your project are precise signals, not filler. They tell you that a detail is genuinely variable and that a responsible answer needs your particulars or a fresh check. They distinguish our confident statements about durable practice from our conditional statements about specifics that change. Reading the difference lets you separate what you can plan around now from what still needs confirmation.
Our illustrative scenarios are constructed as general, representative examples of the kinds of situations productions face, not as named case studies with identifiable clients. We do not attach real names, budgets, dates, or approval outcomes to them. This protects client confidentiality and keeps us honest, because a disguised real case could wrongly imply that one production's experience predicts another's. We would rather publish an honest general illustration than an invented or embellished specific one, even if the specific one might read as more persuasive.
We are transparent that we are a private service and hope readers who need help will engage us, but that commercial interest never entitles us to distort information. We do not exaggerate difficulty or invent obstacles to make our service seem more necessary, and where a task is genuinely straightforward we say so. We keep a clear line between informational guidance and commercial promotion, and we are not affiliated with or speaking for any government body. Our long-term credibility depends on being the source that does not cry wolf.
You can contact us to flag anything that looks incorrect, out of date, or misleading, and we welcome these reports regardless of who sends them. We review the report against our sourcing and practice standards rather than defaulting to defend the existing text, and if it is right, we correct the page. Material corrections, especially on regulatory topics, are noted so the change is visible rather than silent, and serious errors are addressed with priority. A well-managed corrections practice is evidence that the site is maintained, not that it is unreliable.
Updating is continuous rather than occasional, because the underlying rules and details shift over time. Higher-risk pages, such as those touching fees, timelines, drone rules, and protected-area handling, are revisited more frequently, and any page can be revised when we learn something has changed. When a material change is made, we note that the page was updated. If you are relying on a page as of a particular date, contact us and we can tell you what we can about when it was last reviewed.
No. Our public content never reveals identifiable details of the productions we support, including concepts, location plans, dates, or even the fact that a specific production is coming to Nepal, where that is confidential. Illustrative examples on the site are kept general and are not tied to real clients. The handling of the actual documents and data you share with us is governed by our separate confidentiality and document-security materials. If you ever spot public content that appears to expose a real production's plans, treat it as a serious error and tell us immediately.
Because honesty requires matching the firmness of our wording to the solidity of the underlying fact. Durable practice, such as how foreign productions typically prepare or what document categories usually matter, changes slowly and reflects our direct experience, so we state it plainly. Specifics like fees, exact timelines, and the current issuing authority are exactly the things that vary and shift, so we will not assert them as verified fact. This lets the confident parts of the site stay genuinely reliable while the variable parts are flagged for confirmation.
Use the site to get ready and to ask better questions, then confirm the specifics for your actual project. Sort what you read into durable guidance you can act on now and regulatory specifics you should confirm before committing. Bring the general understanding into your planning, and when a budget line, date, or location hinges on a variable detail, have that detail checked against current sources and your particulars. The site is a strong starting point and a poor substitute for a real review, and treating it as the former is how you get the most value while staying protected.