Who agreed to what on site this morning?
Your site notes become the report: what was decided, who owes what, by when. Written before the next meeting.
For your own business, or as a service you charge other businesses like yours for.
Nobody runs this lab yet. Take it, give it your hours and your prices, and it is yours.
Address, footprint, type of work, depth, planned dates. One sheet per job, and everything else hangs off it.
The list of operators concerned, sensitive ones first, with what the portal prepared and what you still have to send yourself.
A named chase-up to the silent operators, with the send date and the consultation number, before the start date.
The ground marking traced, dated and described from your photos and notes, plus any gap found against the plans.
The French one-stop utility portal does exactly one thing: it tells you which network operators sit under your dig footprint and it pre-fills the forms. It sends nothing. You file, you gather the receipts before work actually starts, you trace the marking on the ground, and you pay if a sensitive line goes. The hole in a dig notice file is almost never a missing notice: it is a receipt that never came back and nobody chased, and a marking no paper proves. A lab keeps the register job by job, and tells you what is missing while there is still time to claim it.
Worth more in month six than in week one.
The collections belong to the lab, not to any single magik. Every magik reads them and every run adds to them, which is why this lab is worth more in month six than in week one.
They all start empty. The first run writes the first row.
It wears your name, not ours.
The same lab, under your name, your colours and your logo. Your customers never see ours.
On the Pro plan, and not needed to take a lab. A fully bespoke theme exists as an upgrade, hand built rather than self-serve.
And whatever you already use: any tool available through an API or an MCP server, connected with your own account.
A tool built for exactly your job, and only that, will go deeper at that one job. This is for the jobs nothing covers, or the ones spread across three tools today.
No, and that is the first source of holes in a file. The portal identifies the operators concerned and pre-fills the forms. Sending them stays on you, and an unsent notice is invisible until something happens on site.
Not on sensitive networks: their receipts have to be in hand before work actually starts. This lab does not decide for you, it tells you which one is missing and for how many days, which is exactly the thing you do not know once the digger is already hired.
For any buried line inside the dig footprint or within two metres of it, using the standard colour codes, and it has to be kept legible for the whole job. Marking washed out after three weeks of rain is marking to redo, not marking done.
Operators now answer with centimetre-grade plans on sensitive networks everywhere and on non-sensitive ones in urban areas. The plans became usable. That is good news on site and bad news in a dispute: a contractor who did not trace them on the ground loses the vague-plan argument.
There is a joint damage report form, and it gets filled in on site, not three days later from memory. This lab drafts it from your photos and your notes of the moment. On what you must keep and for how long, it will say nothing: that retention period mostly circulates on training-provider websites, and we do not publish a deadline we have not checked against the text.
A tool built for exactly groundworks and utility contractors who file their own dig notices, and only that, will go deeper at that one job. This lab is for the jobs no tool covers, or the ones spread across three tools today, and it runs under your name.
Every audience is still open.
Nobody has taken a square on this idea yet. You declare your audience when you take the lab (“roofers in Brittany”, “plumbers around Paris”), and two people can start from the same idea on two different audiences without getting in each other’s way.
And it wears your name, not ours.
The bundle describes a lab that does not exist yet : the jobs it would do, and an example of each output.
Open Knowledge Format : plain markdown, re-importable into any agent. No account, no lock-in.
Your site notes become the report: what was decided, who owes what, by when. Written before the next meeting.
The quotes that went silent get a follow-up that sounds like you wrote it. Because you read it before it goes.
Your grant file is checked before you send it, so it does not come back three weeks later because one paper is missing.
Still comparing tools? Best AI for site reports.
Job ST-2611 - 14 rue des Peupliers, Bourg
Drinking water service extension, 22 m trench along the pavement, even-numbered side.
| ItemItem | ValueValue |
|---|---|
| Declared footprint | 22 m x 1.5 m, pavement and verge |
| Maximum depth | 1.40 m |
| Method | 3T excavator, hand digging within 1.50 m of any located line |
| Planned start | Monday 24th, 7:30am |
| Duration | 3 days |
What this sheet fixes and what stops being negotiable after it
The footprint above is the one that goes into the notices. If the route moves by more than two metres on site, it is no longer the same job as far as the notice is concerned: you re-file, you do not widen the line by hand.
Open point
The connection at the property boundary has not been settled with the client. Until it is, the 1.40 m depth stays an assumption and the marking cannot be treated as final.
| Operator | Network | Sensitive | State |
|---|---|---|---|
| Enedis | Medium-voltage power | Yes | Notice sent on the 12th |
| GRDF | Gas | Yes | Notice sent on the 12th |
| Orange | Telecom | No | Notice sent on the 12th |
| Water authority | Drinking water | No | Form pre-filled, NOT SENT |
+ 1 more rows
Two forms pre-filled by the portal and never sent. The portal transmits nothing: while they sit like this, they exist for nobody.
Hello, Our dig notice was sent to you on 12 August for job ST-2611, 14 rue des Peupliers in Bourg, under consultation number 2026080912345. We have not received your receipt. Work is due to start on Monday 24 August at 7:30am. Your network is classed as sensitive across this footprint. We will therefore not start without your receipt, and if we have to postpone, we will send you the delay report together with the plant standby costs. If the notice never reached you, tell us today: we resend it the same day. Regards, Site management
Ground marking record - job ST-2611
Done on 22 August, 9:10am, dry weather. Footprint sprayed over the full 22 m length.
What was traced
| NetworkNetwork | ColourColour | Traced positionTraced position | Gap against planGap against plan |
|---|---|---|---|
| Medium-voltage power | red | centreline 0.80 m from the gutter | matches |
| Gas | yellow | centreline 1.35 m from the gutter | matches |
| Telecom | green | centreline 2.10 m from the gutter | 40 cm out |
The gap, and what we do about it
The telecom duct is traced 40 cm further from the kerb than the plan we received shows. The gap is recorded, photographed and reported to the operator today. It does not block the start: the network is not sensitive and digging will go manual as we approach it.
Had the gap been on gas or power, the call would have been the opposite: stop work and call the operator back, because the position found on site would no longer match the marking.
Upkeep
Marking to be re-checked at the start of each day. Three days of work announced, rain forecast for Wednesday.