DPDP Act Compliance Checklist for Businesses

  • Blog|Company Law|
  • 16 Min Read

A DPDP compliance checklist for businesses: the fifteen subject areas and 49 requirements in Appendix A, the first-ninety-days readiness checklist in Figure 12.1, the three phases to 13 May 2027, governance, policies, training and vendors.

  • By Taxmann
  • |
  • Last Updated on 16 November, 2026

DPDP Act Compliance

The substantive provisions of the DPDP Act come into force on 13 May 2027, and every organisation that processes digital personal data within the territorial scope of section 3 must have a functioning compliance programme in place by that date. A DPDP compliance checklist therefore has two halves: what has to be in place, and the order in which to build it. Taxmann’s Digital Personal Data Protection supplies both. Appendix A consolidates every obligation under the Act and the Rules into 49 testable requirements across fifteen subject areas, and Figure 12.1 sets out the readiness checklist for the first ninety days in four blocks: governance, discovery, gap analysis and prioritisation. The book is blunt about the timetable: the eighteen-month window from the Timelines Notification of 13 November 2025 is not generous.

Table of Contents

  1. What does DPDP compliance require, and by when?
  2. What is the DPDP framework the checklist is built on?
  3. What is on the DPDP compliance checklist?
  4. What should the first ninety days produce?
  5. How should the work be phased up to 13 May 2027?
  6. Who should own the programme?
  7. Which policies and training does the programme need?
  8. Where do vendors and Data Processors fit?
  9. Does a startup or small business have to comply?
  10. Does the checklist change for regulated sectors?
  11. What goes wrong in DPDP compliance programmes?
  12. Quick answers

1. What does DPDP compliance require, and by when?

A functioning compliance programme by 13 May 2027. The Timelines Notification G.S.R. 843(E), dated 13 November 2025, provides that the substantive provisions of the Act, namely sections 3 to 17, sections 27 to 34, sections 36 and 37 and section 44(2), come into force eighteen months from its publication, which places the enforcement date at 13 May 2027. Every organisation that processes digital personal data within the territorial scope of section 3 must have a functioning compliance programme in place by that date (Chapter 12, opening).

The book is specific about what a programme is. It is not a single document or a single project. It is a governance structure, a set of policies, a collection of processes, a technology infrastructure, a training programme, an evidence architecture and a monitoring mechanism, all operating together so that the obligations of the Act are observed in practice and can be demonstrated on demand (Chapter 12, opening).

One part of the regime is already running. The second commencement phase, from 13 November 2026, brought in Consent Manager registration under section 6(9), the Board’s jurisdiction over breaches of Consent Manager registration conditions under section 27(1)(d), and Rule 4 (para 1.6). For everyone else, the date that matters is 13 May 2027. Whether the Act applies at all is a two-question test under section 3, set out in the overview of the DPDP Act.

2. What is the DPDP framework the checklist is built on?

The Act, the Rules and the notifications of 13 November 2025, read together. The book’s legal citations are to the Digital Personal Data Protection Act, 2023 (No. 22 of 2023) and three instruments dated 13 November 2025: the Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E)), the Board Establishment Notification (G.S.R. 844(E)) and the Timelines Notification (G.S.R. 843(E)) (How to Use This Book).

The relationship between the Act and the Rules is one of framework and operational detail. The Act establishes the obligation; the Rules specify how it is to be discharged. Section 8(5) tells a Data Fiduciary that it must take reasonable security safeguards to prevent a personal data breach; Rule 6(1) tells it what those safeguards must, at a minimum, include. Section 8(6) requires intimation of a breach; Rule 7 prescribes its content, the seventy-two-hour timeline and what must be furnished to the Board. The book’s conclusion is the reason a checklist has to cite both: any compliance programme that reads the Act without the Rules will be incomplete, and any programme that reads the Rules without the Act will lack the legal foundation (para 1.7).

The Rules contain 23 operative rules and seven Schedules, and their structure follows the obligation architecture of the Act (para 1.7). The Act, the Rules and the three notifications are on Taxmann.com | Research under Indian Acts and Rules.

3. What is on the DPDP compliance checklist?

Fifteen subject areas. Appendix A to the book, the Consolidated Requirements Register, maps every obligation under the Act and the Rules to its legal reference and to the specific audit evidence that an auditor or the Board may request. Where the Rules expand, clarify or operationalise an obligation under the Act, the requirement is merged into a single entry with both references, and each requirement is stated as a testable statement. The result is 49 consolidated entries (Appendix A). The book intends it to be used as a working document throughout the programme, not a reference read once (How to Use This Book).

What each area requires the organisation to have in place:

# Subject area What has to be in place Principal provisions
1 Scope, applicability and roles A documented determination of whether the Act applies, a role classification (Data Fiduciary, Data Processor or both) for each processing activity, and an assessment of Significant Data Fiduciary status Sections 3(a)-(b), 2(i), 2(k), 10(1)
2 Notice and consent A standalone notice given before or at the time consent is requested, with an itemised description of the personal data and purpose and the means to withdraw consent, exercise rights and complain to the Board; notices to existing Data Principals; English and Eighth Schedule language options; consent that is free, specific, informed, unconditional and unambiguous, given by clear affirmative action and limited to the necessary data; withdrawal as easy as giving consent; records able to prove notice and consent; a lawful basis, consent or a section 7 legitimate use, for every activity Sections 4 to 7; Rule 3
3 Children’s data and persons with disability Verifiable consent of a parent before processing a child’s personal data, by reference to reliable identity and age details already held or provided, or a virtual token; no processing detrimental to a child’s well-being; no tracking, behavioural monitoring or targeted advertising directed at children; verified lawful guardians for persons with disability Section 9; Rules 10 to 12; Fourth Schedule
4 Data Principal rights and request handling A prominently published means of making requests, with proportionate identification, and a process to answer access, correction, completion, updating, erasure and nomination requests Sections 11, 12, 14; Rule 14(1), (2), (4)
5 Security safeguards Reasonable security safeguards meeting the seven minimum measures: encryption, obfuscation, masking or virtual tokens; access controls; logging, monitoring and review; business continuity and backups; one-year log retention; contractual provisions with Data Processors; technical and organisational measures Section 8(5); Rule 6(1)(a)-(g)
6 Breach response and notification Intimation to each affected Data Principal without delay, covering five prescribed elements, and to the Board without delay, followed by a detailed report within seventy-two hours Section 8(6); Rule 7(1), (2)
7 Retention and deletion A retention schedule; erasure when the purpose is no longer served; the forty-eight-hour pre-deletion notice where it applies; one-year retention of processing logs; erasure by Data Processors when directed Section 8(7), (8); Rule 8; Third and Seventh Schedules
8 Data Processor and vendor management Acceptance that the Data Fiduciary remains responsible for processing done on its behalf, irrespective of any agreement to the contrary; a valid contract for every Data Processor engagement, with security provisions Section 8(1), (2); Rule 6(1)(f)
9 Cross-border transfer A record of transfers outside India and monitoring for any Central Government restriction on transfers to a country; for Significant Data Fiduciaries, readiness for data localisation of specified categories Section 16; Rule 15; Rule 13(4)
10 Grievance redressal A readily available grievance mechanism, a published response period not exceeding ninety days, and records showing that the period is met Sections 8(10), 13; Rule 14(3)
11 Governance, accountability and Significant Data Fiduciary obligations Documented accountability and published contact details of the Data Protection Officer or designated contact person; for Significant Data Fiduciaries, a Data Protection Officer based in India, an independent data auditor, periodic Data Protection Impact Assessments and audits reported to the Board, and algorithmic risk assessment Sections 8(1), 8(9), 10; Rules 9, 13
12 Consent Manager obligations Only for an organisation that is a Consent Manager: registration with the Board on the First Schedule conditions, including a net worth of at least Rs. 2 crore, and the Part B obligations Section 6(9); Rule 4; First Schedule
13 Exemptions A documented basis for every exemption claimed, with sections 8(1) and 8(5) still observed for exempt processing Section 17; Rule 16; Second Schedule
14 Enforcement, penalties and dispute resolution Awareness of the penalty schedule, a protocol for Board inquiries and directions, and a process for information requests from the Central Government Sections 27, 28, 32, 33, 36; Rules 19(9), 23; Schedule
15 Commencement timelines An implementation roadmap aligned with the phased commencement dates of 13 November 2025, 13 November 2026 and 13 May 2027 G.S.R. 843(E); Rule 1(2)-(4)

The table compresses each area into its core; the register itself states every requirement in full, with the evidence that proves it (Appendix A; paras 1.7, 1.9.3, 5.8, 6.1, 8.10, 9.3 and 10.8). The book’s own description of its purpose is the right way to use it: for each requirement, determine whether each listed evidence artefact has been produced, whether it is current and accurate, and whether it is stored in a retrievable format, so that no obligation is overlooked before a Board inquiry or an independent data audit (para 12.2.4). How such an audit is scoped and what it tests are covered in how a DPDP compliance audit is conducted.

Taxmann.com | Research | Subscribe Now!

4. What should the first ninety days produce?

Foundations. For an organisation starting from a standing start, the book prioritises the activities that generate the artefacts on which everything else depends: a programme sponsor at senior management level, a steering committee drawn from legal, information technology, human resources, procurement and the principal business functions, a personal data inventory identifying every system, process and vendor relationship in which digital personal data is collected, stored, processed, shared or deleted, and a lawful basis assessment mapping each processing activity to consent or a specific section 7 legitimate use (para 12.1.2).

Figure 12.1, the DPDP Compliance Readiness Checklist for the first ninety days, is the checklist in its most usable form (para 12.1.3):

Block Checklist items
Governance Programme sponsor appointed at senior management level; steering committee constituted with cross-functional representation; programme plan with milestones and resource allocation approved
Discovery Personal data inventory completed across all systems, processes and vendors; data flow maps produced for each processing activity; role classification completed (Data Fiduciary, Data Processor or both); lawful basis register drafted for each processing activity
Gap analysis Notice compliance gap assessment (section 5, Rule 3); consent mechanism gap assessment (section 6); security safeguard gap assessment against Rule 6(1)(a)-(g); breach response capability assessment; rights fulfilment mechanism assessment; grievance redressal mechanism assessment; Data Processor contract review (section 8(2), Rule 6(1)(f)); retention schedule drafted with legal retention cross-references; children’s data processing assessment (section 9, Fourth Schedule); cross-border transfer mapping completed; gap analysis report produced with priority ranking
Prioritisation Remediation plan with owners and timelines approved; budget allocation for the next phase confirmed

By the end of the ninety days the organisation should hold a documented data inventory, a preliminary lawful basis register, an initial gap analysis identifying the highest-priority remediation areas, a programme plan with milestones and resource requirements, and a governance structure with defined roles and accountabilities. Those artefacts ensure that the programme proceeds from a foundation of fact rather than assumption (para 12.1.2). The inventory is the same record discussed in the Record of Processing Activities (ROPA), and the role classification should be recorded for each processing activity, with the basis for it and the date and authorship of the assessment, because section 6(10) puts the burden of proof on the Data Fiduciary (paras 2.14.1 and 2.14.2).

5. How should the work be phased up to 13 May 2027?

In three phases, measured against the eighteen-month window that opened with the Timelines Notification (para 12.1.1):

Phase Duration Focus
Discovery and assessment Approximately the first three to four months Identify all processing activities; map data flows; classify the organisation’s role for each activity; determine the applicable lawful basis; assess existing controls against Rule 6(1); conduct an initial gap analysis
Design and implementation Approximately the next eight to ten months Draft policies; design notices and consent mechanisms; build rights fulfilment and grievance workflows; remediate security gaps; renegotiate Data Processor contracts; develop training content
Testing and validation The final two to three months before enforcement Verify that all mechanisms work as designed; run tabletop exercises for breach response; test consent collection and withdrawal flows; confirm that notices comply with Rule 3; prepare the evidence files required in the event of a Board inquiry

The book’s reason for front-loading the work is the size of it. An organisation that processes personal data across several business lines, jurisdictions, technology platforms and Data Processors faces data inventory and mapping, lawful basis determination, notice and consent redesign, security gap assessment and remediation, breach response design, rights and grievance mechanisms, vendor contract renegotiation, training and governance, each with its own planning, resourcing, execution and testing cycle (para 12.1.1).

The sequencing rule follows from that. A well-structured programme works backwards from 13 May 2027, identifying the obligations with the longest lead time, such as notice redesign, consent mechanism overhaul, security safeguard remediation, breach response capability and Data Processing Agreement renegotiation, and sequencing implementation accordingly (para 1.9.2). The book’s warning is concrete: an organisation that forms its DPDP steering committee only in January 2027 would have little more than four months to complete notice redesign, consent mechanism rebuild and security safeguard remediation, work that better-prepared peers will have spread across the full window (para 1.9.2).

6. Who should own the programme?

More than one function, because the obligations cut across the organisation. The notice obligation needs the business functions that set purposes and the legal function that checks Rule 3. The consent mechanism needs user experience designers, front-end developers and legal. The Rule 6(1) safeguards need information security, infrastructure and vendor management. The grievance mechanism needs customer service, legal and the designated contact person under Rule 9 (para 12.2.1).

The book’s structure has three tiers (para 12.2.1):

Tier Who Role
Programme sponsor A member of senior management or, where applicable, the Data Protection Officer appointed under section 10(2)(a) Overall accountability for the programme; reports to the board of directors or equivalent governing body
Steering committee Workstream leads from legal, information technology, information security, human resources, procurement and the principal business units Reviews progress, resolves inter-functional dependencies and approves deliverables, typically fortnightly during implementation and monthly in steady state
Workstream teams Teams under the same workstream leads Draft policies, build mechanisms, conduct assessments, remediate gaps and produce evidence, continuously between committee meetings

The second and third tiers are nested and run concurrently rather than as a strict chain of command (para 12.2.1). Where the mechanisms have to be built rather than listed, including compliance SOPs and automation of compliances, Taxmann Advisory provides implementation support.

7. Which policies and training does the programme need?

The Act and Rules do not prescribe a set of policies. The obligations are stated as outcomes, such as giving notice, obtaining consent, taking reasonable security safeguards and establishing an effective grievance mechanism, rather than as documents. But they cannot be operationalised at scale without policies that translate statutory requirements into internal standards and give a basis for training, monitoring and audit (para 12.2.2). The book’s minimum set is eight (para 12.2.2):

  1. A data protection policy, establishing the commitment to compliance and assigning accountability.
  2. A notice and consent policy, covering notice drafting, translation and version management, and consent collection and withdrawal.
  3. A data retention and deletion policy, covering retention periods, legal retention requirements, the Third Schedule periods where applicable and the Rule 8(2) pre-deletion notice.
  4. A security safeguards policy implementing the seven minimum requirements of Rule 6(1).
  5. A breach response policy, with templates for intimation to the Board and to Data Principals under Rule 7.
  6. A Data Principal rights policy for access, correction, completion, updating, erasure and nomination requests.
  7. A grievance redressal policy under section 13 and Rule 14(3).
  8. A vendor and Data Processor management policy under section 8(2) and Rule 6(1)(f).

Training belongs on the checklist as an obligation, not an extra. The technical and organisational measures required by section 8(4) and Rule 6(1)(g) include the capability of the organisation’s personnel to discharge their data protection responsibilities, and the book puts the point plainly: a security safeguard is only as effective as the person who operates it (para 12.2.3). It recommends two tiers, general awareness training for everyone who handles personal data and role-specific training for legal, IT, customer service, HR and procurement teams, with completion recorded and retained as evidence of the measures implemented under section 8(4) (para 12.2.3). Role-specific sessions of this kind, live or recorded, run on Taxmann.com | Learning.

Taxmann's Digital Personal Data Protection Act 2023 with Rules – Bare Act with Section Notes

8. Where do vendors and Data Processors fit?

At the centre of the accountability question. Section 8(1) makes the Data Fiduciary responsible for complying with the Act and the Rules in respect of any processing undertaken by it or on its behalf by a Data Processor, irrespective of any agreement to the contrary. A contractual clause that purports to transfer the obligations to the Data Processor does not relieve the Data Fiduciary; it may delegate the processing, but not the accountability (para 2.4).

For the checklist, that means vendor oversight is part of the compliance programme rather than procurement housekeeping. The book’s list is specific: a register of all Data Processors, a valid contract for each engagement under section 8(2) with the security provisions required by Rule 6(1)(f), monitoring of compliance with those provisions, periodic assessments of each Data Processor’s security posture, and confirmation that each Data Processor can support the Data Fiduciary’s obligations on breach notification, erasure and Data Principal rights. Organisations that treat vendor management as a procurement function rather than a compliance function will find that the gap between the contract and the practice is where enforcement risk accumulates (para 5.7.1). Which vendors are Data Processors, and which are Data Fiduciaries in their own right, is a prior question, covered in Data Fiduciary, Data Processor or both.

The Data Processor carries obligations of its own, though they are mainly derivative: it must process in accordance with the contract, implement reasonable security safeguards as the contract provides, and erase personal data when directed under section 8(7)(b) (para 2.4). The clauses the contract should contain are covered in the data processing agreement.

9. Does a startup or small business have to comply?

Yes, if it falls within section 3. Applicability under section 3 turns on where digital personal data is collected and whether processing outside India is connected with offering goods or services to Data Principals in India, and none of the three limbs of section 3 refers to the size of the organisation (para 1.4).

Section 17(3) allows the Central Government to exempt notified classes of Data Fiduciaries from certain provisions, and the book treats startup and small entity exemptions under that provision. The operative word is notified: until a notification is issued, the exemptions it would trigger do not take effect (paras 1.5.3 and 2.13). A small business should not plan on the basis of an exemption that has not been notified. The current position on exemptions is in exemptions under the DPDP Act, and the wider picture for smaller organisations in the DPDP Act and startups and SMEs.

Where a specific question turns on how the Act applies to a particular business model, it can be put to Taxmann AI, which answers questions against the law and drafts from it.

10. Does the checklist change for regulated sectors?

It adds to it. Section 38(1) provides that the Act is in addition to and not in derogation of any other law for the time being in force, and section 38(2) provides that in the event of conflict the DPDP Act prevails to the extent of the conflict. The practical consequence is that the compliance programme has to be designed to operate alongside, and in some cases on top of, the obligations imposed by sectoral regulators (para 12.3).

The same applies to existing certifications. An organisation that assumes its ISO 27001 certification or SOC 2 report satisfies the DPDP Act will find gaps precisely where the Act goes beyond information security into data protection governance, transparency and individual rights. Existing frameworks are a foundation for the programme, not a substitute for it (para 12.3). Sector-specific posts cover FinTech and BFSI and healthcare and HealthTech.

11. What goes wrong in DPDP compliance programmes?

The book lists five findings that recur at programme level (para 12.3, Audit considerations):

  1. The programme is treated as a one-time project, with no ongoing governance or periodic review.
  2. Policies are drafted but not communicated to operational staff.
  3. Training is given to legal and IT teams but not to the customer-facing staff who handle rights requests and grievances.
  4. The evidence framework is not maintained: policies exist, but supporting records such as consent logs, grievance logs and deletion logs are not systematically captured.
  5. An existing ISO 27001 or SOC 2 framework is treated as sufficient, without addressing the data protection-specific gaps in notice, consent, rights and retention.

Each of these is a checklist item in reverse. The first is avoided by building review into the governance structure; the fourth by treating the evidence framework as part of the programme rather than an afterthought. On that point the book’s reasoning is worth having in mind from day one: section 6(10) puts the burden of proving valid notice and consent on the Data Fiduciary, and section 28(5) lets the Board inquire into the affairs of any person to ascertain compliance, which together create an effective obligation to be able to produce evidence of compliance on demand (para 12.2.4). How a Board inquiry runs, and how to prepare for one, is covered in the Data Protection Board of India.

The book also offers a reassurance that is easy to overlook. Many of the disciplines a DPDP programme needs are not new to the professionals expected to lead it: a Data Protection Impact Assessment is structurally a risk assessment, a requirements register is a control matrix, and a Board inquiry response file is evidence preparation for a regulatory proceeding (para 12.3).

12. Quick answers

What is a DPDP compliance assessment?

In Figure 12.1 of Taxmann’s Digital Personal Data Protection, it is the gap analysis block of the first ninety days: assessments of notice compliance, the consent mechanism, security safeguards against Rule 6(1)(a)-(g), breach response capability, rights fulfilment, grievance redressal, Data Processor contracts, retention, children’s data and cross-border transfers, ending in a gap analysis report with priority ranking. For security, the book’s method is to map existing controls against each Rule 6(1) requirement, system by system, identifying where controls exist, where they are partially implemented and where they are absent.

How to get DPDP compliant?

By running a compliance programme rather than a one-off project: a programme sponsor and cross-functional steering committee; a personal data inventory, role classification and lawful basis register; a gap analysis against the Act and the Rules; then design and implementation of notices, consent, rights and grievance workflows, security remediation, Data Processor contracts and training; and finally testing and validation, including breach tabletop exercises, before 13 May 2027.

What is the DPDP framework?

The Digital Personal Data Protection Act, 2023, the Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E)) and the notifications of 13 November 2025 establishing the Data Protection Board (G.S.R. 844(E)) and the commencement timelines (G.S.R. 843(E)). The Act sets each obligation and the Rules specify how it is to be discharged, so a compliance programme has to read both.

What are the requirements for compliance with the DPDP Act in India?

They fall into fifteen areas: scope and roles; notice and consent; children’s data and persons with disability; Data Principal rights; security safeguards; breach notification; retention and deletion; Data Processor management; cross-border transfer; grievance redressal; governance and Significant Data Fiduciary obligations; Consent Manager obligations; exemptions; enforcement; and commencement timelines. Appendix A of Taxmann’s Digital Personal Data Protection consolidates them into 49 testable requirements.

By when must an organisation be DPDP compliant?

By 13 May 2027, when sections 3 to 17, sections 27 to 34, sections 36 and 37 and section 44(2) of the Act come into force under Notification G.S.R. 843(E). Consent Manager registration under section 6(9) and Rule 4 has applied since 13 November 2026.

Does the DPDP Act apply to small businesses and startups?

Yes, if they process digital personal data within the scope of section 3, which sets no size threshold. Section 17(3) allows the Central Government to exempt notified classes of Data Fiduciaries from certain provisions, but no such exemption takes effect until it is notified.


This article draws on Chapter 12 of Taxmann’s Digital Personal Data Protection – An Essential Guide to India’s DPDP Law by CA Narasimhan Elangovan (2026 Edition), which sets out the compliance programme: the implementation roadmap against May 2027, the first ninety days and the Compliance Readiness Checklist in Figure 12.1, the governance structure, the minimum policy architecture, training, demonstrable compliance and the evidence framework, preparation for a Board inquiry, and the interaction with existing regulatory obligations. It also draws on Appendix A, the Consolidated Requirements Register, and on Chapters 1, 2 and 5 on commencement, role classification and Data Processor accountability. Law stated as updated till 15 September 2026.

The DPDP Act, 2023, the DPDP Rules, 2025 and the notifications of 13 November 2025 are available on Taxmann.com | Research under Indian Acts and Rules.

Related reading: overview of the DPDP Act · scope and key definitions · rights of Data Principals · lawful processing and consent · obligations of Data Fiduciaries · cross-border data transfers · breach, enforcement and penalties · the DPDP Act and the IT Act · the DPDP Act and the EU GDPR · startups and SMEs · FinTech and BFSI · healthcare and HealthTech.

More in this series: the SPDI Rules and the DPDP Act · the Record of Processing Activities (ROPA) · the incident response plan · data retention and erasure · the privacy notice under Rule 3 · the data processing agreement · data localisation and cross-border transfers · employee data and workplace monitoring · exemptions under the DPDP Act · legitimate uses under section 7 · the Data Protection Board of India · how a DPDP compliance audit is conducted · Significant Data Fiduciary obligations · Consent Managers under the DPDP framework · personal data breach intimation under Rule 7 · handling Data Principal rights requests · Data Fiduciary, Data Processor or both · children’s data and verifiable parental consent.

Disclaimer: The content/information published on the website is only for general information of the user and shall not be construed as legal advice. While the Taxmann has exercised reasonable efforts to ensure the veracity of information/content published, Taxmann shall be under no liability in any manner whatsoever for incorrect information, if any.

Leave a Reply

Your email address will not be published. Required fields are marked *

Everything on Tax and Corporate Laws of India

To subscribe to our weekly newsletter please log in/register on Taxmann.com

Author: Taxmann

Taxmann Publications has a dedicated in-house Research & Editorial Team. This team consists of a team of Chartered Accountants, Company Secretaries, and Lawyers. This team works under the guidance and supervision of editor-in-chief Mr Rakesh Bhargava.

The Research and Editorial Team is responsible for developing reliable and accurate content for the readers. The team follows the six-sigma approach to achieve the benchmark of zero error in its publications and research platforms. The team ensures that the following publication guidelines are thoroughly followed while developing the content:

  • The statutory material is obtained only from the authorized and reliable sources
  • All the latest developments in the judicial and legislative fields are covered
  • Prepare the analytical write-ups on current, controversial, and important issues to help the readers to understand the concept and its implications
  • Every content published by Taxmann is complete, accurate and lucid
  • All evidence-based statements are supported with proper reference to Section, Circular No., Notification No. or citations
  • The golden rules of grammar, style and consistency are thoroughly followed
  • Font and size that's easy to read and remain consistent across all imprint and digital publications are applied