Performance Verification Report?

Hi Mark thanks for your post! If you're still looking for input on this it may be an idea to cross-post to the Ticketing & Admissions Community? Hopefully you'll receive some responses over there. 

- Gill Tasker, Community Manager 

Hi Mark Levine,

You may have already found these:

- Performance Listing

- Performance Base Price and Availability

Here's a related question on verifying price layers, that may also be helpful.

I actually have in mind to create a custom report like this for our box office--to check the granular or custom setup stuff that isn't captured in standard reports--but haven't done so yet. Would be happy to share or compare, whenever I manage to start that one.Or if you're looking for specific data to create your own, maybe I or one of the many database magicians around the forums could point you towards relevant tables.

Best,

Ryan

Thanks Ryan Mauldin . I'm looking for a lot more.

I created a somewhat substantial report in another system (AudienceView) for an previous job. It had ticket-text, a buy tix link, all the prices and fees, holds/capacities, promocodes and links, seating chart image, presale codes/links. I made all of my promoters (Live Nation, AEG, etc) sign it before I put it onsale so that they could verify everything. It was also pretty helpful for my resident companies when we would build a few different subscription packages.

Right now, I just want to check my own work, because, you know how it goes... paranoia of screwing something up.

Thanks Gill Tasker (she/her). I'll do that!

Completely understand.  Most of our box office setup-checks are vary manual and scattered, which is why I'm planning to do the same. There really are so many pieces, not even accounting for third-party, custom web, etc etc.

Mark Levine,

Not so much a report to evaluate the work you have done, but we have a crucial checklist built as an extensive Excel document that we call a "build log" that is used by the staff that build our events.

There is an entry for everything on it.  From the basic things like the performance name, to keywords, to MOSes and Offers, Price Type Templates and even optional things like individual Content Tab items.  It is detailed and specific, and outlines exactly what information is supposed to be represented in each section and, when relevant, whether it is supposed to be built on the Performance level or Production Season level (or higher).  The builder also indicates their initials in that column so it is known who built each event.

Importantly, too, whoever is building the event checks off each element (with an 'x') after they have added it to the event, or, in the case of items that are not added to that event, they check that off as well (with an 'o') so as to indicate that that item was considered and intentionally not added rather than just "maybe not done yet".

Lastly, when the event is fully built and "ready", the builder lets someone else know so that they can go over everything again, proof it, and add their initials as well when done.  Maybe it is not as fluid as a report which would collate everything together, and yes, it takes a little bit of training to make sure one is proofing in detail rather than just assuming that the builder got it right in the first place, but we have found it to be highly effective in terms of catching most of the issues prior to putting something on sale.  And, when something ends up slipping through the cracks, you can often go back and look at the log and, not place blame because that rarely helps, but to use it as a learning moment to recognize what happened (e-mail correspondence that did not go to each member of the team, misunderstanding of how one particular element works, etc...), and then to update the build log and/or practice of communication to avoid that from happening in the future.

I first built this guide for my own use back in 2013 as I had to get the buy in of the Box Office Manager back then.  But once it started being regularly used, it has undergone many transitions and evolutions.  It is now a fully integral part of the build process, and there are now two separate documents, one for proper performances and another for education events.  Things just do not get built now without going into the build logs.  Again, nothing is perfect, but this works extremely well for us.  As well as being useful for training new staff on how to build things as it literally has everything that needs to be done there in black and white (and colours!  Because sometimes it is nice to add colours to your Excel.).

Best of luck in your building!

John A. Moskal II

I would love to take a look at this.  If you wouldn't mind sending to heather.fails@houstonsymphony.org.

Thank you!

John,

I would also love to see this excel if you are willing to share!  Right now I think I have most of the things across multiple worksheets in an excel file, but would be great to see how someone else formats a show build setup sheet!

mason@operaphila.org

Jeff

Hi John - I'd love to also see this excel building setup doc if you are wiling to share.    arenfo@umich.edu

Thanks! 

Sent.  I hope it proves helpful in some fashion.

Given how frequently I find myself learning/benefiting from your posts...  could I just ask you to send me a zip of your C: drive? 

I would love to see this too if you dont mind lrm6@kent.ac.uk. 

The implied compliment is exceedingly kind, and I thank you very much for it.  Please feel free to reach out for this and/or any other content I have offered at any time.  jmoskal@thecenterpresents.org

Hi, John A. Moskal II.  I too would love to see your checklist.  It sounds like it would be extremely helpful to our team.  Thank you so much! 

Diane 

DianeFontana@spokanesymphony.org

Oops!  Should have commented here.  I would also love to see your build document if you're still willing to share.  dianefontana@spokanesymphony.org.

Thank you!!!

Diane Fontana