With Hoshon you define templates for processes that need to be repeated over and over.
Each template specifies a series of steps. Then, use these templates to generate checklists to be completed by members of your team, each time a process needs to be completed.
Example Create a template to codify what needs to be done before releasing a new episode of a podcast. Then, for each new episode, use this podcast template to create a checklist for the team to complete before hitting 'publish'.
Hot Tip You don't need to repeat the name of your template when you name your checklists.
A template defines a standard series of tasks. Once a single template has been made, it is used to create a checklist each time your team needs to complete that process.
If a checklist needs to be tweaked (e.g., a podcast episode that includes a bonus segment), consider creating a derived template.
Hot Tip If your process is more than nine steps, consider creating two templates.
Based on a template, a checklist specifies a series of steps that need to be completed. Hoshon keeps track of which steps have been completed, when, and by whom.
Hoshon supports two types of templates.
A "Read Do" template creates checklists that are intended to be completed one step at a time. Like when following a recipe, the order in which steps are completed typically matters for a "Read-Do" template.
A "Do Confirm" template creates checklists that are intended to be "marked-off" after a process has been completed, like double checking your grocery list at the register. For a "Do-Confirm" template, the order in which steps are completed typically does not matter; all that matters is that the steps get done.
Fun Fact These terms originate from aviation.
A derived template is a template that is created based on an existing template.
The advantage of using a derived template is that the templates are linked together and that all of the tasks are prepopulated instead of you needing to re-enter them manually.
Example You can create a derived template for "Publishing a podcast requiring agent approval" based on the "Publishing a podcast" template if there are additional steps that only need to be performed when interviewing high profile guests.
Hot Tip It is typically better to use a derived template than to make modifications to an existing template. Making a derived template makes analytics easier to compare.
A team centralizes how users share templates with one another. A team can also be used to keep templates and their associated checklists private. In other words, templates (and their associated checklists) owned by a private team will only be visible to members of that team.
An archived checklist is a checklist that is no longer being actively worked on. They do not appear under complete or incomplete checklists, but they do appear under all checklists.
Example You may have created a checklist for a podcast episode with a guest who later decides to decline the interview. Instead of deleting the checklist, which would lose relevant historical information like comments, or artificially "completing" the checklist so that it no longer shows up as incomplete, try archiving the checklist instead.
For customers looking to integrate Hoshon programatically into existing workflows, there is a RESTful API available to Pro Customers.
Please reach out to firstname.lastname@example.org to learn more.
Hoshon works on any internet connected device with a modern browser. If you're interested in a native mobile application, please let us know.
Note Hoshon does not support Internet Explorer.
Yes. Descriptions and comments can be formatted using markdown-like syntax.
|Bold Text||**Bold Text** OR __Bold Text__|
|Bulleted list||* item|
|Numbered list||1. item|
Timestamps are rendered based on the local timezone for each web browser.
For example, if a user in San Francisco marks something as complete at
another user viewing the same thing in New York would see it as completed at