Skip to content
Explore the website
Discuss your project

contact@almousa.dev

WORK / PROJECT STUDY

BuildTrack — Construction Coordination System

A system that organizes documents and coordinates the owner, contractor, and engineering office, with a web interface, backend services, and PostgreSQL data storage.

BuildTrack construction coordination landing page, including an interface example for documenting a finding, decision and follow-up.Enlarge screenshot
Interface screenshot supplied by the developer; displayed figures are not measured client outcomes.
Project name
BuildTrack — construction tracking
Sector
Construction and contracting
Launch year
2025
Technologies
C# · .NET 10 · EF Core · TypeScript · Next.js · React 19 · TSX · PostgreSQL · SQL · HTML · CSS · CSS Modules · JavaScript / MJS · Python · Bash / Shell · GitHub Actions · YAML · JSON
Platform
Web application
ALMOUSA’s role
Developing the web interface, backend services, APIs and data-access layer, connected to the document and coordination workflow shared by the owner, contractor and engineering office.

The challenge

Scattered documents that were difficult to find, limited coordination between the owner, contractor, and engineering office, and overlapping work that wasted resources.

What we built

We developed a system to organize work and coordinate activities among all three parties, addressing fragmented documentation within the workflow.

Implementation scope

  • Coordinating work among the owner, contractor, and engineering office.
  • Organizing documents within the workflow and making them easier to track.
  • Separating domain logic, the application layer, and infrastructure.

Technical architecture

The system was built with C# and .NET 10 for backend services and APIs, TypeScript, Next.js, and React 19 for the web interface and backend-for-frontend (BFF) layer, and PostgreSQL for data management with EF Core for data access.

The architecture separates domain logic, the application layer, and infrastructure. It also uses database row-level access policies and Python and Bash scripts for automation and security and operational checks.

  1. Web interface & BFFNext.js · React 19 · TypeScript
  2. System services & APIsC# · .NET 10
  3. Data accessEF Core
  4. Database & row-level policiesPostgreSQL
Responsibilities from the web interface to the database. This diagram describes system components, not a performance measurement.

Implementation layers and technologies

LayerTechnologies
Backend services and APIsC# · .NET 10 · EF Core
Web interface and BFFTypeScript · Next.js · React 19 · TSX
DataPostgreSQL · SQL
Interface structure and stylingHTML · CSS · CSS Modules
Operations and security scriptsJavaScript / MJS · Python · Bash / Shell
Build and deployment configurationGitHub Actions · YAML · JSON

An implementation decision

The architecture separates domain logic from the application layer and infrastructure. This makes each responsibility explicit when tracing a change from the interface to data, while the BFF connects the web interface’s needs to system services.

The outcome and experience

The system helped improve coordination, made documents easier to track, and addressed overlapping work that had been wasting resources.