An event is not one appointment.
Work separates into phases such as build, show and teardown, each with its own timing, roles and crew requirements.
Client results
Operational growth · Heavy AV
From paper check-in sheets to a connected labor operation.
Heavy AV asked for a mobile application to track crew hours. Understanding the operation behind that request revealed a larger constraint: growth was making coordination and administration increasingly difficult to carry through disconnected tools and manual records.
The business worked. It was working at the limit of what a manual process could carry.
Heavy AV supplies and coordinates the people who build live events. Getting the right people, cleared and confirmed, to the right venue at the right time is central to the service.
That work depended on Google documents and spreadsheets, paper check-in sheets, individual messages, calls and emails. Confirmations had to be interpreted and recorded by a person. Hours captured on site were entered again for payroll preparation and again for invoicing.
The initial request focused on tracking crew hours. The wider operational evidence showed that time capture was only one point in a connected workflow spanning enquiry, planning, booking, confirmation, attendance and administration.
The problem was not a lack of software.
Heavy AV investigated packaged project-management, crew-scheduling and time-tracking products. The issue was structural: each product covered part of the work while leaving the business to connect the remaining pieces through spreadsheets and manual coordination.
Participation must fit the workforce.
A distributed contractor network cannot be treated like an internal team expected to maintain another application and login.
Historical records must remain true.
Rate and role changes cannot silently rewrite the meaning of work that has already happened.
Access follows responsibility.
Office staff, planners and on-site crew chiefs need different capabilities and genuinely different access to business data.
The OpSol decision
Build around the operation—not around the original feature request.
The engagement expanded because connected operational evidence justified connected capabilities, not because a larger predetermined package was imposed.
Map the real work
Understand phases, roles, decisions, records and exceptions before designing interfaces.
Include non-users
Design for the people who participate in the workflow without expecting them to become software users.
Connect the record
Allow one trusted operational record to support later coordination and administration.
Introduce capability gradually
Validate new behaviour on real work before relying on it more broadly.
Delivered capability
One operational foundation, expressed through the interfaces each group needs.
The solution connects the workflow without forcing every participant into the same interface or asking the business to abandon its real operating structure.
Sales intake
Public enquiries become tracked leads instead of disappearing into a separate inbox, giving staff a clear place to qualify and progress each opportunity.
Booking and coordination
Events retain their real build, show and teardown structure, with crew requirements attached to each phase.
Contractor participation
Crew can respond to an invitation through a secure browser link instead of being required to install another application.
Hours and administration
On-site time capture creates a consistent record that can support payroll preparation and client invoicing.
Sales intake
From public enquiry to a visible operational pipeline.
Enquiry submittedPublic intake
Lead createdOperational pipeline
Privacy protectedLead details redacted
A public submission becomes visible work in the lead pipeline. Identifiable lead details and live volume counts have been redacted.
Booking and coordination
An event keeps the phases, roles and staffing state the operation actually depends on.
Privacy protectedEvent and crew details redacted
Build and teardown remain distinct phases with their own schedules, role requirements, assignments and response state. Event, address and crew identities have been redacted.
Contractor participation
One invitation lets a contractor review and respond without installing an application or creating an account.
01 · SMS invitation
02A · Confirmation page — details
02B · Same page — response controls
The invitation opens one secure browser page: the middle capture shows its event and phase details, while the right capture shows the response controls further down that same page. No response has been submitted in these captures. Gordon’s name is shown as Heavy AV’s founder; event, location, map, and token details have been redacted.
Hours and administration
Controlled time records become a payroll-ready administrative output.
Privacy protectedCrew identities redacted
Hours reviewedControlled time record
Administration preparedConfigured payroll export
Reviewed hours retain straight-time and overtime distinctions, then move into a configurable payroll export without reconstructing the record in a separate system. Personal identities have been redacted.
The result is capacity, not merely more software.
Crew requirements can be represented in the same structure the business uses to plan an event. Invitations and responses become visible assignment data. On-site hours become a controlled record that supports downstream administration. Managers can coordinate work without reconstructing the current state from separate conversations and documents.
Heavy AV has since expanded beyond its earlier regional operating footprint while continuing to develop the platform with OpSol. The platform provides a foundation the team can continue extending as the operation evolves.
The lesson
A visible technology request may be only one symptom of the constraint.
Heavy AV did not need custom software simply because packaged products existed. A tailored intervention became responsible because growth had exposed a connected, business-specific operating model that the available combinations could not carry without recreating the same manual coordination.
That is the distinction OpSol looks for: not “what can we build?” but “what is limiting the business, what capability would remove that constraint, and which intervention is justified?”