Final-year team project · Hosted prototype
AutoConstruct
Integration, security & reporting
A final-year team project designed around one connected path from a public quotation request to accountable project delivery and management oversight.
From scattered operations to one workflow.
A small contractor can receive enquiries in one place, track customers and projects somewhere else, and prepare schedules, documents, payments, and reports through separate manual processes. That fragmentation makes ownership and project status harder to see.
Our team designed AutoConstruct around a connected operational flow for AB BIZ ONE: capture a public enquiry, turn an accepted quotation into a project, coordinate delivery, and surface useful information to staff and management.
A broad contractor-management prototype.
The project combines a public construction-services website with an authenticated operations area. The implementation is a multi-page web application backed by Firebase services rather than a single-page framework.
- Public quotation intake connected to client and project records.
- Role-aware workflows for Admin/Clerk, Site Supervisor, and Top Management.
- Project progress, supervisor assignment, schedules, inventory, expenses, and payments.
- Quotation, invoice, and receipt publication with document history.
- Operational and management reports, including target-versus-actual delivery status.
I focused on integration and failure paths.
AutoConstruct is collaborative work; I did not build the original MVP or every module. My strongest ownership came during the final integration and hardening phase, where connected workflows needed to remain correct across retries, roles, and multiple records.
- Moved sensitive cross-record operations into transactional and idempotent Cloud Functions.
- Strengthened UID-based role checks and Firestore and Storage authorization boundaries.
- Built a controlled publication flow for official PDFs with immutable final records.
- Connected project lifecycle events to planned and actual dates, delay states, and reports.
- Derived document payment states and improved shared UI, accessibility, and error handling.
Make authoritative actions explicit.
The core engineering decision was to keep multi-record and privileged work out of direct browser writes. Server-authoritative callables validate identity and state, apply transactions, and make retries safe before updating related records.
The frontend remains intentionally simple—HTML, CSS, and JavaScript modules—while Firebase Authentication, Firestore, Cloud Functions, Storage, App Check, and the Emulator Suite provide the application boundary and local validation environment.
Claims tied back to repository history.
GitHub currently attributes 55 commits reachable from main and three merged pull requests to my account. The current repository head has a successful Firebase Hosting workflow and the public AutoConstruct site is reachable at abbizone.my.
A major hardening commit records 73 unit tests, 69 Firestore-rules tests, static audits, and emulator smoke checks. Those counts are repository-reported local validation, not current CI test artifacts, so I present them with that qualification.
What this case study does not claim.
This is a team-built final-year prototype. Teammates created the original product surface and substantial modules, and the private repository remains unpublished. The verified live result is the public hosted surface; this case study does not claim independent proof of every production backend workflow.
There are no measured adoption, revenue, time-saving, or customer-satisfaction outcomes yet. The value I can defend is the implementation work, the integration decisions, and the clearer operational model—not an invented business metric.