Files scatter. The client's brief is an email attachment, the revised layout is in a text thread, the photos are on somebody's phone, and the agreement everyone is arguing about exists in four slightly different copies. Each file made sense where it landed; together they make a job nobody can reconstruct.
Version confusion is the expensive part. When 'final', 'final-v2', and 'final-FINAL' sit in the same folder, someone eventually works from the wrong one — and the wrong one has a way of reaching the client at the worst possible moment.
And when the person who saved the file is out, the file might as well not exist. An operation shouldn't need one specific human present to know what was uploaded, which version is current, and where any of it came from.
Each work record is provisioned with its own project folder the moment it exists. Nest folders however your operation thinks — the point is that files land with the job, not with a person.
When an upload matches an existing file, OpsVue asks the right question: is this a new version of the same document, a different file to keep alongside it, or a duplicate to skip? Version families keep the full history and mark which version is current.
The documents OpsVue generates, like quotes, agreements, and invoices, appear in the job's files as version chains too, so the paperwork you produced and the files you collected read as one record.
Every file carries who uploaded it, when, and what it was originally called. Six months later, 'where did this come from' has an answer instead of a shrug.
Share folders with the specific people who need them. Team members in limited roles see only what's been shared with them, so a field team member gets the working files without getting the whole cabinet.
Search by file name, original name, tag, note, uploader, work record, client, or folder — and results say which of those matched. Favorites and file comments keep the frequently used and the discussed close at hand.
Each work record has a files view of its own: an overview of what's there, the documents, a timeline of activity, and an attention list that includes uploads the job's workflow still expects but doesn't have.
An event planner keeps the venue layout, vendor agreements, and the final timeline in the event's folder — and when the client swaps the layout twice, the versions stack in one family instead of multiplying as copies.
OpsVue for Event Planners →A balloon decorator saves the client's inspiration photos, the approved mockup, and the install photos on the booking, so the crew builds from the approved version rather than the first draft.
OpsVue for Balloon Decorators →A photo booth operator stores print template proofs and the backdrop selection per event, and the version history shows exactly which proof the client approved.
OpsVue for Photo Booth & 360 →An AV company keeps plots, stage files, and vendor paperwork per show, with attribution showing which tech uploaded the revised plot the night before load-in.
OpsVue for AV & Production →Yes. Clients can upload files back through the same document link they use to view and respond to paperwork — no account needed on their side. The workspace gets a notification when a file arrives, and the file lands on the job.
OpsVue detects the duplicate before storing it and asks what you mean: add it as a new version of the existing file, keep both as separate files, or skip it. Version families keep every version with a clearly marked current one.
Sharing works at the folder level, per person. Members in limited roles see only the folders shared with them, while owners and managers see the whole tree.
Start for free and set up your first workflow today.
No credit card required.