πŸ”‘ Admin β€” Setup Step

Building Your Yearly Job List Sheet

Before you create a single time slot in TidySlot, you need a job list sheet for each service. This guide shows you exactly how to build them β€” and why the URL never needs to change.

Do this before setting up slots. TidySlot's power comes from linking each slot to a job list URL. Without well-structured sheets, your slots won't deliver the clarity your team needs. Spend 30–60 minutes setting up your sheets first β€” it's a one-time investment.

Why your job list sheet matters

TidySlot does not store your client list or job details. It stores a URL β€” a link to wherever your clients and jobs already live. When a slot fires, TidySlot opens that URL for the assigned team member. The work happens in your sheet, not in TidySlot.

This means the quality of your job list sheet directly determines how useful TidySlot is for your team. A well-structured yearly sheet lets your team member open the sheet, go straight to the current month's column, and start working β€” without any instruction from you.

One sheet per service type. Don't create one giant sheet for everything. Create a separate sheet for each service category β€” GST returns, ITR filing, bank reconciliation, payroll, etc. Each sheet gets linked to its own set of time slots.

The yearly sheet structure

The standard structure for a TidySlot-compatible yearly job list sheet is:

Example β€” GST Return Filing Sheet (Monthly)
Client Name GSTIN Jan 25 Feb 25 Mar 25 Apr 25 May 25
Mehta Textiles 24AABCM… βœ“ Filed βœ“ Filed βœ“ Filed Pending β€”
Shah & Sons 24AADCS… βœ“ Filed βœ“ Filed βœ“ Filed βœ“ Filed β€”
Patel Exports 24AABCP… βœ“ Filed βœ“ Filed Docs pending β€” β€”

The team member opens this sheet each month, works the current column, and marks each row Done as they file. No instructions needed β€” the structure tells them exactly what to do and what's outstanding.

Building your sheet β€” step by step

Adding new clients mid-year

This is one of TidySlot's most powerful design principles: adding a new client requires zero TidySlot changes.

  1. Open the relevant service sheet (e.g., GST Returns FY25-26).
  2. Add a new row for the new client.
  3. Fill in their details in the row.
  4. Done β€” the slot already fires to the right URL, the team member opens the sheet, the new client row is there.

The slot URL in TidySlot is permanent and never changes. The sheet grows with your firm. TidySlot doesn't need to know about new clients β€” it just opens the sheet.

This is what "scalability without overhead" means in practice. 10 new clients this quarter = 10 new rows in your sheet = 0 changes in TidySlot. No reconfiguration, no new slots, no admin overhead.

Sheet structures for common CA firm services

πŸ“Š GST Returns

Rows = clients. Columns = months (Apr–Mar). Status per cell: Filed βœ“ / Pending / Docs Awaited / NA.

One sheet per financial year. Slot fires on: data collection day + filing day.

πŸ“ ITR Filing

Rows = clients. Columns = filing type or phase (Data collected / Draft sent / Client approved / Filed). One row per client per year.

Slot fires: once per phase. Each phase is a separate slot linked to the same sheet.

🏦 Bank Reconciliation

Rows = clients. Columns = months. Status: Reconciled βœ“ / Pending / Discrepancy noted. Include bank name as a column if clients have multiple accounts.

Slot fires: monthly. Same sheet URL for the full year.

πŸ’Ό Payroll

Rows = clients (or employees if your firm runs payroll internally). Columns = months. Status: Processed βœ“ / Pending / On Hold.

Slot fires: monthly. Two slots if payroll and payslips are separate tasks.

🏒 MCA / ROC Compliance

Rows = clients. Columns = filing type (AOC-4 / MGT-7 / DIN KYC etc.). Due date column essential here β€” ROC filings are date-specific, not monthly.

Slot fires: as per due dates. Consider a dedicated ROC calendar sheet with due date column.

πŸ“‹ TDS Returns

Rows = clients. Columns = quarters (Q1–Q4). Status: Challan paid βœ“ / Return filed βœ“ / Certificate issued βœ“. Three sub-tasks per quarter.

Slot fires: quarterly with 3 separate slots per quarter for each sub-task.

Best practices