From one-off requests to employee development plans

Form Builder supports both one-off requests and ongoing people processes. Common use cases include learning budget requests, salary change requests, onboarding plans, development plans, and performance improvement plans. If a process starts with collecting information, Form Builder can support it.

One-off forms capture a single request or decision, such as a learning budget request. Ongoing forms are designed for processes that evolve over time, like development plans or PIPs, where progress, updates, and collaboration matter beyond the initial submission.

Each form has clear ownership defined upfront. Form owners can oversee submissions, track progress, and manage approvals across the organization, while employees and managers see only what’s relevant to them.

Yes. You can set fine-grained permissions for visibility and editing. This ensures sensitive information is shared appropriately, while keeping the right people informed and involved.

Ongoing forms, such as development plans, connect directly to goals and learning paths. This keeps progress, growth, and skills development linked in one system. Additional module connections, including reviews, are planned.

Yes. Employees can start forms like development plans or requests on their own, within the structures defined by HR. This encourages ownership while keeping processes consistent and easy to manage.

Managers automatically see relevant submissions, updates, and progress tied to their team. They can review, comment, and approve directly in Leapsome, without chasing documents or switching tools.

Yes. Form Builder is designed to scale with your organization, supporting everything from simple requests to complex, long-running processes. As your people processes evolve, your forms can evolve with them — without rebuilding workflows from scratch.