Internal User: Potential system needs for 'Director's Determinations'

#### Description:

From the internal user role meeting on March 25, IRC confirmed that Supplementary and Corrected reports are a new submission of a report, but that a Director's Determination is more like an attachment or appendix to a report. This ticket captures the implementation of adding an extra field (possibly more?) for it

NOTE: Currently if a Director's determination is required, it would be emailed to the Operation and a record saved with the Business Area. We may not need this functionality in the system.

Other considerations: a checkbox or other way to flag for internal users that a Director's determination has been made on a specific report?

#### Acceptance Criteria:

Given
When
Then

#### Development Checklist:

- [ ] Checklist item
- [ ] Checklist item
- [ ] Checklist item
- [ ] Meets the DOD

**Definition of Ready** (Note: If any of these points are not applicable, mark N/A)

- [ ] User story is included
- [ ] User role and type are identified
- [ ] Acceptance criteria are included
- [ ] Wireframes are included (if required)
- [ ] Design / Solution is accepted by Product Owner
- [ ] Dependencies are identified (technical, business, regulatory/policy)
- [ ] Story has been estimated (under 13 pts)

**Definition of Done** (Note: If any of these points are not applicable, mark N/A)

- [ ] Acceptance criteria are tested by the CI pipeline
- [ ] UI meets accessibility requirements
- [ ] Configuration changes are documented, documentation and designs are updated
- [ ] Passes code peer-review
- [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
- [ ] Ticket is ready to be merged to main branch
- [ ] Can be demoed in Sprint Review
- [ ] Bugs or future work cards are identified and created
- [ ] Reviewed and approved by Product Owner

#### Notes:

-

Start with the March 25 internal user role meeting and clarify whether a Director's Determination belongs in the system or remains an emailed record. Define the required field or flag, user workflow, dependencies, and acceptance criteria with the Product Owner; the work is done when the solution and criteria are accepted.

Written by the indexing model from the issue text.