Service line inventory
Import the city's list once. Material on each side, category, premise ID, coordinates. Two services at one address stay two records.
Lead service line field operations
The field record for lead line replacement.
Inventory, test pits, right of entry, markouts, routing, restorations — and the photo, video and signature behind every one. Captured at the curb on a phone, not retyped from a notebook at nine o'clock at night.
Built by a contractor running lead line programs, on live jobs, in New Jersey.
Why it exists
A replacement program is a paperwork program that happens to involve digging.
Every property on a lead program generates a record: what the service line is made of on both sides, who looked, when, with what evidence, whether the owner let you in, whether the markout was valid on the day you dug, what you put back and what it should be paid at.
Most of that record ends up spread across a spreadsheet, a phone's camera roll, an inbox and somebody's memory. It holds together until the engineer asks about one address from three months ago, or the city gets a resident complaint, or the state asks for the inventory.
Gooseneck keeps it in one place, entered once, by the person standing at the curb. The crew screens are built for a phone in the rain with gloves on. The office side is built for the question you actually get asked: what is happening at this address?
It was not designed in a product meeting. It was built on live replacement programs, by the contractor running them, and every screen in it exists because a crew needed it on a Tuesday.
What it does
The whole job, from the inventory to the final restoration.
Each piece writes into the same property record, so nothing has to be reconciled later.
Test pits
Findings at the curb stop with photos, depth, connection material and the engineer inspector's sign-off. No property is called a replacement until both sides are actually identified.
Right of entry
Signed at the door on a phone, or by the homeowner online from a link the city can publish. Produces a PDF, filed against the property. Refusals and the reason are recorded too.
Markouts
One Call tickets tracked against the blocks they cover, with valid-from and expiry on the crew's screen. An expired markout stops the dig before the crew is standing on it.
Routing and look-ahead
Build a route that sweeps outward from the yard, then export a two-week day-by-day plan with maps — the document the crew works to and the city posts no-parking signs from.
Preconstruction evidence
Photo and video of the frontage before anything is opened, stamped and filed against the property. The thing you reach for when a driveway was already cracked.
Restorations and quantities
Open restorations as a live list with days outstanding, and every pay quantity logged as the work is recorded rather than reconstructed at the end of the month.
The property record
One address, everything known about it, evidence attached, printable as a PDF. This is what gets sent when somebody asks what happened at a house.
Live dashboard
Properties by stage, test pits done, replacements, restorations open and closed, unresponsive homes — the numbers a progress meeting actually runs on.
What it looks like
Plan the week. Dig it. Prove it happened.
Five screens, in the order a property moves through them — routing the week, the record it builds, the look-ahead the city works to, the number the engineer asks for on a Monday morning, and the live play-by-play on your phone.
route planner — suggest & split
Suggest & split
Tell it the crew, the work type, how many homes a day and how many days, tap a start point, and press Suggest & split. It takes the homes that are ready for that work, walks them from where the crew starts, and splits them into days.
Every home is on the map in the color of its state, and the legend counts them: completed, in route, ready with a markout, markout starting soon, on hold, blacked out, and available. The plan preview lists each day with its stops, and each stop shows where that home has got to and whether a markout covers it.
- One start point — the plan begins where the crew is, not at the top of a list
- Status and markout on every stop, so the crew sees what each stop needs before they leave
- Saving replaces the crew's whole forward route, so nobody works to a stale one
property record — shared view
Lead found — both sides Replaced 2 Oct Restoration open 6 days
The service
Public / street sideLead
Curb stopLead
Customer / house sideGalvanized
At the meterCopper — verified inside
Replaced with1″ copper · 42 ft main to curb
Who said yes, and when
Right of entrySigned 24 Sep 2026
Signed byL. Marsh · owner
PreconstructionVideo + photo · 22 Sep 2026
Legal to dig
One Call ticket20260921-0412
Valid24 Sep – 8 Oct 2026
Who did the work
Test pit28 Sep 2026 · Crew 1
Dug byA. Whitlock
Inspector presentR. Vance · engineer
Photographs — 11 on file
40.00277, −75.02724
40.00277, −75.02724
40.00277, −75.02724
Documents
Right of entry — signed
Test pit report
Replacement report
Tap card
One address, the whole file
This is what the city opens when a resident rings up, and what the engineer opens before approving a payment. Material on both sides of the curb stop, who signed the right of entry and on what day, the One Call ticket the hole was legal under, who dug it, which inspector stood there, and every photograph with the time and the coordinates burned into it.
None of it was retyped from a notebook at nine o'clock at night. It was recorded at the curb, on a phone, by the person doing the work.
- Photographs carry their own stamp — time, address, coordinates
- Every document regenerates from the record, so the PDF and the data never drift
- Printable and shareable without giving anyone a login to the whole program
Calderton_Lookahead_2026-10-12.pdf
Two-Week Look-Ahead
City of Calderton — Lead Service Line Replacement
Issued 7 Oct 2026
Crew 1 · 19 stops
Crew 1 · 19 stops
| Date | Address | Work | Markout |
|---|---|---|---|
| Week of 12 October | |||
| Mon 12 | 204–214 MAPLE ST | Test pit ×6 | Valid to 26 Oct |
| Tue 13 | 31–39 BIRCH ST | Test pit ×5 | Valid to 26 Oct |
| Wed 14 | 12–20 BROAD ST | Replacement ×5 | Expires Thu 15 |
| Thu 15 | 18–22 CEDAR AVE | Replacement ×3 | Call in by Wed |
| Fri 16 | 204–208 MAPLE ST | Restoration ×3 | Not required |
| Week of 19 October | |||
| Mon 19 | 40–48 CANAL ST | Test pit ×4 | Blackout lifts 17 Oct |
| Tue 20 | 8–16 CEDAR AVE | Test pit ×5 | Valid to 2 Nov |
| Wed 21 | 31–35 BIRCH ST | Replacement ×3 | Valid to 2 Nov |
CANAL ST is blacked out 12–16 Oct for city paving; those four homes are held to week two. One block on CEDAR AVE needs calling in to One Call before Wednesday.
Posted to residents · no-parking signs set 48 hours ahead
Also exported as Excel
What the street finds out
The same plan, as the document everybody outside the crew actually works from. The city posts no-parking signs off it, the engineer schedules inspectors against it, and residents get told which day their water goes off.
It carries the markout column, because a date the crew cannot legally dig on is a date nobody should be putting a sign up for. Exported as PDF and Excel, and emailed the moment it is produced.
- Produced from the saved plan, so it cannot disagree with the crew's route
- Blackouts and expiring tickets are on the page, not in somebody's head
- Two weeks out — far enough ahead for signs, permits and letters
project dashboard
Pipeline
Key numbers
Right of entry obtained61276% of 806 contacted
Refused415% · 12 since appeal letter
Unresponsive1533+ attempts, no answer
Appointments set28next 10 working days
Test pits done48837 this week
Lead found27156% of pits dug
Replacements logged224 / 30076 left of contract base
Restorations open53avg 9 days open
Restorations complete17124 this week
Geocoded for map1,142of 1,142 · all mapped
Markouts & blackouts
46 markouts valid
7 expiring this week
2 expired
3 pending
1 street blacked out
This week
61 door attempts
37 test pits
19 replacements
24 restorations
3,180 ft of service replaced
The number somebody asks for on a Monday
One screen for the city, the engineer and the contractor, reading off the records the crews filled in that morning. How many homes have been knocked on, how many said yes, how many pits are dug, how much lead has been found, how many streets are back in one piece — and how far through the contract base the replacements are.
Every number opens the list behind it. “Fifty-three restorations open” becomes fifty-three addresses with the date each one was dug, which is what somebody needs when they are about to do something about it rather than just report it.
- The funnel — contacted, consented, dug, replaced, restored — as counts and shares
- Replacements against the contract base, so nobody has to go and work it out
- Markouts, blackouts and the last seven days on the same page
The live project dashboard, on your phone
A play-by-play of the project as it happens. Who is on the clock and since when, how many doors were knocked, how many said yes, how many pits were dug, and how that stacks up against the week and against the whole contract — refreshed through the day without opening the platform.
Employees' locations are on the map, with their progress updating in real time as the work is logged. If you need a route or a property while you are out, look it up on the phone: the crew's stops for the day, or the full record on any house.
- Today, this week, last week, project — the same numbers at every scale, by day, by inspector, by crew
- Live map of the crews, with each person's progress as it is recorded
- Routes and property look-up from the same screen when you are away from a desk
The route planner and the phone dashboard are real screenshots of the app running on demo data. The other three panels are drawn to match the real screens and documents. Every resident and crew member shown is invented. We will not put another client's residents on a marketing page. Ask for a demo and you will see the working platform, with your own program in it.
Who it's for
Three parties, one record, different views.
Every lead program has an owner, an engineer and a water utility. Each gets a link and a code — no account to create, nothing to install — and every lookup is logged.
Cities and boroughs
You answer to the residents and to the state. You need to be able to look it up yourself.
- Search any address and see what has happened there
- Restoration backlog, with how long each has been open
- Homes that need a right of entry, and unresponsive owners for outreach
- The inventory you owe the state, exportable
- A copy of everything delivered to storage you own
Engineers
You verify and approve. Your unit of work is the property, not the aggregate.
- The per-property evidence package in one page
- Test pit date, crew, materials both sides, photos, signatures
- Markout ticket with the dates it was valid
- Exception lists — unable to locate, mismarks, refusals
- Print or save any record as a PDF
Water utilities
You own the asset record. You care what was found, not how the week went.
- Material on the company side and the customer side, per service
- Curb box coordinates for your GIS
- A read-only feed any GIS can consume, or a scheduled export
- Keyed on premise ID, so it joins to what you already have
- Updated as the crews work, not in a monthly spreadsheet
And the contractor running the work
Which is where it came from. Routing, markout tracking, the two-week look-ahead, crew productivity and pay quantities exist because a contractor needed them to get through a program without losing a day to paperwork.
How it works
Stood up in days, not a procurement cycle.
We set it up for your program
Your city, your engineer, your utility, your contract label, your status vocabulary and your pay items. Your crews and inspectors. Nothing is hardcoded to somebody else's job.
Your inventory goes in
The service line list you already have, however it is formatted. Columns are mapped on screen, you see exactly what will be created or updated before anything is committed, and addresses are matched on premise ID so a re-import never doubles the list.
Crews work from a link and a code
No app store, no accounts, no devices to manage. It opens on whatever phone the crew already carries and saves to the home screen. Every entry is attributed to the person who made it.
Everyone else reads the same record
The city, the engineer and the utility each get their own link and code, read-only, revocable one at a time. Records and media export to storage you own on a schedule, so the program's history is never only in one place.
What's included
Run as a service, per program.
Priced per contract, because no two lead programs are the same size. Here is what the engagement covers.
- Set-up and configuration — your program, your parties, your pay items, your statuses.
- Loading your inventory — including the cleaning it usually needs first.
- Hosting and operation — we run it; nothing for your IT department to host or patch.
- Crew training — a short session, because the screens are built to need one.
- Access for all three parties — city, engineer and utility, issued and revocable.
- Scheduled exports — records and media delivered to storage you own.
- Support through the program — a person who knows the job, not a ticket queue.
- Your data back on request — complete, in open formats, at any time.
Questions we get asked
The procurement conversation, up front.
Does our staff need an account to use it?
No. The city, engineer and utility each get a link and a code. There is nothing to sign up for and nothing to install. Only the people who administer the program sign in.
Who owns the data?
You do. It is your program's record. We operate the system; the records and the media are yours, you get them back in open formats on request, and a complete copy is delivered to storage you own on a schedule so you are never dependent on us to answer a records request.
What happens if we stop using it?
You get a full export — every record and every file — and your data is removed from our systems once you confirm you have it. Your copy keeps working without us, because it is delivered in formats you can open yourself.
Is the service line inventory sensitive?
The inventory itself is a public record. Under the Lead and Copper Rule Revisions every water system has to make its service line inventory publicly accessible, and systems serving more than 50,000 people have to publish it online. What does need care is the homeowner contact details and the signatures on right-of-entry forms, and those are handled accordingly.
Can it feed our GIS?
Yes. Every property carries coordinates and a premise ID, so it joins to what you already have. That can be a read-only feed your GIS reads directly, or a scheduled export — whichever fits how your system is set up, including systems that sit behind your own firewall.
Does it work without a signal?
Not fully, and we would rather say so. The crew screens need a connection. For basements and back yards with no coverage, the practical answer is to capture at the curb and submit when the phone comes back — which is how crews use it today.
Can we host it ourselves?
It can run inside your own cloud tenant, under your administrators and your retention rules, if that is what your policy requires. It cannot be installed on a server inside your building — if that is a hard requirement, we will tell you plainly that this is not the right product rather than waste your time.
How quickly can it be running?
Days, once we have your inventory list. The long pole is usually getting that list out of whoever is holding it, not the set-up.
See it
Request a demo.
A walk through the live platform on a sample program — the crew screens on a phone, the property record, the look-ahead and the client view. Half an hour, no slides.
Or email sales@foreman.solutions directly.