Last updated: 2026-09-05 · 5 min read

A mold maintenance schedule is how a guaranteed shot count survives contact with production. The structure that works everywhere is the same: tasks at three frequencies — per mold changeover, per running day, and at shot-count milestones — each written down, each with an owner, all of it logged. The daily and weekly tasks keep the tool running correctly today; the shot-count milestones catch wear before it becomes damage. Neither half works without the other, and a quotation that promises a lifespan without naming this program is promising a number it cannot control.

Key facts

<>

  • Three task frequencies: changeover setup, running-day checks, and shot-count milestone inspections.
  • Changeover care causes or prevents most early problems: cleaning, lubrication, cooling and fit checks before the first shot.
  • Milestone inspections are keyed to the shot counter — the wear schedule follows shots, not calendar dates.
  • Slides, lifters, springs and gates are scheduled wear items; the cavity plates are what those items protect.
  • The logbook is the asset: shot counts, tasks done, parts replaced — evidence that keeps the lifespan guarantee meaningful.

    • Preventive maintenance — Preventive mold maintenance — scheduled cleaning, inspection and component replacement to extend mold life. Daily: clean parting line, check vents. Every 10k shots: clean ejector pins, lubricate guides. Every 50k shots: inspect gate for wear, check heater resistance. Every 100k shots: replace worn components. The related guide covers adjacent topics.

    Preventive maintenance versus running to failure

    Every molded part is a small subtraction from the tool that made it: a little wear on the shut-off edges, a little fatigue in the slides, a little scale in the cooling lines. Nothing is visible per cycle, which is why unmaintained molds seem to fail suddenly — the damage was accumulating on a schedule nobody was reading. Preventive maintenance is simply the decision to spend small, planned amounts of money at known intervals instead of large, unplanned amounts when the tool stops mid-program.

    Preventive mold maintenance — a written program of cleaning, lubrication, inspection and replacement tasks triggered by mold changeovers, running time and shot counts, with results logged against the tool’s history. Its purpose is not to avoid all wear but to make wear visible, gradual and budgeted. The lifespan math it protects is covered in the mold lifespan guide.

    Task set one: at every mold changeover

    Most early-life mold problems are installed at setup, not worn in later. The changeover routine is where the tool’s next campaign is decided:

  • Clean every surface that will touch plastic. Cavity, core, vents and runners cleared of old residue and rust preventive; contaminants left at setup copy themselves into the first hundred parts and score the steel as they move.
  • Lubricate slides, lifters and guide pins. The correct grease in the correct amount — over-greasing contaminates the cavity as surely as under-greasing wears the gib.
  • Inspect shut-off edges and parting line. A magnified look at the edges that prevent flash. Any nick or rounding noted now is a repair decision made cheaply; the same nick found later is flash on a running program.
  • Verify cooling connections. Flow and leak test every circuit before mounting. A restricted line discovered at full production costs cycle time for weeks; found at setup it costs ten minutes.
  • Check ejection travel and spring condition. Ejector plates move freely, springs return true, no binding at the end of stroke. Ejection problems diagnosed at speed are ejection damage on parts.
  • First-shot confirmation. Dimensions and appearance of the first shots checked against the last known-good sample before the run is allowed to settle into the schedule.

    • Task set two: daily and weekly checks during production

  • Daily: vent cleaning. Deposits at the vents block air escape and create burns and short shots; a quick wipe keeps them working. Vent depth and layout are mold-specific decisions made at design time — see the DFM agenda for where they get reviewed.
  • Daily: parting-line and appearance watch. Sampled parts checked for flash onset and surface hazing. Flash that appears gradually is parting-line wear reporting itself early.
  • Daily: shot counter reading. The counter is logged at shift change; it is the clock that drives every milestone task below, so an unmaintained counter unmaintains the whole program.
  • Weekly: slide and lifter function. Movement observed at low speed for hesitation or noise; gibs and wear plates checked for play that doubles with every extra millimeter.
  • Weekly: cooling performance. Temperature deltas across circuits compared against the recorded baseline; drift means scale or blockage building somewhere in the lines.
  • Weekly: fasteners, hoses and fittings. Thermal cycling loosens what vibration finishes; a torque and leak pass catches both before they become downtime events.

    • Task set three: milestone inspections by shot count

    Calendar dates lie about wear; shots do not. The milestone inspections below are scheduled on the shot counter, and their intervals scale with mold class — a production tool built to a million-shot guarantee earns deeper inspections than a prototype build, and the class system described in the class guide sets which depth applies:

    1. Every 50,000 shots: wear-item pass. Springs, seals, small pins and gate inserts inspected and replaced at the first sign of fatigue. These components cost little; the downtime they cause does not.
    2. Every 100,000 shots: slide and lifter service. Disassembly, cleaning, regreasing, gib and wear-plate measurement. Side-action components cycle more violently than anything else on the tool and carry the highest failure rate per shot.
    3. Every 250,000 shots: deep inspection. Cavity and core surfaces inspected for finish loss and corrosion, shut-off edges measured, cooling channels flushed or descaled, dimensional spot-check against the drawing. This is the inspection where emerging problems are still repairs rather than rebuilds.
    4. Every 500,000 shots: life review. The full maintenance history reviewed against remaining program volume: is the tool on a trajectory to finish its guaranteed life, and which component groups need scheduled replacement to get there? The output is a written recommendation — rebuild scope, replacement plan, or confirmation to continue.

    The logbook: what the record must contain

    The schedule only exists if it leaves evidence. A maintenance record worth its name contains five entries per tool, updated every time the tool moves:

  • Cumulative shot count, read from the counter at every milestone — the clock the entire program runs on.
  • Tasks performed, with dates and sign-off, so it is documented which checklist items were actually done and by whom, not merely claimed.
  • Parts replaced, with part numbers, building the tool’s replacement history so the next service is planned from fact rather than guesswork.
  • Measurements and findings, especially shut-off edge condition and cooling deltas, so trends are visible across inspections instead of rediscovered at each one.
  • Problems deferred and why, because a consciously postponed repair with a plan is managed risk, while an unrecorded one is just accumulating damage.

    • For tools that change hands — transferred programs, exported molds, second-life tooling — this logbook is the difference between buying an asset with a known history and buying a mystery. Insist on receiving the record with the tool, the same way you would insist on the dimensional report with the first samples.

    Who owns maintenance when the mold lives at the factory?

    In outsourced production the mold physically lives at the factory while its lifespan belongs to the buyer — and that split only works when ownership of the maintenance program is written down. Three items belong in the production agreement: which tasks the factory performs under the standard schedule, which milestone inspections and repairs need buyer approval and cost quotation, and how the logbook is shared — ideally with the periodic production reports. Once those three are agreed, the question “whose fault is the wear” stops existing, because every event is in the record. Where the ownership is never named, the argument arrives exactly when the tool needs its first rebuild — at the moment of maximum leverage for whoever did not write anything down.

    Ask me to guess a mold’s remaining life and I will ask for two things first: the shot counter and the logbook. The steel tells me the ceiling, but the record tells me where the tool actually sits below it. Every mold that exceeded its guarantee had a boring story — the same checklist, the same intervals, the same person signing the same book. The ones that died early were never boring; they just had no paperwork to argue with.

    — Arthur, Tooling Engineer at aCatMould

    Signs the schedule is not actually being followed

    A written program that nobody executes is worse than no program at all, because the paperwork hides the drift. These are the symptoms that the schedule exists only in the quotation, not on the shop floor:

  • The shot counter is frozen or missing. If the clock that drives every milestone is not maintained, no milestone ever really happens — everything after that runs on memory and goodwill.
  • Flash appears gradually and is met with process adjustments. Rising pack pressure to chase flash is the classic signature of wearing shut-off edges getting treated as a settings problem. Maintenance answers it with steel; tuning only buys days.
  • Slides get louder before they get inspected. Noise or hesitation in side actions that is reported but never opened up means the weekly check is not happening — or not happening at low speed, where the problem is visible.
  • Cycle time creeps upward with no explanation. Cooling scale builds quietly; a program watching its temperature deltas would catch it. Unexplained drift means the weekly cooling comparison is a formality or a fiction.
  • The logbook cannot answer a single follow-up question. Ask what was done at the last milestone, who signed it, and which parts were replaced. A record that cannot answer three simple questions is decoration.

    • Buyers can run this audit remotely: request the counter reading, the last milestone entry and the replacement list in one message. A factory that runs the program answers in minutes; the others negotiate. The answer itself is the diagnostic, before any part quality argument starts.

    Frequently asked questions

    Why schedule maintenance by shot count instead of calendar dates?

    Because wear follows cycles, not months. A mold running three shifts accumulates a year’s wear in a quarter, while an idle mold ages differently — corrosion, not wear. The shot counter is the only clock that matches the actual damage mechanism.

    Does every mold need the same milestone intervals?

    No. Intervals scale with mold class, resin aggressiveness and duty cycle: a million-shot production tool running abrasive resin earns tighter intervals than a prototype mold running clean commodity grades. The quotation should name the intervals it assumes.

    What is the single most neglected maintenance task?

    Vent cleaning, closely followed by cooling channel care. Both are invisible when they fail to be done — the symptoms arrive later as burns, short shots or creeping cycle time, far from the cause.

    Should spare wear parts be stocked from the start?

    For components with known replacement intervals — springs, gate inserts, seals, and matched slide components — yes. Stocking them from the start turns a future failure into a scheduled swap instead of a machining lead-time emergency.

    How detailed must the maintenance logbook be?

    Detailed enough that a stranger could reconstruct the tool’s history: shot counts, tasks with dates and sign-offs, replaced parts, measurements and deferred work. If the log cannot answer “what was done at the last milestone,” it is not a logbook.

    Does a maintenance program void or protect the shot guarantee?

    Protects it. Guarantees are written against agreed running and maintenance conditions; the logbook is the evidence that those conditions were kept. Without it, any guarantee discussion becomes a claim without documentation.

    Key takeaways

    1. Maintenance runs at three frequencies: changeover setup, running-day checks, and shot-count milestones — each with a written checklist.
    2. Changeover care installs or prevents most early problems; daily checks catch flash, vent and cooling drift while they are small.
    3. Milestone inspections follow the shot counter, scaled to mold class: wear items, slide service, deep inspection, life review.
    4. The logbook is the asset: shot counts, tasks, replacements and measurements, signed and shared — evidence that keeps the guarantee real.
    5. When the tool lives at the factory, ownership of the schedule and the record must be written into the production agreement.

    If you are planning a production program, ask us how the maintenance schedule is built into the quotation: which tasks are included, which intervals we assume for your resin and volume, and how the logbook is kept and shared. You will get the answer in writing, from a named engineer, before any money moves.

    Sources
    HASCO — the pioneer of mouldmaking: standard mold units and spare components
    DME — global supplier of mold bases, components and molding supplies
    LKM (Lung Kee) — mould bases and mold steel for the toolmaking industry

    Sources: Plastics Technology · Plastics Technology Online · Society of Plastics Engineers (SPE) · MoldMaking Technology