Trail implementation checklist

When implementing Trail, you can use this list to help with going through what has been done, and what hasn't. You can also print this document and add your own notes.

Adding items

Have you decided on departments?

• Departments in Trail can be used to easily limit which users can see which items. It is recommendable to decide on departments before starting to collect item information. This helps everybody to add the information the same way.

How will you add locations?

• It is possible to add a location hierarchy, where the item is located either to parent locations, sublocations, or as content to another item. It is recommendable to decide how to write and add locations before starting to collect item information. This helps everybody to add the information the same way.

Language usage?

• Before starting to collect item information, we recommend to decide in what language will the information be added. Will you use your native language or some other that all of your users will understand. The system itself is available in three languages: English, Finnish and Swedish.

How many items have been added to Trail?

• Have all of the items been added or are some still missing?
• Which ones are still missing:

1.                                                                                                                                                                

2.                                                                                                                                                                

3.                                                                                                                                                                

Other:

Have you decided on a schedule? 

• At the very beginning of the implementation state, we recommend scheduling a time plan for each step, for example when to collect item information, adding items to Trail, training, labeling, and adding users. Creating a schedule can help with a smooth start when starting to use a new system. 

Have you selected key users?

• Key users will guide others with Trail usage and support in implementing it to the whole organization. There could be two or three key users or one from each team for example.

Have you added users?

• Who will get access to Trail and what kind of user rights will they need?
• Will user rights be added separately to each user or will users get needed rights from different user groups?
• Will users sign in manually or could a Single Sign-on addition bring more help in logging in?

Labeling items?

• Have you ordered your own printer package or the labels as a service?
  • You can ask for and order possible labeling options from Trail's support: support@trail.fi
  • Note! It is possible to add your own company logo to the label template. If you are interested, please send a black-and-white version of the logo to Trail support.

• Have you installed the printer?
• Have the labels been printed and attached to the items?

Has the implementation meeting been kept?

• During the implementation meeting, Trail support will go through how to add items and users to the system. Possible times can be requested from Trail support: support@trail.fi

Have you had a Trail training?

• Has everyone gone through the Trail training and learned the basic functionalities?

Have you decided on your own usage process?

• It is recommended to define internally in your organization how to name and add items in Trail (e.g. how to name a reservation).
• This can ease the usage and finding of information. It is good to start thinking of the process from the start, but at least after the implementation, when more of your users will start using the system.

Other:

To the printed version you can also add your own notes that need to be remembered when implementing Trail:

1.                                                                                                                                                                

2.                                                                                                                                                                

3.