An employee onboarding app for people operations teams. Add a new hire, start a reusable checklist, coordinate owners and due dates, and close onboarding when the required work is complete.

Firstday follows onboarding from a new hire’s details to a completed welcome. Choose a checklist when adding a person; the app creates their tasks with owners and due dates based on the start date. Use the overview to spot approaching starts and blockers, then open a person’s workspace to manage the work. Required tasks must be done before onboarding can be completed with a handover note. The pilot uses ToolJet Database and fictional records. Choose Deploy to ToolJet to start on Cloud, or download the application package for self-hosting. Follow the included README to import the app and load its fictional sample data.
Built for People operations teams and hiring managers coordinating HR, IT, and workplace preparation for office-based and remote employees.
Start a real onboarding record, work through its checklist, and keep the completion decision with the person.
Review upcoming starts, task readiness, overdue work, and blockers. The overview highlights the next three starters and a short blocker list; open People for the full directory.
Add the person’s name, work email, role, department, manager, location, and start date. Choose a reusable checklist to create their tasks once, with default owners and dates relative to their start.
Edit task owners, due dates, statuses, and notes. Update profile details, resolve required tasks, and record a completion note. Reopen onboarding with a reason when more work is needed; prior completion and reopening decisions stay in the history.
Create reusable checklists and add or edit their tasks, teams, default owners, due-date offsets, and required status. Changes apply to future hires without overwriting existing onboarding progress.
The overview brings approaching start dates and preparation into one view. Readiness is calculated from saved task statuses, while overdue tasks and blockers show where a coordinator needs to act.
Create a hire and their individual checklist together. A unique work email helps prevent duplicate onboarding records; manager-owned tasks use the manager entered for that hire.
Manage each task in the hire workspace with an owner, due date, status, and current note. Distinguish To do, In progress, Blocked, and Done, and update the plan as preparation moves forward.
Complete onboarding only after all required tasks are done and a completion note is entered. Completed records retain their checklist; reopening requires a reason and keeps previous lifecycle decisions in the history.
Maintain a checklist library for different working arrangements. Each hire keeps their own copy, so improving a recipe does not reset progress or change dates on existing records.
The pilot uses 2 tables with fictional records. No external database is needed to explore the source app.
| Table | Sample data | What it stores |
|---|---|---|
| Reusable checklists | 3 sample checklists | Named checklist recipes with task titles, teams, default owners, required flags, and due dates relative to a hire’s start date. |
| New hires | 6 sample hires | Profile and start details, an individual checklist, onboarding status, and completion or reopening history. The sample hires contain 33 tasks in total. |
This English desktop pilot tracks onboarding work; it does not provision accounts, send reminders, connect to an HRIS or payroll system, collect files, or capture signatures. Access policies have not been validated. Work email and start date are fixed after creating a hire; other profile details and individual task due dates can be edited. The overview shows a selection of upcoming people and blockers. Reads are capped at 1,000 hires and 1,000 checklists; larger deployments need server pagination. Package export and clean installation remain unverified.
This design is a starting point. Describe the look you want, add your logo and brand colors, or ask for new features in a prompt. Use the starter prompt to build your own version in the ToolJet AI builder, or use a suggested prompt to modify an app you already have. Review and test the result.
Suggested prompts describe changes you can request. Additional features and translations still need to be built and tested.
Choose ToolJet Cloud, or download the application package to import into your self-hosted instance. Unzip the download, import its application JSON, then follow its README to load the fictional sample data.
Explore the sample records in ToolJet Database, then add your records and configure the workflow for your team.
Describe your preferred design, branding, and new features in the AI builder. Test your workflow, then share your app with the people who need it.