codeforboston / codeforboston/docassemble-maexpungement

Expungement App: Outstanding design questions

Open
#6 3 comments 0 reactions 1 assignee Claimed by @jeremylang View on GitHub
Dominant language
Python
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Design Follow Up:

- [ ] 1. “isn’t noted in the criminal record” vs “not sure” single button, but feels like they might go in different directions
- [x] 2. Where do we educate the user on the ability to enter multiple forms? Feels like there is an opportunity when asking about MA cases and again when we start the docket collection process
- [ ] 3. Attach supporting docs (optional) - do users need this if they already have the document in hand? Seems like they could just print it themselves so that we don’t need to run those documents through the cloud.
- [x] 4. From Chris: Maybe unify missing doc into one step? (missing docket sheet, number, criminal record)? (THIS MAY BE A BAD IDEA) Or put one step earlier that says: Do you have a) docket sheet, b) docket number, c) criminal record, d) all of the above. Then you can have one “get resource” and “exit” path instead of 3?
- [x] 5. What do the court department and division mean and how do we help people with that?
- [ ] 6. Does expungement app speak to trafficking and distribution charges not being expunge able? Only possession allowed.
- [ ] 7. Does sealing app speak to making it more difficult to expunge later? Does expunge speak to sealing causing more work?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.