CIT Forced-Labor Tariff Cases Still Have Motions, Not Orders
The parties proposed 26-03345 as a master case and asked to finish merits briefing by September 29. At the verified cutoff, the public docket showed motions and unsigned proposed orders, not operative deadlines.
Defendants asked the court to designate 26-03345, brought by Burlap & Barrel and Collective Horology, as the master case. The plaintiffs did not oppose that request. In a separate joint motion, all parties proposed an accelerated merits schedule. The first pages of both filings are unsigned proposed orders. Their judge and date lines are blank.
That distinction creates the immediate operating problem. The requested dates are useful preparation targets. They were not verified as court deadlines at the cutoff. Counsel and policy teams should run a preparation calendar and an operative court calendar until a later docket entry joins them.
The docket shows requests, not orders
The same two requests appear across the three dockets. The scheduling motion is ECF 9 in 26-03345, ECF 12 in 26-03347, and ECF 10 in 26-03467. The case-management filing is ECF 10, ECF 13, and ECF 11, respectively.
The public feed labels the case-management entries as Motion to Alter/Amend/Correct. The filing itself is titled Defendants' Unopposed Motion for Case Management Order. Neither event label is an entered order. The word ORDER at the top of a party's proposed form does not change that status.
This is a narrow but consequential distinction. A news alert can accurately describe what the parties requested without establishing what the court ordered. An internal deadline should identify the docket event that made it operative. Here, the cited events were motions.
The proposed master case would be a filing hub, not one combined action
The proposed case-management order would designate 26-03345 as the master case. Documents filed in 26-03347 and 26-03467 would also be filed in 26-03345 to the extent applicable and treated as filed in each individual action. The proposal then says the cases would otherwise proceed without formal consolidation.
That design is administrative. It can reduce duplicate filing and give the court one place to manage common papers. It does not make the plaintiffs interchangeable. The Burlap importer case, the Learning Resources group, and the state plaintiffs remain separate parties in separate actions unless a later order says otherwise.
Coordination also does not answer class status or remedy. The Burlap complaint requests certification of an importer class, but no class-certification order was verified at the cutoff. No verified order stopped collection, protected liquidation, granted refunds, or extended relief to absent importers. Master-case routing, formal consolidation, class certification, and relief are four different questions.
That is why this analysis does not replace Traverse's work on economy-by-economy severability, the state plaintiffs' refund boundary, or USTR's decision chain. The new issue is docket control. A shared filing channel can coexist with different claims, standing records, entries, and requested remedies.
The requested calendar still compresses preparation
The parties proposed that USTR file an index of the agency record on August 10. They proposed that each plaintiff file a separate motion for judgment on the agency record under USCIT Rule 56.1 on August 14. The four-day interval is the most important feature of the request for working teams.
Those dates were not operative at the cutoff. They still show how quickly the case could move if the court enters the proposal without material change. A team that waits for the order to begin preparing may have only a short period to compare the index with the record it expected to see.
The rest of the proposed sequence is also compressed. The proposal gives each plaintiff motion a 14,000-word limit. The government would file one consolidated response of up to 30,000 words on September 15. Plaintiffs would file replies of up to 7,000 words each on September 29, followed by a joint appendix on October 2. The proposal asks for oral argument at the earliest available date in October, but leaves the date, time, and courtroom blank. It does not establish an October hearing.
The motion says expedited merits briefing is intended to avoid the need for preliminary injunction proceedings. That describes the parties' proposed procedural bargain. It does not stop collection, protect liquidation, or supply interim relief.
The parties propose an index under U.S. Court of International Trade Rule 73.3 on the agency record, followed by a joint appendix after briefing rather than the full record at the outset. An index is a map of what USTR identifies as the record. It is not the underlying collection of every indexed document, and it does not establish that the record is complete.
The record index matters because the USTR final action in 91 FR 47318 rests on 60 investigations and a common implementation framework. The index will show how USTR organizes the material it considers part of the reviewable record. The parties may disagree about completeness, organization, or whether a document belongs in that record. Those disputes are not resolved by the scheduling motion.
Run two calendars until the docket changes
The first calendar is a preparation calendar. It should contain the parties' requested dates, clearly marked proposed. Teams can use it to allocate work, reserve review time, and identify who will compare the agency-record index with the expected source file.
The second calendar is the operative court calendar. It should contain only deadlines established by a court entry, with the order number, filing time, and any later amendment. If the court adopts the proposed dates, the same event can then move from the preparation calendar to the operative calendar.
Event
Status at the cutoff
Working response
Designate 26-03345 as master case
Requested in unopposed motion
Monitor all three dockets until a court entry establishes routing
USTR agency-record index on August 10
Proposed
Prepare an expected-record checklist, do not label the date court ordered
Separate Rule 56.1 motions on August 14
Proposed
Assign merits teams and source owners now
Consolidated government response on September 15
Proposed
Reserve review capacity, keep the date conditional
Plaintiff replies on September 29
Proposed
Track separately for each plaintiff group
Joint appendix on October 2
Proposed
Identify document and citation owners
October oral argument
No date, time, or courtroom proposed
Do not calendar a hearing
Each calendar entry should carry four fields: event type, status, source, and verification time. Event type distinguishes a motion, proposed order, entered order, and amended order. Status prevents a preparation target from being repeated as a legal deadline. Source links the entry to the official docket. Verification time makes later changes auditable.
A practical alert should say, for example, Joint motion proposes August 10 agency-record index, not USTR record due August 10. If the court later enters the order, the alert can identify the order and change the verb.
What teams should do now
Counsel should monitor the master-case request and the individual dockets. Until routing is entered, a filing in one docket should not be assumed to control the others.
The policy team should build an expected-record map from the notices, hearing materials, comments, presidential direction, and final action already in its file. The purpose is not to decide a future completeness dispute in advance. It is to make the short proposed interval between index and merits motions usable.
Customs teams should keep collection, entry, and liquidation work separate from the briefing calendar. A case-management order would not itself protect entries or create a refund path. Any operational change must come from the exact terms of a later injunction, judgment, or CBP instruction.
Client and management updates should preserve the status words. Requested, proposed, entered, amended, and effective are not interchangeable. The fastest way to lose control of a live litigation calendar is to remove those verbs in a summary.
What would change the calculus
A court-entered case-management order would establish whether 26-03345 becomes the filing hub and how papers in the other actions are treated. A court-entered scheduling order would make dates operative, subject to its actual text.
The calculus would also change if the court enters different dates, word limits, or briefing architecture. An amended order could change an earlier deadline. A filed agency-record index would replace the expected-record map with a document that can be tested. The three Rule 56.1 motions would show which issues the plaintiffs actually place before the court.
An oral-argument notice would supply the date, time, courtroom, and any allocation among the plaintiff groups. Until that event appears, October is a requested window, not a scheduled hearing.
Caveats
This account is limited to the public record available at 6:39 p.m. ET on August 4, 2026. The first pages of the two filings are proposed orders with blank judge and date lines, and the motions follow. A later docket entry could make the requested coordination and dates operative.
Until a later order says otherwise, the requests do not formally consolidate the cases, certify a class, protect entries, or grant any remedy. The proposed schedule can guide preparation while remaining nonoperative. That is the point of the two-calendar approach.
Free account
Keep reading with a free account.
Today's analysis is open to everyone. A free account opens the full archive and full tool output. No card required.