# Communication Method

**URL:** <https://www.protaxcommunity.com/t/communication-method/12500>\
**Category:** Product Suggestions\
**Created:** [June 17, 2026, 5:34pm UTC](https://www.protaxcommunity.com/t/communication-method/12500 "2026-06-17T17:34:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jglass](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/jglass/32/723_2.png) [@jglass](https://www.protaxcommunity.com/u/jglass)\
**Post date:** [June 17, 2026, 5:34pm UTC](https://www.protaxcommunity.com/t/communication-method/12500/1 "2026-06-17T17:34:34Z")

</div>

I would like to suggest adding separate communication/delivery method fields for the tax planning package and the completed return package.

Currently, the Engagement Information screen has a single “Method of Communication” field. In our office, we use this field to determine whether TaxCycle prints paper packages or produces digital-only packages. This works well when a client wants both the planning package and completed return delivered the same way.

However, client preferences are increasingly mixed. For example:

- Mail planning package, receive completed return electronically.

- Receive planning package electronically, pick up completed return in person.

- Receive planning package electronically, receive a printed copy of the completed return by mail.

With only a single communication method field, there is no straightforward way to distinguish these workflows. My firm has created custom workarounds but mostly maintains additional tracking outside TaxCycle which is inefficient.

A possible solution would be to add separate fields such as:

- Planning Package Delivery Method

- Completed Return Delivery Method

These could use the same options currently available in Method of Communication.

Alternatively, a dedicated “Return Delivery Method” field alone would solve most of the problem while remaining backwards compatible with existing workflows.

As more firms adopt portals, e-signatures, and hybrid delivery methods, I suspect this distinction will become increasingly common.

Is anyone else encountering this issue, or has anyone found a clean workaround within TaxCycle?

---

<div class="post-metadata">

**Author:** ![BertMulderCGA](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/bertmuldercga/32/42_2.png) [@BertMulderCGA](https://www.protaxcommunity.com/u/BertMulderCGA)\
**Post date:** [June 17, 2026, 11:20pm UTC](https://www.protaxcommunity.com/t/communication-method/12500/2 "2026-06-17T23:20:43Z")

</div>

I use custom fields for this.