Skip to content
deCONEgestion
Our purposeReport equipmentOffice portal

deCONEgestion

Every cone accounted for

Council discussion paper · 17 November 2026 · Version 0.2

The proposal: give every temporary sign, cone or accountable batch a durable identity. Record where it was placed, who owns the job and when it is due back. Give the collection crew the same checklist. Keep the job open until the equipment is accounted for and an authorised person completes the clearance check.

Decision requested: nominate a highways sponsor, one depot and a contractor partner to design a small, measured pilot. This is a request to test the process, not a request for a county-wide technology purchase.

1. The problem to solve

The supplied voice brief describes cones and signs left after roadworks, including a road closed sign reportedly remaining after the rest of a site had been removed. These are accounts in the brief, not independently verified incidents or a quantified national loss estimate. The speaker also describes a council collection initiative; its scale and costs need checking with the authority.

The operational gap is a handover gap: the person placing equipment may not be the person collecting it. A closed works order does not necessarily prove that every advance sign, remote diversion sign or item at an approach road has gone.

deCONEgestion creates one equipment record across that handover. It should complement the council's traffic management procedures and works system, rather than pretend to authorise road reopening or replace a competent site inspection.

Working with traffic management providers

The follow-up brief highlights a practical partnership: involve the providers who place and recover equipment, alongside the utility or principal contractor commissioning the works and the highway authority overseeing them. Start by identifying the regular local providers with the council, rather than assuming their number or approaching isolated sites without the responsible organisation. No provider or council is confirmed as a partner yet.

The proposed shared record should connect the works reference, equipment owner, each placement, collection responsibility, outstanding exceptions and confirmed recovery. This makes the handover between different crews explicit. The office website would coordinate jobs and follow-up; the Android app would record field actions against those same jobs. Version 0.3.0 implements the shared office database and staff authentication. Deployment receipts distinguish the available service from future field capabilities.

A supplied industry account describes a costly dispute after signs were not collected. It is anecdotal context, not an independently verified case study, a statement of typical fines or evidence of savings from deCONEgestion. The pilot should measure actual equipment recovery, additional collection visits and completion time before making financial claims.

The partnership proposition is mutual: communities gain tidier streets; traffic management providers recover their assets; utilities and contractors get clearer handovers; councils gain a better view of collection progress. Equipment reconciliation supports existing procedures; it does not certify legal compliance or road safety. DfT inspection guidance includes checking proper site clearance after works.

2. The workflow

  1. Register: a depot assigns an asset ID, owner, type and durable QR label. Scan testing determines label placement and whether individual cones or accountable batches are sensible.
  2. Deploy: the crew selects the works reference, records each item or controlled batch, placement note, device location with accuracy and timestamp, and a photo where useful. A remote diversion sign is a separate placement point, not hidden under the main worksite pin.
  3. Handover: the job names the collection owner and due time. The incoming crew sees what was deployed, changes since deployment and the outstanding list.
  4. Collect: crews scan or confirm physical recovery of each item at a safe working location. A scan identifies an asset; it does not prove the road is safe or the item has been loaded. Counts and exceptions remain visible.
  5. Resolve exceptions: an item reported not found remains outstanding. Missing, damaged, moved, hired or transferred items need a named owner and an explicit supervisor resolution. Production transfers must keep ownership and receiving-job records; they are not equivalent to collection.
  6. Clear the site: reconcile all recorded assets, carry out the required visual inspection including approach roads, then record authorised clearance. Produce a report with placement, collection and exception evidence. An unrecorded item can still exist, so a zero count is necessary but insufficient.

3. Choose the tag around the job

OptionPractical useLimitation / recommendation
Durable QR plus printed IDExisting Android phone or tablet camera; cheap to trial; manual fallbackNeeds line of sight and readable labels. Start here for signs and selected cones. Test mud, rain, gloves, darkness and repeated stacking.
Passive NFCA close tap with compatible hardwareNot live positioning. Do not assume an iPad can read it; check the exact device or use an external reader. Optional phone trial after QR.
Passive UHF RFIDMultiple items read with a dedicated handheld reader connected to a host deviceTablet alone is insufficient. Metal signs, antenna orientation and nearby jobs can affect reads; conduct a controlled physical trial. A missed radio read must never silently mean collected.
Active Bluetooth tagNearby detection with batteries and a receiverProximity is not precise GPS; batteries, gateways and maintenance add cost. Consider for higher-value equipment if evidence justifies it.
GPS/cellular trackerEquipment that needs independent location updatesPower, hardware size and connectivity costs make this a different proposition from a tiny passive tag. Reserve for high-value assets if required.

A penny-sized passive label can carry identity; it cannot independently transmit a GPS position. The proposed map shows the last observed position recorded by a crew/device. Label dimensions and housing must be field-tested; coin size is an aspiration, not a guaranteed specification. Metal signs may require an on-metal tag design if radio tagging is used.

TSL documents Bluetooth UHF readers for Android and iOS hosts; that establishes a plausible reader route, not a verified compatibility endorsement for a particular council's tablets. NXP documents close-range NFC tag operation and reader-based energy harvesting. See sources below.

4. Product surfaces

Proposed Android crew workflow, intended for Google Play: job list, deployment, QR scanning, placement notes, location/accuracy capture, photos, recovery, offline queue and explicit sync status. Use an internal testing track first. Scanner cancellation and denied permissions must leave manual entry available. Do not request background location for the initial pilot; record foreground location only when needed for a placement/inspection.

Council/contractor web dashboard, usable on iPad: authorised job visibility, map and list, overdue queues, contractor ownership, exception resolution, evidence export and pilot measures. Cross-council views require explicit tenancy boundaries and agreed access.

Office website: https://deconegestion.co.uk/portal/ is the authenticated shared office workspace. Public equipment reports enter through /report/ and are reviewed before assignment or collection. The original fictional device-local demonstration remains separate at /demo/; its layout toggle is not authorisation.

Version 0.3.0 implementation: public equipment reporting with a location, private photo and optional contact details; a role-controlled shared staff workspace; report review and assignment; registered assets, jobs, placement/collection records, missing-item closure guards and audit history; business administration and correspondence drafts. The public Android candidate has five phone navigation destinations, an expanded rail and a reporting flow. Crew scanning remains in the separate original demonstration; physical scanning, field workflow rollout and Google Play publication require further verification. See the release manifest for actual deployment/provider status.

Before operational use: sign-in and roles, server database, secure council/contractor boundaries, real mapping/geolocation, registered inventory and reusable asset lifecycle, photos, conflict-safe offline sync, server audit trail, exception approvals, device-loss controls, backups and field testing. None is simulated as complete in this prototype. The current data is device-only and can be edited or lost by clearing app storage.

5. Technical plan

Keep one web interface packaged as an Android app with Capacitor, rather than maintain separate demonstration code. A production service should keep organisations, users/memberships, assets, jobs, placements, handovers, observations, recoveries, exceptions and immutable audit events.

Each field event needs a unique operation ID so sync retries cannot collect an item twice. The server, not a tablet counter, validates ownership, active placement and authorisation. Preserve device observation time separately from server receipt time. A recovered asset must not resurrect a stale deployment when another device comes online. A job cannot be certified clear while relevant events remain unsynchronised. Devices must visibly distinguish saved-on-device, awaiting-sync, sync-error and server-confirmed records.

Mapping should expose last observation time and accuracy, avoid false precision and provide a list fallback. Inspect the council's existing works/asset systems before building an integration. Start with a controlled export/works reference; do not promise Street Manager, one.network or procurement-system integration without access and agreement.

AI is optional. Deterministic IDs, records and reminders solve the core problem. Later, if justified, AI could assist photo classification or summarise exceptions with bounded inputs, cached results, measured costs and human review. It must not decide that a road can reopen or that a site is clear.

6. Suggested pilot

Proposed scale, to agree with the council: one depot, two crews, one contractor, around 100 signs/cones/barriers across 10–20 works jobs, including remote diversion routes. Begin with signs and higher-value items; compare individual cone scanning with controlled batch accountability rather than impose excessive roadside administration.

Six-week structure: week 1 baseline/process design; week 2 tag durability and device tests plus crew training; weeks 3–5 supervised use alongside existing procedures; week 6 reconciliation, crew interviews and results. This is a proposed trial schedule after resourcing, access and safety approval, not a delivery commitment for production software.

Measure: equipment remaining after scheduled clearance; time between end of works and final recovery; unexplained losses; extra recovery trips; scan time per job; label failure rate; offline/sync failures; and completion of remote-approach checks. Establish baseline and denominator first. Suggested acceptance targets to agree: 100% of pilot placements reconciled or explicitly resolved, no silent sync loss, all clearance records checked by an authorised supervisor, and no unsafe scanning behaviour. Savings claims require measured baseline, labour and equipment costs.

Test deliberate failures: one uncollected sign; wrong-job scan; duplicate scan; damaged label; no signal; denied camera/location; moved or hired item; two crews editing the same job; device loss; and an unrecorded item found on visual inspection. A missing item must remain visible until investigated.

7. Budget and commercial shape

Do not buy a fleet of specialist readers before comparing QR, batch processes and existing supplier systems. Ask the council for current inventory ownership, contractor processes, device estate and any asset-tracking capability already licensed.

Illustrative planning allowance only , not supplier quotes or an offer: £500–£1,500 for trial labels/mounting/field consumables; £0 if existing suitable devices can be used, otherwise obtain device quotes; £8,000–£20,000 for a limited authenticated pilot service and Android implementation; £2,000–£5,000 for onboarding, field support and evaluation. Indicative total £10,500–£26,500 excluding devices, optional RFID, ongoing hosting/support and VAT. These are scoping estimates made for discussion; the range must be replaced by a fixed deliverable specification and competitive supplier quotes before procurement. No money has been committed.

A possible future commercial model is authority/contractor software licensing with optional hardware supply. Validate willingness to pay, interoperability and incumbent alternatives through the pilot. Do not claim a patented invention, unique market position or nationwide savings without separate research.

8. Governance and Google Play

Get the authority's highways lead to check the process against applicable signing, lighting, guarding and clearance procedures. The Department for Transport's cited code supports safe street/road works; its stated coverage excludes motorways and dual carriageways at 50 mph or above. Do not treat this app as a compliance certificate.

Before collecting real data, agree the controller/processor roles, lawful use, retention, staff privacy information, location/photo handling, supplier terms and any DPIA screening with the authority. Prefer job/asset observations over ongoing employee tracking. Do not store personal data on public QR codes.

For Play release: confirm publisher, package ID ownership and signing owner; retain signing secrets outside source control; build and test a signed Android App Bundle; complete app access, privacy policy, Data safety, content rating and permission declarations; satisfy the account's testing/review requirements and verify the listing. Google currently states that new apps/updates must target API 36 or higher from 31 August 2026; verify the rule again at submission. The working package ID is a development choice, not a verified brand/domain registration. Publishing is a separate release action; nothing in the prototype is a published Play listing.

9. Next meeting

Demonstrate the Belton example: six signs recovered, one road closed sign outstanding. Show that clearance is blocked. Collect the final sign and clear the job. Then deploy a new item to an active job and hand it to another crew. The map and names are illustrative, not actual council operational data.

Agree the sponsor, depot/contractor, works references and equipment sample; identify current software; then turn the measured pilot into a delivery specification.

Sources checked 17 November 2026

  • DfT: Safety at street works and road works , purpose and stated coverage of the code.
  • DfT: Inspecting street works , post-works site clearance and reinstatement checks.
  • TSL: 1128 Bluetooth UHF RFID reader , external reader and multi-platform host capability.
  • NXP: NFC Forum-compliant tag IC and NXP NFC overview , close-range tag operation and reader energy harvesting.
  • Apple: Core NFC , requires compatible NFC hardware.
  • Capacitor: Android, Barcode scanner, Google Play deployment , native packaging and scanning route.
  • Google Play: target API requirements , current submission targets. Council-specific legal, procurement and privacy approval has not been obtained.
Built by Flying Penguin
PrivacyCookiesAccessibilityContact