# Tips for Tags

<figure><img src="https://3923904090-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNy7IznbrPLUq6GJDDQDk%2Fuploads%2FrX2c2QrXcKEElHYa76dh%2Fimage.png?alt=media&#x26;token=7f45cf83-a56d-4dcd-aa75-9f5af54ec67e" alt="" width="409"><figcaption></figcaption></figure>

## Introduction <a href="#jpxwn0k09xs0" id="jpxwn0k09xs0"></a>

Tags provide a flexible way to organise records when existing fields don’t capture what you need. They’re especially useful for ad-hoc or temporary categorisation. However, keep in mind that while you can filter and search on Tags, they can’t be reported on, which is a limitation.

In this Playbook, we’ll look at ways to keep your Tags in order and make them work for your team, and some ideas on how to customise available menus and sub-registers to create a more sustainable solution to Tags.

## Creating and using Tags <a href="#id-1cfbeibufv30" id="id-1cfbeibufv30"></a>

Tags are highly useful because any user can create or delete them, allowing for quick organisation. However, this flexibility can make tags unmanageable if not carefully maintained. In Crisisworks, tags are unique to each register and sub-register, which can lead to an accumulation of misspelt, vague, or outdated tags. Here are some tips to help prevent this:

* **Set naming conventions:** Work with your Team to establish and communicate clear naming conventions for Tags.
* **Create a reference guide:** record your most useful tags and their meanings in an Information entry, then promote this entry to the Dashboard for easy access.
* **Use descriptive Tags:** choose Tags that clearly convey their purpose. For example, instead of a vague tag like Flood, use more specific tags such as Flood Level 1 or Flood Level 2. Similarly, avoid generic tags like animals and use more descriptive tags like animals at ERC.

### Examples of Tags uses <a href="#id-35onwrz0dg70" id="id-35onwrz0dg70"></a>

* **LIBRARY -** Tag documents, guidelines, templates etc with the role name that would use them, such as EMLO, ERC, MRM or MECC. This allows the same document to be tagged for use by multiple groups. For example, ERC Operating Guidelines could be tagged both ERC and MRM.
* **CALLBACKS -** when you’re working through a list of cases to call back, add a Tag like Lisa to call to easily locate them. Remember to remove the Tag once the task is completed. See [Alternatives to Tags](#_ghec4tsjsa2k) for more ideas on handling follow up tasks.

{% hint style="info" %}
**Share your ideas!** If you have effective ways of using tags, share them by adding a comment here, and we’ll add it to the Playbook.
{% endhint %}

### Bulk add and remove Tags <a href="#tksgus1difs1" id="tksgus1difs1"></a>

To clean up tags effectively, you can use the bulk edit function. This is a quick way to remove outdated or misspelled tags and add new or replacement tags as needed.

<figure><img src="https://3923904090-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNy7IznbrPLUq6GJDDQDk%2Fuploads%2FEQe2Gn07I9J4bS52vkVK%2Fimage.png?alt=media&#x26;token=841cabcc-be6d-4d6f-8e0f-05f6d5bc8374" alt="" width="375"><figcaption></figcaption></figure>

## Alternatives to Tags <a href="#ghec4tsjsa2k" id="ghec4tsjsa2k"></a>

While tags offer a quick and flexible way to manage data, especially in emergency situations. However, for more structured and sustainable management with added features like reporting, assignments, and timelines, consider these alternatives:

### Classifications <a href="#vjf8oo4vq8vv" id="vjf8oo4vq8vv"></a>

> #### **Classifications offer a more organised approach to tags, allowing you to apply predefined terms to data in the Contacts and Recovery Cases registers.** <a href="#qk7bcbko5vwb" id="qk7bcbko5vwb"></a>

#### Classifications are created and managed through **Lookups** (Administration>Settings>Lookups). <a href="#plj898lxynvx" id="plj898lxynvx"></a>

* Classification Categories are **‘Recovery: Case Classification** and **Contacts: Classifications**.
* Creating and assigning Classifications is limited to the Position of MRM in the case of Recovery Case Classifications) and MEMO in the case of Contact Classifications.

### Utilise Needs and Tasks <a href="#dox32kvjyv1e" id="dox32kvjyv1e"></a>

Consider creating a Need & Task for a Recovery Case rather than using tags. Needs & Tasks can be assigned to a Position, can be given a due date, and can capture more information on the topic. New Need & Task Categories can be created through Lookups (Administration>Settings>Lookups) using the Recovery:Immediate Needs category.

### Useful links <a href="#i5dw9783d9u9" id="i5dw9783d9u9"></a>

* [More on Contacts & Expertise](https://docs.cw.crisisworks.com/modules/operations/contacts/expertise)
* [More on Recovery Cases](https://docs.cw.crisisworks.com/modules/recovery)
* [More on Modifying Lookups](https://docs.cw.crisisworks.com/system-administration/configuring-the-system/lookups)
