How a CDRL decides whether your invoice gets paid on time

What a CDRL actually is

The CDRL (DD Form 1423) is the list of every data item the Government wants from you besides the hardware or service itself. That includes reports, plans, drawings, test data and software documentation. Each line points to a Data Item Description that explains the content and format.

The rule behind it hasn't changed. When data must be delivered, the form belongs in the solicitation. We found no sign of a rewrite of that requirement, and the form is still in routine use. A January 2026 Army solicitation attachment for a shipboard power pack uses the standard price-group layout. One vendor blog puts the current form edition at 02/22/2024. We couldn't confirm that against the official DoD forms page, so check it before you build templates around it.

So what: Treat the CDRL as part of the price and schedule, not as an attachment you skim after the technical volume is done.

The three boxes that quietly set your payment date

Most CDRL pain lives in three items on the form.

• Item 8 (draft approval). If a draft is required, the Government approves it before you prepare the final. That's an extra review loop with its own clock.
• Item 7 (inspection and acceptance). This says how the Government will inspect and accept the data item. Acceptance is usually the event that unlocks payment for that line, though your contract's payment terms control, so check them.
• Item 9 (distribution statement). This says who may see the data. A wrong or missing marking is a classic reason for a rejected submission.

Here's the mechanical problem. If your schedule assumes a final goes out on day 30, but a draft review plus a rejection and resubmission takes three cycles, the delay isn't on your Gantt chart. It's in your cash flow.

So what: For every CDRL line, write down who reviews it, how long they have, and what happens if they say nothing. Raise unclear answers before award, when you still have leverage.

What changed around the form in 2026

The form didn't move, but the data-rights rules around it did. Starting February 1, 2026, DoD issued class deviations as part of its overhaul of the DFARS. One of them (Class Deviation 2026-O0036) reworks the data-rights guidance. Here's what matters to you:

• The guidance now splits by commerciality. Commercial items and other-than-commercial items each get their own section.
• Several data-rights clauses were merged and given new numbers. The two main rights clauses for technical data and software became one, and the two validation clauses became one.
• Contracting officers are told to have offerors price each deliverable data or software item separately and identify restricted-rights data they will deliver. That is the same idea the CDRL price groups already serve.
• They are also told not to require you to give up rights in privately developed software or data as a condition of award.

Two cautions. A law firm reports the overhaul stretches the Government's window to challenge restrictive markings from three years to six after final payment or delivery. We couldn't verify that against the deviation text, so read it yourself. And a law firm also notes that most existing contracts keep the old clause numbers until modified. Your legacy CDRLs and your new bids may cite different numbering for the same ideas.

So what: Before your next proposal, check which version of the data-rights language your solicitation uses. Make sure your assertions list matches the data items on the CDRL.

A CDRL tracking template you can copy

Build one row per CDRL line and keep it alive after award. A spreadsheet works fine.

Field	What to write	Why it matters
CDRL number and title	Exact line and DID name	Avoids "which report?" arguments
Due date and frequency	One time, monthly, or event-driven	Late items stall acceptance
Draft required? (Item 8)	Yes or no, plus review days	Adds a full review loop
Acceptance method (Item 7)	Who inspects, how, how long	Sets when the line can be paid
Distribution statement (Item 9)	Marking and who approved it	Wrong marking means rejection
Separately priced?	Price group and amount in dollars	Shows what is at stake per item
Restrictions asserted	Data delivered with limited or restricted rights	Protects your private investment
Submitted / accepted dates	Actual dates with reviewer name	Proof when payment is questioned

So what: The last row is the one that saves you. When an invoice stalls, a dated record of submission and acceptance ends the conversation faster than any email thread.

What to do this week

1. Pull your active CDRLs and fill in the template above. Gaps in Items 7 and 8 are your risk list.
2. Confirm you are using the current DD Form 1423 edition from the official DoD forms page.
3. Read the 2026 data-rights deviation and the quality assurance and acceptance deviation (2026-O0035). We haven't read the latter, so we can't tell you what it changes for data acceptance.
4. Watch for a proposed rule that would turn these deviations into permanent text. We found none yet, and an open rights case on technical data is still on DoD's list.

One more note. We found no GAO protest decision specifically about a CDRL or DID dispute. Don't count on a protest to fix a CDRL problem. These issues get resolved in the contract file, so keep yours clean.

Reading a CDRL Before You Commit to It

Block	What It Tells You	The Trap	What To Ask
Data item description	The format and content required	A DID can be far heavier than the title suggests	Have we actually read the DID?
Frequency	How often it is due	Monthly for five years is 60 deliverables	Did we price the recurrence?
Approval code	Whether the government approves or just receives	Approval means rework cycles you do not control	How many review cycles are assumed?
Distribution	Who gets it	Wider distribution can affect your data rights markings	Are our markings right for this list?