Understanding Job List Types

Examples: Monthly bookkeeping, GST returns, TDS compliance, income tax filing, statutory audit, ROC filings, company secretarial compliance, monthly retainer services.

The structure that works

Create one job list per service in your preferred tool. Each financial year gets its own tab or page.

• Rows = your clients (add new clients as new rows — the URL never changes)
• Columns = months or quarters depending on the service cycle
• Each cell = a status dropdown showing where that client's work actually stands

Example: monthly bookkeeping service

The status stages for bookkeeping are not the same as for GST returns. Here's what a bookkeeping list looks like in practice:

The team member opens this list at their scheduled slot, works the current month's column, and updates each row as they go. No instructions needed — the structure makes it obvious what to do.

In TidySlot: one stage = one focused job

Because each stage involves different work, you can break a service into multiple scheduled jobs — one per stage. A team member who only does bank reconciliation works that stage for all clients in a single focused session. Another handles finalisation. Same list, different slots, zero context switching.

Examples: Client billing and collection, staff payroll, vendor payments, team training, YouTube or content production, social media posting, performance reviews.

The structure is identical to Type 1 — one job list per operation, one tab or page per financial year. The difference is what goes in the rows and columns, since these lists track internal operations rather than client services.

Example: client billing & collection

More backend list examples

Examples: Weekly timesheet review, team schedule review, leave approvals, project board check-ins, CRM pipeline reviews.

For these jobs, you don't need to build a separate list. The TidySlot job carries a direct link to the software itself. The team member opens the job, clicks the link, and lands straight in the tool — no context switching.

Common software-linked review jobs

Client examples: New service engagement, special advisory request, one-time filing, document collection, client complaint resolution.

Internal examples: Hiring, vendor changes, setting up a new process, IT task, training material creation.

The challenge: two different people, two different needs

Non-recurring jobs arise unpredictably. Two different types of people interact with the same list — and they need completely different access to it.

The non-recurring list structure

Unlike recurring lists (which use a client × time-period grid), non-recurring lists use a simple row-per-job structure:

The universal status dropdown

Non-recurring lists use statuses that apply to any type of job — not delivery stages, but flow states:

For jobs that take more than one sitting

Use the Comments column in your list to log where you stopped, what's blocking, and what's next. When the doer returns to the job the following day, they read the comment and pick up exactly where they left off — no chasing, no lost work.

Scaling with workload

Start with one shared list. As volume grows, split by job type or team role — each with its own TidySlot daily job for the relevant team members.

• Low volume → one shared list, everyone filters by their name
• High volume → separate lists by job type (e.g., one for new engagements, one for advisory jobs, one for internal tasks)