Waiting on a webmaster for a one-line change
A sold-out night, a corrected name, a curtain time moved by half an hour. The words are ready. Publishing them still means writing to someone else and waiting.
The change is usually small. Saturday is sold out. An actor’s name was misspelled in the hero. Thursday moved from 19:30 to 19:00. The person who runs the season already knows the right words. They are the same words that went to the box office and into the Instagram caption.
What happens next is the slow part. The note goes to a webmaster, a freelancer, or an agency. It sits in a queue beside other clients. Someone has to open the right page, find the right field, publish, and write back to say it is live. If the first reply is “which Saturday?”, the change waits another day.
The theatre feels this as tedium. A task that would take a minute becomes a thread. The marketing lead checks the site the next morning, sees the old line still there, and sends a follow-up. By the time the page is right, part of the audience has already planned around the wrong time, or tried to buy a ticket for a performance that was full.
The delay is rarely malice. The webmaster is often doing the job the website requires: a person who understands the tool, standing between the company and the publish button. The people who know the show are kept away from that button, because the tool was not made for them.
That gap grows in a loud week. Opening week, a festival weekend, a sudden cast change. The building is full of facts that need to be public. The website still moves at the speed of an external inbox. Front of house hears the complaints first. The correction then goes back into the same queue that caused them.
Companies invent workarounds. A pinned Instagram story carries the real curtain time. A printed insert in the programme corrects the website. A staff member answers the same question by email twenty times. None of that replaces a page that says the right thing.
A theatre website should let the person who already wrote the update put it on the page. The one-line change should stay a one-line change. Hosting and security can stay with the platform. The publish button belongs with the people who already know Saturday is full.