Planning · Services
The right people on the right weeks, before Thursday.
This is the board.
The team's week, by person: who is on what, who is free, what is still unassigned, and where two things collide. Drag a block to fix it and the person has it on their phone.
By person, by project, by day.
By person
Who is doing what this week, and who has room.
By person, by project, by day.
Who is doing what this week, and who has room.
What a plan needs.
What an assignment is, and what counts as a conflict, is yours to define.
Assignments by drag
Place a person on a project, a visit or a shift; move it, split it, copy it to next week.
Open shifts
Leave a slot open, let the team claim it, and see who did.
Templates and recurring plans
The maintenance round, the weekly review, the on-call rota: planned once, repeated on schedule.
Capacity
Hours available against hours planned, per person and for the team, so the gap is a number.
Time off already on the board
Leave and public holidays come from Time Off, so a plan is never made on a day someone is not there.
Everyone has their week on their phone
Change the plan and the people affected know, without a message.
People on a timeline, whatever the work is.
What adapts: what an assignment is (a shift, a project block, a visit), what it is placed against (a role, a person, a project), what counts as a conflict, and what the plan is measured against afterwards.
A catering brigade
Assignments are shifts on events, placed by role first (chef, service, logistics) and by person second. A conflict is a person on two events, or a role unfilled 48 hours before service. The plan is measured against the event's staffing budget.
A consultancy
Assignments are weekly blocks on engagements, placed by person, in days. A conflict is a person over five days in a week or planned on leave. The plan is measured against the engagement's retainer and the person's utilisation target.
Planned hours beside logged hours.
The plan is what the timesheet is measured against. Planning puts 12 hours of Mathilde on the showroom refit this week; Timesheets says she logged 12.50. The project sees both, the margin reads from the second, and the planner sees where the next week's plan was wrong.
The conflict raises itself.
Two assignments on one person at one time. A visit planned on a day off. A project given fewer hours than its milestone needs. Each one is a rule, each one raises an alert on the board and on the phone of the person who can fix it, and none of them waits for Thursday.
The scheduling tool you would otherwise buy does not know what the work is.
People on a timeline
- A shared calendar
- Sort of
- A scheduling tool
- Yes
- A suite module
- Yes
- Enobase
- Yes, by person, project or day
What the work is
- A shared calendar
- A title
- A scheduling tool
- A title
- A suite module
- The project
- Enobase
- The project, the visit, the ticket, with their records
Conflicts caught
- A shared calendar
- No
- A scheduling tool
- Overlaps
- A suite module
- Overlaps
- Enobase
- Overlaps, days off, and hours short of a milestone
Time off already on the board
- A shared calendar
- No
- A scheduling tool
- If synced
- A suite module
- Yes
- Enobase
- Yes, from Time Off
Planned beside logged
- A shared calendar
- No
- A scheduling tool
- No
- A suite module
- Sometimes
- Enobase
- Yes, per person, per week
Everyone's week on their phone
- A shared calendar
- Yes
- A scheduling tool
- Yes
- A suite module
- Yes
- Enobase
- Yes, and the change notifies them
Time to live
- A shared calendar
- A day
- A scheduling tool
- A week
- A suite module
- Months
- Enobase
- One week
| What you need | A shared calendar | A scheduling tool | A suite module | Enobase |
|---|---|---|---|---|
| People on a timeline | Sort of | Yes | Yes | Yes, by person, project or day |
| What the work is | A title | A title | The project | The project, the visit, the ticket, with their records |
| Conflicts caught | No | Overlaps | Overlaps | Overlaps, days off, and hours short of a milestone |
| Time off already on the board | No | If synced | Yes | Yes, from Time Off |
| Planned beside logged | No | No | Sometimes | Yes, per person, per week |
| Everyone's week on their phone | Yes | Yes | Yes | Yes, and the change notifies them |
| Time to live | A day | A week | Months | One week |
Questions about Planning
Yes. On its own it is people on a timeline with conflicts caught. Connect Project and the blocks are projects with milestones; connect Timesheets and the plan is measured against what was logged.