Paper Trails: Why Your Call Sheet Deserves a Place in the Portfolio

I keep a box file of call sheets. It is not a stylish box file. It is the kind of thing you buy in a stationery panic before a tour and then cannot quite throw away. Inside are folded A4 sheets with venue addresses, get-in times, contact numbers and the occasional coffee ring. To most people, they are admin. To me, they are proof.

This is an opinion, but I think it is a useful one: the backstage paper trail is part of the portfolio. Not the whole portfolio. Not a replacement for the finished work. But a record of how the work was made, who made it with you and what it actually took to get the thing on its feet.

The tidy lie of the polished portfolio

Most creative websites show outcomes. A poster, a production shot, a shiny project page, a list of credits. All of that matters. But it can create a tidy lie: that the work arrived fully formed, made by one person, in a straight line.

A call sheet says otherwise. It shows a company. It shows a schedule. It shows that the show had a get-in at 8am, a technical rehearsal at 2pm and a note session that ran longer than planned because the lighting cue on the final scene was not quite right. It shows the person who drove the van, the venue contact who saved the day and the stage manager who quietly moved everything forward by fifteen minutes when the traffic went wrong.

For a UK touring context, that matters. Regional venues are not interchangeable backdrops. A call sheet from a wet Tuesday in Leeds tells a different story from one in a seaside theatre with a tiny loading bay and a very specific rule about where you can park. The admin is local knowledge. The admin is craft.

What to save, and what to let go

Not everything deserves a folder. A portfolio artifact should do at least one of three things: show collaboration, show process or show a useful bit of context. If it does none of those, it can probably go in the recycling.

Save the call sheet for a show that meant something, especially if it shows the shape of the day. Save a sign-in sheet if it captures a company or a workshop — but redact personal details before it goes anywhere near a website. Save prop lists, rehearsal notes, annotated scripts, ground plans, get-in schedules and the photographs of whiteboards that you took because you knew the board would be wiped by lunchtime.

Let go of the fifth copy of the same risk assessment. Let go of receipts unless they tell a genuinely funny story. Let go of anything that includes somebody's phone number, home address or medical information. The point is not to archive every piece of paper. The point is to keep the bits that make the work legible.

A small system that does not become a scrapbook

The easiest way to ruin a good artifact is to dump it into a website with no context. A blurry photo of a call sheet is not a story. A blurry photo of a call sheet with one clear caption is.

Start with one folder per project. Name the files properly: a date, a project name, a document type. Something like 2026-03-14_ProjectName_CallSheet. Scan or photograph the paper flat, in good light, without your lunch in the background. Then write one sentence that explains why you kept it. Not an essay. One sentence: “The day we loaded into a venue with a lift that could take one flight case at a time.”

Then choose three to five artifacts for the public page. Not thirty. Three to five. A call sheet, a prop list, a rehearsal note, maybe a photograph of the get-in. Group them by story rather than by format. The question is not “what did I keep?” It is “what does this help someone understand?”

Sharing artifacts without oversharing

A personal site is a good home for this because you can control the frame. Put the artifacts in a project page or a behind-the-scenes section, and use them to support a short piece of writing. The artifact is the evidence; the caption is the argument.

Redact anything personal. Crop out phone numbers and signatures unless you have clear permission to share them. Check with collaborators before publishing a call sheet that carries their names. If in doubt, describe the artifact rather than reproducing it. A sentence about the get-in can do almost as much work as the document itself.

And make the images accessible. Alt text is not optional. A call sheet is a visual document, but the useful information is in the details. Write alt text that says what the artifact is and why it is there, not just “call sheet”.

The artifact as a calling card

There is a commercial argument here, too. If you are a producer, stage manager, designer, performer or creative freelancer, a portfolio of artifacts shows that you understand the unglamorous machinery. It shows you can plan, communicate and work with a team. That is often more persuasive than another glossy headshot.

It also gives collaborators something to recognise. A venue may not remember every show in a busy season, but it will remember the company that arrived organised, signed in properly and left the dressing room tidy. A call sheet is a small piece of that reputation.

So keep the paper trail. Not as clutter, and not as nostalgia. Keep it as evidence that the work was made by people, in places, on days with weather and traffic and too much gaffer tape. Then curate it with care. The archive does not need to be big. It needs to be honest.