A clear glass cloche over a yellow sphere, with a blank cream card on plum velvet.
Original AI-generated editorial illustration; not a real account, product sale or completed job. View full-size image.

A magician's booking description should explain what the audience is being invited to experience, which details the performer has approved for public use, and what still needs confirmation. Keep descriptions of visible events separate from explanations of how an effect works. A public description can be useful without becoming an instruction sheet or a guarantee about a performance.

The performance in this guide is invented: a colored ring is described as appearing beneath a clear display cover. No trick has been designed, rehearsed, booked or performed. The example gives no method, safety procedure, rights clearance or claim of membership in a professional association. The workflow is a proposal for reviewing words and disclosure boundaries.

Write only what the intended audience needs to know

Begin with the purpose of the copy. An event listing may need a short description of the act's character and format. A private booking discussion may need questions about the venue and the planned audience. Neither automatically needs the mechanics of the fictional ring effect.

For the invented listing, a working sentence might say, “A short close-up performance built around an unexpected appearance beneath a clear cover.” Treat that sentence as draft copy for the fictional exercise. It doesn't establish that a performer offers the act, can perform it in a particular room, or has approved those words for advertising.

Ask the performer which visible details can be described in advance. They may prefer to name a broad experience while keeping a particular reveal out of public copy. Record the answer rather than deciding that a more detailed explanation will sell the booking better. A surprising detail can lose its purpose when a listing gives it away.

The event run-sheet guide addresses owners, transitions and timing. This task comes before those running-order decisions. Its deliverable is a publishable description with a clear approval boundary, not an account of where the performer stands or how the effect is achieved.

Separate the public copy from the private question

Use two working areas: the proposed audience description and questions that need a restricted conversation with the performer. A note asking whether a line reveals too much belongs in the review area. Don't paste a confidential explanation into the public draft as supporting material.

Google Drive's sharing guidance distinguishes viewer, commenter and editor access. Those are document permissions with different capabilities. They give a basis for choosing how someone can review a copy; they don't establish confidentiality, prevent every disclosure, or authorize publication of the performer's material.

Ask the owner to choose the appropriate review access for the actual task. A person checking wording may not need to reorganize a shared folder or alter unrelated files. Keep the public-copy draft small enough that it can be reviewed without access to a folder of private show notes.

For the fictional ring description, the reviewer might need only the sentence and a question: “May the listing mention the clear cover?” There is no need to invent or record a secret mechanism to ask that question. If the performer needs to discuss a private detail, agree on the appropriate channel before collecting it.

Check the promises hidden inside ordinary words

Words such as “anywhere,” “every guest” and “guaranteed” can make the listing say more than its writer intended. An audience description should not turn an unconfirmed format into a promise about every venue or viewer. Ask what the performer has actually agreed to describe and what remains a booking question.

In the invented example, “a clear cover” identifies a visible object in the proposed copy. It doesn't establish how well a distant audience could see it. If the organizer wants a large-room performance, record that requirement as a question for the performer. Don't write a viewing-distance or capacity claim without an actual basis.

Keep participation wording equally careful. “A guest may be invited to take part” is a proposed description whose use still needs agreement. It doesn't give the writer permission to assign a real person a role, promise how they will respond or state that a particular activity is suitable for them.

This guide doesn't assess audience suitability, venue safety or physical performance requirements. Those decisions require the responsible people and the actual circumstances. The copy review can identify an unanswered question without resolving it through more confident wording.

One useful test is to underline each promise in the draft. Ask whether it describes the approved fictional concept, an actual statement from the performer in a real assignment, or an assumption introduced by the writer. Remove or return the assumption for clarification before calling the copy ready.

Review a description without silently approving it

Google Docs' suggesting guidance describes changes that can be reviewed and accepted or rejected. Use that distinction to keep a writer's proposal visibly separate from the performer's decision. Accepting a document suggestion records a text decision within that review; it doesn't by itself demonstrate a booking, licence or completed performance.

Suppose the fictional draft says the ring “appears without anything being touched.” A reviewer proposes “an unexpected appearance beneath a clear cover.” The second sentence removes an unnecessary mechanism-like assertion. It is still a proposal until the relevant reviewer approves it for the intended use.

Keep a question attached to its exact wording. “Is this acceptable?” becomes ambiguous after someone rewrites the paragraph. A more useful comment identifies the clause under discussion and asks whether it may appear in the event listing. If the destination changes to a video caption, review that use separately rather than treating approval for one placement as unlimited permission.

The product-copy claim guide deals with traceable product statements. Here the distinctive review issue is what the audience can be told about an effect while preserving the performer's chosen disclosure boundary. A factual-sounding sentence can still reveal a detail the performer doesn't want published.

Prepare a copy that can travel without the review notes

Create a clean recipient copy only after the relevant wording decision is made in a real assignment. Label its intended destination and keep unresolved questions outside the publishable passage. In this fictional exercise, the status remains “draft description for review” because nobody has approved an actual booking description.

Read the clean copy on its own. Does a reader understand the proposed experience without seeing private questions? Does it still contain a promise that was removed during review? Has a note such as “confirm venue format” accidentally become part of the public sentence? This is a copy check, not a performance rehearsal.

Keep any cover image separate from evidence about the act. The illustration accompanying this guide is conceptual, with glass, velvet and a colored sphere. It is not a photograph of the fictional ring effect, a real performer, or a tested method. A cover shouldn't suggest that someone has watched or verified a show.

If the performer changes the visible effect or asks for less detail, return the description for a new wording decision. Preserve which copy had been approved for which use. Don't solve the mismatch by publishing an older paragraph because it sounds stronger.

The finished handoff should contain the intended passage, its destination and any outstanding condition that prevents use. Nothing in this exercise authorizes an actual publication. The useful result is a description another person can review without needing the secret method or being asked to believe a performance claim that hasn't been established.