Digikase

Tax and legal teams handle hundreds of cases across many clients, financial years and departments. When this lives in spreadsheets, emails and notebooks, hearing dates get missed, case status is unclear and finding one case is slow. The team needed one secure system where every case, client and hearing date is recorded, searchable and visible to the right people.

• Keep all cases, clients and hearing details in one central system
• Make upcoming hearing dates visible so none are missed
• Search and filter cases by tax type, case type and keyword
• Track the status of every case from a simple dropdown
• Control who can see and do what with organisations and role-based access
• Generate reports and export case data when needed
• Handle support requests through a built-in tickets module

I built Digikase as a Next.js web application with a clean admin dashboard. A sidebar gives quick access to Dashboard, Organizations, IAM, Manage (cases), Customers, Reports, Tickets and Settings. The cases screen lists every case with client, creator, hearing date, tax type, financial year and status, with search, filters, export, and view, edit and delete actions on each row. A Next Hearing Date banner highlights upcoming hearings, and the IAM module controls users and roles. Login supports email with “Remember me” and Google sign-in.

Key features

• 01Case management with add, view, edit and delete
• 02Case details: CNR number, client, hearing date, tax type, financial year, description
• 03Next Hearing Date banner for upcoming hearings
• 04Search, tax type filter, case filter and export
• 05Status tracking with a one-click dropdown
• 06Organizations, IAM and role-based user access
• 07Customer management, reports and support tickets
• 08Secure login with email and Google sign-in, notifications and pagination

Technology stack

• Next.js
• REST APIs
• Google OAuth
• CSS3
• JavaScript (ES6+)
• MongoDb
• Node.js

1. 1

   Scope

   Understand how the team tracks cases, hearings, clients and users today.

2. 2

   Data & roles

   Define case fields, tax types, statuses and user roles.

3. 3

   UI design

   Design a clear admin dashboard with a sidebar and a data-heavy case table.

4. 4

   Architecture

   Plan REST APIs and database models for cases, clients, organisations and users.

5. 5

   Frontend build

   Build the dashboard, case list, filters, forms and status controls in Next.js.

6. 6

   Access & login

   Add role-based access (IAM) and email and Google login.

7. 7

   Reports & tickets

   Build export, reports and the support tickets module.

8. 8

   QA & launch

   Test with real case data, deploy and hand over.