MCL 780.621 application framework
Section 780.621 is the core application statute. The matter should show conviction type, eligibility theory, court, prosecutor notice, victim issues where relevant, and order status.
Educational guide
Michigan set-aside work combines application-based relief and Clean Slate automation.
Michigan uses set-aside terminology. Clean Slate automation changed the operating context, but defense teams still need to track application-based petitions, automatic set-aside verification, MSP records, court forms, and post-order effects.
Direct answer
A Michigan workflow should separate automatic set-aside verification from petition work.
Michigan's Clean Slate process began automatic set-asides in 2023 for eligible convictions, while MCL 780.621 and related provisions still govern application-based set-aside work. A defense workflow should track whether the matter is automatic, petition-based, marijuana-specific, or another set-aside path; then it should document court forms, MSP status, hearing events, order status, and client advice.
Regulatory framework
Michigan set-aside law is a statute sequence, not one expungement checkbox.
The Michigan Legal Core page references set-aside context. This guide goes deeper into Clean Slate automation and application-based practice.
Automatic set-aside under MCL 780.621g
Michigan State Police materials explain automatic set-aside processing. A workflow should track whether counsel is verifying automatic relief rather than preparing a petition.
Procedure under MCL 780.621d
Procedure and notice requirements belong in the matter record. The system should keep application, fingerprints or record materials, service, hearing, and court-order context together.
Effect under MCL 780.622
Client advice depends on the legal effect and exceptions. Store attorney-approved disclosure notes separately from public-facing matter labels.
Automatic relief requires verification evidence
Automatic set-aside can create a temptation to assume completion because the statute says qualifying records will be processed. A defense workflow should keep the actual source checked, the date checked, the result, and any attorney-approved follow-up.
Procedure walkthrough
Track set-aside path, court, MSP, and post-order effect.
Michigan practices need a workflow that keeps Clean Slate verification and petition drafting distinct.
Identify the set-aside path
Label the matter as automatic Clean Slate verification, application-based set-aside, marijuana set-aside, or another path. Avoid generic expungement labels when Michigan sources use set-aside.
Attach court and SCAO materials
Michigan set-aside work often relies on court forms and local court handling. Keep SCAO forms, local instructions, court notices, and signed orders with the matter.
Track MSP and ICHAT verification
For automatic relief, counsel may need to verify whether MSP records changed. The matter should store review dates, source checked, and follow-up tasks.
Keep Detroit court layers distinct
Detroit matters may involve 36th District Court misdemeanor history and Wayne County Circuit Court felony history. The workflow should identify which court owns each record.
Document client advice on remaining consequences
Set-aside relief may not erase every legal consequence. Client-facing language should be approved by counsel and tied to the relevant statute and order.
Preserve pre-Clean-Slate and post-Clean-Slate history
Michigan firms may have old expungement notes, newer set-aside petitions, and automatic Clean Slate verification in the same legacy system. Migration should keep those historical labels visible until counsel decides how each matter should be categorized.
Local variation
Michigan local court structure changes the file.
The statute is statewide, but Detroit and Michigan county practice require court-specific scoping.
Wayne County Circuit Court
Felony set-aside work in Detroit should anchor to Wayne County Circuit Court context, including filing, hearing, and order status.
36th District Court
Misdemeanor and district-court records should be handled separately from circuit-court files. The matter should preserve the original court and case number.
Automatic Clean Slate verification
Automatic set-aside can create a verification workflow even when no petition was filed. Store MSP, court, and client communication records together.
Professional licensing effects
State agency materials show that set-aside relief can intersect with professional licensing discipline. Those questions require attorney review and should not be reduced to a checkbox.
Implementation check
Test Michigan set-aside with both automatic and petition examples.
Michigan implementation should prove the system can handle Clean Slate verification and application-based files.
Use separate workflows for automatic and petition paths
Automatic Clean Slate review should not ask staff to prepare a court petition. Petition-based work should not be marked complete just because an automatic-relief source was checked.
Store MSP verification details
Keep the date checked, source reviewed, result, and follow-up action in the matter record.
Track court-specific forms and orders
SCAO forms, local court instructions, filed applications, notices, hearing dates, and orders should remain tied to the specific court.
Audit migration labels
Search old matter names, notes, tasks, and exports for charge text before trusting a set-aside label after migration.
Track professional licensing follow-up
When a client asks about licensing or employment consequences, the workflow should route the question to attorney review and preserve the source used, rather than turning set-aside status into a universal clearance label.
Practitioner review limits
Michigan set-aside analysis remains attorney-reviewed.
Clean Slate automation does not remove the need for legal review.
Eligibility stays with counsel
Michigan set-aside workflow can be represented as matter status, source references, packet tasks, and review notes. A lawyer decides whether MCL 780.621, 780.621g, marijuana-specific relief, or another pathway applies and what the client may accurately say after relief.
Court orders and agency handling control the record
Michigan courts, MSP records, SCAO forms, signed orders, and agency handling control the file. Software can keep the court, agency, prosecutor, rule, order, and follow-up context together, but a lawyer still reviews the controlling source before relying on it.
Sensitive record access needs separate decisions
Record relief files often include client history, law enforcement records, disposition documents, investigator notes, and privileged work product. Access, export, search visibility, and migration behavior should be scoped deliberately.
Migration needs a parallel review
Firms moving from Clio, MyCase, Smokeball, PracticePanther, Filevine, or a custom system should test old matters with sensitive titles, documents, notes, tasks, and calendar entries before cutover.
Butler workflow relevance
Legal Core can organize Michigan set-aside work without deciding Clean Slate eligibility.
Legal Core can keep set-aside path, statute reference, court, SCAO forms, MSP verification, hearing status, signed order, sensitive labels, and migration checks near the matter. It does not determine eligibility, query ICHAT automatically, file applications, or guarantee agency updates.
Related Butler pages
Move from Michigan set-aside procedure to local Legal Core context.
FAQ
Common Michigan set-aside workflow questions.
Is this Michigan set-aside workflow guide legal advice?
No. It is an educational workflow guide for criminal defense practices. Eligibility, deadlines, filings, notices, objections, remedies, and client advice remain attorney-reviewed. Treat the page as a source map for software evaluation, then confirm the controlling statute, court form, local rule, and matter record before making any client-facing conclusion.
Can Butler automatically decide Michigan set-aside workflow eligibility or compliance?
No. Legal Core can organize dates, documents, review status, source references, assignments, and sensitive matter labels. It does not determine legal eligibility, legal compliance, or filing strategy. If a workflow requires legal judgment, the system should expose the source and review owner instead of converting that judgment into an automated approval.
Why does this page cite state and local sources for Michigan?
The state statute supplies the legal framework, but implementation often turns on court forms, clerk instructions, local filing practice, prosecutor response, and post-order record handling. That is why the source list combines statewide law with county, city, court, or agency materials where they affect the practical workflow.
How should a firm use this page during software evaluation?
Use it to build demo scenarios from real matters. Test how the system stores orders, petitions, sensitive records, court dates, review notes, local court references, and migration artifacts. A good demo should include a clean matter, an edge-case matter, and an old migrated matter so the team can see how exceptions are handled.
Does Butler claim direct court filing or court data integration here?
No. These educational pages describe firm-side organization and implementation scoping. Direct filing, court feeds, or automated submissions would require separate validation. Where court portals, clerk systems, or agency databases are mentioned, the claim is about keeping the firm-side workflow organized around those authorities.
Where should a practitioner go next after reading this Michigan set-aside workflow guide?
Start with Michigan Legal Core for geographic context, then review Legal Core pricing if user count, trial timing, founding cohort eligibility, and migration are the buying questions. For regulated or deadline-sensitive workflows, bring one attorney-reviewed sample matter into the evaluation so the product conversation stays tied to real practice rather than abstract feature labels.
Sources checked
Michigan claims are tied to MCL provisions, MSP materials, court resources, and Detroit court context.
Sources include Michigan set-aside statutes, Michigan State Police Clean Slate materials, Attorney General expungement assistance, SCAO resources, trial court resources, and Detroit court context.
Michigan MCL 780.621Michigan MCL 780.621cMichigan MCL 780.621dMichigan MCL 780.621gMichigan MCL 780.622Michigan State Police: Clean SlateMichigan State Police: Conviction Set Aside Public InformationMichigan Attorney General: Expungement AssistanceMichigan Courts: SCAO FormsMichigan Courts: Trial CourtsWayne County Third Circuit Court Criminal Division36th District Court Criminal Division
Next step
Evaluate Michigan set-aside with both petition and Clean Slate scenarios.
A useful review should show application-based petition work, automatic Clean Slate verification, MSP status, local court forms, sensitive access, and post-order review.