Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Amendments Editor topic
No spam. Unsubscribe anytime.
Drafters and developers debate statuses, releasing, and copy-editing in the amendments editor
Summary
The drafting/editor module demo prompted questions about statuses (drafting, pending, released), how release and pending states should be used by drafters versus docket staff, and whether enrolled/engrossed recalls should preserve pre-enrolled snapshots.
The group walked through the amendments dashboard and editor. Presenter (S4) demonstrated creating a new amendment and the sequence of statuses (drafting, release, pending), explaining how release signals that a document is available for others to consume. Staff (S7) reminded the group that drafters typically draft and hand a document to the senator privately; that document remains private until the member authorizes offering it on the floor, so status fields should reflect internal roles rather than public availability.
A key operational concern arose around recall and enrolled/enrolled snapshots. Staff worried that recalling an enrolled copy might remove the previously engrossed amendment content. Presenter (S4) showed a recall flow but staff argued for an "unlock" or pre-enrolled snapshot that preserves the engrossed content while allowing last-minute tweaks. S7 summarized the concern: users want to "lock and unlock" rather than erase previous work if they need to tweak a comma in a late stage. Developers agreed to explore a recall/restore that returns to a pre-enrolled snapshot instead of clearing engrossed content.
