Before
Field closeout, job notes, time, photos, scheduling, review, and billing prep lived in scattered handoffs. The office needed cleaner packets before work could be reviewed and turned into invoice-ready output.
Case file
VacTrack
Paid field-operations system
A paid field-operations build for moving work from crews to manager review to office-ready packets. The public demo uses sanitized data; private client details stay private. What matters is the operating shape: jobs, people, time, photos, closeout, review, and billing prep in one surface.
Paid buildBuilt around a real field-to-office workflow.Sanitized demoPublic version shows the system shape without exposing private business data.Reusable patternThe same field-to-office model fits service crews, property teams, repair shops, and admin-heavy operations.
Before / after
After
VacTrack gives the operation one manager surface for jobs, crews, tickets, field proof, payroll review, draft review, setup, records, and office packet prep.
Field-to-office flow
1. ScheduleJobs and crews start with a visible plan.
2. CaptureTime, notes, tickets, and field photo proof stay attached to the work.
3. ReviewManagers check closeout, drafts, records, and exceptions.
4. PackageThe office gets a cleaner packet for billing prep.
5. ExportQuickBooks-style output supports the admin handoff.
The problem
Field activity needed to become reviewable office flow: crews, tickets, time, photos, closeout, billing prep, and manager controls.
The build
Crew closeout, job tracking, manager review, records, backups, setup flow, and invoice-ready packets.
What got built
Payroll reviewSchedule boardTeam plannerCrew and client recordsTicket creationField photo proofDraft reviewOffice packet / billing prepQuickBooks-style exportManager settingsRecords and backupsSetup wizard
Operational shape
VacTrack turns field activity into reviewable office flow: crews, tickets, time, photos, closeout, billing prep, and manager controls.
Reusable pattern
This same build pattern can apply to service businesses, property teams, field crews, internal admin teams, and any operation where work starts in the field and ends in office review.
What it proves
Threshold can build operational software for real business workflows and still make the interface feel authored.