Plan project staffing with a weekly capacity grid, skill-specific requests, tentative bookings, leave and allocation changes.

Roster connects project demand to a shared people directory. Create a project, request a skill for a particular week and assign a person with matching skills and enough available hours. Confirmed and tentative bookings both reserve capacity; recorded leave reduces the available total. Change or release allocations with a rationale, and close a project after its requests and bookings are released. The opening view shows the next four weeks for the first six people, while the directories and registers expose the bounded dataset.
Built for Resource managers, delivery leads and operations teams in agencies, consultancies and IT services.
Plan project staffing with a weekly capacity grid, skill-specific requests, tentative bookings, leave and allocation changes.
Review weekly staffing pressure and unfilled demand.
Create or open a project with an accountable delivery lead.
Request skills, assign available people, then change or release weekly bookings.
Add people and record weekly leave before allocating their time.
Compare booked and available hours by person and week. The grid includes tentative bookings and subtracts recorded leave, so overlapping project commitments stay visible.
Create an owned project, then request a work package, required skill, week and number of hours. Unfilled requests remain separate from reserved capacity.
Assign only when the selected skill matches and weekly capacity permits it. Change a booking or release it with a rationale; release all work before closing a project.
Maintain people, comma-separated skills and baseline weekly capacity. Record one leave entry per person per week and use the grid to identify allocations affected by reduced availability.
The pilot uses 2 tables with fictional records. No external database is needed to explore the source app.
| Table | Sample data | What it stores |
|---|---|---|
| People & availability | 6 sample directory entries | Fictional person records providing ownership and planning context. |
| Staffing projects | 4 sample records | Fictional project records with linked work items, decisions and activity history. |
English desktop pilot. The outlook shows the next four weeks and first six people; registers read up to 1,000 rows per table. Capacity checks use loaded project records and are not a transactional lock across simultaneous planners. Skills use exact comma-separated labels. Leave entries are additive with one entry per person/week; editing or cancelling leave and recurring holidays are not implemented. No timesheets, payroll, calendar integration or notifications.
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 once the template is released.
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.
It compares the requested weekly hours with the person’s baseline capacity minus leave and existing tentative or confirmed bookings. The check uses loaded records; it does not provide transactional locking across simultaneous planners.
Yes. Tentative bookings reserve capacity just like confirmed bookings. Change or release the allocation when the staffing decision changes.
A staffing request specifies a skill, which must match one of the comma-separated skills in the selected person’s record.
No. This template covers staffing requests, planned weekly allocations and recorded leave. Timesheets, payroll and calendar synchronization need additional implementation.
Yes. Use the starter prompt as a starting point, or describe changes to an app in the ToolJet AI builder. Ask for your branding, a different layout or extra workflow features, then review and test the generated changes.