It does not seem to make a lot of sense to me to create another communication artifact to show resources the schedule, tailored to the point of view of a resource, other than what you already have available to use. If you point to the schedule, perhaps in the gantt view or something, and they do not look at it, that might mean they neither want nor need to look at it--in which case that would be a valuable datum that says do not waste your time or money communicating something about which they do not care.
The Work Authorization Document (WAD) is a typical tool to communicate what piece of work is next. The WAD is not only a required document if you stood up an ANSI-certified EVMS, but is also an easy to use tool to communicate to each resource the work ahead. It not only authorizes a person to when to begin turning wrenches and thus accruing costs, but also relays valuable information such as expected inputs, expected outputs, other requirements, expected time and cost targets, risks, dependencies, etc. You can create this WAD as simple or sophisticated as you want.
If something changes, a WAD is reissued with the updated information. It requires you to have such a capability to administer this WAD, but this is the cost of doing business in a controlled way. In other words, this is part of your PM LOE and you would / should have budgeted for it accordingly. It does NOT have to be overly complicated and formal, either. You can create this capability to be consistent with the size and complexity of your project. But leaving home without is ill-advised.