A bespoke telecoms civils measurement and final-accounting system
Final Measures is a professional internal system developed by the person behind Atinamos to support a specialist telecoms civils workflow.
The Python-based application brings together existing project information, records work measured in the field and matches completed activities against the relevant Bill of Measure codes. This provides a structured basis for comparing recorded quantities and preparing final accounts.
The project demonstrates how a focused digital tool can be designed around a complex operational process without requiring an organisation to replace every existing data source.
Turning field measurements into a structured final account
Telecoms civils final accounting requires the work carried out in the field to be compared against the relevant Bill of Measure structure. This can involve project information from existing data sources, field measurements, completed work items, Bill of Measure codes, submitted quantities, review and reconciliation, and final-account preparation.
The challenge was not simply recording quantities. The workflow needed to connect what had been planned or submitted with what had actually been measured in the field, using the correct Bill of Measure codes throughout the comparison.
When the information is spread across separate spreadsheets, databases and working records, it becomes harder to maintain one clear view of the final measure.
Built around a real telecoms civils workflow
Final Measures was developed around a genuine operational requirement. The workflow, terminology and comparison process were shaped by practical experience of telecoms civils delivery and final accounting.
The system was created from direct professional experience and designed around the way field and commercial information needed to be reviewed. It is not a speculative demonstration — it was built to support a specific internal workflow. This public case study is intentionally anonymised to protect confidential commercial information.
What the system does
The application combines data intake, structured records, field measurements and comparison tools within one workflow:
Existing project-data intake
Information from existing operational databases and data sources can be brought into the system so that users do not need to recreate every project or work record manually.
Supabase-backed central records
Supabase provides the central database used to hold and manage the structured records required by the application.
Field-measurement records
The system records work measured in the field, providing a structured record of what was actually completed.
Bill of Measure code matching
Measured work is associated with the relevant Bill of Measure codes so that quantities can be reviewed against the commercial structure used for final accounting.
Quantity comparison & reconciliation
The application supports comparison between submitted or recorded quantities and the quantities established through field measurement. Users can review differences, amend records where appropriate and work towards a reviewed final measure.
Final-account preparation
The structured records provide a clearer basis for preparing and reviewing final-account information.
Python application with a Supabase data layer
The technical design followed the workflow rather than forcing the workflow into a generic off-the-shelf product. Python was used to create the application logic and interface, while Supabase provides the central data layer.
Existing project information can be brought into the application, mapped into a consistent structure and combined with field-measurement records for comparison and review.
Working with data the organisation already holds
The system was designed to work alongside existing data sources rather than requiring all project information to be rebuilt from scratch.
Information from operational databases and other structured sources can be brought into the application and combined with records managed in Supabase. This creates a more consistent view for field measurement, Bill of Measure matching and final-account review.
Designed around comparison, not just storage
The important part of Final Measures is not simply that it stores project and measurement data. It connects field-measured work to the relevant Bill of Measure structure and provides a practical way to compare those records during final-account preparation.
A focused tool for a specialist commercial workflow
Final Measures developed into a structured internal application that brings together existing project information, field measurements, Bill of Measure codes and final-account review within one workflow.
It demonstrates the ability to understand a specialist operational process, design an appropriate data model and build a practical application around the people who use it.
What the project demonstrates
- Specialist operational discovery
- Telecoms civils workflow understanding
- Python application development
- Supabase database design
- Existing-database and data-source integration
- Data import and mapping
- Record normalisation
- Bill of Measure code matching
- Field-measurement workflows
- Quantity comparison and reconciliation
- Final-account support
- Development around real commercial processes
Working with a specialist process that does not fit an off-the-shelf system?
Tell us where information comes from, how it needs to be compared and what the final output should support. We will help you explore whether a focused digital tool could bring the workflow together.