You should consider to keep them simple and use any data for analysis during the timebox to see where to explore next. The charter is just a mission to get you started, not a detailed work assignment and reporting tool.

I like the format ckenst proposes in his writing exploratory charters:

How to Write Exploratory Charters

This is based on "A simple charter template" from Elisabeth Hendrickson's awesome book Explore It!, Chapter 2, page 67 of 502 (ebook).

Explore (target) With (resources) To discover (information)

• Target: What are you exploring? It could be a feature, a requirement, or a module.
• Resources: What resources will you bring with you? Resources can be anything: a tool, a data set, a technique, a configuration, or perhaps an interdependent feature.
• Information: What kind of information are you hoping to find? Are you characterizing the security, performance, reliability, capability, usability or some other aspect of the system? Are you looking for consistency of design or violations of a standard?

Read more and examples at: https://github.com/ckenst/testing-guides/blob/master/test%20design/writing_exploratory_charters.md

You should consider to keep them simple and use any data for analysis during the timebox to see where to explore next. The charter is just a mission to get you started, not a detailed work assignment and reporting tool.

I like the format ckenst proposes in his writing exploratory charters:

How to Write Exploratory Charters

This is based on "A simple charter template" from Elisabeth Hendrickson's awesome book Explore It!, Chapter 2, page 67 of 502 (ebook).

Explore (target) With (resources) To discover (information)

• Target: What are you exploring? It could be a feature, a requirement, or a module.
• Resources: What resources will you bring with you? Resources can be anything: a tool, a data set, a technique, a configuration, or perhaps an interdependent feature.
• Information: What kind of information are you hoping to find? Are you characterizing the security, performance, reliability, capability, usability or some other aspect of the system? Are you looking for consistency of design or violations of a standard?

Read more and examples at: https://github.com/ckenst/testing-guides/blob/master/test%20design/writing_exploratory_charters.md