Evidence Items

Evidence Items

Purpose and when to use this record

BriskCatalog storesan item of evidence itemsunder asits partcase ofwith identifying detail, storage location, condition, and custody state.

At a glance

• Identify it by: Collected Date, and Status.

• Check its business context: Case, Logged By, Evidence Type, and Current Custodian.

• Why care: Use the lawagency’s enforcementapproved module.terminology Thisand generatedaccess referencepolicy. Preserve dates, responsible personnel, case links, and audit history because these records may support official reporting or custody review.

• Why care: Status communicates workflow progress to other staff. Change it only when the underlying work, approval, payment, or handoff has actually occurred.

Before you begin

You need the Brisk permission for the action you are taking on evidence items. If a Create, Edit, or Delete control is awaitingabsent, workflowdo review.not work around it with another user’s account; ask an administrator to review your role.

Create aan recordEvidence Item

TheCreate evidencean packetEvidence identifiesItem only after confirming that the viewsource document or operational event has not already been entered.

1. Select the business context first: Case, Logged By, Evidence Type, and sourceCurrent locationCustodian.

2. Enter the required identifying and operational values: Tag Number.

3. Review Status deliberately; these choices control availability or workflow rather than merely describing the record.

4. Save the Evidence Item, then confirm Collected Date, and Status on its detail page before continuing.

After saving: Add a chain-of-custody entry for thisevery action.transfer Confirmor user-facingmaterial stepshandling beforeevent approvingand verify that Current Custodian and Current Location agree with physical custody.

Delete an Evidence Item

Delete this page.Evidence Item only when it was entered by mistake and no downstream history depends on it. Use a reversal, void, credit, counter-adjustment, or status correction for a real event that later changed.

Before confirming, check for related Evidence Chain Entries. Brisk may refuse deletion when another record depends on this one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.

On the confirmation page, verify Collected Date, and Status. After confirmation, return to the Evidence Items list and make sure only the intended Evidence Item was removed.

ViewReview recordEvidence Item details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Evidence Item currently means. Verify Collected Date, and sourceStatus locationbefore relying on it for thisa action.decision.

Confirm

Follow user-facingCase, stepsLogged beforeBy, approvingEvidence Type, and Current Custodian to determine whether the issue is on this Evidence Item or on one of those linked records.

Next check: Add a chain-of-custody entry for every transfer or material handling event and verify that Current Custodian and Current Location agree with physical custody.

Edit an existing Evidence Item

Edit this Evidence Item to correct or complete the same source document or operational event; use the supported reversal or follow-up workflow when the business event itself changed.

1. Open the detail page. Compare Case, Logged By, Evidence Type, and Current Custodian with the supporting document or approved request.

2. Recheck Collected Date, and Status. These values are most likely to change case history, custody, dispatch, official reporting, or audit review.

3. Save the change, return to the list, and confirm that the Evidence Item now appears under the expected Status.

After the change: Add a chain-of-custody entry for every transfer or material handling event and verify that Current Custodian and Current Location agree with physical custody.

Find and review recordsevidence items

The evidence packet identifiesUse the viewEvidence Items list to find the correct record before opening or changing it. Compare Collected Date, and sourceStatus. locationRecords with similar names or numbers can still belong to different Case, Logged By, Evidence Type, and Current Custodian.

• The initial order emphasizes Collected Date, and Tag Number. Select a column heading when you need a different comparison.

Open the Evidence Item whose Collected Date, and Status match the task. If it is missing, clear the list filters and recheck Status rather than creating a replacement immediately.

Fields and business rules

Brisk stores 12 user-relevant fields for this action.Evidence ConfirmItem, user-facingincluding steps4 beforelinked-record approvingselections and 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

location user-facingstepsbeforeapprovingthis page.

Delete a record

user-facingstepsbeforeapproving

Field	Required	What it controls
Case	No	The case associated with this evidence item.
Logged By	No	The logged by associated with this evidence item.
Evidence Type	No	The evidence packettype identifiesassociated thewith viewthis andevidence sourceitem.
Current Custodian	No	The current custodian associated with this evidence item.
Tag Number	Yes	The tag number recorded for this action.evidence Confirmitem.
Summary	No	The evidencesummary packet identifies the view and source locationrecorded for this action.evidence Confirmitem.
Description	No	Description of this page.evidence item.
Current Location	No	The current location recorded for this evidence item.
Collected Date	No	Date recorded for collected date on this evidence item.
Status	No	Current status of this evidence item. Available values: Collected, In Storage, Checked Out, Submitted, Returned, Disposed, Released.
Disposition	No	The disposition recorded for this evidence item.
Memo	No	The memo recorded for this evidence item.

What happens next

Add a chain-of-custody entry for every transfer or material handling event and verify that Current Custodian and Current Location agree with physical custody.

Common mistakes and troubleshooting

• The record will not save: Recheck Tag Number and any message beside the field. A required related record may also be inactive or unavailable to your role.

• The record saved but is not available where expected: Recheck Status, then clear the filters on the destination list. A saved record can still be inactive, unpublished, locked, unapproved, or in the wrong workflow state.

• The values look right but the result is wrong: Open Case, Logged By, Evidence Type, and Current Custodian from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.