Collect before filing
Keep a controlled folder for the applicant, entity, premises, people and proposed licence scope.
National document guide · source-backed preparation
PSARA Licence Documents Required in India: Complete Checklist
Understand which records are generally relevant, which may be State or UT-specific, and what to verify before submitting a PSARA application.
NationalFramework firstStart with the Act and central material.
LocalConfirm the jurisdictionState and UT filing requirements can differ.
BoundaryPreparation is not approvalThe competent authority decides.
Short answer. A PSARA application requires prescribed information and supporting documentation. The exact checklist can vary with the applicant or entity, licence scope, State or UT rules and the applicable process. Prepare and cross-check records before submission, but remember that document readiness does not guarantee a licence.
Answer first
What should an applicant prepare?
Think of the file in layers: applicant and entity identity, address and premises, relevant people, declarations, verification, operating scope and any local or case-specific records. An incomplete or inconsistent set can affect scrutiny, processing or verification.
Classify every record
Label it as national framework, State/UT-specific or case-specific instead of assuming universal compulsion.
Verify the current route
The relevant authority's current instructions control the final filing list and submission method.
After the overview
Need help sorting the preparation questions?
Share the applicant structure and target jurisdiction for a preparation conversation. Assistance is not an official filing channel or approval promise.
The document architecture
Twelve categories keep the file readable
These are preparation categories, not a declaration that every item within them is mandatory in every State or UT.
01
Applicant / business identity
Start with the real applicant and the intended private-security activity. Record the applicant name exactly as it will appear in the application.
02
Constitution / entity documents
Keep the records that establish the legal form: proprietorship, partnership, LLP, company or applicable association of persons.
03
Address / premises
Prepare the registered or business address and premises evidence that the current process asks for. Ownership, rent or lease evidence may be relevant to the case.
04
People and ownership
Map proprietors, partners, directors, majority shareholders and other relevant responsible persons to the applicant structure.
05
Identity and citizenship
Prepare applicable identity, citizenship and antecedent particulars without treating one identity document as a universal PSARA rule.
06
Affidavits / declarations
Use the affidavit, declaration and undertaking language and execution instructions prescribed by the applicable law, rules or process.
07
Training / MOU
Training evidence or an MOU may form part of the application depending on the State, UT and arrangement. Confirm before committing.
08
Guard / supervisor records
Keep agency-level records separate from guard and supervisor records. The latter can arise where the applicable rules or process request them.
09
Antecedent / verification information
Give the authority the information and forms it requests for antecedent or police verification. Verification is not an approval guarantee.
10
Licence application information
Confirm licence scope, districts, State or UT, responsible persons, declarations, attachments and the current filing channel.
11
Additional State / UT documents
Additional forms, portal fields, local authority records or supporting documents may apply. Do not copy another jurisdiction's list.
12
Renewal / change records
For renewal or a change, compare the current licence and entity records with the updated information and the applicable official process.
The safety boundary
Core documents, local documents and case records are different
The national framework gives the starting point. The final file is shaped by the controlling authority, the applicant's structure, the premises and the requested licence scope.
Core / national framework
Information and documents arising from the PSARA Act and central framework, including the applicant, structure, scope, prescribed application context and authority-led verification.
State / UT-specific
Additional forms, declarations, portal fields, training or MOU requirements, local authority records and other supporting documents may vary by jurisdiction.
Case-specific
Additional records can depend on entity structure, premises, ownership or management, licence scope, personnel or a particular change in circumstances.
Document-by-document guide
Know what each record is doing in the file
Use the filter to separate the national starting point from local and case-dependent records. The labels describe relevance, not an approval outcome.
PAN
- Establishes:
- Tax or identity information associated with the applicant or entity.
- Who may need it:
- The applicant and, where the applicable process asks, relevant entity or key-person records.
- Check:
- Name and entity details should match the application and constitution records. Confirm the current authority checklist for the exact attachment.
Aadhaar or other identity proof
- Establishes:
- Identity details for a person whose record is requested.
- Who may need it:
- Proprietor, partners, directors, shareholders, guards or supervisors only where the applicable process requires it.
- Check:
- Do not treat Aadhaar as universally mandatory. Use the current official form or instruction and redact or secure sensitive material appropriately.
Address proof
- Establishes:
- A person's address or the applicant's registered or business address, depending on the record.
- Who may need it:
- The applicant, key persons or premises owner/occupier where applicable.
- Check:
- Check spelling, district, State, currentness and whether the address is residential, registered or operating premises.
Incorporation, registration or constitution records
- Establishes:
- The legal form and existence of the applicant.
- Who may need it:
- Company, partnership, LLP, firm, proprietorship or applicable association of persons.
- Check:
- The legal name, registration number, partners/directors and ownership record should align with the application.
Proprietorship business proof
- Establishes:
- Business identity where a sole proprietorship does not have incorporation documents.
- Who may need it:
- A proprietor, where the applicable process accepts or requests supporting business evidence.
- Check:
- GST, Udyam, Shop Act or another registration must not be presented as universally required PSARA documents.
Office or premises proof
- Establishes:
- The applicant's relationship with the stated business premises.
- Who may need it:
- An agency where the application or local process asks for premises evidence.
- Check:
- Match the address across rent/lease/ownership evidence, application, declarations and any authority correspondence.
Photographs
- Establishes:
- A visual identifier for a person where the current form or process asks for it.
- Who may need it:
- Applicant or relevant people, only as requested.
- Check:
- Use the current official instruction for quantity, recency, dimensions and submission method; do not invent a national photo rule.
Affidavits, declarations and undertakings
- Establishes:
- The applicant's prescribed confirmations or declarations.
- Who may need it:
- The applicant and relevant responsible persons where the applicable process requires them.
- Check:
- Use the current prescribed wording, signatory, stamp/notarisation and execution instructions. There is no universal template on this page.
Training or Training Institute MOU
- Establishes:
- A training arrangement or evidence relevant to the application where required.
- Who may need it:
- An agency where the target State/UT process requires training or MOU evidence.
- Check:
- Confirm institute, duration, certificate, format and any fee from current official material. No one arrangement is mandatory nationwide.
Antecedent or verification information
- Establishes:
- Information needed for authority-led antecedent or police verification.
- Who may need it:
- The applicant and relevant persons covered by the current form or inquiry.
- Check:
- Answer consistently and completely; verification is a process step, not a clean-pass certificate or approval promise.
Guard and supervisor records
- Establishes:
- Information about personnel where guard/supervisor conditions or the filing process calls for it.
- Who may need it:
- The agency and personnel covered by the applicable rules or process.
- Check:
- Keep these records separate from the agency's eligibility file and confirm the current scope of the request.
Licence-scope and application information
- Establishes:
- The requested State/UT, districts, agency activity and filing scope.
- Who may need it:
- Every applicant preparing a fresh application, renewal or change.
- Check:
- The scope, district and State/UT should be identical across the form, declarations, fee treatment and supporting records.
Preliminary organization aid
Mark the records you have in view
This mobile-friendly checklist helps organize a conversation and a working folder. It does not replace the applicable official State or UT checklist and does not create a legal guarantee.
Preparation progress0/16
A checked item means “in your working folder”, not “accepted by the authority”.
After the checklist
Turn the open boxes into a source log
A preparation conversation can help separate records you have from records the current authority still needs you to verify.
Before submission
Run a consistency check across the whole file
A strong document set is not only complete. Its names, addresses, entity details and scope tell the same story.
Spelling of proprietor, director and partner names
Business or entity name and legal constitution
Registered or business address, district and State/UT
Licence scope and proposed operating districts
Currentness or validity where a document must be current
Signatures, declarations and execution details
Readable scans, complete pages and correct orientation
File format and size only where the relevant State portal specifies them
Secure digital preparation
Scan complete pages in the correct orientation, keep signatures legible where required, use current documents where the process requires them, and store sensitive records in a controlled folder. Follow the relevant State portal's stated format and size limits; do not upload identity or business documents to unofficial websites.
Match the record to the applicant
Entity-specific preparation notes
The exact document requirement depends on the legal structure and the applicable rules. These are orientation points, not unsupported eligibility conclusions.
Proprietorship
Prepare proprietor identity, PAN, address, applicable business proof and premises records. GST, Udyam or Shop Act evidence is not presented here as universally mandatory.
Partnership firm
Keep the partnership constitution, partners' relevant particulars, authority or signatory details and records requested by the current process.
LLP
Treat an LLP as its own legal structure. Confirm its registration, designated-person and filing treatment instead of automatically copying a partnership checklist.
Company
Keep incorporation and constitutional records, directors, ownership or control information and applicable responsible-person details aligned.
Association of persons
Confirm the legal constitution, India registration and current application treatment before relying on an association route.
Training and MOU
Confirm the arrangement, not a nationwide template
Training-related documentation can form part of an application. Training or MOU arrangements can vary by State or UT and applicable rules. Do not assume one institute, duration, certificate or MOU format is mandatory nationwide. Review the application process and licence framework alongside current official material.
Affidavits and declarations
Use the prescribed execution instructions
Affidavits, declarations and undertakings may be required under the applicable law, rules or process. Do not rely on a copied universal format. Check the current authority material, signatory, wording, stamp or notarisation and submission method.
Review the official source trailFresh application, renewal or change
Do not reuse a stale file without a review
Fresh applications and renewal or change situations may require different or updated documentation. Compare what has changed before filing.
Fresh application
Build the applicant, constitution, premises, responsible-person, declaration, scope and verification record from the current structure.
Map the application processRenewal
Review the existing licence, expiry, scope, entity, address, people and current authority instructions. Do not assume the original file is still current.
Read the renewal guideChange situation
Ownership, management, constitution, address, scope or personnel changes may need a separate review under the applicable process.
Discuss the change scopeState / UT variation
There is no safe universal State checklist
Document requirements can differ because of applicable rules, designated authorities, forms, portals, training arrangements, local authority requirements and filing systems. This national page intentionally does not hardcode unverified State names or requirements. PSARA India will provide State-specific document checklists only after the applicable official requirements are independently verified.
Avoidable errors
Common document mistakes
Uploading incomplete scans or missing pages
Mismatched names, addresses or entity information
Using outdated documents where current records are required
Missing signatures, declarations or execution details
Using the wrong district, State/UT or licence scope
Assuming another State's checklist applies
Skipping the current official instructions before submission
Treating consultancy records as government-mandated documents
Confusing optional or case-specific records with universal requirements
Keep the money lines separate
Documents connect to fees, but a document cost is not a government fee
Use the centralized fee page for the current breakdown. The following separation is important when planning the file.
Government statutory fee
₹5,000 one district · ₹10,000 more than one and up to five districts · ₹25,000 whole State
PSARA India professional / consultancy
₹25,000; separate from the government fee and not universally compulsory
Training MOU
₹25,000–₹35,000 depending on State and applicable arrangement
Documents / affidavit / notarization
₹5,000; not a government fee and not universally compulsory
Armed Guard Endorsement
₹15,000, optional and only where applicable
Other costs
Statutory, third-party, tax and special-compliance costs as applicable
Questions applicants ask
PSARA document FAQs
These answers use the same wording as the FAQ structured data published with this page.
What documents are required for a PSARA Licence?
A PSARA application requires prescribed information and supporting records relating to the applicant, entity, address, responsible persons, declarations, verification and licence scope. The exact checklist varies by State or UT, entity and case, so confirm the current official instructions.
What are the basic PSARA documents for a new security agency?
Begin with applicant and entity identity, constitution or registration records, PAN, applicable identity and address records, responsible-person details, prescribed declarations, scope information and any training or verification records requested by the applicable process.
Is PAN required for PSARA?
PAN is generally relevant when preparing an applicant or entity record, but the exact attachment and person to whom it applies should be confirmed in the current State or UT process. Match the PAN name to the application and constitution records.
Is Aadhaar mandatory for PSARA?
This page does not treat Aadhaar as universally mandatory. Identity evidence depends on the applicable form, authority and person concerned. Use the current official instruction and handle sensitive identity documents securely.
Is address proof required?
Address information and supporting proof may be relevant for the applicant, key person or premises. The requested type and currentness can depend on the application process, so check the current State or UT checklist.
Are company incorporation documents required?
For a company, incorporation and constitution records are generally relevant to establish the entity and its responsible people. Partnership, LLP, proprietorship and association records differ; prepare the records that match the actual legal structure.
Are affidavits required for PSARA?
Affidavits, declarations or undertakings may be required under the applicable law, rules or application process. Use current prescribed wording and execution instructions rather than assuming a universal affidavit format.
Is a training MOU required?
Training or an MOU may be applicable depending on the State, UT and arrangement. Confirm the current institute, evidence, duration and format; this guide does not state that one MOU is mandatory nationwide.
Are police verification documents required?
Antecedent or police verification may form part of an authority-led inquiry, and the information or forms requested can vary. Provide what the current process asks for; verification does not guarantee approval.
Do PSARA documents differ by State?
Yes. State or UT rules, designated authorities, forms, portals, training arrangements and supporting-document requirements may differ. Do not copy another jurisdiction's checklist.
What documents are needed for PSARA renewal?
Renewal or change situations may require updated or different records. Compare the current licence, entity, address, people, scope and correspondence records with the current renewal instructions. See the renewal guide for the process context.
Can I use the same documents for multiple districts?
Some applicant and entity records may be reusable, but scope, premises, local instructions and filing treatment still need confirmation. Do not assume one document set automatically satisfies every district or State process.
How should PSARA documents be prepared for online submission?
Use complete, readable, correctly oriented scans with legible signatures where required. Check the current portal's specified format and size limits, keep a secure submission record and do not upload sensitive documents to unofficial websites.
What happens if documents contain inconsistent information?
Inconsistent names, addresses, entity details, scope or signatures can create scrutiny or a request for correction. Run a consistency review before submission and explain or correct genuine changes through the applicable process.
Is the PSARA India document checklist the same as the government checklist?
No. This is a national preparation and organization guide, not an official filing checklist. The applicable authority's current State or UT instructions control, and PSARA India does not guarantee approval or claim government affiliation.
Official source trail
Read the framework behind the preparation guide
The national starting point is the Private Security Agencies (Regulation) Act, 2005 on India Code, Ministry of Home Affairs PSARA materials or FAQ, the official PSARA portal and applicable State or UT rules where already verified.
For source links and the evidence boundary used by PSARA India, visit the official sources page. A source-backed guide still requires the applicant to confirm the current filing instructions of the relevant authority.
Keep these internal guides nearby
Before you submit
Build a careful file, then verify the local instruction
Use this national guide to organize the questions. Use the applicable official State or UT process to decide what must actually be filed. If you need preparation support, keep the proposed entity, scope and open document questions ready.