# Required Playbook Fields

**URL:** <https://community.hubspot.com/t/required-playbook-fields/13745>\
**Category:** HubSpot Ideas\
**Tags:** object\
**Created:** [March 28, 2019, 9:26pm UTC](https://community.hubspot.com/t/required-playbook-fields/13745 "2019-03-28T21:26:38Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [March 28, 2019, 9:26pm UTC](https://community.hubspot.com/t/required-playbook-fields/13745/1 "2019-03-28T21:26:38Z")

</div>

It would be ideal if **Playbook** authors could set a field to **required response**.

---

<div class="post-metadata">

**Author:** ![PaulAlmond91](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/paulalmond91/32/48165_2.png) [@PaulAlmond91](https://community.hubspot.com/u/PaulAlmond91)\
**Post date:** [September 19, 2019, 9:02am UTC](https://community.hubspot.com/t/required-playbook-fields/13745/2 "2019-09-19T09:02:24Z")

</div>

Great idea - helps ensure that playbooks designed to support data capture accurately collect everything that is required!

---

<div class="post-metadata">

**Author:** ![BenWholley](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/benwholley/32/38114_2.png) [@BenWholley](https://community.hubspot.com/u/BenWholley)\
**Post date:** [June 9, 2021, 11:44am UTC](https://community.hubspot.com/t/required-playbook-fields/13745/3 "2021-06-09T11:44:57Z")

</div>

It’s so painful that our staff can complete a playbook and leave fields blank, really need this feature adding. As well as date and users support.

---

<div class="post-metadata">

**Author:** ![THubspot](https://avatars.discourse-cdn.com/v4/letter/t/c57346/32.png) [@THubspot](https://community.hubspot.com/u/THubspot)\
**Post date:** [December 20, 2021, 2:28pm UTC](https://community.hubspot.com/t/required-playbook-fields/13745/4 "2021-12-20T14:28:59Z")

</div>

Yes, that’s a good idea to set some fields as required.

---

<div class="post-metadata">

**Author:** ![SpencerHodgson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/spencerhodgson/32/57633_2.png) [@SpencerHodgson](https://community.hubspot.com/u/SpencerHodgson)\
**Post date:** [December 22, 2021, 4:15pm UTC](https://community.hubspot.com/t/required-playbook-fields/13745/5 "2021-12-22T16:15:18Z")

</div>

As I considered the fact that this ISN’T possible, I went to the Ideas section here assuming there would be an Idea with a lot of comments and upvotes already, but suprisingly there isn’t! Only three comments and 15 upvotes in almost 3 years. This seems like it should be VERY easy to implement, and it would greatly benefit many processes. Currently certain reps might leave notes in the playbook under the property, but not actually update the property itself, which is essentially useless. It doesn’t seem all that challenging to me to not let the playbook submit unless every question which is marked as required is filled out. I trust the computer much more to make sure the form is filled out correctly than I do our reps to pay attention to each detail.

---

<div class="post-metadata">

**Author:** ![ASolares](https://avatars.discourse-cdn.com/v4/letter/a/73ab20/32.png) [@ASolares](https://community.hubspot.com/u/ASolares)\
**Post date:** [January 11, 2022, 10:11pm UTC](https://community.hubspot.com/t/required-playbook-fields/13745/6 "2022-01-11T22:11:05Z")

</div>

This is absolutely needed! We use one of the fields to trigger a workflow.

---

<div class="post-metadata">

**Author:** ![MYapp](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/myapp/32/89259_2.png) [@MYapp](https://community.hubspot.com/u/MYapp)\
**Post date:** [January 31, 2022, 8:02pm UTC](https://community.hubspot.com/t/required-playbook-fields/13745/7 "2022-01-31T20:02:36Z")

</div>

+1 for this feature request. Playbooks are the best tool for certain team processes, but those processes can break down when certain fields are left blank. Hubspot should upgrade this feature to allow required input fields.

---

<div class="post-metadata">

**Author:** ![SKvarda](https://avatars.discourse-cdn.com/v4/letter/s/6f9a4e/32.png) [@SKvarda](https://community.hubspot.com/u/SKvarda)\
**Post date:** [March 23, 2022, 2:44pm UTC](https://community.hubspot.com/t/required-playbook-fields/13745/8 "2022-03-23T14:44:08Z")

</div>

+1 to this idea. I am rolling out playbooks for SDRs assuming it would have required fields and now that it doesn’t were looking for a workaround

---

<div class="post-metadata">

**Author:** ![LLynam](https://avatars.discourse-cdn.com/v4/letter/l/9d8465/32.png) [@LLynam](https://community.hubspot.com/u/LLynam)\
**Post date:** [May 17, 2022, 4:01pm UTC](https://community.hubspot.com/t/required-playbook-fields/13745/9 "2022-05-17T16:01:45Z")

</div>

We set up lots of playbooks and now we have realised that by not being able to have mandatory fields, our data quality is becoming poor. Basically means we will need to stop using them so we lose a feature…

---

<div class="post-metadata">

**Author:** ![TErickson\_OW](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/terickson_ow/32/56389_2.png) [@TErickson\_OW](https://community.hubspot.com/u/TErickson_OW)\
**Post date:** [August 2, 2022, 11:01pm UTC](https://community.hubspot.com/t/required-playbook-fields/13745/10 "2022-08-02T23:01:15Z")

</div>

Yes please, this would is truly needed to ensure data integrity.

---

<div class="post-metadata">

**Author:** ![Jpbsalibe](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jpbsalibe/32/38114_2.png) [@Jpbsalibe](https://community.hubspot.com/u/Jpbsalibe)\
**Post date:** [September 12, 2022, 6:30pm UTC](https://community.hubspot.com/t/required-playbook-fields/13745/11 "2022-09-12T18:30:58Z")

</div>

I really need this feature to be implemented. I upgraded my Hubspot subscription, thinking that playbooks were going to resolve a lot of issues that I was having and now I have less control than before on the data input.
