## Bottom-line recommendation StreamLedger should **not** ask for a broad six-month discovery stay, and it should not simply file a full merits opposition without preserving the record that the certification motion is premature. The best course is a **combined, limited approach**: 1. **File a short, targeted motion** asking the court to: - **defer certification briefing/hearing only for a limited period**, and - **compel production of specific named-plaintiff account files** that StreamLedger already requested and that the plaintiffs promised but did not produce. 2. **File a present-record opposition to class certification** — or, if the court allows a conditional filing, a short “preliminary opposition” — so that StreamLedger does not waive the argument that certification should be **denied now** if the court declines to defer. 3. **Do not request broad merits discovery.** Ask only for the narrow set of documents necessary to decide standing, typicality, and predominance for the three named plaintiffs. 4. **If the court grants deferral and the files are produced**, file a supplemental opposition based on what the files show. **If the court denies deferral**, proceed to full merits opposition and argue that the full class fails on the present record. This approach fits the governing rule allowing the court to defer certification and compel targeted discovery when the movant controls specific, previously requested information essential to standing, typicality, or predominance, and when broad delay for unfocused discovery is not appropriate. --- # I. Standing, Typicality, and Adequacy of the Named Plaintiffs on the Present Record The certification motion fails, or at least should be held, on the present record because the three proposed representatives have material evidentiary gaps that go to the prerequisites for class treatment, not merely to merits details. ## A. General standard applied here Under the assumed rules: - A class may be certified only if the representatives have **standing**. - The representatives’ claims must be **typical** of the class. - The representatives must be **adequate**. - Standing and typicality must be shown from **evidence**, not allegations alone. - Material uncertainty about a representative’s **enrollment path, assent, refund status, or personal loss** may defeat or postpone certification. Plaintiffs’ argument that the missing files are “merits details” is not correct on this record. The missing files go directly to whether the named plaintiffs are proper representatives and whether common proof can support the class. ## B. Milo Chen — mobile enrollment, uncertain assent ### 1. Standing Milo alleges he enrolled on mobile and was charged the $7.95 fee. On the present record, he may have a facially colorable payment injury. But the record does not clearly establish that he suffered an **unreimbursed** economic loss. He has not produced: - bank or card statements, - refund records, - chargeback records, - employer-reimbursement records, or - confirmation emails. If the ledger or bank records show a full refund or completed chargeback, he lacks the required unreimbursed loss. ### 2. Typicality Milo alleges mobile enrollment, but mobile enrollment involved a **preselected box** and a link explaining the free ordinary option. Milo does not remember: - whether the box was already selected, or - whether he opened the linked explanation. Those facts matter because they bear on: - what representation he actually saw, - whether he was exposed to the preselected-fee presentation, - whether he assented to the fee, - whether his claim arises from the same conduct and legal theory as the mobile subclass. On the present record, Milo cannot show typicality for a mobile subclass, and he certainly cannot show typicality for the full proposed class, which includes desktop, legacy, and call customers. ### 3. Adequacy Milo’s uncertainty about the assent mechanics may make him a less than ideal representative. That uncertainty is curable if StreamLedger’s transaction logs, confirmation emails, or UI records show what was presented and whether the link was opened. But on the present record, the court should not certify a class based on a representative whose own enrollment mechanics are materially uncertain. **Conclusion for Milo:** Certification should be **postponed** pending production of his enrollment and payment files, or **denied** if the court declines to defer and the record remains incomplete. ## C. Tara Vale — call enrollment, no date or representative identified ### 1. Standing Tara alleges a call-center representative told her the fee was mandatory. That allegation, if proven, could support a consumer-statute claim. But she does not remember the date or representative. Without the date, StreamLedger cannot locate: - the call log, - the agent, - the script version, - any retained recording, or - the corresponding charge and refund records. On the present record, her payment injury and unreimbursed loss are not fully established. ### 2. Typicality The call enrollment path used **six different scripts**, and StreamLedger retained only samples of recordings from each script period. Tara’s claim depends on what was said in her particular call. Because she cannot identify the call date or representative, she cannot show that her claim arises from the same script or course of conduct as other call customers. Her claim may be typical of a narrow “call script” subclass only if her call can be tied to a specific script and that script was materially uniform. That cannot be shown on the present record. ### 3. Adequacy A representative who cannot identify the date, agent, or script of the call is a poor candidate to manage a class whose core liability question turns on oral representations. Tara’s inability to identify the call may make her inadequate to represent call customers, let alone the full class. **Conclusion for Tara:** Certification should be **postponed** pending production of her bank/card statement, call-related records, and refund records. If the court declines to defer, certification should be **denied** because her standing, typicality, and adequacy are not established. ## D. Jae Morgan — ambiguous refund/chargeback status ### 1. Standing Jae alleges no refund was received. But StreamLedger’s ledger contains an ambiguous “CB-R” code that could mean either: - a completed chargeback, or - a rejected chargeback request. If the code means a completed chargeback, Jae did not suffer an unreimbursed loss. If it means a rejected request, he may have. This is not a minor ambiguity. It goes directly to the required **unreimbursed economic loss** element. ### 2. Typicality Jae cannot be a typical representative of a class of unreimbursed-loss claimants if his own loss status is disputed by the record. The court cannot certify a damages class where the representative’s own damage status is materially uncertain. ### 3. Adequacy Jae’s adequacy also depends on resolving the CB-R ambiguity. A representative whose loss status is unclear cannot adequately protect the interests of a class whose damages depend on unreimbursed loss. **Conclusion for Jae:** The court should order production of the ledger explanation, payment-processor records, and bank/card statements. If the ambiguity is not resolved, certification should be **denied**. ## E. Adequacy of the trio as a group Even if each named plaintiff’s individual gaps were cured, the three together are inadequate to represent the full proposed class of 62,400 customers because: - one alleges mobile enrollment, - one alleges call enrollment, - the third’s path is not specified, - none is identified as a desktop or legacy representative, - their claims involve different representations, different assent mechanics, and different proof requirements. A representative group that spans materially different enrollment paths without showing common proof is not adequate to represent the full class. --- # II. Common Liability Questions Versus Enrollment-Path-Specific Questions The plaintiffs rely on one marketing page and the common backend queue. That is not enough. ## A. What is genuinely common The following questions are common or can be answered from common records: 1. **Did StreamLedger charge a $7.95 priority-processing fee?** Yes, the records show that. 2. **Can class membership be identified?** Yes, to the extent “charged” is the definition. 3. **What was the average backend performance of priority processing?** Yes, the backend data shows an 18-hour average weekday improvement and no average weekend improvement. 4. **What are the enrollment-path counts?** Yes, StreamLedger’s records identify the four paths and their approximate sizes. But these common facts do not establish the consumer-statute or contract elements for every class member. ## B. What is not common: representation, reliance, causation, and assent The liability questions are path-specific. ### 1. Consumer-statute exposure The consumer statute requires that each claimant was exposed to a deceptive representation or omission. The four enrollment paths involved materially different disclosures: - desktop: separate unchecked box with clear fee disclosure and free ordinary option; - mobile: preselected box with a link explaining the free option; - legacy: email link landing page disclosing the fee only in linked service terms; - call: six different scripts with oral representations. There is no materially uniform representation across all four paths. Therefore, reliance cannot be inferred for the full class. ### 2. Causation Causation also varies by path: - desktop customers affirmatively checked a box; - mobile customers proceeded with a preselected box, but some may have seen the link and still not unselected it; - legacy customers enrolled through an email link where the fee appeared only in terms; - call customers were exposed to different oral statements. Whether the representation caused the payment is not a single class-wide question. ### 3. Contract assent The contract claim depends on the terms presented and assented to by the customer. Assent records differ materially: - desktop: unchecked checkbox; - mobile: preselected checkbox with link; - legacy: service terms linked from landing page; - call: oral script and any post-call confirmation. Therefore, contract liability is highly path-dependent. ## C. Common backend queue is not enough The common backend queue may show that the fee was processed and that average performance varied by weekday/weekend. It does not show that every customer saw the same representation or that the representation caused each payment. The one marketing page cited by plaintiffs may be common, but it is not shown to be the representation that each class member actually saw at enrollment. --- # III. Predominance for the Consumer-Statute Claim ## A. Full proposed class: individualized questions predominate For the full class of every person charged the fee, the following individualized questions predominate: 1. **Which enrollment path did the customer use?** Desktop, mobile, legacy, or call. 2. **What exact representation or omission did the customer encounter?** This varies by path and, for calls, by script. 3. **Was that representation materially deceptive or an omission?** This depends on the disclosure. 4. **Can reliance be inferred?** Only from a materially uniform representation. There is no materially uniform representation across all four paths. 5. **Did the representation cause the payment?** This depends on the enrollment mechanics. 6. **Did the customer receive a full refund or completed chargeback?** Yes for 5,400 full refunds and 1,180 chargebacks, at least facially. 7. **Did the customer personally bear the expense if paid on an employer card?** Unknown for 7,900 employer-card payments. 8. **Did the customer receive a benefit?** Weekend performance shows no average improvement; weekday performance shows an 18-hour average improvement. 9. **What is the unreimbursed economic loss?** Depends on refunds, chargebacks, employer reimbursement, and possibly benefit offsets. These individualized questions go to liability, causation, and damages. They predominate over the few common questions. ## B. Desktop customers The desktop presentation was a separate unchecked box stating: > “Add priority verification for $7.95; ordinary verification remains available at no charge.” This is strong evidence against a uniform deception theory for desktop customers. They saw a clear, affirmative opt-in disclosure. They also affirmatively selected the fee. For desktop customers: - consumer-statute deception is weak; - reliance inference is weak; - contract recovery is weak because they knowingly and separately selected the fee under a disclosed term. A class of desktop customers is unlikely to be appropriate. ## C. Mobile customers The mobile path used a preselected box stating: > “Priority processing, $7.95,” with a link explaining the free ordinary option. This path may support a narrower theory that the preselected presentation was materially deceptive or misleading. But even within the mobile group, the court needs to know: - whether the UI was materially uniform across the class period; - whether the customer saw the link; - whether the customer unselected or left selected the box; - whether the customer was refunded or charged back; - whether the customer personally bore the expense; - whether the customer received a weekday or weekend benefit. A mobile subclass or mobile issue class is more plausible than a full class, but it is not certified on the present record. ## D. Legacy customers Legacy customers enrolled through an email link whose landing page disclosed the fee only in the linked service terms. That path may support an omission theory, but the court needs to know: - whether the landing page and terms were materially uniform; - whether the customer opened the terms; - whether the customer received a confirmation email; - whether the customer was refunded; - whether the customer personally bore the expense. A legacy subclass or issue class is possible in theory, but not on the present record. ## E. Call customers The call path is the weakest for class treatment. There were six scripts. StreamLedger retained only sample recordings from each script period. Tara Vale cannot identify the date or representative. For call customers, the court would need to determine: - which script was used; - what the agent said; - whether the statement was materially deceptive; - whether the customer relied on it; - whether the customer was refunded; - whether the customer personally bore the expense. Because the oral communications differ, and because recordings are only sampled, individualized proof likely predominates for call customers. --- # IV. Predominance for the Contract Claim The contract claim is even weaker for class treatment. ## A. Contract claim depends on terms and assent A contract claim depends on: - the terms presented to the customer, - the customer’s assent, - enforceability of the disclosed term, - whether the customer knowingly and separately selected the fee. A customer cannot recover a fee that the customer knowingly and separately selected under an enforceable disclosed term. ## B. Desktop contract claim Desktop customers saw a clear unchecked box and affirmatively added the fee. That is strong evidence that they knowingly selected the fee under a disclosed term. The contract claim for desktop customers is likely barred. ## C. Mobile contract claim Mobile customers saw a preselected box and a link explaining the free option. Whether that constitutes knowing selection depends on the terms, UI, and customer conduct. But because the fee was disclosed, the contract claim may still fail. At minimum, it requires individualized proof of the terms and assent. ## D. Legacy contract claim Legacy customers had the fee disclosed in linked service terms. Whether that was sufficient for contract assent depends on the presentation and the customer’s conduct. Again, individualized proof is required. ## E. Call contract claim Call customers were exposed to six scripts. Contract assent depends on what was said and how the customer agreed. Individualized proof is required. ## F. Contract predominance For the full class, the contract claim fails predominance because the terms, disclosures, and assent records differ by enrollment path. --- # V. Effect of the Four Disclosure Paths, Six Call Scripts, Weekday/Weekend Performance, and Differing Assent Records The defendant does not need to argue that “every customer is different.” It is enough to connect material variations to elements or remedies. | Variation | Element or remedy affected | Consequence | |---|---|---| | Four disclosure paths | Deceptive representation/omission; reliance; causation; contract terms | No common proof across full class | | Six call scripts | Oral representation; reliance; causation | Individualized proof; possible script subclasses only | | Weekday vs. weekend performance | “No benefit” theory; damages model | No class-wide no-benefit model | | Differing assent records | Contract claim | Individualized proof | | Refunds and chargebacks | Unreimbursed loss | Individual deductions | | Employer-card payments | Personal economic loss | Individual proof or exclusion | These variations are not abstract. They map directly to the consumer-statute elements and the contract elements. ## A. The “uniformly hidden” allegation is contradicted The complaint alleges the fee was uniformly hidden. The records show at least four different presentations: - desktop: clear separate unchecked box; - mobile: preselected box with link; - legacy: fee only in linked terms; - call: six scripts. That is not uniformly hidden. It is varied disclosure. ## B. Weekday and weekend performance defeats a class-wide no-benefit theory The complaint alleges the fee provided no benefit. Backend records show: - weekday priority processing reduced average verification time by 18 hours; - weekend priority processing produced no average improvement. If plaintiffs rely on a “no benefit” theory, the class cannot include all customers. At minimum, the court must decide whether to: - narrow the class to weekend verifications, - require a benefit offset for weekday customers, or - require plaintiffs to specify how weekday performance affects damages. The complaint’s broad no-benefit allegation is not supportable for the full class. --- # VI. Refunds, Chargebacks, Employer Payments, and the Required Damages Model ## A. Refunds and chargebacks must be deducted StreamLedger issued: - 5,400 full fee refunds; - 1,180 processed chargebacks. Those customers likely do not have unreimbursed economic loss, unless the records show otherwise. A damages model that simply assigns $7.95 to every class member would be defective. The out-of-pocket model must deduct: - full refunds, - completed chargebacks, - employer reimbursements or other offsets, depending on the certified theory. ## B. Employer-card payments require individual proof StreamLedger’s business-account field identifies 7,900 payments made on employer cards. But the field does not establish whether the customer: - personally reimbursed the employer, or - personally bore the expense. If the customer did not personally bear the expense, the customer may not have a personal unreimbursed economic loss. This is an individualized question for each employer-card customer. ## C. The damages model must match the certified theory If the certified theory is out-of-pocket loss, the model should be: > $7.95 > minus full refunds > minus completed chargebacks > minus employer reimbursement or other offset, > possibly adjusted for benefit depending on the theory. If the certified theory is “no benefit,” then the model must address the weekday 18-hour improvement. The court should not certify a class where the damages model is inconsistent with the certified theory. ## D. Class-wide damages are not manageable without account-level records The class includes customers with different: - refund status, - chargeback status, - employer-payment status, - verification dates, - weekday/weekend performance, - benefit received. A class-wide full-refund damages model is not appropriate. --- # VII. Could an Issue Class or Subclasses Cure the Variations? Yes, some variations can be cured by subclasses or issue classes, but not all, and not on the present record. ## A. Path-based subclasses The court could consider subclasses by enrollment path: 1. **Desktop subclass** Likely not appropriate. The disclosure was clear and the customer affirmatively selected the fee. 2. **Mobile subclass** More plausible. The preselected box may present a common deception/omission question. 3. **Legacy subclass** Plausible if the landing page and terms were materially uniform. The fee-only-in-terms presentation may raise a common omission question. 4. **Call subclasses** Possible only if the six scripts can be grouped into materially similar categories and the call records can identify which customers received which script. As currently presented, call customers are too varied. ## B. Issue class The court could certify a narrower issue class, for example: - “Was the mobile preselected box materially deceptive or misleading?” or - “Was the legacy fee-only-in-terms disclosure materially misleading?” An issue class can separate the common liability question from individual damages. That may be appropriate if: - the named plaintiff for that issue has standing and typicality, - the representation was materially uniform, - individual damages can be managed through records or a common model, - the proceeding remains manageable. But an issue class does not cure the current named-plaintiff defects. ## C. Weekend/weekday damages issue The court could also consider a damages issue class or subclass based on weekday versus weekend verification. For example: - weekend customers may support a no-benefit theory; - weekday customers may require a benefit analysis. But this does not cure the enrollment-path variations. ## D. What subclasses or issue classes do not cure They do not cure: - uncertainty about the named plaintiffs’ standing, - uncertainty about refunds or chargebacks, - uncertainty about employer reimbursement, - the need for individual damages deductions, - the need to identify the exact representation and assent for each path. So subclasses may be a possible endpoint, but not a reason to certify the current full class. --- # VIII. The Exact Named-Plaintiff Materials That Matter and Why The following documents are not broad merits discovery. They go to the prerequisites for certification. ## A. For all three named plaintiffs ### 1. Original confirmation emails **Why:** They can show the exact enrollment representation, fee disclosure, terms presented, and date. ### 2. Bank or card statements **Why:** They show: - whether the fee was charged, - the charge date, - whether the card was personal or employer, - whether the charge was reversed, - whether a refund was received. This is critical for standing, personal loss, and damages. ### 3. Refund or chargeback records **Why:** They show whether the customer suffered unreimbursed loss. This is especially important for Jae Morgan because of the ambiguous “CB-R” code. ### 4. Employer-reimbursement records **Why:** They show whether the customer personally bore the expense if the payment was made on an employer card. ### 5. Communications concerning enrollment **Why:** They may show the representation, reliance, or post-enrollment clarification. ## B. For Milo Chen ### 1. Mobile transaction logs or UI records **Why:** They can show: - the mobile enrollment screen, - whether the box was preselected, - whether the customer opened the link, - whether the customer unselected the box before payment. ### 2. Confirmation email **Why:** It may show the fee disclosure and terms as presented to him. ### 3. Bank/card statement **Why:** It shows the charge, date, card type, and any reversal. ### 4. Refund/chargeback records **Why:** They show whether he has unreimbursed loss. ## C. For Tara Vale ### 1. Bank/card statement showing the charge date **Why:** The date is necessary to locate the call log, agent, script, and any retained recording. ### 2. Call logs or metadata **Why:** They can identify: - the call date, - the agent, - the duration, - the script version, if recorded. ### 3. Any retained call recording or notes **Why:** They can show whether the agent said the fee was mandatory. ### 4. Confirmation email or post-call summary **Why:** It may confirm the enrollment representation and terms. ### 5. Refund/chargeback records **Why:** They show whether she has unreimbursed loss. ## D. For Jae Morgan ### 1. Explanation of the “CB-R” code **Why:** The ledger entry is ambiguous. The code may mean completed chargeback or rejected request. The meaning determines whether he has unreimbursed loss. ### 2. Payment-processor records **Why:** They can confirm whether the chargeback was completed or rejected. ### 3. Bank/card statement **Why:** It can show whether the money was returned to him. ### 4. Employer-reimbursement records, if applicable **Why:** They show whether he personally bore the expense. ## E. Why StreamLedger’s database is not enough by itself StreamLedger’s database may show that a customer was charged and the general enrollment path. But it does not necessarily show: - the exact screen the customer saw, - whether the customer opened the link, - the exact call statement made, - whether the customer personally reimbursed an employer, - whether a chargeback was completed, - the customer’s personal bank records. For the named plaintiffs, their own files are necessary to establish standing, typicality, and adequacy. --- # IX. Strategic Choice: Deferral, Opposition, Broad Discovery, or a Combination? ## A. Immediate denial Immediate denial is available as an argument, but it should be presented as the alternative if the court is unwilling to defer. On the present record, certification should be denied because: - the named plaintiffs’ standing, typicality, and adequacy are not established, - there is no materially uniform representation across the full class, - individualized questions predominate, - the damages model is not yet reliable, - the full class is not superior to feasible alternatives. But because the missing files are specific, previously requested, and promised, a limited deferral is more appropriate than demanding immediate denial as the only relief. ## B. Broad six-month discovery stay StreamLedger should **not** request a broad six-month stay. That would be overbroad and likely inappropriate because: - the missing information is specific, - it was requested four months ago, - the plaintiffs promised to produce it by June 1, - the court only needs targeted discovery to decide certification prerequisites, - broad delay for unfocused discovery is not permitted. A six-month stay would also invite the court to view StreamLedger as seeking delay rather than a focused resolution. ## C. Full merits briefing now StreamLedger should be prepared to brief the merits now, but it should not do so without preserving the argument that the certification motion is premature. If the court denies the deferral motion, StreamLedger should file a full opposition and argue that certification must be denied on the present record. ## D. Combined approach The best approach is: 1. **Move for limited deferral and targeted production.** 2. **Oppose certification on the present record.** 3. **If production occurs, supplement the opposition.** 4. **If production is denied or not made, seek denial of certification.** This avoids overreaching, preserves all arguments, and aligns with the rule allowing targeted discovery before certification briefing. --- # X. Concrete Filing Sequence for the Next 21 Days The following sequence is practical and avoids overstating what the missing files will prove. ## Day 1–2: Serve a focused production demand and meet-and-confer request StreamLedger should send a short written demand to plaintiffs’ counsel that: 1. reminds them of the prior request made four months ago; 2. notes their agreement to produce by June 1; 3. lists the specific documents needed for Chen, Vale, and Morgan; 4. requests production within a short deadline, such as 10 days; 5. asks for a meet-and-confer call or email exchange; 6. states that the documents are essential to standing, typicality, and predominance, not broad merits discovery. The demand should include a proposed document list: - original confirmation emails; - bank or card statements; - refund and chargeback records; - employer-reimbursement records; - enrollment confirmation screenshots or UI records in their possession; - call-related communications; - any other records showing the named plaintiff’s enrollment path, assent, refund status, or personal loss. The letter should include a careful phrase such as: > StreamLedger does not ask the court to assume that the missing files will establish any defense. It asks only that the named plaintiffs produce the specific records necessary to show that they have standing and are typical and adequate representatives, as required before certification. ## Day 3–5: File the limited motion to defer and compel targeted production StreamLedger should file: **Defendant’s Motion to Defer Certification Briefing and Compel Targeted Production of Named Plaintiffs’ Account Files** The motion should ask the court to enter an order that: 1. stays certification briefing and hearing only for a limited period; 2. compels production of the specified documents for the three named plaintiffs; 3. sets a short production deadline, such as 10–14 days; 4. sets a short supplemental briefing period after production, such as 14–21 days; 5. does not authorize broad merits discovery; 6. preserves StreamLedger’s right to oppose certification if production is not made. The motion should include: - the prior request letter; - the plaintiffs’ June 1 production promise, if documented; - the certification motion; - a proposed order; - a document-by-document explanation of decisional significance. The proposed order could say: > IT IS ORDERED that, within 14 days, plaintiffs shall produce for each named plaintiff the specific documents identified in the exhibit, subject to a protective order. > > Defendant shall produce corresponding account, ledger, call-log, refund, chargeback, and performance records for the named plaintiffs to the extent in its possession, custody, or control. > > Certification briefing and hearing are stayed only until 21 days after substantial compliance with this order. > > If plaintiffs fail to produce the requested documents, the court may deny certification or preclude reliance on the named plaintiffs’ accounts. > > No broad merits discovery is authorized by this order. ## Day 5–10: Request a status conference If the court has not set a hearing, StreamLedger should request a brief status conference. The purpose is not to litigate the merits but to set a narrow schedule for production and supplemental briefing. The status letter should say: - the documents were previously requested; - plaintiffs promised to produce them; - they did not produce them; - the documents are essential to standing, typicality, and predominance; - StreamLedger seeks only a limited deferral. ## Day 10–14: Follow up on production If plaintiffs have not produced: - send a short follow-up letter; - note that the court’s deadline or requested deadline has passed or is approaching; - reserve the right to seek enforcement. If plaintiffs produce: - log the production; - review it promptly; - prepare a short status report if the court wants one; - do not assume the files prove StreamLedger’s case; instead, analyze what they show about standing, typicality, and predominance. ## Day 15–20: File a present-record opposition or conditional opposition Unless the court has already granted a deferral that expressly extends the opposition deadline, StreamLedger should file an opposition before the 21-day deadline. The opposition should be framed carefully: > On the present record, certification should be denied. If the court grants defendant’s motion to defer and compel targeted production, this opposition is without prejudice and defendant requests that merits briefing be stayed until after production. If the court denies deferral, defendant submits this opposition on the present record. The opposition should include: 1. named-plaintiff deficiencies; 2. lack of common representation; 3. predominance problems for consumer-statute and contract claims; 4. effect of the four disclosure paths and six call scripts; 5. weekday/weekend performance problem; 6. refund/chargeback/employer damages problem; 7. request for denial of the full class; 8. optional invitation to consider subclasses or issue classes only after proper discovery. This preserves the argument that the court should not certify the class now. ## Day 21: File any required reply or status report If the court requires a reply to plaintiffs’ opposition to the deferral motion, file it by the deadline. If the court has granted deferral and production is pending, file a short status report if needed. If the court has denied deferral, ensure the opposition is complete and on time. --- # XI. Recommended Relief in the Motion StreamLedger should ask for a narrow order, not a broad stay. ## A. Requested relief 1. **Compel targeted production** for the three named plaintiffs within 10–14 days. 2. **Stay certification briefing/hearing** only until 21 days after substantial compliance. 3. **Require a certification of completeness** for the production. 4. **Allow a protective order** for bank, card, employer, and reimbursement records. 5. **State that broad merits discovery is not authorized.** 6. **State that failure to produce may result in denial of certification or preclusion of reliance on the named plaintiffs’ accounts.** ## B. What not to request Do not request: - a six-month stay; - broad class discovery; - all account files for all 62,400 customers at this stage; - an inference that the missing documents prove StreamLedger’s defense. The motion should be precise: the court needs specific named-plaintiff files to decide whether certification is appropriate. --- # XII. How to Frame the Missing Files Without Overstating StreamLedger should avoid saying: > The missing files prove the named plaintiffs lack standing. Instead, it should say: > The present record contains material uncertainty about each named plaintiff’s enrollment path, assent, refund status, or personal loss. Under the governing rules, that uncertainty requires the court either to defer certification and compel targeted production or to deny certification on the present record. StreamLedger does not ask the court to assume what the missing files will show. It asks only that the named plaintiffs produce the specific records necessary to establish that they are proper representatives. This framing is stronger because it is accurate and does not invite the court to view StreamLedger as seeking delay. --- # XIII. Likely Endpoints ## A. If the court grants deferral and plaintiffs produce StreamLedger should then analyze the files and file a supplemental opposition. Possible outcomes: - if a named plaintiff lacks standing, move to deny or strike that representative; - if a named plaintiff is not typical, argue denial; - if the files show the full class is not common, argue denial of the full class; - if the files show a viable mobile or legacy subclass, consider whether to consent to a narrow class or continue opposing it. ## B. If the court grants deferral but plaintiffs fail to produce StreamLedger should seek an order that: - denies certification, or - precludes reliance on the nonproducing named plaintiff’s account, or - imposes another appropriate sanction consistent with the court’s discretion. The key is to tie the consequence to the prerequisite problem: standing, typicality, or adequacy. ## C. If the court denies deferral StreamLedger should proceed to full merits opposition and argue that certification must be denied now because: - the named plaintiffs’ standing and typicality are not established; - there is no materially uniform representation; - individualized questions predominate; - the damages model is not reliable; - the full class is not superior. --- # Final Recommendation StreamLedger should file a **limited motion to defer certification briefing and compel targeted production** of the three named plaintiffs’ specific account files, and it should simultaneously preserve a **present-record opposition** to class certification. It should not request a broad six-month stay. It should not argue that the missing files will prove the merits. It should ask the court to require only the narrow records necessary to determine whether the named plaintiffs have standing, are typical, and can represent a class whose liability and damages questions are not common across all 62,400 customers.