Navigating the Thulasi Confirmation Process for Kerala PSC Employees
The confirmation process through the Thulasi portal has been a recurring headache for temporary employees across Kerala's government departments. I've watched people waste weeks trying to figure out where to click and what order to do things in. Let me walk through how it actually works in practice, not just what the circulars say. First, you need to understand that Thulasi (Transaction based Unified Labour And Social Insurance) is Kerala's centralized personnel management system. It handles everything from attendance to promotion to confirmation. For temporary staff who've completed their probation period, the confirmation workflow runs entirely through this portal now. There's no paper file moving between offices anymore. That alone has reduced processing time significantly, though the portal itself can be unreliable at times.
Kerala Psc Thulasi Confirmation
Here's the actual step-by-step process. You start by logging into the Thulasi portal using your employee ID and password. If you've never changed your password from the default, do that immediately after logging in. The system will flag you to change it anyway, but don't wait for the reminder. Once you're in, navigate to the "Service Book" or "Confirmation" module depending on your department's configuration. Your department's administrative officer should have already initiated the confirmation proposal. If they haven't, that's your first problem to solve. After the AO initiates the proposal, it moves to the next level - usually the Head of Department or their designated authority. This is where most people get stuck. The proposal sits in the approver's pending queue until they take action. I've seen files linger there for three to four months because the concerned officer was transferred, didn't know about the new system, or simply forgot. The workaround I used was to physically visit the department office with a printed copy of my service details and politely ask someone to check the Thulasi portal for pending items. Sometimes just reminding them that the file exists there instead of on a desk makes a difference. Once approved at the HoD level, the file goes to the Finance Department for verification. This step checks that all financial formalities are in order - that you've completed the required service period, that there are no outstanding disciplinary cases, and that the pay fixation has been properly calculated. The finance verification usually takes two to three weeks if everything is clean. I learned the hard way that any discrepancy in your pay fixation history can send the file bouncing back, adding another month or two to the process.
After finance clearance, the final approval comes from the competent authority, typically the Secretary of the concerned department or the Principal Secretary. This is usually a formality if everything else is in order, but again, portal delays happen. The system occasionally shows the file as "approved" when it's actually still in the approval queue. I always recommend printing or screenshotting the approval status page and keeping a record. Portal data can sometimes show inconsistent information during peak usage hours, especially during the annual review season when thousands of employees are processed simultaneously. There are a few things the official guides don't mention. Your service certificate and probation completion certificate must be uploaded before the confirmation proposal can move forward. Some departments skip this requirement initially and only flag it later, causing unnecessary delays. Make sure these documents are in your Thulasi profile from day one of your temporary service, not just when confirmation is due. Another counter-intuitive issue: if you've been transferred between departments during your probationary period, the confirmation proposal needs to be coordinated between both departments. The originating department initiates it, but the current department must acknowledge and process it. I had a case where the file got stuck because the receiving department hadn't updated your department code in their system, and the proposal was technically bouncing between two different departmental hierarchies. The fix was getting both departmental IT coordinators to verify your service history was correctly merged in the central database. That took about two weeks of back-and-forth emails.
Get the Full Details
The portal has genuine limitations. It's slow during office hours because of low server capacity relative to the volume of users. Processing confirmation files between 10 AM and 4 PM on weekdays can feel like watching paint dry. The system tends to be more responsive early morning or late evening. Also, the mobile version is essentially useless for this process. You need a desktop or laptop with a reasonably modern browser. Firefox and Chrome work best. The portal sometimes misbehaves with Safari, so avoid using it on a Mac if you can help it. If you're facing prolonged delays and the standard follow-up approach isn't working, you can file a grievance through the Thulasi grievance redressal module. It's not a fast track by any means, but it does create a documented trail that higher authorities can see. I've used this twice, and while it didn't dramatically speed things up, it did prevent my file from being completely ignored in the queue. The entire process, assuming no complications, should take about six to eight weeks from initiation to final approval. In practice, with the typical delays from approvers sitting on pending files and the occasional portal glitch, budget ten to twelve weeks. If it's taking longer than that, something is wrong and you should investigate rather than just waiting.
For downloading any related circulars or notifications, the official Thulasi portal hosts all the relevant government orders under the "Notifications" section. The Kerala PSC website also publishes updates related to confirmation policies. Keep both bookmarks handy because sometimes the department-specific instructions differ slightly from the general policy.
