Write monitor requests a sound engineer can interpret

Describe listening needs before naming outputs

Start with performer IDs and a consistent stage perspective. In this worksheet, left and right are the performer’s view facing the audience; label that convention on the plot and request sheet. Use source names that match the input list so “more guitar” does not leave the engineer guessing which guitar or whose monitor.

Yamaha explains that aux sends can create monitor balances separately from the audience mix and that available sends/configuration constrain the possible mixes. Its examples explain a signal-flow principle, not a guarantee about the venue’s desk or your show. The engineer should confirm the actual routing.

Write priorities in plain language: own vocal essential, harmony vocal useful, guitar if needed. Avoid invented fader settings or copying percentages from another room. A request sheet is a conversation aid; it does not establish safe listening level, gain-before-feedback or a complete IEM system design.

Worked request: three performers, two proposed balances

Fictional performers are P01 lead singer at center, P02 guitarist with backing vocal at performer-right, and P03 drummer at rear. Explicit input sources include V1 lead vocal, V2 backing vocal, G1 guitar and K1 kick. Four inputs are not four monitor buses.

This proposal uses three physical wedges but only two requested balances: M1 shared by P01 and P02, and M2 for P03. Sharing M1 is a proposal contingent on both performers accepting the same balance and the engineer confirming a suitable implementation. It is not achieved simply by writing the same label twice.

If P02 later needs a materially different balance, that may require another independent mix or a different agreed arrangement. If the venue confirms only one mix, do not mark M2 supplied. Retain the conflict, clarify priorities and agree a feasible revision before sending a final packet.

The sample deliberately leaves the provider and physical output patch unconfirmed. No wedge, cable, amplifier, personal-monitor system or channel is assumed to exist because an icon appears in a drawing. A performer’s request, venue capacity and actual soundcheck result are three separate records.

Reconcile the request with the venue and current source list

Ask the engineer to confirm the number of usable independent mixes, delivery type, provider, relevant connections and any substitutions. Mono/stereo choices and IEM requirements can change resource needs; this worksheet does not calculate them from the number of performers. Do not treat an effect send as available for monitoring without confirmation.

Keep source IDs aligned with the current input list and update a request if a performer or instrument changes. Remove obsolete needs explicitly rather than leaving the engineer to infer that an older PDF is no longer current. Include event/date and a revision reference, then retain the version actually shared.

At soundcheck, communicate one specific listening change at a time through the agreed method and let the engineer manage the system. Record confirmed revisions to the request; do not prescribe electrical connections, microphone placement, sound-pressure targets or hearing-safety settings from this planning table.

PlotCue prepares an advance packet from explicit records

PlotCue’s current listing describes a master setup with venue variants, contacts/schedule, readiness checks, source-derived patch rows, packing counts, monitor capacity, venue changes/questions, stage diagrams and a multi-page advance PDF. It does not create technical inputs merely because instrument icons exist.

We publish PlotCue. The current public listing offers a first standard PDF export free, with weekly/yearly Pro subscriptions for expanded saved plots, clean PDF exports and JSON backup tools. Check the current localized prices, renewal terms and free export conditions before choosing a plan.

Advances stay locally unless deliberately exported/shared; no cloud team account is required. A readiness percentage or PDF is not venue acceptance, equipment delivery or soundcheck proof. Use this independent CSV to clarify listening requests alongside the app’s stage/advance records; it is not an automatic console patch or app import.