Checklist variations

Question

I am looking to create a checklist for our Preventative Maintenance. I am hoping that someone can help me think of an elegant solution to creating this.

The main issue is that we have many machines, and each has a different set of items to check off. Although, some of the items do cross over but not many of them.

I currently have a similar checklist set up, but it's a little messy to make updates to, and I'm hoping there may be an easier solution. Currently, I have a checklist with 6 different variations, and I've added 6 sections with the checklist items on them. Each section only appears when it's option is selected. However, this is a lot of fields as I have to add all items under each section. This checklist I have set up already has 10-12 checklist items on it and is already cumbersome to update. These new checklists have 50-100 items on them.

Does anyone know of some way to make this a little simpler?

I have added some screenshots of the lists I currently have. As you can see in the first image, my first field allows the user to select the type of checklist they are completing. Once this is selected it shows the correlating section for them to complete. This method has these 6 short checklists in one form with 173 fields. Many of these checklist items overlapped, but not in the same order.

I would appreciate any thoughts on this you may have.

Thanks!

mcfneil · Answer

I'd recommend turning the checklist into a child table. Then you would have a template checklist table, and when they pick the 'type' and push a button, only those child records would load into the checklist.

Then you can customize the lists for every type, and if down the road your list changes, you just change the template, without causing any problems to the old checklists.

It is a much more scale-able solution, and gives you much better reporting capabilities.

andreonnagarret · Answer

So like one table, that lists all of the checklist items. This would also have a field that ties them to a specific record type. And then an embedded report on my main table would pull in with only those related items?

andreonnagarret · Answer

For example, I currently have each item set up in sections. I would instead make each of these items on the child table and reference both the type of checklist this applies to, as well as the section it applies to? Images attached.

mcfneil · Answer

It would be one 'checklist' table. &nbsp;And you would have one "Template Checklist" table. &nbsp;Each 'Release Type' would have many checklist templates. &nbsp;You can then make your lists, so for 'x' release type we have these 10 questions, and for 'y' we have these 12 questions.Each 'Release/Receiving' (or whatever you call the main item) would have many 'Checklists'.But, instead of picking the the 'type' on the checklist, you would pick the type on the parent (Release/Receiving).Then you would load (via script) multiple child records or checklist items that match that 'type'.***I absolutely butchered that explanation. &nbsp;I can always show better then explain*** &nbsp;Or do you get what I was trying to say?&nbsp;

andreonnagarret · Answer

I follow your explanation but am not 100% sure how to set it up to pull correctly. I am not certain I have worked with script enough to visualize how this works.&nbsp;

Forum Discussion

Checklist variations

Related Content

Questions & Checklist setup

Trying to Create a Attendance Checklist

Building Checklists

Displaying a checklist/questions based on a field?

New checklist field from field duratio input