All work · Commerce & services
Field labour capture for a network contractor: technicians, approvals and pay-period rules, replacing the slow Access front end accounting had been living with, and catching the duplicate dates and pay-period errors that were costing money.
Technicians' hours, meals, travel and mileage against job sites were reaching accounting through a slow Access front end, with no approval chain and no way to catch duplicate dates or pay-period errors before they were paid.
The field capture system with a signature step, then the approval chain above it: project managers approving in batches, a five-day report that mails itself out, pay-period and duplicate-date rules that stop errors at entry, and a browser-based administration application replacing the Access front end.
When a middle layer made the program unreliable over the office VPN, I removed it and had the program talk to the database directly rather than leave the field with a flaky tool. Ran in production and was handed over with the source code.
Stack
Tell me what it does for the business, what it is written in, and what stops when it goes down. I will say plainly whether I can help.
Tell me what it runs on