Maintenance Backlog Calculator

Ready work hours divided by effective weekly crew capacity.

This selection changes review context only. Formulas and example inputs stay unchanged. Check the model assumptions and applicability for the actual process.

Identify the actual asset, process, work boundary, source documents, units and assumptions. Confirm that the selected model or template applies before using its results.

1 Inputs

Minimum: 0

Minimum: 1

Minimum: 1

Minimum: 1 · Maximum: 100

2 Results

Weeks of backlog
6 wk
Weekly capacity
300 h
Crew-weeks of work
6
Days of backlog
30 d
W = B / (N × H × U)
Ready work hours divided by effective weekly crew capacity. The day conversion assumes five working days per week. Compare trends and job criticality with your planning targets; a short backlog alone does not prove excess staffing.

Worked example

Example values are illustrative. Replace them with your measured data.

InputValue
Total ready backlog1800 labour-hours
Crew size10 technicians
Paid hours / tech / week40 hours
Wrench-time utilisation75 %

Weeks of backlog: 6 wk

Related tools

About this calculator

How it works

Weekly crew capacity = crew size × paid hours per technician per week × wrench-time utilisation. Weeks of backlog = ready backlog hours ÷ weekly capacity. Days of backlog = weeks × 5.

Worked example (illustrative inputs)

1,800 hours of ready backlog, 10 technicians, 40 paid hours each, 75% wrench time. Capacity = 10 × 40 × 0.75 = 300 hours a week. Backlog = 1,800 ÷ 300 = 6.0 weeks, or 30 working days.

How to read the result

The tool treats 2–4 weeks as a healthy planning window. Under 2 weeks is flagged as low (a risk of reactive work or over-staffing), 4–6 weeks as acceptable but worth watching, and over 6 weeks as excessive, where work ages and contractors or overtime may be needed. The example sits at the top of the acceptable band.

When to use it

Use it in weekly scheduling. Count only ready work (planned, kitted and schedulable) and track total backlog separately.

À propos de ce calculateur

Traduction (brouillon) — à relire.

Fonctionnement

Capacité hebdomadaire = effectif × heures payées par technicien et par semaine × taux de temps productif. Semaines de carnet = heures de travaux prêts ÷ capacité hebdomadaire. Jours de carnet = semaines × 5.

Exemple chiffré (valeurs d'illustration)

1 800 heures de travaux prêts, 10 techniciens, 40 heures payées chacun, 75 % de temps productif. Capacité = 10 × 40 × 0,75 = 300 h/semaine. Carnet = 1 800 ÷ 300 = 6,0 semaines, soit 30 jours ouvrés.

Lire le résultat

L'outil considère 2 à 4 semaines comme une fenêtre de planification saine. Moins de 2 semaines est signalé comme bas (risque de travail réactif ou de sureffectif), 4 à 6 semaines comme acceptable mais à surveiller, et plus de 6 semaines comme excessif : les travaux vieillissent et la sous-traitance ou les heures supplémentaires peuvent s'imposer. L'exemple est en haut de la bande acceptable.

Quand l'utiliser

À utiliser lors de l'ordonnancement hebdomadaire. Ne comptez que les travaux prêts (planifiés, kittés, ordonnançables) et suivez le carnet total à part.

حول هذه الحاسبة

ترجمة (مسودة) — للمراجعة.

طريقة الحساب

الطاقة الأسبوعية للفريق = عدد الفنيين × الساعات المدفوعة لكل فني أسبوعياً × نسبة الوقت الإنتاجي. أسابيع الأعمال المتراكمة = ساعات الأعمال الجاهزة ÷ الطاقة الأسبوعية. أيام الأعمال المتراكمة = الأسابيع × 5.

مثال محسوب (قيم توضيحية)

1800 ساعة أعمال جاهزة، 10 فنيين، 40 ساعة مدفوعة لكل منهم، 75% وقت إنتاجي. الطاقة = 10 × 40 × 0.75 = 300 ساعة في الأسبوع. الأعمال المتراكمة = 1800 ÷ 300 = 6.0 أسابيع، أي 30 يوم عمل.

قراءة النتيجة

تعتبر الأداة 2–4 أسابيع نافذة تخطيط صحية. أقل من أسبوعين يُعلَّم كمنخفض (خطر العمل التفاعلي أو زيادة العمالة)، و4–6 أسابيع مقبول مع المتابعة، وأكثر من 6 أسابيع مفرط: تتقادم الأعمال وقد تلزم الاستعانة بمقاولين أو ساعات إضافية. يقع المثال في أعلى النطاق المقبول.

متى تستخدمه

استخدمها في الجدولة الأسبوعية. احسب الأعمال الجاهزة فقط (المخططة والمجهزة والقابلة للجدولة)، وتابع إجمالي الأعمال المتراكمة بشكل منفصل.

In one line

Ready work hours divided by effective weekly crew capacity. The day conversion assumes five working days per week. Compare trends and job criticality with your planning targets; a short backlog alone does not prove excess staffing.

Worked example

EXAMPLE

Illustrative values (the calculator defaults), not data from a real site.

Inputs
Total ready backlog1800 labour-hours
Crew size10 technicians
Paid hours / tech / week40 hours
Wrench-time utilisation75 %
Results
Weeks of backlog6 wk
Weekly capacity300 h
Crew-weeks of work6
Health (2–4 wk)Off target
Days of backlog30 d

Frequently asked questions

What is a healthy maintenance backlog?

2–4 weeks of crew capacity is the widely-cited SMRP target. Below 2 weeks you risk over-resourcing or reactive work; above 6 weeks jobs age, priorities drift and customer trust erodes.

Total backlog vs ready backlog?

Total backlog is every open work order. Ready (or 'planned') backlog is work that is fully planned, kitted and schedulable now. Only ready backlog should drive scheduling decisions, and it's what this calculator expects as its input.

What counts as wrench-time utilisation?

It's the share of a technician's paid hours actually spent doing hands-on repair or PM work, after subtracting travel, waiting for parts or permits, meetings, training and admin time. Many plants run 40–60% in practice even though 75–85% is often achievable with better planning — use your own measured figure, not an aspirational one, for an accurate result.

What should I do if my backlog is too high?

Options include temporary overtime or contractors to burn down the queue, reviewing priorities to defer lower-risk work, and checking whether the backlog is high because planning and scheduling are inefficient rather than because there's genuinely too much work. A backlog that keeps climbing even after these levers usually means the crew is undersized for the asset base.

What if my backlog is very low, near zero?

A near-zero ready backlog isn't automatically good — it can mean the crew is over-resourced for the current workload, or that work isn't being logged properly and reactive firefighting is bypassing the backlog entirely. Check whether emergency work is being tracked at all before concluding capacity is the issue.

Donate · Faire un don · تبرّع