Frames Don't Put Themselves Up: Scheduling Marquee Crews

Frames Don't Put Themselves Up: Scheduling Marquee Crews

Seven in the morning, a field an hour out of town, a truck with a 40x80 frame tent on it. Two people are standing next to it. The job needed four.

The tent went on the calendar eleven months ago. The crew went on the yard whiteboard in August. One of the four told the office he'd be away that week, and the person who answers the office phone isn't the person who keeps the whiteboard.

The install still has to happen, so the two who showed up start calling around. The day that was supposed to end at four ends at nine.

The tent was booked in one place and the crew in another, and nothing put the two side by side. In tent and marquee rental the booking runs longer than the event, the labor does too, and marquee crew scheduling has to cover every one of those days.

A Saturday wedding is a site visit, two install days, a handover and a strike, spread over a week and usually split between two crews. A roster that only knows Monday, Tuesday and Wednesday can't hold that.

Crews Belong to the Build, Not to the Day

Most shops roster by day because every other business does, three on Monday and four on Tuesday. That works for a counter that opens at nine and closes at five, and it stops working once the work is a tent on somebody's lawn.

Here's a made-up job written out as work instead of as a date. Job M-0442, the Ellery wedding: a 40x80 frame tent (about 12 x 24 meters) with sidewalls, liner, flooring, lighting and heaters for an October Saturday.

Day Task Who is needed
Mon, Oct 19 Site visit and measure 1 senior, half day
Wed, Oct 21 Frame and top up Crew A, 4 people, truck
Thu, Oct 22 Sidewalls, liner, flooring, lighting, heaters Crew A, 3 people
Fri, Oct 23 Client walk-through and handover 1 senior, 2 hours
Sat, Oct 24 Event 1 person on call if wind is forecast
Mon, Oct 26 Strike and load out Crew B, 4 people, truck

Crew A is on this job Wednesday and Thursday. If wind pushes the frame to Thursday, Crew A should move with it, and whatever Crew A had on Friday is now in the way. A roster that only says "Crew A, Wednesday" leaves four people on an empty day and nobody on the day the frame goes up.

Add the table up at a 10-hour install day and an 8-hour strike and the Ellery job is about 108 crew hours. That's 4 for the visit, 40 on Wednesday, 30 on Thursday, 2 at handover and 32 on the strike, before anyone drives anywhere.

Bar chart of crew hours by day on a 40x80 wedding tent job, adding up to 108 crew hours

Put the hours on the job and you find out which installs lose money. Two long days on a soft lawn down a narrow driveway isn't the same job as a flat parking lot with a gate the truck drives straight through, even when the tent and the invoice match. If the hours sit against the booking you can see that at the end of the season, and if they sit against the week you see payroll and nothing else.

In EquipDash, staff rostering runs on the Schedule grid. Each shift belongs to one person on one date at one of your locations, and you write the job in the shift notes ("Ellery, frame up, 40x80"). Shifts don't follow a rental booking on their own, so when an install moves you drag its shifts to the new day or to another person's row.

The grid does show the rental side. A Booking demand row above the staff rows counts each day's pickups and returns, and a Heads up bar warns you about any day with a pickup or return and no shifts at all.

Publishing the Schedule emails each person their shifts, and Publish Updates emails only the people whose shifts changed. Staff can send you the hours they can work and ask for days off from a link or the EquipDash app. Once a day off is approved, the shift form warns you if you try to put that person on that date, so a week away no longer depends on someone remembering to update the whiteboard.

The site visit is a shift too

Site visits fall off rosters because they don't look like installs. Half a day, one person, no truck, often six weeks before anything happens. So they go in somebody's personal calendar, and three of them eat a Monday the office thought was free for yard work.

Put the visit on the Schedule as a shift the day it's promised. It stops you telling a client you can fit a measure in next week when the person who measures is already out twice.

The visit also tells you what other dated work the job needs. Before any stakes go in, someone calls 811 to get buried lines marked (Before You Dig Australia and beforeUdig do the same job in Australia and New Zealand). On caliche, a patio or a parking lot you ballast instead of staking, so the truck carries concrete blocks or water barrels and the crew needs extra hands to load them.

Most US cities use the International Fire Code, and under its tent chapter a tent over 400 square feet usually needs a permit. The fire marshal will usually want the flame certificate for the top and sidewalls under NFPA 701. If there's an inspection before guests arrive, that's one more date with one of your people on site, and it moves when the install does.

The Clash Nobody Sees Until Thursday Morning

The double booking people picture is two installs starting the same morning. That one gets caught, because both jobs sit on the same line of the whiteboard.

The one that gets through looks like this. In March, Crew A goes on the Ellery install for Wednesday and Thursday. In May, someone else books the Hartnell strike for that same Thursday and puts Crew A on it, because in May the Ellery install was a line on a calendar nobody was reading.

Whoever took the Hartnell job never looked at Crew A's Thursday, because Crew A's Thursday wasn't written anywhere they could see it.

You want to see the overlap when it's created. In EquipDash, dragging a shift onto one the same person already has gets refused, and the shift form refuses a new shift on the same hours. If Crew A's Thursday already says Ellery from 7 to 5, a Hartnell shift for those hours is turned away in May, when sorting it out costs one phone call.

Schedule grid showing an overlapping shift refused on a crew member's Thursday

A shorter shift that sits inside Crew A's day can still save from the form, so look at the person's row before you add one.

That check only works if Crew A's Thursday is on the Schedule in March, and two habits make sure it is.

Put names on every day of the job the day you take the booking. An install with no crew against it is an unbooked install, however far out it is. Provisional names beat empty cells, because a provisional name generates a clash and an empty cell does not.

Taking a booking at 9 p.m.? Open the Schedule for those dates before you say yes, so you aren't texting the crew lead in the morning to find out he's already promised. If half your crew is casual and may not be back next summer, put the shift on a crew lead you know will be there and swap names when you hire for the season.

Order changes count too. The client calls on a Tuesday and adds 40 guests, so the 40x80 becomes a 40x100. That's another 20 feet of frame, more sidewall and flooring, and maybe another pair of hands on install day, so update the shifts when you update the order.

Go down next week's list with the crew leads every Thursday. Same time each week, say after lunch, job by job: installs, strikes, site visits, inspections and the names against each.

If somebody is down for two jobs on one day, you find out then. In a two-owner shop it might be a phone call on Sunday night, and twenty minutes is usually enough either way.

A Dash bot can do the prep. You describe it to Dash in plain words, for example "every Thursday at noon, email me next week's installs and strikes with the names on the Schedule against each, and list any job with nobody on it," and set it to run weekly on that day and time. Bots can read both the bookings and the staff Schedule, so the list lands in your inbox from the system instead of from memory.

Not Everyone on the Van Can Rig

Tent work comes with licenses and cards, and they expire. A single truck rated at 26,001 pounds or more needs a Class B CDL to drive, and forklift operators need training with an OSHA re-evaluation at least every three years. Australian states share the same heavy vehicle classes, so a two-axle truck over 8 metric tons GVM needs a Medium Rigid (MR) license whether you're in Sydney or Brisbane.

First aid and CPR cards and aerial lift training go on the same pile, plus whatever your insurer wants to see at renewal. Ask your broker for that list in writing before the season, so you know which cards to chase.

A forklift card runs out in February, nobody looks, and in June that person spends a day loading the truck with it. Under the same OSHA rule the employer certifies each operator's training and evaluation, so a lapsed card lands on the company.

In EquipDash, each person's Profile tab has a Certifications card. Driver's License, First Aid and CPR are built-in types, and a forklift card or lift ticket goes in as Specialty Endorsement or Other, with the issuing body, the number and the expiry date. Guide and boat certs such as Swiftwater Rescue and USCG licenses have their own types too.

Staff profile Certifications card with an expired forklift card flagged

You type each card in once and only look at it again when the reminder comes.

Scan the card itself onto the person's Documents tab, so the copy is in the office system and not in a folder in somebody's truck.

Anything expired or due within 30 days shows as a row on the Dashboard and in a weekly Monday email to admins who've opted in. Turn on the Certifications column in the Staff list and it shows there as a red or amber chip too.

Thirty days matters, because a renewal class can take weeks to book.

With four of you, everyone knows who can run the forklift, drive the 26-footer or lead a crew on a 40x80. The April hires are what break it. By June the owner is the only one who knows which of them can be trusted on the forklift, and the owner isn't always in the yard at six in the morning.

Staff Roles in EquipDash are roles you name yourself in Settings > Staff Roles, so you can set up Crew lead, Installer and Driver and filter the Schedule by role. A filtered Thursday showing two installers and no crew lead tells you on Tuesday what you'd otherwise find out on the lawn. The filter shows roles, not whether a card is current, so check the Dashboard's certification rows for lapsed cards when you fill the week.

Hours on the Job, Not Reconstructed From Memory

Installs run long, and a tent crew rarely leaves at the time on the schedule. The ground is softer than the visit suggested, a section is bent and has to be swapped, and the eight-hour day runs to eleven. Plan for it.

When hours get rebuilt from memory, payroll is a guess and staff notice fast. Job costing is a guess too, and nobody notices that at all.

Guessed hours also hide overtime. Under federal overtime rules, time and a half starts past 40 hours in a workweek, so four 10-hour install days put a crew at 40 by Thursday night and the whole Friday job is overtime. California also counts past 8 hours in a workday, and in Australia your modern award sets the overtime and weekend rates.

In EquipDash the crew can clock in on a shared time clock tablet in the yard with a 4-digit PIN, or from the EquipDash app on their own phones when the day starts on site. With clock-in location switched on, a phone punch shows the name of your yard, the customer's name and address when they're at one of that day's delivery stops, or Off site.

Each punch is matched to that person's scheduled shift, so Timesheets show scheduled against actual and flag a late start. An eight-hour install that ran to eleven shows up as three extra hours on that day, instead of a vague sense that the Ellery job was hard work.

Missed punches get fixed with Add entry, and the week exports to CSV, so your bookkeeper applies your state's or award's overtime rule to real hours. Shops on Xero Payroll in Australia, New Zealand or the UK get hours sent to Xero every night as draft timesheets to approve, which beats typing in hours the crew texted you on Sunday night.

After a season of punches you have real labor hours for each tent size and each kind of site, so quote from those. On paper the Ellery job is about 108 crew hours, and your timesheets tell you whether the private-lawn jobs run past that and how far. The gap is real money and belongs in the price, along with the access and site costs in the quote.

The Schedule, time clock and timesheets come with staff management on the Growth plan, and the pricing page has the prices. Its team member limit counts people with their own EquipDash login, not everyone on the Schedule.

When the Forecast Moves the Week

Wind stops an install. A soaked field stops the truck getting through the gate without tearing up the lawn. Thunder stops it too, because nobody should be holding an aluminum frame leg in a storm: the National Weather Service says to wait 30 minutes after the last rumble of thunder before going back out.

Afternoon storms are the usual summer pattern. In Arizona the monsoon officially runs June 15 to September 30, and the National Weather Service says storms build over the mountains in the afternoon and their outflow can hit lower ground with winds of 50 mph or more.

OSHA's heat guidance is water, rest and shade, with morning work and shorter shifts, so a July install in Phoenix that's two days on paper may need three short ones starting at 5 a.m.

Push the Ellery frame from Wednesday to Thursday and this has to move:

  • Crew A, who were on Wednesday and Thursday, are now on Thursday and Friday
  • Crew A were also on the Dorsey install Friday, which is now a clash that didn't exist an hour ago
  • The truck goes out a day later, which hits whatever it was doing on Friday
  • The sidewalls, liner, flooring and heaters that follow the frame slide a day, and so does their wash and dry before the next event
  • The Friday walk-through gets squeezed toward the event
  • The Monday strike may need to move if the job behind it is tight

Weather push moving the frame to Thursday, with the crew and truck clashes that follow

Move the booking's dates in EquipDash and the tent, liner and flooring move with it, and the Booking demand row on the Schedule shifts to the new days.

Then drag the crew shifts, starting with the last day. Crew A's Thursday shifts go to Friday first, and the Schedule refuses them because they overlap the Dorsey install.

Sort out Dorsey, move Thursday to Friday, then Wednesday to Thursday. Publish Updates emails only the people whose week changed.

When the same move lives across a whiteboard, a spreadsheet and three phones, a Tuesday weather call turns into an afternoon of calls, and at least one person doesn't get the message.

Making the weather call

Make the call the afternoon before, at the same hour every day in season, from the gust forecast and the wind rating in the tent maker's manual. Wait until seven the next morning and the crew has already loaded the truck and may be an hour down the road.

Keep a short list of people who'll take a call the day before: former crew, a couple of college students home for the summer. Message the list a week or two out with the days you might need them, and if you need one of them to keep a Saturday free, pay a flat fee to hold it.

Once you've called it, tell the crew first so nobody loads the truck, then phone the client yourself. The client shouldn't hear it from their planner or from a crew member's text.

The wind limit, who pays for a postponed install and what happens to a deposit when the client pulls out after the truck is loaded all belong in the signed contract, written before the season. One free date move for weather, then the deposit stays with you, is a rule clients understand, and it saves an argument by text at 11 p.m.

Builds That Run Longer Than a Shift

Bigger work breaks the daily model completely. A county fair, a three-day festival or a corporate install with a phased handover means five to ten days on site, crews rotating, a skeleton team in the middle and a strike that needs more people than the install did, because everything comes down at once.

Take a three-day festival with a six-day install and a two-day strike. A roster with the same four names against all eleven days tells you nothing about whether the Thursday of the install is covered. Every EquipDash shift is one person on one date, so the festival becomes a block of shifts you can copy and drag, and each day shows who is really there.

Aerial view of long structure tents at a fair site with vendor booths

Write the rotation down before day one: who works install days one to six, who swaps in from yard work, and who gets a day off before the strike. Otherwise you find out on day seven that the same three people have worked every day. In California, a seventh straight day in a workweek is time and a half from the first hour.

If the site is three hours away, the drive is part of the job and the day is shorter than it looks on paper. Rostering a full install day at the end of a three-hour drive is how an install slips into a second day, and the motel nights belong on the job too.

The strike often wants more bodies and fewer specialists, and it's rarely the same crew who put the tent up two weeks earlier.

Somebody also has to be the one phone number on site for the client, the fire marshal or council inspector, the venue manager and the other vendors working the same field. Name that person on the job.

A four-person crew idle for a day on a festival install, because the flooring truck was scheduled behind the frame instead of with it, is a day of wages against a job that was already priced.

Tent and marquee rental software that holds the tent, liner, flooring and the install-to-strike dates on one booking covers the stock side of that sequence. Shifts with the job in the notes cover the crew side, so the order is written down once instead of remembered separately by four people. AV companies hit the same problem when they send crew as well as gear.

FAQ

What is marquee crew scheduling?

It's rostering install crews against specific jobs and days instead of against a weekly shift pattern. A tent job is a site visit, one or more install days, the event and a strike, so the crew you need is different on each of those days and usually means two crews. On the roster that means a named person on each day of each job, with the job written on the shift.

Why is rostering by day a problem for a marquee company?

Because the work is a job, not a day. If Crew A is rostered to Wednesday and the install moves to Thursday for weather, the roster says four people are working a day with nothing on it and nobody is on the day the frame goes up. Write the job on each shift and move the shifts when the job moves, and any new clash shows up as you move them.

How do you stop two builds being assigned the same crew?

Roster crews when the booking is taken instead of the week before, and use a schedule that refuses an overlapping shift when it's entered. The clash that catches people out is usually a two-day install running into a strike someone else booked weeks earlier for the second day. In EquipDash a dragged shift that overlaps one the same person already has gets refused, and the shift form refuses a new shift on the same hours, so check the person's row before you add a shorter one.

How should rigging and working-at-height certifications be tracked?

Against the person, with an expiry date, and with a warning weeks before the date instead of on it. Renewals take time to book, so a warning on the day the card lapses comes too late. In EquipDash each person's Certifications card holds the type, number and expiry date, and anything expired or due within 30 days shows on the Dashboard and in a Monday email to admins.

How do you record crew hours on a build accurately?

Capture them against the shift as they happen instead of rebuilding them at the end of the month. Crew clock in on a shared tablet with a 4-digit PIN or from the EquipDash app on site, each punch is matched to the scheduled shift, and Timesheets show scheduled against actual. Missed punches get fixed by hand, the week exports to CSV for payroll, and you end up with labor hours per job to price the next difficult site.

What has to move when the weather pushes a build by a day?

The crew on that install, the truck, the sidewalls, liner and flooring that follow the frame, the client handover, and sometimes the strike behind it. Each of those can clash with another job, which is why the reschedule is more work than the call. In EquipDash, moving the booking's dates moves the tent and stock, and when you drag the crew shifts to the new days the Schedule refuses any that overlap another job.

How is scheduling different on a multi-day festival or show build?

Crew assignments need specific days instead of a block, because a ten-day install with four names against the whole period doesn't tell you whether Thursday is covered. Rotation and rest need planning up front, travel time counts as committed hours, and the strike crew is often bigger than and different from the install crew. One named person should own the site as the contact for the client, the fire marshal and the other vendors working the same ground.

Can general staff rostering software handle marquee builds?

For the shifts themselves, yes: a standard roster app handles shifts, availability, time off and notices to the crew. The gap is the tent: when an install moves, you change the booking in one system and the shifts in another, and the roster has no idea the job moved. In EquipDash the day's pickups and returns sit in a Booking demand row above the staff grid, and a Heads up bar flags any day with a pickup or return and no shifts.

Does ChatGPT send customers to you?
See who AI recommends when people in your town ask. Free, in about a minute.
Manage your business
in one place
Start your free 21-day trial and see how EquipDash's AI-native platform (with Dash AI and Dash Bots) simplifies your operations.
EquipDash Dashboard