Task Management for Temples
Give project work an owner, due date and visible status.
Does this function belong in your operation?
Use when work crosses people or requires follow-up beyond personal reminders.
A piece of work needs assignment or follow-up.
Priests are assigned to bookings by specialisation, language and available days, and each priest opens the day’s list of sevas and sankalpas.
Bring the records the workflow depends on.
- Task descriptions
- Owners and due dates
- Project and dependency references
Outputs to check
- Owned task register
- Overdue and blocked-work list
- Completion and handover history
Follow the task management workflow.
Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.
Who uses the module, and who approves?
Keep responsibilities distinct even when one person holds more than one role.
Decide how exceptions are handled.
These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.
Can this work independently?
Tasks can stand alone with named users and due dates. Project schedules, time records and document approvals provide context when connected. Completing a task should not automatically post an invoice, release stock or approve a document unless that separate handoff is explicitly designed.
Systems and records it connects with
- Project timelines with Gantt charts: Planned dates, dependencies and recorded milestone progress.
- Project time tracking: Approved task hours and their billable classification.
- Notifications: Approved event messages and delivery or failure status.
- Client portal: Permitted customer documents, requests and account views.
Configure, test and introduce the workflow.
- Name the kinds of tasks your team handles. We return task types and checklists for each.
- List the clients or projects tasks belong under. A structure arrives to browse. Open tasks from your sheets or chats are loaded. Owners are checked and dates fixed.
- A few people use it daily. Phone use is tested, and the rest join after changes.
Check the result before rollout.
Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.
- Open tasks have an owner.
- Overdue tasks are identifiable.
- Closed work retains its completion record.
How the business operates.
The temple office runs Temple Management Software, set up by GullySystem for trusts with a seva counter. Counter staff, priests and trustees use it. Seva and pooja bookings, donations by type, numbered PDF receipts, devotee details with gothra and nakshatra, festivals and priest duties sit together. The temple also gets a website with timings, sevas and a donation page.
The records that hold the operation together.
- Pooja booking. Set each seva’s price type, duration, days, time slots, bookings per slot and required devotee details. Bookings are numbered and move from pending to confirmed, assigned, completed or cancelled.
- Online seva booking. Let devotees request a seva from your temple website with date, slot, gothra, nakshatra and sankalpa. The office confirms the request and takes payment at the counter when the family arrives.
- Donations by type. Record every donation against a head you define, such as annadana, gau seva, building fund or hundi, with the donor’s tax ID, payment mode, reference and purpose. Each fund reads separately.
- Online donations. Let devotees give from your website by bank transfer and enter the transaction reference. A numbered receipt is raised with that reference for matching against the bank statement.
Operational bottlenecks to check
Receipt books run out on festival days
On festival days a queue forms before the doors open. Receipts written by hand smudge in the heat of the counter, and the evening total may not match the cash box or the hundi count.
Bookings for the next day are not visible
Bookings arrive at the counter, by phone and through trustees, and each carries a different slip. The priest learns the sankalpa count only when names are read out at the homa.
How work flows across this business
This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.
1. Sevas and slots
Enter each pooja or seva with the name your office uses, the amount or free-will offering, the days performed, time slots and bookings per slot. Choose which ones devotees may request online, and which stay counter-only.
2. Booking
At the counter, staff pick the seva, date and slot, note the gothra, nakshatra, rashi and sankalpa, and take payment. Online requests arrive as pending bookings with those details filled in by the devotee.
3. Receipt
Every paid booking or donation takes the next number in the series and comes out as a PDF. Donation receipts carry the trust’s tax-exemption details and the donor’s tax ID where the trust is registered for exemption.
4. Priest assignment
The office assigns a priest to the booking and marks it confirmed, assigned or completed. The priest opens the day’s list with every sankalpa on it, in the order of the homa.
5. Closing the day
The dashboard shows today’s donations, the month’s total, the day’s bookings and online requests still waiting, with collections by payment mode. Exports go to the trust’s accountant for the audit file.
Industry reports to connect with
- Today’s and this month’s donations
- Donations and seva bookings totals
- Collections by payment mode: cash, cheque, bank transfer and online
- Receipts register, downloadable as CSV
Questions before implementation.
When should temples consider task management?
Use when work crosses people or requires follow-up beyond personal reminders. A piece of work needs assignment or follow-up.
What should we bring to the requirements discussion?
Bring anonymised examples of Task descriptions; Owners and due dates; Project and dependency references. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.
Does this replace our existing business software?
The starting point is your current system and the gap you need to close. Give project work an owner, due date and visible status. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.
What is outside this module?
A completed status records the team's decision rather than independent proof that work meets a standard.
How are scope, price and rollout decided?
The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Open tasks have an owner. Use this check when reviewing the first working version.
Discuss task management for your business.
Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.
What happens after you share your requirements
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- Review the scope and commercial terms before deciding whether to proceed.
Start with your requirements
Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.
Share your requirements