1. Calendar system. Google Workspace or Microsoft 365? This changes the invite implementation, not just a setting, so we need it before build starts.
2. Interview rounds. What are the actual rounds per role family, and who sits on each panel?
3. Retention periods. Do the durations on the archival slide match Eskay's policy? Is there any statutory retention already followed?
4. Referral bonus numbers. The programme is in scope. We need the actual amounts per grade, the milestone split, and the retention period before the second instalment. Our placeholder is 40 percent on joining and 60 percent after six months.
5. Master data. We need the list of departments, locations and designations.
6. Is CTC shown on public job posts? Our recommendation is no, with the band held internally.
7. WhatsApp in phase 1? Read rates are far better than email in India, but it changes the notification design and needs template approval.
8. Who signs off a rejection? Recruiter alone, or HR Manager countersign?
9. Walk-in applicants. Does HR key them in, or do we need a kiosk mode at the gate?
10. Volume. Applications per month today, and how many roles are open at once?
11. Sensitive fields on Annexure I. Blood group, height and weight, and spouse, children and parent details are personal data of people who are not applying. Our recommendation is to collect these after an offer is accepted rather than from every interviewee. Confirm which you want at which stage.
12. Change control on the forms. Annexure I is a controlled format under SOP PAS/010. Who approves a change to the digital version, and does it need a format revision number each time?
13. Group companies. Which entities take part, and in what way? Referring only, or do their vacancies appear on the careers site too? We also need the name of the entity that legally holds candidate data, and confirmation that the hiring company's bonus policy applies rather than the referrer's.
14. Job board subscriptions. What does Eskay pay for today on Naukri, LinkedIn or Indeed, and can we have API credentials? The job feed and tracked links ship at launch either way, so posting works from day one. The API only removes the manual paste.
15. Spine HRMS integration. pravESKAY ends where Spine begins. We want to read your employee master from Spine so nobody maintains a second list, and to push the selected candidate across with the Annexure I data and offer breakup so onboarding starts from clean data. We need to know which Spine modules you run, and what Spine exposes for integration.

Workflow approval signature

By signing below, the undersigned confirm that the workflow described in this walkthrough is a true representation of the hiring process to be supported, and that the proposed roles, permissions, candidate communication, retention policy and reports are acceptable. Items listed on slide 20 remain open and will be confirmed separately.