--- title: "Workforce Assignment: A Practical Guide | Orangescrum" description: "How to decide who does which work: balance skill, availability, and growth instead of always picking the fastest person." canonical: https://www.orangescrum.com/optimization/workforce-assignment --- # Workforce Assignment: A Practical Guide | Orangescrum > For the complete documentation index, see [llms.txt](https://www.orangescrum.com/llms.txt). [Home](/) / [Planning techniques](/optimization) / Workforce assignment Planning technique # Workforce Assignment, _Explained Properly_ The best person for the job is usually the busiest person, and the only one who can do it. Here is how to assign work deliberately, and what Orangescrum shows you before you decide. [Start free trial](/sign-up?utm_source=site&utm_medium=technique&utm_campaign=optimization_workforce-assignment) [See all features](/features) ## What is workforce assignment? Workforce assignment means deciding which person does which piece of work. Done well it balances three things that pull against each other: who has the skill to do it, who has the time to do it, and who would grow from doing it. Most teams optimise only the first, which is exactly why the best person for a job is also the busiest and remains the only one who can do it. Deliberate assignment spreads capability on purpose, accepting slightly slower delivery now in exchange for a team with fewer single points of failure later. It is a management judgement informed by data, not a matching problem with a correct answer. ## Where assignment _quietly creates risk_ - **The expert is given everything**Each task goes to whoever is fastest at it, so one person accumulates the queue, becomes the bottleneck, and turns into the single largest delivery risk in the team. - **Assignment happens in a stand-up and is never revisited**Names are attached to work in a two minute conversation and stay attached for weeks, long after the workload behind them has changed completely. - **Nobody has a record of who can do what**Skills live in a manager's memory, so assignment is limited to the people they happen to think of, and quieter team members are never considered. - **Availability is assumed rather than checked**Work is given to someone who is on approved leave next week or already committed to another project. The task looks assigned and nothing happens to it. ## What Orangescrum _actually gives you_ Real features, named. Nothing here is an algorithm that decides for you. [**Record what people can actually do**Skills held against people mean assignment considers everyone with the capability, not only the two names that come to mind in the meeting._Skills_](/resource-management)[**Check availability before you choose a name**Availability and allocation show how much of a person is genuinely free in the period, so the assignment is made against reality rather than against hope._Resource management_](/resource-management)[**See the load before you add to it**The workload heat map shows who is already at or beyond capacity, which is the difference between assigning work and simply lengthening somebody's queue._Workload heat map_](/workload-management-software)[**Know when leave will get in the way**In Self-Hosted, attendance and approved leave feed the capacity you assign against, so nobody is given work through a holiday that was signed off weeks ago. Self-Hosted only._Attendance and leave_](/attendance-leave-management)[**Make the assignment visible to everyone**A board shows who holds what right now, so an uneven distribution is obvious to the whole team rather than known only to the person carrying it._Kanban board_](/kanban-board)[**Learn what the assignment actually cost**Time logged against the work shows whether the person took the effort you assumed. That is how the next assignment and the next estimate both improve._Time tracking_](/time-tracking) ## How to _assign work deliberately_ 1. **Write down the skills you actually schedule around**Not a full competency framework. The handful of capabilities that decide who can take a piece of work, recorded where the planning happens. 2. **Check availability before you pick a name**Look at what the person is already committed to across every project. An assignment made without that check is a guess with somebody's name on it. 3. **Assign for capability growth, not only for speed**Some of the time, deliberately give work to the second best person with the best person supporting them. That is how a second person becomes able to do it. 4. **Look at the workload view after assigning, not before**Individually reasonable assignments add up to an over-allocated person. The total only becomes visible once every assignment for the period is in. 5. **Review the pattern every few weeks**Ask who is receiving the interesting work and who is receiving the queue. Assignment patterns compound quietly, and by the time they are complained about they are entrenched. ## What Orangescrum does not do here Orangescrum does not assign work for you. There is no matching engine that reads a skill profile, compares it with a task, and picks a person, and there is no automatic assignment of any kind in any edition. What it does is put the information a manager needs in one place: who has which skills, who is available, who is already over-allocated, and what similar work has cost before. The decision stays with a person, which is right, because assignment is as much about growth, fairness, and risk as it is about finding the fastest match. Resource management, skills, and the workload heat map are on the Cloud Premium plan and included in Self-Hosted. Attendance and leave feeding capacity is Self-Hosted only. ## Workforce assignment FAQ Does Orangescrum automatically assign tasks by skill match? No. There is no skill matching engine and no automatic assignment in any edition. Skills, availability, and current workload are visible in one place, and a person decides. Assignment involves judgements about growth and risk that no matching rule would make well. Where are skills recorded? Against people in resource management, alongside their availability and allocation. Keeping them there rather than in a separate document is the point, because they are only useful at the moment somebody is deciding who takes a piece of work. How do I stop one person becoming the bottleneck? Look at the workload heat map for the person consistently at the top, then deliberately assign some of their work elsewhere with them supporting rather than doing. It costs time in the short term and removes a single point of failure permanently. Should I always assign the fastest person? No. Doing so is right for an urgent piece of work and wrong as a habit, because it concentrates capability and creates the bottleneck you will complain about in six months. Mix in assignments that build a second capable person. How do I account for leave when assigning? In Self-Hosted, attendance and approved leave feed the capacity you assign against, so it is handled for you. On Cloud, keep leave on the project calendar and check it before committing a name to dated work. Which plan or edition do I need for this? Resource management, including skills and availability, and the workload heat map are on the Cloud Premium plan and included in Self-Hosted. The Kanban board and the project calendar are in all three editions. Attendance and leave feeding capacity is Self-Hosted only. How often should assignments be reviewed? At least every sprint or every fortnight. Workload changes underneath an assignment that was sensible when it was made, and nothing tells you it has stopped being sensible except looking. Is this the same as resource-constrained scheduling? They are close but answer different questions. Workforce assignment is about who does a piece of work. Resource-constrained scheduling is about when work can happen given how little of those people you have. Most teams need both, and they use the same underlying capacity picture. ## Decide with the facts in front of you Free 14 day trial, no credit card. Every plan includes unlimited users. [Start free trial](/sign-up?utm_source=site&utm_medium=technique_cta&utm_campaign=optimization_workforce-assignment) ## Related [**Resource management**Skills, availability, allocation](/resource-management)[**Workload management**Who is already over-committed](/workload-management-software)[**Resource-constrained scheduling**Planning around limited people](/optimization/resource-constrained-scheduling)[**Multi-project scheduling**Several projects, one team](/optimization/multi-project-scheduling)