Skip to main content

Evidence Types

Evidence Types

Purpose and when to use this record

BriskMaintain storesthe controlled evidence typesclassifications asused partfor ofsearch, storage, and reporting.

At a glance

  • Identify it by: Name, and Code.

  • 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: Availability and publication flags affect future use without erasing history. Prefer disabling an obsolete setup record when existing transactions still refer to it.

Before you begin

You need the Brisk permission for the action you are taking on evidence types. 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 Type

Brisk Evidence Types create screen displayed with fictional documentation-demo data.
The Evidence Types create screen in the Brisk documentation demo.

TheCreate evidencean packetEvidence identifiesType only when the viewexisting choices do not represent the policy or classification you need. Near-duplicate setup values split reporting and sourcemake locationlater selection harder.

  1. Select the business context first.

  2. Enter the required identifying and operational values: Name.

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

  4. Save the Evidence Type, then confirm Name, and Code on its detail page before continuing.

After saving: Open Evidence Items and confirm the Evidence Type appears with the intended label and availability. Keep the old value for thishistorical action.records Confirmwhen user-facingchanging stepsit beforewould approvingsplit or relabel prior reporting.

Delete an Evidence Type

Delete this page.Evidence Type only if it is an unused duplicate or setup mistake. Once other records refer to it, preserve that history and make the value inactive when the screen provides that option.

If the record is merely obsolete, use Active to remove it from future use while preserving existing references.

Before confirming, check for related Evidence Items. 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 Name, and Code. After confirmation, return to the Evidence Types list and make sure only the intended Evidence Type was removed.

ViewReview recordEvidence Type details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Evidence Type currently means. Verify Active before relying on it for a decision.

Compare the Evidence Type with its source document or approved setup request before deciding that it needs correction.

Next check: Open Evidence Items and sourceconfirm locationthe Evidence Type appears with the intended label and availability. Keep the old value for thishistorical action.records Confirmwhen user-facingchanging stepsit beforewould approvingsplit or relabel prior reporting.

Edit an existing Evidence Type

Edit this Evidence Type when the underlying policy or classification changed. First determine whether historical transactions should retain the old value; if so, deactivate the old choice and create a new one.

  1. Open the detail page. Compare Name, and Code with the supporting document or approved request.

  2. Recheck Active. 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 Type now appears under the expected Active.

After the change: Open Evidence Items and confirm the Evidence Type appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

Find and review recordsevidence types

Brisk Evidence Types list screen displayed with fictional documentation-demo data.
The Evidence Types list screen in the Brisk documentation demo.

The evidence packet identifiesUse the viewEvidence Types list to find the correct record before opening or changing it. Compare Name, and sourceCode. locationCompare the full identifier rather than relying on a similar name.

Open the Evidence Type whose Name, and Code match the task. If it is missing, clear the list filters and recheck Active rather than creating a replacement immediately.

Fields and business rules

Brisk stores 4 user-relevant fields for this action.Evidence ConfirmType, user-facingincluding steps0 beforelinked-record approvingselections and 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

The

evidencetheviewandsourcelocation user-facingstepsbeforeapproving
Field Required What packetit identifiescontrols
NameYesHuman-readable name for this action.evidence Confirmtype.
Code NoShort code used to identify this page.evidence type.
ActiveNoWhether this evidence type is active and available for use.
DescriptionNoDescription of this evidence type.

What happens next

Open Evidence Items and confirm the Evidence Type appears with the intended label and availability. Keep the old value for historical records when changing it would split or relabel prior reporting.

DeleteCommon amistakes and troubleshooting

  • The record

    Thewill evidencenot packetsave: identifiesRecheck Name and any message beside the viewfield. andA required related record may also be inactive or unavailable to your role.

  • The record saved but is not available where expected: Recheck Active, 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: Compare this Evidence Type with the source locationdocument foror thisapproved action.setup Confirmdecision, user-facingthen stepscheck beforethe approvingdownstream thisscreen page.where it is used.