bcgov / bcgov/range-web

INFO - Minor Amendment

Open
#706 0 comments 0 reactions 1 assignee Claimed by @LisaMoore1 View on GitHub
Dominant language
TypeScript
Stars
9
Forks
11
PR merge metrics
No merged PRs in 30d

Description

These are for thought — I’m open to discussion but each touches on an important principle that needs to be addressed (all content of #703 applies):
- [x] only AHs can initiate minor amendments
- [ ] AH should see all amendments that are in “stands” as “stands” regardless of whether they have been reviewed or not
- there is no difference to an AH operationally and they should not be bothered with wondering when it will get reviewed (the majority are left as “stands” and those that are not generally get the attention of staff/DDM quickly)
- [ ] a minor amendment becomes the current legal version as soon as it is signed by AH(s) and submitted
- [x] both “stands” and “stands-wrongly made” are considered current legal version statuses (i.e. changing to stands-wrongly made does not require a current legal version roll-back)
- [ ] the previous current legal version becomes the current legal version if a minor amendment is determined “wrongly made-without effect“
- the wrongly made-without effect” version becomes part of the “not implemented” group of versions
- not that that particularly means anything except that it is useful to know in general terms
- [ ] headers need to reflect amendment language
- ??Does that mean they should all be made more generic or review all and make more specific for amendments?

**Workflow Overview**
- [ ] AH initiates the amendment
- only AH(s) can see the content
- [ ] AH identifies as minor and submits
- AH sees “stands”
- Staff sees “minor amendment for review” (or something like that)
- [ ] has options to either: “Review Not Required” or “Review Required
- [ ] IF “Review Not Required” THEN
- Process ends
- no longer indicates staff action required
- AH still sees “stands”
- [ ] IF “Review Required”
- staff prepare a recommendation package for DM and submit
- [ ] DM chooses between options
- stands
- stands-wrongly made
- wrongly made-without effect
- submit as a mandatory amendment —> this kicks it back to staff to a staff initiated mandatory amendment process

**Questions**
- can a wrongly made determination include conditions? (Need to know this for when we do DM workflow online)

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.