One record per job for telecom contractors. The crew marks the map and submits, and the tally comes from the marks, priced from your price book, ready for the invoice.
Book a Fit CallStop chasing crew updates via text and email. TCS keeps one record per job. The crew marks the map and submits, so the record shows what was done without adding busywork to your field teams.
The office creates the job with its project number, PO and address, and uploads the map. Crews mark it using the codes from your price book.
The crew marks the map in TCS Map Annotator, placing each code and quantity where the work was done. The tally comes from the marks.
The office job list shows how many submitted maps each job has and when the last one came in.
Crews mark the map and submit once from the field. The marked-up map and its tally land on the job record, so nobody calls to ask what was done.
When the crew corrects a job, they submit again. A resubmission replaces the old marked-up map and its tally. The earlier version stays in the map's history.
The tally is counted from the crew's marks and priced from your price book, ready for the invoice.
Here's how it flows:
The office creates the job with its project number, PO and address, and uploads the map. Crews mark it using the codes from your price book.
The crew signs in on a phone and opens the job's map, the same map the office set up.
On site, the crew places each code and quantity on the map where the work was done. The tally comes from the marks, not from a count typed in later.
At job end, the crew submits the marked map once from the field. The record shows what was placed and when it was submitted.
The office sees the priced tally instead of rebuilding the count by hand.
If the crew resubmits, the new submission replaces the old tally.
Would it be a bad idea to spend 30 minutes walking one of your jobs from the map to the invoice? Free 30-minute Fit Call. We will tell you whether an Operations Audit is a fit.
Book a Fit Call