Technical Documentation – After (and Pre-Show Checks)
I am extremely pleased with the results of our technical documentation and feel that the hours spent creating and developing them have been well spent.
We used a ‘Progeny Theatre’ layout, font and format to ‘brand’ our documentation, which gave them a professional look as well as used previous examples of other Theatre Company’s work as case studies for our own documents. The response to our documentation from the venue has been very positive and, as such, the LPAC are prepared for our arrival, which is now at 9am on Sunday 19th May.
All technical documentation can be viewed here.
Myself and the Stage Manager have produced a Performance Day Schedule which underlines the ‘desired’ performance day schedule. However, due to the recent date change (we were originally booked to complete our get-in the evening prior to performance day) we are aware that, because we are a’ tech-heavy’ group, our get-in may over-run and have planned our day accordingly.
We have completed a Pre-Show Check-list of all technical requirements and I am confident that we are fully prepared for performance day.
- Technical Documentation – completed and sent to venue.
- QLab file – completed 3 weeks prior to performance and has been kept up-to-date. Saved on memory stick to transfer to LPAC Apple Mac.
- Sound – all files saved in numerous locations in case of file corruption.
- Props – sourced and stored in venue.
- Set – finished and stored in venue.
- Costume – completed and stored in venue.
- Actors – briefed on Risk Assessment and Performance Day Schedule.
- Budget – up-to-date and with £30 left for last minute expenses.
Kate Dawson
Word Count: 251