Minnesota telecommunications-fraud defense guide
Telecommunications and Information Services Fraud under Minnesota Statutes § 609.893
Minnesota Statutes § 609.893 reaches three materially different accusations. Subdivision 1 concerns a person who, intending to evade a lawful charge, obtains telecommunications service for that person’s own use by fraudulent means. Subdivision 2 separately makes it a felony to make, offer, or advertise a device or information in order to facilitate another person’s subdivision 1 violation, or to make, assemble, or possess a device designed or adapted for service fraud or concealment. The correct defense analysis begins by identifying the charged provision, not by treating every disputed account, code, call, device, or network event as the same offense.
I separate the billing dispute, service record, device theory, and criminal intent.
If you hire me, I identify the exact subdivision and charged verb; the provider and service; the Minnesota connection; the account, device, code, or information involved; what service was actually obtained; whose use it served; the lawful charge allegedly evaded; the alleged fraudulent means; and the valuation method. For a facilitation count, I test what was made, assembled, possessed, offered, advertised, or supplied, how it was designed or adapted, and what evidence connects it to another person’s proposed subdivision 1 violation.
Section 609.893 does not create one generic telecommunications offense
Subdivision 1 and the two alternatives in subdivision 2 require different proof. A complaint should identify the subdivision, but the discovery and proposed jury instructions must reveal the state’s actual theory.
Intent to evade
The service-fraud theory requires an intent to avoid a lawful charge, not merely nonpayment, confusion, or an account dispute.
Service obtained
The person must obtain telecommunications service; an unsuccessful plan may raise other questions but does not silently satisfy this completed-offense verb.
Own use
Subdivision 1 expressly says the service is obtained for the person’s own use. The user, subscriber, payer, device holder, and beneficiary may be different people.
Fraudulent means
The prosecution must identify the particular misrepresentation, code, account method, manipulation, or other means it contends was fraudulent.
Offer or supply
Subdivision 2(1) reaches making a device or information available—or offering or advertising it—with the purpose of facilitating another’s subdivision 1 violation.
Device design
Subdivision 2(2) reaches making, assembling, or possessing a device designed or adapted for service fraud or specified concealment.
| charged theory | Conduct and mental-state focus | Classification trigger |
|---|---|---|
| Subdivision 1 | With intent to evade a lawful charge, obtains telecommunications service for the person’s own use by fraudulent means. | Value controls: misdemeanor through $500; felony above $500. |
| Subdivision 2(1) | Makes available, offers, or advertises a device or information in order to facilitate another’s subdivision 1 violation. | Felony regardless of a stated service-value threshold. |
| Subdivision 2(2) | Makes, assembles, or possesses a device designed or adapted to violate subdivision 1 or conceal service existence, origin, or destination. | Felony regardless of a stated service-value threshold. |
The state must commit to the selected statutory alternative
“Telecommunications fraud” is not enough. A subdivision 1 case should specify the service, use, lawful charge, fraudulent means, value, and acts attributed to the accused person. A subdivision 2(1) case should identify what was made available, offered, or advertised, to whom, and how the purpose to facilitate another’s service fraud is shown. A subdivision 2(2) case should identify the device, the charged act, its design or adaptation, and whether the theory is fraud or concealment. When alternatives materially differ, notice, discovery, instructions, unanimity, and the verdict form should be evaluated on the actual record.
The object must fit the telecommunications statute’s own vocabulary
Section 609.892 supplies definitions specifically for this statutory scheme. Similar words in Minnesota’s computer-crime provisions do not automatically carry the same definition.
Telecommunications service
The service must be provided or offered in exchange for pecuniary consideration and transmit messages, signals, facsimiles, or other communication between physically separated persons. The listed means include telephone, telegraph, cable, wire, fiber-optic cable, or projected energy without a physical connection. It must originate or end, or both originate and end, in Minnesota. That text makes the service’s commercial character, function, endpoints, and Minnesota nexus actual proof questions.
Telecommunications device
A device can be an instrument, apparatus, equipment mechanism, operating procedure, or code designed or adapted for a particular use and intended or usable in violation of § 609.893. The nonexclusive examples include hardware, software, programs, email systems, voicemail systems, identification-validation systems, private branch exchanges, and other means of facilitating service. Because the definition is broad, the defense should demand technical evidence about the particular object rather than accept the label “device.” Ordinary hardware or software with lawful uses does not prove the charged design, adaptation, purpose, possession, or connection by itself.
Access device and credit-card number
An access device is a card, plate, code, account number, or other account-access means usable alone or with another access device to obtain telecommunications service. A credit-card number under this section concerns a supplier-issued identification card or plate permitting service on credit, and the definition includes its number or description even when no physical card is produced. These definitions matter to records and aggregation. They are not interchangeable with the separate “access device” definition in Minnesota’s computer-crime statute, § 609.87.
Provider
A telecommunications provider can be a person, firm, association, or private or municipal corporation that owns, operates, or manages facilities used to provide the service. The state should identify the provider, its facilities or role, and the witness or records capable of establishing the lawful charge and service delivery.
| Defined term | Statutory core | Defense question |
|---|---|---|
| Telecommunications service | Paid transmission between physically separated persons with a Minnesota origin or endpoint. | What was transmitted, for consideration, between whom, by what system, and with which Minnesota endpoint? |
| Telecommunications device | Instrument, mechanism, procedure, or code designed/adapted and intended or usable for § 609.893 conduct. | What feature supplies the alleged design or adaptation, and what lawful functions or users exist? |
| Access device | Account-access means usable alone or together to obtain service. | Was it valid, assigned, authorized, used, and capable of obtaining the charged service? |
| Provider | Private or municipal person or entity owning, operating, or managing service facilities. | Which entity supplied the service and proves the lawful charge and value? |
Obtaining service by fraud requires more than an unpaid bill
Intent to evade a lawful charge
The statute requires a purpose directed at a lawful charge. Evidence may include account creation, false credentials, bypass steps, repeated warnings, altered configuration, concealment, messages, payments, refunds, internal instructions, or admissions. But late payment, inability to pay, an expired card, a disputed invoice, a provider’s billing error, auto-renewal confusion, unauthorized account activity, or a good-faith coverage or contract dispute does not automatically establish intent. The defense should reconstruct what the person understood when the service was obtained, not infer intent solely from a later balance.
The word “lawful” also matters. The charging theory should identify the charge the provider was entitled to impose for the service at issue. Contracts, tariffs, rate plans, credits, promotions, usage classifications, roaming arrangements, wholesale agreements, business-authority records, taxes, and adjustments may affect the amount. A criminal court is not a routine collection forum; the state still must prove the statutory intent and conduct beyond a reasonable doubt.
Obtains service
Provider data should show that covered service was delivered, not merely that someone possessed a code or attempted access. Session records, call-detail records, routing logs, usage records, account records, switch or PBX data, network events, invoices, and knowledgeable testimony can bear on whether service occurred. An alert, login, configuration file, or installed program may support an inference, but each must be connected to actual statutory service and to the accused person.
For the person’s own use
This phrase should not disappear from the analysis. A billed subscriber may not be the caller or user; a device holder may be acting for an employer, household member, customer, or unknown third party; and credentials may be shared, stolen, cloned, or compromised. The state should identify the practical beneficiary and prove that the accused obtained the service for the accused’s own use. A subdivision 2 theory may fit an alleged supplier more closely, but the prosecution cannot rewrite subdivision 1 to omit its express text.
By fraudulent means
The statute does not provide a separate exhaustive definition of “fraudulent means,” and official exact-citation research did not locate a published Minnesota appellate opinion comprehensively defining the phrase in § 609.893. The state should therefore identify the concrete means alleged and prove why it was fraudulent under controlling law and instructions. Defense review can test whether the accused made or adopted the representation, whether it was false, whether the account or code was authorized, whether a system defect rather than deception produced the service, and whether incomplete records make an innocent explanation reasonable.
Identity and attribution cannot be assumed from an account name
Account names, IP addresses, device identifiers, subscriber records, email addresses, phone numbers, cookies, and payment instruments can be relevant without being conclusive. NAT, shared networks, public Wi-Fi, VPNs, remote administration, device resale, family or employee use, credential compromise, SIM changes, spoofing, automation, and provider data-retention practices can complicate attribution. A reliable analysis links the person, device, account, event, service, and time through multiple authenticated sources.
The conduct structure dates to 1990; the misdemeanor fine changed in 2004
1990 Minnesota Laws chapter 494 enacted §§ 609.892 and 609.893. Sections 1 through 7 became effective August 1, 1990 and apply to crimes committed on or after that date. The original law already contained the current $500 and $2,500 value dividing lines, the ten-year and five-year felony ceilings, the aggregation provision, and the subdivision 2 facilitation theories. Its lowest tier carried a $700 maximum fine.
2004 Minnesota Laws chapter 228, article 1, section 72 directed the Revisor to change specified misdemeanor maximum fines from $700 to $1,000, including the fine in § 609.893. It did not change this statute’s value thresholds or felony ceilings. For an old alleged offense, counsel should retrieve the official edition in force on the conduct date rather than apply today’s fine retroactively or describe the 2004 instruction as a wholesale restructuring.
| Period | Relevant law | Practical effect |
|---|---|---|
| Before August 1, 1990 | Section 609.893 was not yet effective. | Do not apply this enactment to earlier conduct. |
| August 1, 1990 through the 2004 fine revision | Current conduct theories and value thresholds; lowest tier stated a $700 maximum fine. | Use the official offense-date edition and any other then-applicable general law. |
| Current law | Lowest tier states up to 90 days and/or $1,000; felony thresholds and ceilings remain as enacted. | Match each alleged act and aggregated amount to the correct date and tier. |
Continuing conduct needs a dated transaction record
A case may span recurring bills, sessions, calls, account changes, code distributions, or device possession. The state should identify the acts and values assigned to each period and its aggregation theory. The defense should not assume that the last event makes every earlier act subject to later law. Limitations, venue, amendment, ex post facto, jury-instruction, and sentencing questions depend on the charge and dates and require case-specific research.
Provider summaries should be tested against the native records
Build one chronology across the provider, account, device, and person
A useful timeline identifies account creation and changes, authorization, device assignments, access-device issuance, alleged service events, endpoints, invoices, credits, payments, complaints, warnings, configuration changes, advertisements or offers, seizures, interviews, and evidence collection. Time-zone conversion, daylight-saving changes, clock drift, log rollover, retention windows, and provider normalization can create false sequences unless documented.
Obtain the underlying data and data dictionary
A spreadsheet or investigator-selected screenshot may omit fields, filters, failed events, reversals, user roles, system-generated actions, or alternative accounts. Seek native exports, schemas, field definitions, query parameters, audit logs, error records, retention policies, billing calculations, and the person who can explain them. Determine whether records reflect actual service, an attempted session, a rating event, a duplicated entry, an estimate, or a later adjustment.
Authenticate messages, listings, code, and devices
Rule 901 requires evidence sufficient to support a finding that the item is what its proponent claims. Account ownership alone may not prove authorship. Examine headers, message identifiers, account history, recovery methods, login records, device artifacts, recipients, drafts, edits, timestamps, backups, and corroborating context. For software or code, preserve the exact version, hash, dependencies, configuration, compilation method, and execution environment.
Apply the original-writing and summary rules carefully
Rule 1002 may require the original when a party seeks to prove content, subject to the evidence rules’ provisions for duplicates and other proof. Rule 1006 permits summaries of voluminous admissible material when the underlying originals or duplicates are made available as required. A chart is not self-validating. Review source completeness, admissibility, formulas, excluded categories, deduplication, time windows, and whether a visual combines distinct accounts or users.
Relevance and unfair prejudice remain separate
Rules 401 and 403 govern relevance and exclusion when probative value is substantially outweighed by specified dangers. Technical sophistication, encrypted communications, privacy tools, foreign infrastructure, aliases, or possession of network utilities can sound suspicious without proving the statutory elements. The court should evaluate the actual connection to intent, service, use, fraud, facilitation, design, adaptation, or concealment.
Discovery should disclose the government’s technical method
Minnesota Rule of Criminal Procedure 9 governs disclosure. Depending on the case, defense requests may address provider returns, warrants, affidavits, extraction reports, images, logs, source records, expert reports, tools and versions, validation, notes, translations, demonstratives, valuation support, exculpatory information, and evidence of other users or compromise. Protective orders may be appropriate for proprietary systems or sensitive credentials, but they should not prevent meaningful testing.
Exactly $500 is a misdemeanor; exactly $2,500 is the middle felony tier
The statutory boundaries are precise. “In excess of $2,500” means more than $2,500. “More than $500 but not more than $2,500” includes $2,500 but excludes $500. “All other cases” includes $500 and below. The charging value must reflect the covered telecommunications services, not automatically a provider’s entire claimed loss, equipment cost, investigative expense, contractual penalty, or later remediation.
Test what the invoice measures
Ask whether the provider’s amount is a retail rate, wholesale cost, marginal cost, plan overage, tariff, contract price, list price, international rate, tax-inclusive charge, estimate, or adjusted bill. Promotions, bundles, included minutes or data, credits, reversals, duplicate events, failed sessions, roaming settlement, taxes, and fees can affect the number. The applicable statutory measure should be briefed from the actual law and evidence rather than assumed.
Aggregation requires one scheme or course of conduct
Subdivision 3(b) permits—not automatically compels—aggregation of amounts involved under one scheme or course of conduct, whether associated with the same or several credit-card numbers. The state should identify which events it aggregates and what unifies them. Time gaps, different users, different purposes, unrelated accounts, intervening authority, distinct methods, or separate providers may matter. The defense should also guard against double counting and ensure that acquitted, unproved, or noncovered amounts are not silently included in the conviction tier.
Value is an offense-level fact, not just a sentencing detail
Because the value bracket changes subdivision 1 from a misdemeanor to a five- or ten-year felony, the state must prove the bracket required for the charged conviction under applicable constitutional and Minnesota law. Instructions and verdict forms should let the factfinder decide the supported threshold rather than return an undifferentiated finding followed by judicial guesswork.
Current law has one misdemeanor tier and three felony theories
| Conviction theory | Current statutory maximum | Current Guidelines ranking |
|---|---|---|
| Subdivision 1, value $500 or less | Misdemeanor: 90 days and/or $1,000 | Not a felony-grid conviction. |
| Subdivision 1, value over $500 through $2,500 | Felony: five years and/or $10,000 | Severity level 2. |
| Subdivision 1, value over $2,500 | Felony: ten years and/or $20,000 | Severity level 3. |
| Subdivision 2(1) or (2) | Felony: five years and/or $10,000 | Severity level 2. |
Minimum fines do not create a universal custody minimum
Section 609.893 states no universal mandatory minimum jail or prison sentence. Section 609.101 separately supplies 30-percent minimum-fine starting figures of $300 for the $500-or-less misdemeanor, $3,000 for the over-$500-through-$2,500 felony and either facilitation felony, and $6,000 for the over-$2,500 felony. The misdemeanor figure is subject to a lower uniform Judicial Council fine schedule. Qualifying public-defender status, indigence, or undue hardship permits reduction to at least $50; community work service may substitute for a fine; and installments may be authorized. For a felony, the current Guidelines use the conviction offense’s severity level and the person’s criminal-history score to identify a presumptive disposition and duration, subject to controlling statutes, custody-status rules, departure law, and the version applicable on the offense date. The statutory maximum remains an outer ceiling, not a prediction. For the misdemeanor tier, felony-grid rankings do not apply.
Restitution must be tied to compensable loss
Sections 611A.04 and 611A.045 govern restitution procedure and decision factors. A provider may claim unpaid service value and other losses, but the court must apply the statutes to the offense of conviction and the evidence. Examine causation, documentation, reasonableness, duplication, insurance or recovery, ordinary overhead, upgrade costs, investigation expenses, and the defendant’s ability to pay as applicable. A restitution request does not prove guilt or the conviction value bracket.
Multiple counts require a § 609.035 analysis
Service fraud may be charged with identity theft, computer offenses, theft, accomplice liability, conspiracy, or other conduct. Section 609.035 can limit multiple punishment for offenses arising from a single behavioral incident, subject to statutory exceptions and fact-specific analysis of time, place, and criminal objective. It does not automatically erase counts or guarantee concurrent sentences. Preserve the issue at plea, trial, and sentencing.
Collateral consequences depend on the conviction record
A fraud-related felony can affect employment, professional licensing, financial or fiduciary work, government contracting, immigration, housing, and access to information systems. Those effects vary by offense, disposition, agency, occupation, status, and current law. Immigration advice should come from qualified immigration counsel reviewing the actual plea and record. This page does not promise expungement, licensing eligibility, or a particular collateral result.
Test each element before debating the size of the provider’s loss
Identify the exact statutory alternatives
Start with the complaint, probable-cause statement, citation, grand-jury record if any, and proposed instructions. Determine whether the case alleges obtaining service, offering or supplying a device or information, or making, assembling, or possessing a designed/adapted device. If the state blends theories, seek particulars through the procedures available and preserve notice and unanimity issues.
Challenge intent rather than treating nonpayment as fraud
Reconstruct the contract, account history, billing notices, disputes, payment attempts, credits, permissions, service plan, and communications. Identify provider errors, compromises, shared access, employment authority, household arrangements, automatic processes, and good-faith misunderstandings. The prosecution must prove intent to evade a lawful charge under subdivision 1 or facilitation purpose under subdivision 2(1), not merely an unfavorable account outcome.
Prove or disprove actual covered service
Trace each alleged event from raw record to billed service. Determine whether it was completed, failed, reversed, duplicated, included in a plan, or attributable to another account or user. Confirm the statutory Minnesota origin-or-endpoint requirement. Test whether the provider witness understands the underlying system or only a report prepared for litigation.
Separate user, subscriber, device holder, and beneficiary
Analyze who registered the account, controlled credentials, possessed each device, initiated the event, received the communication, benefited from the service, and paid or was expected to pay. Use device artifacts, location data where lawfully obtained, work schedules, witnesses, account changes, network topology, and compromise evidence. Avoid overstating any single identifier.
Examine device design and lawful use
For subdivision 2(2), obtain the actual device, code, or image in a reproducible form. Identify every component and claimed modification; test its function; compare documentation and version history; and preserve lawful uses and authorization. Challenge an opinion that jumps from capability to statutory design or adaptation without a reliable technical method.
Audit value and aggregation independently
Recalculate the service value from source records and the correct plan. Remove duplicates, failed events, unrelated users, unsupported rates, nonservice items, and amounts outside the charged scheme or period. Decide whether the record supports $500 or less, more than $500, or more than $2,500. The difference changes classification and Guidelines ranking.
Review search, seizure, statements, and private collection
Examine warrants, particularity, affidavits, scope, execution, consent, subpoenas, provider disclosures, private searches, interrogation, Miranda issues, device access, cloud process, retention, and chain of custody. Constitutional and suppression outcomes depend on the facts and current law. A defense page should identify the questions without promising exclusion.
Compare the provable theory, supported value, and collateral priorities
A proposed resolution should identify the exact subdivision, value, factual basis, Guidelines classification if felony, restitution framework, and treatment of related counts. Avoid a factual basis that casually admits service for the accused’s own use, intent to evade, another person’s intended violation, device design, or concealment unless the client understands the language and evidence supports it. Compare plea exposure with litigable authentication, intent, attribution, service, nexus, device, valuation, and aggregation issues.
For trial, organize the proof by element rather than by technical drama. A subdivision 1 presentation should trace provider, service, Minnesota endpoint, lawful charge, event, user, own use, fraudulent means, intent, and value. A subdivision 2 presentation should trace the charged verb, object or information, accused person’s connection, recipient or device function, facilitation purpose or design/adaptation, and any concealment theory. Proposed instructions and verdict forms should keep those alternatives intelligible.
Keep native account, billing, device, and communication evidence
Preserve the complaint, warrants, provider notices, complete bills, rate plans, contracts, credits, payment records, dispute records, account exports, messages, email, advertisements, repositories, source code, documentation, device images, serial numbers, logs, access records, employment or household permissions, and names of people who understood the arrangement. Save native files with metadata when possible rather than screenshots alone.
Do not delete messages, wipe devices, alter code, reset equipment, access someone else’s account, test credentials, contact witnesses to coordinate accounts, or attempt to reproduce the alleged bypass. Those actions can destroy evidence, create new network events, violate orders or law, and complicate attribution. Counsel can identify short-retention provider data, send lawful preservation requests, use appropriate experts, and seek discovery without creating a second problem.
Minnesota telecommunications-fraud questions
Is an unpaid telecommunications bill automatically criminal fraud?
No. Subdivision 1 requires intent to evade a lawful charge, covered service obtained for the person’s own use, and fraudulent means. A civil billing dispute or inability to pay does not by itself prove those elements.
Is the charge always a felony?
No. A subdivision 1 case involving $500 or less falls in the “all other” misdemeanor tier, with a maximum of 90 days and/or $1,000. Values above $500 and both subdivision 2 theories are felonies.
What happens at exactly $2,500?
Exactly $2,500 is within the middle tier—more than $500 but not more than $2,500—carrying up to five years and/or $10,000. The ten-year tier requires a value in excess of $2,500.
Can separate service events be added together?
Amounts may be aggregated when they are involved in one scheme or course of conduct, even across several credit-card numbers. The state should identify the included events and prove the unifying scheme rather than simply total every disputed charge.
Must someone actually use a device before subdivision 2 applies?
Not necessarily. Subdivision 2(1) includes making available, offering, or advertising with the required facilitation purpose. Subdivision 2(2) includes making, assembling, or possessing a device with the required design or adaptation. The selected theory’s exact language controls.
Does ordinary network software count as an illegal telecommunications device?
Not automatically. The definition is broad, but the state must connect the particular instrument, procedure, or code to the statutory design, adaptation, intent or usability and prove the charged theory. Lawful function and context matter.
Does the service need a Minnesota connection?
Yes. The § 609.892 definition applies when the telecommunications service originates or ends, or both originates and ends, in Minnesota. Records should identify the relevant endpoints and service.
What Guidelines severity level applies?
Current felony rankings list level 3 for subdivision 1 over $2,500 and level 2 for the subdivision 1 felony at $2,500 or less and for subdivision 2. The $500-or-less misdemeanor tier is not a felony-grid conviction. Offense-date Guidelines and criminal history still require review.
When did the statute take effect?
August 1, 1990, for crimes committed on or after that date. The conduct theories and value thresholds were enacted then. A 2004 Revisor instruction changed the lowest-tier maximum fine from $700 to $1,000.
What should I preserve for a lawyer?
Keep complete bills, plans, contracts, dispute and payment records, provider notices, native messages, account exports, devices, code, documentation, permissions, logs, and court papers. Do not delete, alter, or test accounts or equipment.
Continue with the computer, theft, and court-process pages
A lawyer’s file review of Telecommunications and Information Services Fraud; Crime Defined in Minnesota
The first pass through a criminal file should be exact, not dramatic. I want the statute and subdivision, the alleged date, the conduct the State says satisfies each element, and the source for every fact that raises the degree or punishment.
Read the count as a set of propositions the State must prove
For Telecommunications and Information Services Fraud; Crime Defined in Minnesota, the governing text begins with Minn. Stat. §§ 609.893 and 609.892. That citation matters because a familiar charge name can contain several statutory routes, definitions, and sentencing rules. I read the exact count, the alleged date, and every incorporated definition before deciding which facts are material and which allegations are simply part of the narrative.
Next, I connect each material fact to evidence the prosecution can actually present. The source might be a witness, a recording, a certified record, laboratory work, device data, or an admissible inference—but it should be identifiable and testable. That approach shows whether the real dispute concerns what happened, how evidence was obtained, whether it is admissible, or whether it proves the required element at all.
The evidence I would ask for first
For Telecommunications and Information Services Fraud; Crime Defined in Minnesota, I would not begin with a canned list of defenses. I would begin with the source file: ownership and authorization records, contracts, receipts, valuation material, surveillance video, access logs, account and device records, messages, witness interviews, inventory and loss calculations, restitution support, and the evidence offered to prove identity, intent, entry, possession, value, force, or lack of consent. A police summary can identify what an officer or witness says happened, but it cannot substitute for the recording, photograph, data, or document being summarized. The same is true of a complaint. It identifies the prosecution’s theory at the start of the case; it does not prove the theory.
I put those materials on one chronology. That lets me see what was known at each decision point, which account was contemporaneous, what appeared only after people spoke with one another, and where the record is silent. It also keeps an admissibility question separate from a factual one. A fact can be disputed even if the evidence was lawfully obtained. Evidence can also be accurate yet inadmissible for a particular purpose. Those are different arguments and should not be blurred together.
Read the charging document against the offense date
The alleged date matters because statutes, penalty thresholds, definitions, sentencing rules, and published decisions change. I save the version in force on that date and read the session-law history when the current online text is different. I also check whether a later amendment was merely clarifying or made a substantive change; that is a legal question, not an assumption. The same discipline applies to prior convictions and administrative events. A prior must fit the definition the charged statute actually uses, fall within any stated lookback period, and be proved by a reliable record.
I then compare the formal count with the probable-cause narrative and the discovery. If the prosecution’s theory shifts, I want the amended pleading and enough detail to prepare. If several factual alternatives are alleged, I identify whether they are separate elements, alternative means, enhancement facts, or merely evidentiary details. That distinction affects notice, motions, jury instructions, unanimity arguments, and how a verdict form should be read.
Separate an evidentiary weakness from a suppression issue
Not every troubling fact produces a motion to suppress. Suppression ordinarily requires a constitutional, statutory, or rule-based violation with a remedy that reaches the evidence at issue. A weak identification, an incomplete investigation, or a witness inconsistency may be powerful at trial without making evidence inadmissible. By contrast, a stop, search, interrogation, identification procedure, warrant, or test can raise a legal issue even when the resulting evidence appears incriminating. I analyze both tracks and do not promise dismissal simply because one problem exists.
For a search issue, I reconstruct what officers knew before each intrusion and what authority they claimed. For a statement, I examine custody, questioning, warnings, voluntariness, recording, and the complete context. For scientific or technical evidence, I request the method, underlying data, quality-control material, uncertainty information, and chain of custody. For hearsay or confrontation questions, I identify the actual statement, its purpose, the declarant, and the proposed foundation. Specificity matters; “the evidence is bad” is not a motion.
Prepare negotiation and trial at the same time
A plea decision should be compared with the case the State could present at trial, not with the complaint’s maximum penalty in isolation. I want to know the strongest admissible proof, the weakest required element, the realistic motion practice, the likely instructions, and the consequences of every proposed disposition. That includes custody, probation, treatment, restitution, driving, firearm restrictions, registration, employment or licensing, immigration consultation, family-court effects, and record consequences when they are actually triggered. I avoid telling a client that every collateral consequence applies to every conviction.
Trial preparation gives negotiation its credibility. Witness interviews, exhibit review, motions in limine, expert consultation, demonstrative evidence, jury instructions, and a clean theory of the case force both sides to confront what can be proved. Negotiation can continue while that work is underway. The two tracks are not opposites.
A case-law point worth keeping in its proper place
Appellate decisions matter, but a quotation should not be detached from the issue the court was deciding. In State v. Fleck, 777 N.W.2d 233, 236 (Minn. 2010), the Minnesota Supreme Court described sufficiency review as viewing the evidence “in the light most favorable to the conviction.” That is an appellate-review rule, not a reduction of the State’s trial burden. At trial, the prosecution still must prove every element beyond a reasonable doubt. I cite the case for the proposition it actually decided and then return to the charged statute, the jury instructions, and the admissible evidence in the present file.
What I would want you to understand before choosing an outcome
You should be able to identify the exact charge, the facts that set its level, the disputed elements, the evidence that matters most, the motions that have a legal basis, the realistic trial issues, and the concrete effect of each proposed resolution. If an answer depends on a missing report, recording, expert opinion, or certified record, I will say so. An honest answer about what remains unknown is more useful than a confident guess.