LG4 — LOP overlaps with another LOP
Quick answer: LG4 is the GCS message code for two labor operations billing the same access or removal time. It usually fires when a component operation is claimed alongside a larger assembly operation whose flat time already includes reaching that component. The fix is to remove or zero the redundant line, not to re-code the repair.
LG4 at a glance
LOP overlaps with another LOP — Chrysler GCS message code.
| Why it fires | Two labor lines claim the same teardown. Most often a component operation sits next to an assembly operation that already includes that component's access and removal. |
|---|---|
| What it costs | A round trip. The claim comes back for correction rather than paying on the first pass. |
| How it clears | Remove or zero the redundant line, then resubmit. Where the overlap is genuinely justified, the claim is authorized instead of corrected. |
| What it is not | Published R-Related and O-Optional companion operations are not an LG4 stack. Chrysler intends those claimed together. |
What causes LG4, and what actually clears it
What Chrysler is actually checking
Chrysler does not publish an overlap table. The word overlap does not appear in the Warranty Administration Manual or the dealer policy manual at all; the concept is expressed structurally instead, through a primary operation plus its related operations. That means there is no list to check a claim against before submitting. Two arbitrary labor operations are adjudicated inside GCS, and LG4 is what comes back when the adjudication decides the same access time was billed twice.
The usual trigger
A technician removes an assembly to reach a component. The assembly operation's flat time already contains that removal, so claiming the component's own operation next to it bills the teardown a second time. This is the single most common shape behind an LG4, and it is why the fix is almost always to zero a line rather than to find a different operation.
When an overlap is legitimate
Not every overlap is a violation. Operations on components that genuinely sit in different physical locations may be claimed together, because no teardown is shared. Diesel after-treatment work is the standing example in the other direction: pulling the selective catalytic reduction unit already exposes the diesel exhaust fluid injector, so those operations overlap on paper and are still routinely authorized rather than removed. If the repair genuinely required both, the answer is to submit with justification rather than to give up the line.
Companion operations are not a stack
A labor operation's own published R-Related and O-Optional companions have already netted out shared access time. Claiming a primary operation together with its published companions is not an LG4 exposure, and dealers commonly leave those companions off out of caution. That is money the store earned and did not claim. Coolant drain and fill, oil drain and fill, and head removal for inspection alongside a long block all belong in this category.
The related rule that catches people
Chrysler's manual states that the 85-41 diagnostic operation is not allowed alongside an RSU or service bulletin repair. That is a separate rule from LG4, but it fails for the same underlying reason: the bulletin's published time already accounts for the diagnosis, so claiming diagnostic time next to it bills the same work twice.
How to stop LG4 recurring
The checks that keep it off the next claim.
- 01
One causal labor operation per condition. If a second operation covers the same teardown, it does not get its own line.
- 02
Collapse same-component variants down to a single pick rather than claiming two flavors of the same repair.
- 03
Itemize genuinely distinct repairs. Components in different physical locations are allowed to stack, and a multi-condition repair order should show every distinct repair.
- 04
Claim the published R-Related and O-Optional companions. They are not overlap, and leaving them off is unclaimed money.
- 05
Never put an 85-41 diagnostic line next to an RSU or service bulletin repair.
Frequently Asked Questions
- What does GCS code LG4 mean?
- LG4 is the GCS message code for two labor operations billing the same access or removal time. It usually fires when a component operation is claimed alongside a larger assembly operation whose flat time already includes reaching that component. The fix is to remove or zero the redundant line, not to re-code the repair.
- How do I fix an LG4 rejection?
- Find the two lines that share a teardown and zero or remove the one whose access is already paid inside the other. If both repairs genuinely happened in different places on the vehicle, or the overlap is one Chrysler routinely authorizes, resubmit with the justification rather than dropping the line.
- Are R-Related and O-Optional operations an LG4 overlap?
- No. Published companion operations have already netted out the shared access time, and Chrysler intends a primary operation to be claimed with them. Leaving them off does not protect the claim from LG4; it just gives up money the store already earned.
- Can Forge catch LG4 before the claim is submitted?
- Partly, and the limit is worth being clear about. When Forge drafts a CDJR claim its picking rules say one causal operation per condition and no stacking two operations over the same teardown, so the shape usually never reaches the claim. The deterministic check is narrower: a diagnostic line claimed beside an assembly repair is flagged by name as LG4 and RA8 exposure. Since Chrysler publishes no overlap table, nothing can verify two arbitrary operations mechanically, and that flag advises your administrator rather than blocking the claim. A store that wants nothing filed unreviewed can require approval on every claim instead.
Where this page comes from
Forge prepares and files Chrysler claims for the dealerships it works with, so what is described here is behavior observed on real claims as of August 2026rather than text quoted from a policy manual. Portals change, and a rule’s behavior can change with them. Treat this as a practitioner’s note, check it against your own claims, and follow your dealer agreement and your manufacturer’s published policy where the two differ.
No dealership, claim, or repair order is identified on this page. Forge is not affiliated with, endorsed by, or sponsored by Stellantis and FCA US LLC, and product and portal names are the property of their respective owners.
Contact
Let's get you set up.
Tell us about your dealership and your current warranty workflow. We'll reach out within one business day to schedule a personalized walkthrough.