Actions to Get Started
Before adding Tag Checklists, review your existing processes:
- Review current forms: Examine existing product request forms, reviewer forms, or provider applications. Identify questions or information that you can reformat into a Tag Checklist item. This enables vendors to select options that translate directly into product tags.
- Analyze existing checklists: Review internal checklists or criteria used to evaluate products. If the checklist information can be collected during the vetting process, add the relevant checklist as a Tag Checklist item to your forms.
- Check your workflow: Identify workflow steps where an administrator manually applies a tag to activate a conditional step or update a status. A Tag Checklist can automate this process to ensure consistency.
You can use Tag Checklists to automate workflows across various form types.
Tag Checklists can indirectly collect information about the requestor and the requested product. For instance, when submitting a product request, you can require requestors to select their school, subject, and grade level from a Tag Checklist.
If a condition is added to a workflow step, tags from these responses can trigger conditional reviews.
Examples:
- A teacher requests product and selects High School. The tags are applied to the tool, the workflow is triggered, and the conditional High School step runs.
- Another teacher requests the product and selects Middle School. The tool now has bothMiddle School and High School tags applied, so both the Middle School and High School steps would run for that request.
Reviewers can use Tag Checklists to collect product information during the vetting process. For example, you can create a Tag Checklist with options such as Meets Accessibility Standards or Student Data Privacy Compliant. As reviewers evaluate the product, they can select the relevant items to automatically apply the corresponding tags.
If a condition is added to a workflow step, these tags can also trigger an additional review. For example, if a reviewer selects Student Data Privacy Compliant, the system automatically adds the tag, and assigns the conditional step to the data privacy specialist to the review the product.
You can also use a Tag Checklist with a conditional automation-only step to end a workflow. If a reviewer selects a tag such as Not Approved for Use, the workflow ends automatically and sends a notification to the requestor.
Vendor Applications
When creating a Provider Application, you can use Tag Checklists to collect information directly from vendors regarding product features, integrations, or awards.
The tags from these responses appear to end-users in your library, which helps users locate products. You can also use Tag Checklists to guide conditional reviews. If a vendor selects Meets Accessibility Standards, the application is automatically routed to an accessibility expert for review.
Note: Tag visibility will always depend on (and respect) the tag visibility settings. If tags are only required for a specific request or workflow scenario, consider creating temporary, workflow-only situational tags.