Commercial maintenance software answers whether a vessel is compliant. Naval maintenance answers something harder and more perishable: can this ship fight tonight, and at what level. Readiness is not a status you hold, it is a state you report, and it changes with every defect discovered. Under the casualty reporting system a casualty is defined precisely — an equipment malfunction or deficiency that cannot be corrected within 48 hours and reduces the unit's ability to perform a primary mission. The definition contains a clock. From the moment a fault is found, the ship has two days to restore capability before the condition becomes a reportable casualty transmitted upward, where operational commanders and support staff use it to set priorities and where it feeds directly into the unit's readiness reporting. The link runs the other way too: any maintenance job carried at Priority 1, 2 or 3 — equipment that is critical, extremely important or important to the ship's operation — is required to generate a casualty report. A coding decision made at the deckplate propagates into force-level visibility. Start a free trial of Marine Inspection and see what that chain looks like when the record underneath it is sound.
The definition that governs everything downstream
A casualty is a malfunction that cannot be corrected within 48 hours and reduces the ability to perform a primary mission
Stage 1
Discovery
A fault is found by ship's force. Nothing has been reported. The clock starts here, and what happens in the next two days determines whether this becomes visible outside the lifelines.
Stage 2
The 48-hour window
Restoration depends on three things: parts held aboard, technical knowledge available on the deckplate, and whether anyone can find what was done about this fault last time.
Stage 3
Casualty declared
The condition is reported, categorised and consumed into readiness reporting. Operational commanders set priorities against it, and the ship's declared capability changes.
Everything a maintenance system can influence sits in stage two. It cannot prevent faults and it cannot alter the reporting rules. What it can do is compress the interval between discovery and restoration — and because readiness is measured in days spent degraded rather than in incidents counted, that compression is the entire contribution.
Readiness Is Measured in Days, Not Incidents
This is the metric structure that should reorganise how a defence fleet thinks about its maintenance data, and it is the reason incident counts are a poor proxy for material condition. Book a Marine Inspection demo and see time-to-restore treated as the number that matters.
PCTFREE
Percentage of days free of serious casualties
The proportion of days in a month during which the ship carries no Category 3 or Category 4 casualty. A clean measure of whether the unit was available at the level it is supposed to be, expressed as time rather than as event count.
CASDAYS
Cumulative equipment-days in degraded status
The sum of all days in a month in which each piece of equipment sat in Category 3 or 4 status. Three items degraded across an entire thirty-day month produces ninety casualty days. One number, aggregating both breadth and duration.
What that arithmetic implies
A fault restored in three days and a fault restored in thirty are not one casualty each. They are three casualty days and thirty. On this scale a single protracted parts wait outweighs ten faults cleared quickly, which means the levers that move readiness are diagnostic speed, parts availability and the ability to find out what worked last time — not the raw number of things going wrong.
Research across three ship classes examining manning, crew stability, months since last overhaul, steaming hours and length of time in command found that the most important influences on ship material readiness were those related to manning. The same finding recurs across sectors and decades: the binding constraint is usually people and the knowledge available to them, not the machinery itself.
The Four Categories and What Each One Costs
Severity categorisation determines who sees the report and how urgently the supply and technical assistance system responds to it, so the assessment made aboard has consequences well beyond the ship. Sign up for Marine Inspection and hold the underlying condition evidence that a categorisation rests on.
Category 4
Critical safety or damage control item. Required for performance of the ship's mission. Required to sustain the bare minimum acceptable level of human needs and sanitation. This is the category that changes what the ship can be tasked with.
Category 3
Extremely important safety or damage control item, required for sustained operation. Counted alongside Category 4 in the readiness measures above, so it carries full weight in how the unit's material condition is assessed.
Category 2
Some contribution to efficient performance or to a normal level of human comfort and welfare. Required for the overall integrity of a system other than an essential one or its backup. Contributes to appearance in an important area, and will significantly reduce future maintenance.
Note what sits in Category 2: work that will significantly reduce future maintenance. The lowest severity band explicitly contains the preventive work whose deferral generates the higher bands later. A fleet that clears Category 3 and 4 items and never reaches Category 2 is trading current readiness against next year's.
Condition
Time to restore is the controllable variable
Defect discovery captured at the point and time it occurs, with the equipment identified, the condition found recorded against a stated criterion, and the history of what resolved the same fault previously available on the deckplate rather than in an office. Because readiness is counted in days degraded, every hour removed from the interval between discovery and restoration is readiness returned.
The Report Cycle
Casualty reporting is a sequence rather than a single submission, and each stage has a distinct informational purpose. Getting the middle stages right is what keeps a fleet commander's picture accurate between the fault and the fix. Schedule a walkthrough and see the underlying record carry each stage.
1
Initial
Identifies the status of the casualty and any parts or assistance requirements. Operational and staff authorities use this to set priorities, which makes the quality of the initial description directly determinative of how quickly help arrives.
2
Update
Submits changes to the initial report. The stage most easily neglected, and the one that keeps the force-level picture current rather than stale between a fault and its resolution.
3
Correction
Submitted when the equipment is repaired and back in operational condition. This is the stage that stops the casualty-day clock, so a delay in submitting it is readiness lost on paper that was already restored in fact.
4
Cancellation
Closes out a report where the condition is otherwise resolved or superseded, removing it from the active picture.
Where Work Order Priority Becomes Force-Level Visibility
The mechanical link between deckplate coding and fleet reporting is the most consequential data relationship in naval maintenance, and it runs in one direction only. Start a free trial and see priority coding held with the evidence that justifies it.
Step 1
Priority assigned
Ship's crews are required to identify maintenance work order priorities. Priority 1, 2 and 3 cover equipment that is critical, extremely important or important to the ship's operation, with Priority 1 being mandatory and covering critical safety or damage control items.
Step 2
Report becomes mandatory
Any maintenance job carrying one of those three priority codes is required to generate a casualty report. The coding decision is not an internal scheduling preference — it triggers an external obligation automatically.
Step 3
Readiness reporting
Casualty reports are directly related to the unit's readiness reporting and identify equipment status and its impact on the ship's operations and mission readiness. The report is the mechanism by which material condition becomes declared capability.
Step 4
Force management
The system exists to support senior commanders in the management of assigned forces, requiring an accurate, current operational status for each unit. Priority coding at the deckplate therefore reaches the level at which tasking decisions are made.
The uncomfortable implication is that the integrity of force-level readiness data rests on consistent priority coding by watchstanders under time pressure. A system that makes correct coding easy, that surfaces how similar faults were coded before, and that holds the evidence behind each assessment is not an administrative convenience. It is data quality assurance at the point of origin.
What the Record Has to Carry
Defence maintenance carries a document set that has no commercial equivalent, and its structure is worth understanding before assessing any system against it. Book a walkthrough and map your own record set during the evaluation.
Table 1: The Naval Maintenance Record Set
| Element | What It Is | What It Drives | Where It Degrades |
|---|---|---|---|
| Current maintenance package | The consolidated list of outstanding maintenance requirements for the ship | Reviewed by the type commander and used to develop the authorised alteration package | Items entered inconsistently, so the package understates the real backlog |
| Deferred maintenance actions | Requirements needing external assistance, not achievable by ship's force in a period, arising from an inspection body's uncorrected deficiency, or constituting a safety condition | What gets carried into an availability rather than resolved aboard | The reason for deferral not recorded, so the four categories become one undifferentiated list |
| Ship self-assessment | The ship's own identification of recommended work ahead of an availability | The work requests submitted for the availability | Compiled from memory because the year's findings were never structured |
| Work requests | Formal requests defining specific items of work for a repair activity | Work definition conferences and the assignment of job responsibility | Written without the condition evidence that would justify scope |
| Alteration and repair package | The consolidated scope for an availability | What the repair activity is contracted and resourced to deliver | Scope discovered after arrival, at the highest possible cost |
| Casualty reports | Initial, update, correction and cancellation across the life of each casualty | Readiness reporting, priority setting, technical assistance and parts | Correction reports submitted late, extending the casualty-day count |
| Inspection findings | Uncorrected deficiencies reported by an inspecting activity | Deferred maintenance actions by definition | Held as a report rather than converted into tracked actions |
| Configuration record | What is actually fitted, as opposed to what the drawings say | Parts ordering, technical documentation applicability, repair planning | Diverges silently through cannibalisation and field changes |
| Availability completion evidence | Satisfactory equipment test completions following repairs, and the absence of new casualties arising from work done | Whether the availability delivered what it was scoped to deliver | Tests completed and recorded loosely, so a recurrence has no baseline |
Findings structured across the year so the self-assessment writes itself, not the other way round.
The Four Definitions of Deferred
Deferred maintenance is a defined term with four distinct triggers, and conflating them costs a fleet the ability to see why work is accumulating. Start a free trial and record deferral reason as structured data rather than as a note.
Requires external assistance
The work needs an outside activity or another work centre. A capacity and capability question, and the one most responsive to planning.
Beyond ship's force in the period
Achievable in principle by the crew but not within the time available. A manning and scheduling question, and the category most likely to be reducible.
Uncorrected inspection deficiency
An item reported by an inspecting activity and not yet corrected. Externally visible, externally tracked, and the category with the least tolerance for drift.
A safety condition
Deferred by definition rather than by choice. Any system that cannot distinguish this from a scheduling deferral is hiding the most important line in the backlog.
Four different causes producing one visible symptom. A backlog reported as a single number tells a commander how much work is outstanding and nothing about whether the constraint is capacity, manning, external inspection or safety — which are four different problems requiring four different responses.
Cannibalisation Is a Configuration Problem Wearing a Supply Uniform
Parts shortages produce a practice that solves an immediate problem and creates a durable data one, and it is systematically under-recorded because it is treated as a supply event rather than a configuration change. Schedule a demo and see removals recorded against both hulls.
What it is
Working parts removed from one unit and reused elsewhere because the supply system cannot deliver in time. Analysis of naval sustainment has tracked cannibalisation alongside casualty reports and depot maintenance delay as indicators moving in the wrong direction while steaming hours declined.
What it creates
Two records that should change and usually only one that does. The receiving unit's casualty clears. The donor unit acquires a defect that may not be reported because the equipment was not in use, and both hulls now differ from their configuration baselines in ways the drawings do not show.
What it costs later
Parts ordered against a configuration that no longer exists. Technical documentation that does not match the fitted equipment. An availability scoped from a baseline that drifted. And a diagnostic trail that ends at a component nobody recorded moving.
What fixes it
Treating a removal as a transaction affecting two configuration records rather than as a parts issue affecting one. It costs perhaps a minute at the time and removes an entire class of downstream ambiguity — provided the system has the concept at all, which most commercial platforms do not.
Where a Commercial Platform Fits, and Where It Does Not
This section exists because a defence audience will identify an overclaim immediately, and because the honest boundary is more useful than a broad assertion. Start a free trial if your operation sits on the right of this line.
Where it does not fit
Classified programmes and combat system maintenance, where the record itself carries classification and must reside in an accredited environment
Fleets mandated onto a national maintenance and readiness information system, where a parallel commercial platform would fragment the authoritative record
Any application where casualty reporting must be generated and transmitted through official channels rather than mirrored in a separate system
Environments where data residency, accreditation or supply chain assurance requirements have not been established and satisfied in advance
Where it fits well
Auxiliary, support, training and survey vessels operating outside combat system scope but under the same readiness expectations
Government-owned commercially operated fleets, where a contractor carries the maintenance obligation and the evidence burden
Coast guard, fisheries protection, customs and constabulary fleets running military-style readiness discipline on civil-standard hulls
Hull, mechanical, electrical and habitability maintenance on unclassified systems, feeding the same self-assessment and availability planning cycle
The honest position is that a commercial platform can serve the hull, mechanical and electrical layer of a defence fleet, the inspection and condition record that feeds availability planning, and the whole of an auxiliary or constabulary operation — and that it is not the right tool for classified combat system records or for fleets already mandated onto an accredited national system. Establish which layer you are equipping before evaluating anything.
Evaluating a Platform for a Defence or Government Fleet
The questions below separate platforms that understand readiness from platforms that understand compliance, which are different disciplines. Book a demo with an engineer officer and a readiness reporting officer present.
Table 2: Buyer Questions Specific to Defence and Government Fleets
| Area | The Question | A Real Answer | What Should Worry You |
|---|---|---|---|
| Time to restore | Can we measure days in degraded status, not just defect counts? | Duration from discovery to restoration held per defect and aggregated | Open and closed counts with no elapsed-time dimension |
| Priority coding | Does the system support consistent priority assignment with precedent visible? | Prior coding of similar faults surfaced at the point of assessment | A free priority field with no guidance and no history |
| Deferral reason | Are the distinct causes of deferral recorded as structured categories? | External assistance, time, inspection finding and safety distinguished | One deferred flag with an optional comment |
| Configuration | Can a part removal be recorded against both the donor and the receiver? | A transaction affecting two configuration records | Parts modelled as stock issues against a single asset |
| Self-assessment | Does the availability work list assemble from the year's findings? | An exportable list built from structured records with evidence attached | A self-assessment compiled from memory each cycle |
| Knowledge retention | Can a new watchstander find what resolved this fault last time? | Fault history searchable by equipment, with the resolution recorded | History available only as closed work orders with no diagnosis |
| Data residency | Where does our data physically reside and under whose jurisdiction? | A precise answer with documentation, offered before being asked | Vagueness, or an answer that changes depending on who is asking |
| Scope honesty | Which parts of our maintenance estate should not go on this system? | A vendor willing to name the boundary rather than claim everything | An assurance that it handles any requirement you have |
| Reference | Which defence or government fleets use this today? | A named, contactable reference operating comparable vessels | Commercial references offered as equivalent experience |
2026 DEFENCE MAINTENANCE REALITY
Doctrine is national and this page uses one navy's terminology as a worked example. Casualty categorisation, priority coding, availability planning and readiness reporting exist in analogous form across many navies under different names and instruction numbers. Map the concepts to your own doctrine rather than adopting the vocabulary. Maintenance policy is periodically reissued. Governing instructions covering ship maintenance policy and fleet maintenance procedure are revised on their own cycles, most recently within the last two years for several of the documents referenced here, so work from the current issue. Readiness metrics have been the subject of external criticism. Audit work has found that operational availability and materiel availability were not being fully or accurately tracked despite these being identified as key measures — which is a data quality finding rather than a maintenance one, and precisely the kind of gap a disciplined record addresses. Accreditation is a prerequisite, not a feature. Any system holding defence maintenance data must satisfy the applicable security and data residency requirements before capability is even relevant.
Frequently Asked Questions
What exactly counts as a casualty?
An equipment malfunction or deficiency that cannot be corrected within 48 hours and that reduces the unit's ability to perform a primary mission. The 48-hour element is significant because it makes restoration speed part of the definition rather than merely a performance measure: a fault the ship can clear inside two days does not become a reportable casualty at all. Separately, any maintenance job coded at Priority 1, 2 or 3 — covering equipment critical, extremely important or important to the ship's operation — is required to generate a casualty report regardless. Reports are directly related to the unit's readiness reporting and identify equipment status and its impact on operations.
How is material readiness actually measured?
Principally in days rather than in events. One established measure is the percentage of days in a month during which the ship is free of Category 3 and Category 4 casualties. Another sums the days in which each piece of equipment sat in Category 3 or 4 status — three items degraded across a thirty-day month producing ninety casualty days. The consequence is that duration dominates: one protracted parts wait outweighs many faults cleared quickly. That makes diagnostic speed, parts availability and retrievable fault history the levers that move the number, rather than reducing the raw count of things going wrong.
What is the difference between the casualty report stages?
Four stages with distinct purposes. The initial report identifies the status of the casualty and any parts or assistance required, and operational and staff authorities use it to set priorities — so its quality determines how quickly help is directed. The update submits changes to the initial report and keeps the force-level picture current rather than stale. The correction is submitted when equipment is repaired and back in operational condition, which stops the casualty-day clock; a late correction is readiness lost on paper that was already restored in fact. Cancellation closes out a report where the condition is otherwise resolved or superseded.
Why does deferral reason matter so much?
Because deferred maintenance is a defined term with four distinct triggers, and they call for four different responses. A requirement may be deferred because it needs assistance from an external activity or another work centre; because it is not expected to be accomplished by ship's force within a given period; because it is an uncorrected deficiency reported by an inspecting activity; or because it is a safety condition. Reported as one backlog number, those become indistinguishable. Recorded as structured categories, they tell a commander whether the constraint is external capacity, internal manning, inspection follow-up or safety — and only one of those is fixed by scheduling.
Why treat cannibalisation as a configuration issue?
Because that is what it structurally is, even though it is usually handled as a supply workaround. A working part removed from one unit to restore another clears one casualty and creates a defect on the donor that may go unreported if the equipment was not in use. Both hulls now differ from their configuration baselines in ways the drawings do not reflect, which later produces parts ordered against a configuration that no longer exists, technical documentation that does not match what is fitted, and availability scoping from a drifted baseline. Recording the removal as a transaction affecting two configuration records costs about a minute and removes the whole downstream ambiguity.
Can commercial maintenance software be used on naval vessels at all?
For part of the estate, yes, and it is worth being precise about which part. It is not appropriate for classified programmes or combat system records that must reside in an accredited environment, nor for fleets already mandated onto a national maintenance and readiness information system where a parallel platform would fragment the authoritative record, nor anywhere casualty reporting must be generated through official channels rather than mirrored. It fits well on hull, mechanical, electrical and habitability maintenance on unclassified systems, on auxiliary, support, training and survey vessels, on government-owned commercially operated fleets, and across coast guard and constabulary fleets. Establish which layer you are equipping first.
The Only Variable a Maintenance System Controls Is the Interval
Faults captured at discovery with equipment identified and condition recorded against a criterion. Fault history retrievable on the deckplate so a new watchstander finds what worked last time. Deferral reason held as structured categories rather than as a flag. Part removals recorded against both configurations. Findings structured across the year so the self-assessment assembles itself before an availability rather than being written from memory during it.
