VenueWiki news — what’s new in the manual and the calendar sync.
Ship notes, new connectors, new venues, and the occasional war story from the crew. Pull up a stool.
Ship notes, new connectors, new venues, and the occasional war story from the crew. Pull up a stool.
Connect Claude, ChatGPT or Grok to VenueWiki. Your AI can onboard whole tech packs, add photos and specs, and answer questions about any venue.
You can now connect Claude, ChatGPT or Grok straight to VenueWiki. Hand your AI a venue's tech pack and it will read it, split it into suggestions and send them in for review, or ask it anything about a venue already on VenueWiki.
Connecteam now syncs both ways with VenueWiki: published shifts land in Google Calendar or Outlook, and your calendar's busy time appears in Connecteam as unavailability — times only, no details. Hourly, or instant on plans with webhooks.
Your company rosters you in Connecteam, but your life's in Google Calendar or Outlook — so the roster manager books you on the day you told everyone you were away, because Connecteam never saw it. VenueWiki now syncs both ways: Connecteam shifts land in your calendar, and anything you're busy with in your calendar shows up in Connecteam as unavailability, without you typing it in twice.
Google lists big rooms like the ivy ballroom as their own place, so venues ended up with two pages. VenueWiki now files those listings as rooms inside the venue, and search takes you straight to the room.
You're rostered to the ivy ballroom. You search it, and you find two pages: one for the ballroom, one for ivy, each holding half of what you need. Google lists the ballroom as its own place, so adding it made a second venue. From today, a listing that's really a room inside a venue we already have gets filed as a room, automatically.
An AV company changed your shift without telling you? VenueWiki's two-way calendar sync now emails you the moment a Rentman, Humanity or Deputy shift changes time, date or gets cancelled — and logs what changed and when.
Occasionally an AV company changes a shift without asking you, or telling you. You said yes to a 10am start — but you can't make an 8 or 9am start, and nobody checked. If a company does the sneaky on you like that, VenueWiki now emails you immediately, and keeps a log of what was changed and when.
Link a rigging plot, patch schematic or spec sheet to a suggestion card and it now appears in the venue's AV manual under the right section, in the Files list and on the card itself — with the same voting as photos, and a way to add links straight from the suggest form.
Link a rigging plot, patch schematic or spec sheet to a suggestion card and it now appears in the venue's AV manual under the right section, in the Files list and on the card itself — with the same voting as photos, and a way to add links straight from the suggest form.
Upload a loading dock policy or technical advance and VenueWiki reads the numbers — dock heights, lift dimensions, door widths, room sizes — and shows the exact line each one came from. Also: AV manuals never silently drop a contribution, and venue-wide cards finally reach their pages.
Upload a loading dock policy or technical advance and VenueWiki reads the numbers — dock heights, lift dimensions, door widths, room sizes — and shows the exact line each one came from. Also: AV manuals never silently drop a contribution, and venue-wide cards finally reach their pages.
Upload a technical advance or dock policy and it is sorted into AV manual cards for review. Rigging gets its own category. Record every lift and loading dock a venue has, with dimensions. Attach PDFs and CAD drawings, or link Dropbox, Google Drive, OneDrive, SharePoint and Sync documents, to any card.
Upload a technical advance or dock policy and it is sorted into AV manual cards for review. Rigging gets its own category. Record every lift and loading dock a venue has, with dimensions. Attach PDFs and CAD drawings, or link Dropbox, Google Drive, OneDrive, SharePoint and Sync documents, to any card.
Turn it on from your profile — your polaroid appears at your venues.
You can now add yourself: flip on self-polaroid from your profile, pass the photo check, and your card shows up at the venues you work — supplier badge and all. First one went live at the MCA the same day it shipped. Faces on walls, the proper way.
Keep personal events from marking you unavailable — by tag or colour.
Not every event in your calendar should tell a roster you're busy. Now you can exclude them — by tag, or by colour — and they won't mark you unavailable. Recolour or retag an event and the sync respects it retroactively. Your calendar, your rules.
Faces on the wall — know who you're working with before you load in.
Venue pages now have a staff wall: polaroid cards of the crew who work there, added by venue managers. Walk into a venue already knowing who's who — names, faces, roles. It's the green-room corkboard, except it's there before you are.
Third roster system connected — your company links once, your shifts flow.
If your company rosters through Humanity, they can now connect it to VenueWiki once and every matched crew member's shifts flow to their own calendar automatically. That's three roster systems live — Rentman, Deputy, Humanity — with Humanforce next on the bench.
One glance at your week tells you who each gig's for.
Working for more than one company? You can now give each connected company its own colour — AV1 in one, Scene Change in another — so a glance at your week tells you who the gig's for. Works on Google Calendar and Outlook. And yes, one of the yellows is called "JJ Yellow" in the picker. The crew know why. Colour per company is part of VenueWiki's Calendar Sync.
Two crew flag the same fix, the page updates — and unverified specs say so.
Every spec on a venue page now carries its provenance. Anything unconfirmed wears an UNVERIFIED badge, and when two crew independently submit the same correction, the page updates to the crew-sourced value — no committee, no gatekeeper. What you read is what the room actually is, because the people in the room said so.
Google Calendar or Outlook — your shifts land in whichever you actually use.
Not everyone lives in Google Calendar. Calendar Sync now writes to Outlook too — same automatic sync, same updates and cancellations, pick whichever calendar you actually look at.
The deal we ran for the crew who built the first pages.
The early pages had to come from somewhere. The deal was simple: invite-only beta, and anyone with 10 approved contributions before July 31 locked in membership free for life. The founding crew who took it built the backbone of the manual — and they never pay. That offer's closed now, but it's why the good venues already have good pages.
Your shifts, on your calendar, without you touching anything.
If your company rosters you through Rentman or Deputy, your shifts now land straight in your Google Calendar — new gigs appear, changed times update, cancelled gigs vanish. Rentman runs two-way: block out a day in your personal calendar and your Rentman availability updates itself. No screenshots, no double-entry, no "hang on, i'll check the app."
What this is, who it's for, and why it exists.
VenueWiki is a shared field manual for event venues — loading docks, patch, power, house rig, room by room — written by the techs who actually work them. It's in closed beta now, with venues across Sydney already documented. If you know a venue like the back of your hand, this is where that knowledge stops walking out the door every time someone changes jobs.
Want the news without checking the bar? It lands in VenueWiki News when you're signed up.
Upload a technical advance or dock policy and it is sorted into AV manual cards for review. Rigging gets its own category. Record every lift and loading dock a venue has, with dimensions. Attach PDFs and CAD drawings, or link Dropbox, Google Drive, OneDrive, SharePoint and Sync documents, to any card.
Swipe, or use ← →, to browse articles.
If you tried uploading a venue doc in the last little while and got a page full of nothing — that was a real bug, not you.
The AI sorter was being cut off at 60 seconds while it read your document. Everything else in the pipeline reported success, so the page just landed empty with no explanation. Fixed, and given five times the headroom it needs.
While we were in there: if sorting ever does fail now, you'll see it say so instead of quietly showing you an empty page.
Upload a technical advance, a loading dock policy, a spec sheet. It reads the whole thing, breaks it into cards, and routes each one to the right room and category for you to check before anything goes live.
It sat between Stage and Comms because that's where it belongs — truss, points, motors and load ratings are their own discipline, not a footnote in staging.
Every room on VenueWiki has it already. Nothing to set up.
This one's overdue.
Venues don't have a lift. ivy has two that go to completely different parts of the building. MCA has three. The Opera House has more than twelve and they're nothing like each other — a goods lift, a passenger lift and a scenery lift share a word and not much else.
Up until today VenueWiki could only hold one of each, which made the answer to "will my case fit in the lift" somewhere between useless and wrong.
Now you can add as many docks and lifts as the venue has, name them the way the venue names them, and record dimensions for each. Same for docks — plenty of venues have more than one, at different addresses, with different height limits.
Cards can now carry files, not just photos.
Two ways to do it:
Upload it — PDFs and CAD files (.dwg, .dxf), up to 25 MB. PDFs open
straight in a new tab; CAD downloads.
Or just link it — paste a Dropbox, Google Drive, OneDrive, SharePoint or Sync link. We store the link, not the file. The venue keeps their rigging plot in their own storage, updates it when it changes, and the link on VenueWiki keeps pointing at the current version. Nobody has to remember to re-upload.
Fair warning on links: we can't control who can open a document sitting in someone else's cloud. The link's visibility is theirs, not ours, and we say so on the card.
The "also appears in" picker used to only exist when you submitted a suggestion by hand. It's now on onboarding cards too.
So when you're working through a document and a card about truss belongs in both Rigging and Stage, you tick it once during review rather than going back card-by-card afterwards.
If you're a venue manager or admin onboarding your venue's own document, your cards now publish when you approve them.
You were already able to approve each one individually straight after — this just removes the second lap. You read every card on the review screen; that's the review. Everyone else's submissions still go through the normal voting.
The nomination form was rejecting perfectly valid email addresses. Turned out the fields were in an order that made everyone type their details one row down, so the surname was being submitted as the email.
Email field's first now, first and last names are separate, and if it ever does reject something it'll show you what it read rather than just saying no.
You can nominate anyone — they don't need a VenueWiki account. They'll get an invite, and when they sign up the nomination is already waiting for them.
The onboarding page stops reloading on you. Switch to another tab to check a document, come back, and your place is kept. It was refreshing the whole page every time the browser regained focus.
Manual pages tell you what's going on. Instead of a blank space where a manual should be, you'll see whether it's being generated, whether it's waiting on the first contribution, or whether generation failed.
More room specs to fill in. Room width and depth, floor area, truss height (separate from ceiling height, because they're different numbers and riggers care about the second one), and entry door dimensions — because "will it fit through the door" is a real question with a real answer.
As always — if something's wrong on a page, flag it. That's what the button's for, and a venue page that nobody corrects isn't worth much.