PTS, OASIS, and SLTSLive todayFord warranty claim software for dealerships
Quick answer: Forge is warranty claim software for Ford and Lincoln dealerships. It reads repair orders, matches each line to a published SLTS operation, checks OASIS coverage and outstanding Field Service Actions, and flags overlap and missed allowances before anything is filed. Forge can submit on its own, or hold the claim for your warranty administrator to approve first: your store decides.
The submit is rarely what costs a Ford store money. What costs money is the picking: which published operation, whether it needs its base operation with it, whether a second op overlaps time already bundled into the first, and whether the allowance sitting next to the repair ever got claimed at all.
Where Ford claims go wrong
The failure modes we see most often on Ford and Lincoln repair orders.
Combination operations claimed without their base operation
SLTS publishes operations that carry a footnote reading, in effect, that claiming the combination also requires claiming the base. Operation 23943A10 is the worked example: it needs 23943A alongside it. Claim the combination on its own and the store under-claims the job, quietly, every time that repair comes through. Nothing rejects. The money simply never arrives.
Overlap that Ford's own validation is built to catch
Big-time operations bundle their access work. The published flat for a fan drive clutch on a 6.7L diesel already includes pulling the secondary alternator, because Ford's time study required it to reach the part. Stack a standalone R and I operation on top of that flat and the claim trips LOV, Ford's labor overlap and operations validation code. The published description is the authority: "Includes" means bundled, and "do not use with" lists are explicit.
Published times hiding on the engine-variant row
Large operations such as 6006B and 7000A render as a parent row with empty opcode and time cells, and a separate engine-variant row underneath carrying the real code and hours. Read the parent row alone and the job looks like it has no published time, which pushes an admin toward actual time on a repair that had a flat all along.
Actual time claimed by habit instead of by evidence
SLTS genuinely publishes "Actual Time" rows for work such as extended diagnosis. Those are the audit-safe path to time beyond a flat. An MT actual-time operation is the other legitimate path, but only when punch data and technician comments support the overage. The difference between the two, and claiming either without the backing documentation, is ordinary chargeback territory.
FSA admin work that pays and never gets claimed
On supply-constrained recalls Ford restricts parts to VIN-specific ordering through the Special Service Support Center, and publishes a companion operation with a Y suffix that pays the dealer for filing the attestation. Bulletin 23S65 Supplement #3 added exactly that: 23S65Y, 0.1 hours. It sits in the labor allowance table like any other operation, and it is the kind of line a busy desk never goes looking for.
Coverage and open actions checked after the fact
OASIS reports the warranty start date, the coverage windows, and any outstanding Field Service Actions for the VIN. Checking that after the repair order is closed is how a store discovers it performed campaign work as customer-pay, or missed a coverage window that was open the whole time.
How Forge prepares a Ford claim
The workflow Forge runs on Ford claims in production today.
- 01
Upload the Ford repair order
Drop the repair order into Upload. There is no DMS integration project and nothing for an IT vendor to schedule. Forge reads the labor lines, part numbers, technician narrative, and time punches off the document, including the CDK layouts most Ford stores print.
- 02
Forge looks up SLTS and OASIS for the VIN
Forge searches SLTS by operation number, part number, and section, reads the engine-variant rows where the real time lives, and pulls OASIS for warranty start date, coverage windows, and outstanding Field Service Actions. Causal part and dealer-typed opcode authority are respected rather than overridden.
- 03
Forge drafts the claim and runs Ford pre-checks
The draft is checked against what actually bounces or under-pays: does a picked combination operation need its base, does a second operation overlap time bundled into the first, is actual time backed by punch data, and are handling, paint, sublet, tow, rental, and coverage-window allowances present where the repair supports them.
- 04
Forge submits, or your administrator approves first
Exceptions surface with the reason attached, so the desk works judgment calls instead of transcription. Clean claims go out through your normal path, including the CDK WAR pre-validate screen where your store uses it, and payout is tracked back through the Claim Status Report.
Ford claim rules at a glance
What actually costs a Ford store money on a warranty claim, and the fix.
| Trigger | What it means | The fix before submit |
|---|---|---|
| LOV | Labor overlap and operations validation: a claimed operation duplicates access time already bundled into another line. | Read the published description. "Includes" means bundled; claim the flat alone, or take MT actual time instead of stacking. |
| Missing base operation | A combination operation such as 23943A10 was claimed without its base operation 23943A, so the line under-pays. | Claim the published base alongside the combination whenever the footnote calls for it. |
| Empty time cell | A big-time operation's parent row shows no opcode or hours because they live on the engine-variant row below it. | Read the variant row for the exact vehicle configuration before falling back to actual time. |
| Unsupported actual time | MT actual time claimed without punch data or a technician comment explaining the overage. | Use a published "Actual Time" row where one exists, or attach the punch evidence to the narrative. |
| Unclaimed FSA admin | A supply-constrained recall required VIN-specific SSSC part ordering, and the paid attestation operation was never claimed. | Claim the Y-suffix companion operation the bulletin publishes, such as 23S65Y at 0.1 hours. |
Ford warranty terms
The vocabulary a Ford warranty administrator works in every day.
- SLTS
- Straight Line Time Standards. Ford's published labor operations and times, searchable by operation number, part number, or section.
- PTS
- Professional Technician Society. Ford's repair information portal, and the route to the Vehicle ID tab and bulletin PDFs.
- OASIS
- Ford's VIN lookup: warranty start date, coverage windows, and the outstanding Field Service Action panel.
- FSA
- Field Service Action. Ford's umbrella term for recalls, customer satisfaction programs, and similar campaign work.
- SSSC
- Special Service Support Center. Ford's FSA support desk, and the route for VIN-specific part orders on supply-constrained recalls.
- LOV
- Ford's labor overlap and operations validation rejection, raised when a claimed line duplicates bundled access time.
- MT actual time
- An actual-time operation claimed in place of a published flat when clocked hours are materially higher and documented.
- Causal part
- The part that caused the failure. Ford adjudicates against it, so it has to agree with the operation claimed.
Frequently Asked Questions
- What is Ford warranty claim software?
- Ford warranty claim software reads repair orders and prepares warranty claims for a Ford or Lincoln store. Forge matches each line to a published SLTS operation, checks OASIS coverage and outstanding Field Service Actions, and flags overlap and missed allowances before anything is filed. Forge can submit on its own, or hold the claim for your warranty administrator to approve first: your store decides.
- Does Forge submit Ford warranty claims for us?
- Yes, if you want it to. Forge can file a Ford claim as soon as it passes the pre-submission checks, or hold it for your warranty administrator to approve first. Your store sets which, and Forge handles the repetitive entry and the checks that come before it either way.
- Does Forge replace PTS, OASIS, or SLTS?
- No. Technicians keep using PTS for repair information, and Ford still adjudicates against SLTS and OASIS. Forge reads those sources for you and applies what they say to the repair order in front of it, so the lookup work stops being manual.
- How does Forge catch a Ford labor overlap before we submit?
- Forge treats a published operation's own description as the authority. Text reading "Includes" means that work is bundled and must not be claimed again, and operations publish explicit do-not-use-with lists. When a picked line would duplicate access time already inside a flat, Forge flags it rather than letting the claim trip LOV after submission.
- Do we need a DMS integration to use Forge on Ford claims?
- No. There is no DMS wiring and no IT project. Your admins upload repair orders, and Forge works alongside CDK, Reynolds and Reynolds, and other DMS setups. Most dealerships are live in under an hour.
- Does Forge work for a store that sells both Ford and Lincoln?
- Yes. Ford and Lincoln claims run the same way and Forge handles both from one workflow. Rooftops carrying an additional franchise can run that brand through Forge as well, rather than maintaining a separate manual process per nameplate.
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.