Projects Deep-Dive • Car-Mart Technology Group

You just spent four minutes walking Claude through the Silverado 2014 repossession decision. You covered the broken promises in the collector notes, the title status in Dealertrack, the fact that the back lot already holds seven vehicles, and why this one doesn't qualify for another extension. Next week another Silverado with the same pattern arrives. You type the same context all over again.

A Project stops that loop. Once the context lives inside the Project, you open it and only paste the new account details.

What a Project actually carries

A Project is a named Car-Mart workflow with persistent memory. It is not a folder. It is the exact bundle of systems, criteria, and prior decisions you need every time that workflow appears.

Example: "Car-Mart Repossession Decision" Project

Three-system context: Dealertrack (title and lien status), RouteOne (payment history and extensions), Excel collector notes (contact attempts and broken promises)
Decision criteria: Number of broken promises to pay, prior extensions granted, current back-lot count, title status, and whether the vehicle has been located
Conversation history: The last six similar decisions (including outcomes) so patterns remain visible without retyping

The three Projects you will build during this session

Each one is built around a real recurring workflow that already exists in your stores.

PROJECT 1

Car-Mart Payment Deferral Decision

Pine Bluff store pattern • 11 on-time, 2 missed

The account shows eleven on-time payments followed by two missed. You need to decide whether a one-month deferral is reasonable or whether it simply delays repossession.

Redacted Altima example with exact 11+2 payment pattern

Last three deferral decisions from Pine Bluff (with outcomes)

Regional extension guidelines

PROJECT 2

Car-Mart Weekly Collector Assignment

Jonesboro region • 11 stores

Every Monday you assign field collectors across eleven stores using current delinquency aging and bankruptcy flags. The assignment must be defensible if questioned later.

Last week's redacted assignment spreadsheet

Current delinquency report format from the 11 stores

Store-level bankruptcy flag rules

PROJECT 3

Car-Mart Repo-to-Auction Decision

Conway store • F-150 example

A repossessed F-150 has a reconditioning estimate. You compare that cost against current wholesale value and decide whether to repair or send straight to auction.

Conway reconditioning estimate template

Three prior F-150 decisions with final sale prices

Current wholesale market notes for that trim level

Files to attach to every Project

1

One redacted account sample that shows the exact pattern this workflow handles (Silverado with broken promises, Altima 11+2, F-150 reconditioning numbers).

2

Prior similar cases — at least three real decisions from the last 60–90 days, including what was decided and what actually happened.

3

The relevant regional policy document or internal guideline the team actually references when these decisions are made.

When to create a Project

Create a Project for any workflow you run more than three times in a month.

Repossession decisions (Silverado 2014 pattern)

Payment deferral requests (11 on-time + 2 missed)

Weekly field collector assignments (11 stores)

Repo-to-auction decisions (F-150 reconditioning estimate)

Charge-off determinations (located vehicle + prior lienholder + 1 payment in 90 days)

Customer call script generation (deferral granted, denial, follow-up)

Audit log entries (three facts required for defensible record)

Regional escalation memos (weekly out-of-pattern accounts)

T3+ stretch goal

After the Real-work exercise topic, take the specific workflow you chose and turn it into a Project before you leave. This becomes your Monday-morning artifact.

What each person leaves with

One named Project with the correct files attached and the context already loaded. Ready to open on Monday morning when the next Silverado, Altima, or F-150 lands on your desk.