When a subcontractor has one site, the contracts manager can see every gang. At three or four sites, things start slipping: a gang turns up at a plot that isn't ready, two gangs are sent to the same stage, someone's card expired last month, and on Friday nobody's sure who did plots 40 to 44.
What goes wrong with multi-site gangs?
| Problem | Usual cause | What fixes it |
|---|---|---|
| Gang turns up to a plot that isn't ready | Programme changed, nobody told the gang | Tasks updated on the phone, not by ring-round |
| Two gangs on the same work | Allocation in someone's head | Allocation recorded per site and plot |
| Wrong person on a specialist job | Qualifications in a filing cabinet | Qualifications and renewal dates on the operative's record |
| Payroll arguments | Work recorded at week-end from memory | Work submitted against the plot on the day |
| Shared plots paid twice or not at all | No agreed split | Payment split recorded on the submission |
How should you allocate gangs?
Start from the programme. The housebuilder's programme tells you which plots are ready for which stage next week. Allocate gangs against that, not against last week's habits.
Allocate to plots, not just sites. "Gang B at Meadow View" leaves the gang deciding where to start. "Gang B, plots 31 to 34, second fix" doesn't.
Check qualifications at allocation. If a job needs a specific competence, check it when you allocate, not when the site manager asks.
How do you keep track during the week?
- Tasks on the phone. Each gang sees its tasks for the day and the plot information and drawings that go with them.
- Messages on the task. Questions and photos go on the task, not a WhatsApp group that mixes five sites.
- Submissions the same day. When a stage is finished, the gang submits it against the plot from the app, with quantity and any form.
- Contracts manager view. The CM sees tasks, submissions and issues across all their sites in one place.
A worked example
Fictional example. A dry-lining subcontractor runs five gangs across three sites. On Monday the contracts manager assigns tasks from the programme: Gang A to plots 12 to 15 on Site 1, Gang C to plots 50 to 53 on Site 3. On Tuesday the housebuilder delays plot 14. The CM moves Gang A's task for plot 14 to plot 16; the gang sees it on their phones before they unload. Plot 15 is shared between two operatives, so the submission records a 50/50 split. On Friday, the office approves the week's submissions and the totals per operative are already there.
What about qualifications?
Many trades need operatives to hold specific cards or registrations, and some expire. Keeping copies in a shared drive works until someone needs to know, on site, whether the person in front of them is allowed to do the job. Store operative qualifications with images and renewal dates on their record, and the contracts manager can check from the portal.
Where SubbieNow fits
SubbieNow gives contracts managers a view of operatives, their sites, qualifications and active tasks, and gives operatives a native iOS app for tasks, site information and work submissions with payment splits. It's built around the four user types a subcontractor actually has.
If you're running gangs across several sites from a phone and a spreadsheet, book a 30-minute demo and bring your programme.
Frequently asked questions
How do I know which gang is on which plot?
Allocate gangs to sites and give them plot-specific tasks. When they submit work against a plot, you have a record of where they were and what they did.
How do you split payment when two operatives share a plot?
Agree the split before the work starts and record it on the work submission. SubbieNow supports configurable payment-split logic for shared work.
How do I stop unqualified operatives being sent to a job?
Keep qualifications and renewal dates against each operative and check them when you allocate work.
