Staff urge on-screen provenance for reintroduced bills to prevent coding errors

Staff and system presenters spent the meeting detailing how reintroductions are currently handled and why provenance matters to the drafting workflow. A senior staff member explained that reintroduced bills are typically handled using last year's proofread hard copy to preserve verification marks and to avoid importing code sections changed later: "When we do a reintroduction, we do the hard copy because it has data on those at the bottom that has been proofread, and we know who has proofread it," said Staff member (S1). That practice prompted requests for UI metadata that is visible to drafters and typists but does not print on the final document.

The request reflected two practical risks the staff described. First, automatically inserting last session's text would import code-section references that may have been amended in subsequent bills; S1 warned that "if I pull up last year's bill and insert it, if it has any code sections that have been amended in the previous or during the same session, they're not updated." Second, proofing and accountability were presented as operational safeguards: typists and proofreaders use a validation sheet that flags sections not found in the database, and staff want the system to surface that origin and proofreader metadata on-screen to speed verification without printing it on the public bill copy.

Developers demonstrated a possible solution: a nonprinting dataset visible only on-screen that records the originating session and proofreader initials. Staff said that would be more efficient and would let typists confirm the provenance before finalizing the R-version. The meeting closed with a plan to confirm how the system's bill-status and database (ASG/CD) integrations will populate that provenance flag.