Most people who start researching shift management systems have just finished evaluating an attendance management system. Yet even after clock-in records and payroll calculation are automated, one task stays exactly where it always was: building next month’s roster, still sitting on the desk of one particular line leader. The two systems sound alike, but they solve different problems. This article sets out why the shift side is so often left untouched at Japanese-owned plants in Thailand, and why that situation carries a production-stoppage risk inside it.
Why an attendance management system alone is not enough
Recording what happened and designing what will happen are two different mechanisms
An attendance management system deals with facts that have already occurred. Who entered the site at what time, when they left, and how many of those hours were overtime. It gathers the records and calculates wages in line with the law and the work rules. Its purpose is accurate payment and a record you can defend to the labour authorities and to your own employees. In terms of the flow of time, all of it is after the fact.
A shift management system deals with facts that have not happened yet. Who goes on the night shift on Line A in the second week of next month. Whether there are enough certified welders for a process that requires two of them. If one operator has already used up their overtime allowance for the week, who can be put in instead. This side is design work, done in advance.
Because both draw on the same employee master data, they look like the same mechanism from the outside. But what comes out of them is completely different.
| Point of comparison | Attendance management system | Shift management system |
|---|---|---|
| Point in time it handles | After the fact. Records what was actually worked | Before the fact. Builds the plan for work to come |
| Central question | How much do we pay, and is the calculation compliant | Who goes where and when, and will that staffing hold |
| Primary users | General affairs, HR, payroll staff | Manufacturing managers, line leaders, floor supervisors |
| Primary outputs | Attendance summaries, payroll data, statutory forms | Rosters, staffing charts, surplus and shortage lists |
| Information needed to decide | Clock records, leave requests, approval records | Skills held, certification expiry dates, individual consent and preferences, remaining statutory allowance |
| What happens when it fails | Miscalculated wages, correction orders, loss of employee trust | The line does not start, uncertified people are assigned, statutory limits are exceeded |
The bottom row of that table is where this article begins. A failure in attendance management shows up as a money and trust problem, but a failure in shift management shows up as production itself stopping. Despite that, the one more likely to reach the investment decision table is the former. Reducing payroll workload is easy to express in money, while the burden of roster building gets absorbed into the phrase “the line leader is working hard on it.”
The selection criteria for the attendance side are covered separately in how to choose an attendance management system for a Thai factory. This article is the sequel, dealing with the shift-side problem that plants face once attendance is in place.
Thai labour law requires decisions to be made in advance
The idea that shift work is design done in advance becomes far more concrete once you read the Thai Labour Protection Act. According to a commentary on Thai labour law published by GVA Law Office, working hours for ordinary work are capped at 8 hours a day and 48 hours a week, while hazardous work such as underground work, work involving radiation, metal welding and the transport of dangerous materials carries a shorter cap of 7 hours a day and 42 hours a week.
If it were only a matter of hourly ceilings, an after-the-fact tally would be enough to check compliance. The difficulty lies beyond that. The same commentary states that the combined total of overtime, holiday work and overtime on a holiday must in principle not exceed 36 hours per week. It further explains that overtime and holiday work require the individual consent of the employee on each occasion, and that a blanket provision written into the work rules is not sufficient. On rest periods, it states that employees may not work more than five consecutive hours without a break of at least one hour, and that a break of at least 20 minutes must be given before overtime exceeding two hours.
Every one of these conditions can only be met if it is built into the roster at the point the roster is drawn up. Discovering after the fact that “the week came to more than 36 hours” does not undo the fact. Individual consent is the same: distributing a shift table does not automatically establish consent, so you need to manage who consented to what alongside the staffing plan itself.
In other words, the structure of Thai law positions roster building not as a piece of shop-floor logistics but as an upstream process of compliance. If that upstream process exists only inside one person’s head, then your compliance mechanism depends on one person’s memory.
Regulatory demands are increasing as well
The legislation is moving too. The 9th amendment to the Labour Protection Act, published in the Royal Gazette on 7 November 2025 and effective from 7 December 2025, introduced a new obligation for companies employing 10 or more people to submit a disclosure document covering employment conditions and the working environment to the Director-General of the Department of Labour Protection and Welfare during January each year. The same amendment expanded maternity leave to a maximum of 120 days, of which 60 days are paid in full by the employer and up to 60 days are covered by social security at 50 percent of wages. Spousal parental leave of up to 15 days at full pay was also newly created.
From a shift management standpoint, the expansion of leave entitlements is what bites. Once 120 days of maternity leave and 15 days of spousal parental leave exist as entitlements, staffing plans have to be built on the assumption that they will actually be taken. Long absences were of course happening before, but once they are stated explicitly as a right, the question becomes whether your staffing is designed with those absences built in. Working out how to cover a long-term absence is exactly the kind of task manual work in a spreadsheet is worst at.
Roster building as a single-person dependency, and the BCP risk it creates
Only the person who built the spreadsheet can fix it
The tool used for roster building at Japanese-owned plants in Thailand is, almost without exception, a spreadsheet. There is nothing wrong with that in itself. The problem is that the spreadsheet grows more complex year by year.
Once you try to make roster building more efficient in a spreadsheet, there comes a point where formulas alone are not enough and you reach for automatic assignment through macros. A guide to shift-creation tools notes that in workplaces with large headcounts and a mix of early, late and night shifts, manual entry simply cannot keep up. What follows next, ending up in a state where only the person who wrote the complex formulas and macros can modify them, is a development you see on the shop floor again and again. A commentary on workforce allocation in factories also flags the risk that because the task requires experience and judgement, it becomes concentrated in one individual, handover becomes difficult and the checking function stops working. Filling 24 hours of coverage without gaps is itself a personnel puzzle that weighs heavily on the manager, and the very ingenuity applied to lighten that load ends up creating a dependency no one else can substitute for.
What actually happens on site looks like this. Someone is suddenly absent during the week the roster builder is on leave, and no one can amend the shift table. A macro stops with an error and there is no one in the company who can trace the cause. The roster builder gives notice, but the handover requires them personally to write up a procedure manual, and that work can only be squeezed between their normal duties.
In every case, it is not a system failure but the absence of a person that halts the production plan. Business continuity documents cover natural disasters, power outages and supply chain disruption, but “no one is left who can build the roster” is almost never written down. In terms of probability of occurrence, the latter is far more likely.
Three shifts and 24-hour operation make a puzzle that is hard to fill
Shift management in a factory is difficult not simply because there are many cells to fill. It is difficult because there are many kinds of constraint.
A commentary on factory shift management identifies three problem areas: a mix of employment types, the burden of clock-record management, and compliance risk. For system selection it sets out three criteria: fit with the industry and company size, flexibility for working patterns such as three-shift and 24-hour operation, and cost efficiency. Applied to a plant in Thailand, that mix of employment types runs thicker than it does in Japan. Permanent staff, contract staff, dispatched workers, outsourced contractors and short-term personnel on trainee-style arrangements all stand on the same line, each with different applicable rules and different rates.
On top of that comes the shift rotation cycle. When you rotate morning, day and night shifts on a fixed cycle, the interval since the last shift worked, the number of consecutive working days, the distribution of night shifts and the fairness of days off all apply at once. When a person builds this by hand, it inevitably settles into “the usual combination.” That is not a bad choice in itself, but it carries a side effect: the people outside the usual combination never accumulate skills.
The skills matrix exists but is not being used for staffing
Most Japanese-owned plants already have a skills matrix. It was put together to satisfy the competence management requirements of ISO 9001, or of FSSC 22000 for food-sector plants, and it is updated at every audit.
Yet it is startling how rarely that skills matrix is opened at the point where the shift table is being built. A commentary on workforce allocation in manufacturing raises exactly this issue: skill information is maintained as documentation for audits, but is not put to use in the actual allocation work. The same commentary presents a case in which the time spent on allocation work fell from seven hours a week to one hour. That is published as the result at one company that adopted a particular tool, and it should not be read as the outcome any plant would get. But it is also the flip side of how many plants have no connection between staffing and skill information.
Why does it go unused? The reason is simple: the format does not match. A skills matrix is built as a two-dimensional people-by-skill table, which is the ideal shape for presenting at an audit. What the shift table needs is an axis of date by time slot by process, plus a reverse lookup that answers “who with the skills this process requires is free today.” Performing that reverse lookup daily from a two-dimensional table on paper or in a spreadsheet is not realistic, so the line leader falls back on memory.
What is wrong with relying on memory? First, memory cannot be shared. Second, memory does not get updated. An operator who obtained a certification three months ago can go on being treated indefinitely as “someone we cannot let work alone yet.” Third, memory cannot be verified. When an auditor asks why this person was assigned to this process, there is no evidence to show.
If the skills matrix and staffing are connected, all three are solved at once. Put the other way round, the first thing to check when evaluating a shift management system is whether your own skills matrix can be brought in as data as it stands.
The supply of foreign workers is a variable specific to Thailand
A single-person dependency in roster building becomes especially dangerous when the assumptions about your workforce shift suddenly. Manufacturing in Thailand has lived through exactly that.
According to a report carried by Bangkok Shuho dated 5 June 2026, the Joint Standing Committee on Commerce, Industry and Banking (JSCCIB) stated that the shortage of foreign workers was becoming severe. The number of Cambodian workers, which at one point stood at around 550,000, had fallen sharply to approximately 194,000, with friction stemming from the border issue cited as the main cause. Construction, manufacturing, agriculture, food processing and services were named as the affected sectors. At the same time, JSCCIB left its 2026 GDP growth forecast unchanged at 1.2 to 1.6 percent.
Setting the scale of the numbers aside, the practical implication is clear. A situation in which one nationality of worker leaves the workforce as a bloc is not a hypothetical in Thailand. And what the shop floor then faces is not simply a shortage of headcount. It is a staffing problem: where do you find the skills for the processes those workers were covering.
This is the point at which the price of a single-person dependency in roster building surfaces all at once. When the knowledge of who can work which process sits only inside one head, you cannot spread the redesign of your workforce structure across the team. And the one person who ought to lead that redesign already has their hands full with the ordinary monthly roster.
Treat the dependency as a line item in your BCP review
Taking all of the above together, single-person dependency in roster building can be set out as the following risks.
| Risk event | What stops when it occurs | Difference if the dependency has been removed |
|---|---|---|
| Sudden illness or abrupt resignation of the roster builder | Roster building from the following month onward. For a while you get by copying last month’s | If allocation rules exist as data, another manager can continue on the same basis |
| Unexpected absence | Deciding on a same-day replacement. With no clear criteria, it is easy to misjudge and assign someone uncertified | Candidates meeting the required skills can be filtered by condition |
| Sudden change in workforce composition | Redesign of the staffing plan for each process | Shortfall processes can be identified from the distribution of skills actually held |
| Explaining the basis of an assignment at an audit | Workload for corrective action | The link between assignment history and skill information remains on record |
| Breach of a statutory limit | Response to a correction order, recalculation of wages | Exceeding a limit can be detected at the point the roster is built |
Set this table against your own business continuity documents and you will probably notice that at many sites the first row is missing. It is not unusual to find a plant that has invested in equipment redundancy but not in redundancy for the person who builds the roster.
A model cost-benefit calculation
Stating up front that this is an assumption-based model
The calculation set out below is a hypothetical model constructed for this article, based on a Japanese-owned plant in Thailand. It is not the actual performance of any real company, and both the costs and the benefits are figures set as assumptions. When applying it to your own decision, always recalculate using your own headcount and labour rates.
The assumptions of the model are as follows.
| Assumption | Value set |
|---|---|
| Location and business type | A Japanese-owned assembly plant in an industrial estate in eastern Thailand |
| Headcount | 520 employees, of whom 430 are direct workers covered by the roster |
| Operating pattern | 5 lines, 24-hour operation on three shifts |
| Roster builders | 5 people in total, being 1 manufacturing section manager and 4 line leaders |
| Current build workload | 7 hours per week per builder, including adjustments and rework |
| Manager hourly rate | 350 THB, assumed to include employer social security contributions |
| Average overtime rate | 90 THB, set as an average after premium |
The setting of 7 hours per week for build workload borrows the pre-adoption level presented in the commentary on workforce allocation in manufacturing cited earlier, using it as the starting point for this model. In the original source that figure covers allocation work for the whole site, whereas this model restates it as workload per individual builder. If you have your own measured figure, use that instead.
Build the costs up in layers
The cost of a shift management system looks small when you look only at the licence fee, and suddenly looks large once internal workload is included. Building it up in layers produces a calculation that is harder to chip away at afterwards.
| Cost layer | Content | One-time cost (THB) | Recurring cost (annual THB) |
|---|---|---|---|
| Layer 1 Licence | For 430 people covered by the roster, set at 45 THB per person per month | 0 | 232,200 |
| Layer 2 Initial setup and rule design support | Vendor implementation support. Configuring shift patterns and constraints | 450,000 | 0 |
| Layer 3 Internal workload for master data | Digitising the skills matrix, writing allocation rules down explicitly. 800 hours in total | 280,000 | 0 |
| Layer 4 Training and parallel running | Training for line leaders and supervisors, plus the extra workload of running alongside the old method | 120,000 | 0 |
| Layer 5 Internal workload for ongoing operation | Master data updates, rule revisions. Roughly 24 hours per month | 0 | 100,800 |
| Total | 850,000 | 333,000 |
The first-year total comes to 1,183,000 THB, combining the one-time cost of 850,000 THB with the recurring cost of 333,000 THB. From the second year onward it is 333,000 THB.
Of these five layers, the one most often underestimated internally is Layer 3. Digitising the skills matrix and writing allocation rules down explicitly are not tasks a vendor will do on your behalf. Conditions such as “this process requires at least one certified operator” or “no day shift the day after a night shift ends” can only be put into words by someone inside the company. Push an approval through without this in the estimate and you will run out of capacity partway through the project, with the load ultimately falling back on the original roster builder.
Look at the benefits in three separate streams
On the benefit side too, the discussion holds up better if you avoid mixing things of different natures.
| Benefit | Basis of calculation | Annual value in the standard case (THB) |
|---|---|---|
| Benefit 1 Reduction in build workload | Working time for the 5 builders falls from 7 hours to 2 hours per week. 5 hours saved x 5 people x 52 weeks x 350 THB | 455,000 |
| Benefit 2 Reduction in overtime from emergency absence cover | Emergency overtime caused by absences falls from 200 hours to 140 hours per month. 60 hours x 12 months x 90 THB | 64,800 |
| Benefit 3 Fewer reworks and slow line starts caused by skill mismatch | Set conservatively at the equivalent of 150,000 THB per year | 150,000 |
| Total | 669,800 |
On the size of the reduction in Benefit 1, a vendor commentary on automatic roster creation using AI reports that users of a tool called HRBEST achieved an average 77.5 percent reduction in roster creation time. That is a figure published by the tool’s provider, and there is no guarantee your own plant would see the same reduction rate. This model sets the standard case at a move from 7 hours to 2 hours per week, a reduction of roughly 71 percent, and places a more conservative level and a level closer to the published case alongside it as separate scenarios.
One point worth checking in advance is whether the argument still holds if the portion corresponding to Benefit 3 is set to zero. That benefit assumes that skill information is reflected in staffing decisions, and it does not arise simply from installing a system. It only materialises once digitising the skills matrix, which is Layer 3, has been carried through. If you book the cost of Layer 3 while dropping Benefit 3, the investment case no longer stands up.
Compare payback periods across three scenarios
Varying the benefit estimate across three levels, the payback periods compare as follows.
| Scenario | How the benefits are set | Annual benefit (THB) | Recurring cost (THB) | Net annual gain (THB) | Simple payback period |
|---|---|---|---|---|---|
| A Pessimistic | Build workload falls only from 7 hours to 4.5 hours per week, and Benefits 2 and 3 are not counted | 227,500 | 333,000 | Minus 105,500 | Never pays back |
| B Standard | Reduced to 2 hours per week. Benefits 2 and 3 counted as in the table above | 669,800 | 333,000 | 336,800 | About 2.5 years |
| C Favourable | Reduced to 1 hour per week. Benefit 2 saves 80 hours per month, Benefit 3 is 300,000 THB per year | 932,400 | 333,000 | 599,400 | About 1.4 years |
The simple payback period is the one-time cost of 850,000 THB divided by the net annual gain.
The most important column in this table is neither B nor C. It is A. If you justify a shift management system on the reduction in build workload alone, and that reduction then only goes halfway, the investment is never recovered. Tell the approvers only that “roster building will get easier” and they will naturally picture the world of column A.
What makes the payback work is Benefits 2 and 3, which is to say the quality of absence cover and the accuracy of staffing. And both of those only arise once skill information is connected to staffing decisions. The case for the investment should therefore be framed not as “building the roster gets easier” but as “the basis for staffing decisions stays with the organisation, and anyone can build to the same standard.” That framing matches both the reality and the structure of the return.
Keep the benefits you do not quantify explicitly on the page
There are two benefits not included in the model above. One is the reduction in risk from preventing breaches of statutory limits before they happen. The other is continuity when the roster builder is unavailable. Both could be converted into money if you wanted to, but the assumed probability of occurrence would drive the conclusion, so they have been left out of this model deliberately.
Having left them out, it is worth writing them into the approval document in a separate section. Two lines such as “not included in the payback calculation, but breaches of the 36-hour weekly limit can be detected in advance” and “next month’s roster can still be built when the usual builder is away” often land better precisely because they are not converted into numbers.
How to run selection and implementation
Narrow the selection criteria to five
There are a great many shift management products, and comparing them through feature lists produces no separation. The commentary on factory shift management also gives three selection criteria: fit with industry and company size, flexibility for working patterns, and cost efficiency. Add the conditions of a Japanese-owned plant in Thailand and narrowing to the following five is the practical approach.
| Selection criterion | Question to put to the vendor | How to go beyond a simple “yes we can” |
|---|---|---|
| Flexibility for shift rotation | Can our own three-shift patterns, cycles and shifts spanning midnight be configured as they are | Hand over a real roster and have them reproduce it in the configuration screen |
| Expressiveness of constraints | Can limits on consecutive working days, the handling of the day after a night shift, and the 36-hour weekly allowance be held as conditions | List five of your own constraints and have them demonstrate how far each can be expressed in configuration |
| Integration with skill information | Can our existing skills matrix be imported, and can candidates be filtered by the skills each process requires | Hand over a sample of your own skills matrix and have them import it |
| Connection to the attendance system | Can a finalised roster be passed to the attendance side and variances against actuals fed back | Have them explain the integration method and the reconciliation procedure when variances arise |
| Multilingual support and shop-floor usability | Does it support display in Thai. Can line leaders make corrections on a shop-floor terminal | Let shop-floor staff use it and see how far they get with no training |
The second and third are where products separate most. Plenty of products will build a roster, but few go as far as holding constraints and filtering candidates by skill information. And that is precisely the functionality that carried the payback in this article’s calculation.
Split implementation into five stages
As a sequence, the following approach is standard.
- Stage 1 Understand the current state. Take stock of the existing spreadsheet and the decision rules buried inside it. Allow one to two months here
- Stage 2 Write the rules down. Set out the constraints in plain sentences and identify the points where line leaders interpret them differently
- Stage 3 Digitise the skills matrix. Restructure the audit list into a form mapped to the skills each process requires
- Stage 4 Pilot. Limit it to one line and actually build and run at least two months of rosters
- Stage 5 Full rollout. Reflect the exceptions found in the pilot before widening the scope
Skip Stage 2 and go straight to product selection, and you end up deciding requirements while watching vendor demos, which tends to mean fitting your own rules to the product’s features. Do Stage 2 carefully, on the other hand, and its output on its own works as a cure for the dependency. Put at its strongest, once you have managed to write out every constraint, half the risk is gone before any system is installed.
Reorganising the skills matrix in Stage 3 is most efficient when timed to coincide with the competence management update cycle for ISO 9001 or FSSC 22000. At the point you are reviewing the list for the audit, finish the mapping to processes at the same time. Avoiding a state where you maintain one version for audits and another for staffing is what determines your long-term operating load.
Who runs the project
The hardest part at a Thai site is securing the people to run these five stages. General affairs and HR already have their hands full with attendance and payroll, and the manufacturing managers are absorbed in daily production. And plenty of companies have no dedicated IT staff at the site at all.
A realistic answer, in our view, is a structure where manufacturing leads Stages 1 and 2 and general affairs plus the head-office IT department join from Stage 3 onward. Putting constraints into words is something only the shop floor can do, while system design will not progress with the shop floor alone. How to divide these roles at a site with no resident IT staff is covered in how to cover the absence of IT staff at an overseas plant.
Shift management is also not a mechanism that stands on its own. A finalised roster is the backing for the production plan, and the resulting assignment data feeds into analysis of labour cost by process and equipment utilisation. If you want to draw the whole picture with that connection in view, see also our primer on what a production management system is.
Frequently asked questions
Do we need to run a shift management system and an attendance management system together
At most sites, yes. Attendance management handles the recording of actuals and wage calculation, while shift management handles staffing design in advance, and those are different roles. Some products do carry both sets of functionality, and in that case you should still check separately how far the roster-building part has been developed. A simple roster feature bundled with attendance functionality may be able to copy patterns without being able to filter candidates by constraint.
Can shifts be created automatically even on a three-shift pattern
It depends on the product. Many products support configuring rotation cycles, but what you should actually check is how far your own constraints can be expressed. Look at whether limits on consecutive working days, the handling of the day after a night shift ends, the weekly overtime allowance and the required number of certified operators for a given process can be held as configuration. If the conditions cannot be expressed, people will end up correcting the automatically generated draft by hand, and the workload will not fall as much as expected.
Can a system check the limits in Thai labour law
If the product lets you set the limits themselves as conditions, then detection at the point the roster is built is possible. Under the Thai Labour Protection Act, ordinary work is capped at 8 hours a day and 48 hours a week, hazardous work at 7 hours a day and 42 hours a week, and the combined total of overtime, holiday work and overtime on a holiday is in principle capped at 36 hours a week. However, the individual consent required from employees for overtime and holiday work cannot be substituted by a system calculation. Obtaining and recording that consent has to be designed as an operating procedure. Confirm the specific conditions that apply to you against your work rules and with local labour law advisers.
Do we need to rebuild the skills matrix
In most cases it is a restructuring rather than a rebuild. A skills matrix built for audit purposes is usually a people-by-skill list, whereas what roster building needs is the mapping of which skills each process requires. The work involved is reorganising the existing list, keeping what is there, into a form that supports reverse lookup from the process side. Overlapping it with the review cycle for competence management under ISO 9001 or FSSC 22000 avoids doing the work twice.
How long does implementation take
It depends on scale and requirements, but allowing around six months from understanding the current state to full rollout is realistic. If your existing roster-building rules are undocumented, the first stages of understanding and writing them down will run longer. Put the other way round, the sites where that stage takes longest are the ones where the dependency has gone furthest, and that workload is best treated as unavoidable.
Is there any point at a site with only a few dozen employees
If your shift patterns are simple and someone else can build the same table when the usual builder is away, a spreadsheet will keep you going for now. The criterion is not headcount but whether the build rules are shared with anyone beyond the one person. Even with a small headcount, if the certification and process constraints are complex and only one person understands how they combine, the structure of the risk is no different from a large site. Start by trying to write the rules out and seeing how much of it you cannot write down.
Summary
Evaluating a shift management system by starting from product comparison misses the point. Here are the key points covered in this article.
- Attendance management is after-the-fact recording and wage calculation. Shift management is staffing design done in advance. Installing an attendance system alone leaves the burden of building the roster untouched
- The Thai Labour Protection Act sets working hour caps, a 36-hour weekly overtime allowance, individual consent for overtime and holiday work, and the granting of rest periods, all of which have to be built in at the point the roster is drawn up
- The 9th amendment, effective 7 December 2025, expanded maternity leave to a maximum of 120 days and newly created 15 days of spousal parental leave. Staffing plans now need to assume long absences
- Making a spreadsheet more efficient leads readily to macros, creating a state where only the author can fix it. This is a business continuity risk more probable than equipment failure
- At many sites the skills matrix built for ISO 9001 or FSSC 22000 is not used for staffing. The cause is that its format is audit-oriented and unsuited to reverse lookup from the process
- The supply of foreign workers really can move sharply. A structure that depends on one person to redesign the workforce is precarious
- In the model calculation, reducing build workload alone does not recover the investment. Only when the benefits of absence cover and staffing accuracy are added does payback come in within the two-year range
- Narrow selection to five criteria. Products separate above all on the expressiveness of constraints and integration with skill information
- The most valuable part of implementation is the stage of writing the constraints out as sentences
The first thing to do is not to collect product brochures. It is to have the person who built this month’s roster talk you through the order in which they thought about it and what they weighed, and to write that down. As you write, rules the person themselves had never put into words will emerge without fail. The number of them is the depth of your dependency.
TOMAS TECH has supported Japanese-owned plants in Thailand and across ASEAN in putting shop-floor data to work, through PEGASUS and other production and energy management systems. Designing the move of “who goes on which process” from individual memory to organisational data is a theme we have faced repeatedly in that work. We are happy to help even before you shortlist products, starting with taking stock of your own allocation rules together. Please get in touch through our contact page.
References
- Thai labour law and practice, volume 1 — GVA Law Office. Provisions of the Labour Protection Act on working hour caps, the 36-hour weekly overtime allowance, individual consent for overtime and holiday work, and the granting of rest periods
- Guide to the Thai Labour Protection Act — The 9th amendment, published in the Royal Gazette on 7 November 2025 and effective 7 December 2025. The disclosure filing obligation, the move to 120 days of maternity leave, and the new spousal parental leave
- JSCCIB view on the shortage of foreign workers in Thailand — Bangkok Shuho, announced 5 June 2026. The sharp fall in the number of Cambodian workers, the affected sectors, and the 2026 GDP growth forecast
- Shift management challenges in factories and system selection — The three shift management problems specific to factories and three criteria for system selection
- How to choose a shift creation tool — CloudSign. On how manual spreadsheet work stops keeping up in workplaces with a mix of early, late and night shifts
- Workforce allocation and skill management in manufacturing — Hutzper Inc. The problem that skills matrices are maintained for audits but not used for staffing, and a case in which allocation work fell from seven hours a week to one hour
- Automatic shift creation using AI — TRYETING. An account of an average 77.5 percent reduction in roster creation time among users of HRBEST
- Category overview of shift management systems — ITreview. The general functional scope of shift management systems and an overview of the market
