Role design and job descriptions for Technical Textile Makers: engineers, lab technicians and operators
Process knowledge sits with a few engineers and release decisions with junior lab staff. Clear roles say who sets, who tests and who can hold a roll.
Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsWhy role design and job descriptions matters in technical textile makers
The person who tunes a coating recipe is also the person everyone calls when a roll fails. Lab technicians pass or hold costly rolls but are unsure whether they can push back on a senior. Operators on one line cannot help on another because no one wrote down the tasks. Specifications are read differently by each shift, and a rejection comes with no stated reason.
Role design starts with what must be decided: setting a recipe, approving a change, releasing a roll, reading a specification. For each, name who decides, who advises and who records. Job descriptions then list the line tasks, settings the person may change, tests he performs and when he must stop and call someone. Written once and reviewed with the people in the roles, they become the base for training and pay.
How to set it up
1. List the decisions that matter
Recipe change, line setting change, specification reading, roll release, customer complaint reply. Write down who makes each call today.
2. Write release authority clearly
State who may release or hold a roll, what test results trigger a hold and who can overrule. Tell the lab staff they are expected to hold when results fail.
3. Describe each line role in plain terms
Coating operator, stenter operator, lamination operator, lab technician, process engineer. List tasks, adjustable settings, tests and stop points.
4. Record recipes and why settings work
Ask the process engineers to note the recipe, the range and the reason for each setting. Keep it with the line so others can learn from it.
5. Review the roles with the people in them
Walk each description with the person, fix what is wrong and sign it. Use the result for training and pay. See organisation design.
Check these first
Before changing anything, find out what is true today. These take an afternoon and use your own records.
- Ask three shifts how they read the same customer specification.
- Check who actually decided on the last held roll and whether the lab felt free to hold it.
- List which line settings only one person knows.
- Count operators who have run more than one line.
GullyHR can do this with you. Read how we approach role design and job descriptions in general, or share your requirements and we will tell you where to start.
Questions owners ask
Detailed enough to show tasks, decisions and stop points, but short enough that people read it. One page for most roles works well.
State in writing that holding on a failed test is expected, and back them when a manager pushes. Review each hold as a learning point, not a blame exercise.
They should set and teach, not run it all day. If an engineer is stuck on routine running, nobody else learns the recipes and every new order waits for him.