Manual progress compilation
Physical and financial progress had to be compiled by hand, package by package, division by division.
Illustration · representative concept, not a live system screenClient case study · DPHE · RHD · Contract & progress tracking
Contracts, progress and time extensions, on one governed record.
Two government agencies needed the same thing: one governed record for contracts, physical and financial progress, and time-extension requests, instead of paper files compiled by hand. DPHE's Contract Management System (CMS) and RHD's OneRHD Contract Management and Work & Payment Tracking modules solve it the same way, independently, for each agency's own approval chain.
ClientsDPHE (Ground Water Circle) and RHD (Monitoring Division)
SystemsDPHE's Contract Management System (CMS) · RHD's OneRHD Contract Management and Work & Payment Tracking modules
CoverageDPHE's nationwide Ground Water Circle activity · RHD's road maintenance programmes and packages
2 agenciesthe same governed-record approach, deployed independently
NationwideDPHE's CMS covers contract, tender and billing administration countrywide
4-tier approvalRHD's EE → SE → ACE → CE workflow, digitized end to end
Package-levelphysical and financial progress tracked down to the individual contract package
The assignment
Two agencies, the same paper trail behind every contract.
Before digitization, tracking a contract at RHD meant compiling package-wise progress by hand — a physical-and-financial progress chart per package, per division, and a separate paper form to request a time extension without a cost increase, each requiring manual sign-off up the chain. DPHE faced the same pattern for its nationwide tender and contract administration. Both needed a governed digital record instead of a paper one.
Two agencies · two independent deploymentsDPHE and RHD each own and operate their own system.
DPHE owns and operates its Contract Management System (CMS) for the Ground Water Circle's nationwide activities. RHD owns and operates OneRHD, including its Contract Management and Work & Payment Tracking modules, under the Monitoring Division. Both are built on the same underlying approach, independently, for each agency's own approval chain.
Challenge
Replace paper progress charts and extension requests with a governed record.
Paper-based time extensions
Requesting a contract duration extension meant a separate paper form and a manual approval chain.
Contract records scattered by package
Tender, contract and payment information for each package lived in separate files rather than one record.
DPHE · Contract Management System
CMS: contract, tender and billing administration for DPHE's Ground Water Circle.
CMS administers DPHE's tender, contract and billing activity nationwide, replacing scattered paper files with one governed record for the Ground Water Circle.
Centralized contract and tender records
Tender, contract and billing administration for DPHE's Ground Water Circle, in one system rather than scattered paper files.
Nationwide deployment
Built for use across DPHE's countrywide activities, not a single project or division.
Billing administration in one place
Tender, contract and billing information sit against the same record instead of separate paper files.
One record instead of a filing cabinet
Contract and tender status is visible in the system directly, without reconstructing it from paper each time.
RHD · OneRHD Contract Management & Work and Payment Tracking
A Contract Management Module built for RHD's approval chain.
OneRHD's Contract Management and Work & Payment Tracking modules are purpose-built around how RHD actually approves and pays for work — package by package, up through the Monitoring Division's chain of command.
Centralized contractor database
Contractor details, performance history and payment progress in one record, replacing scattered package files.
Tender management
Package number, work name, procurement method, invitation, closing and approval dates, and approved estimated cost, captured for every package.
Digital contract creation and repository
Once a tender is awarded, the system generates and stores a digital contract with scope, budget, duration and payment terms.
Four-tier approval workflow
Contracts and payment requests move through Executive Engineer, Superintending Engineer, Additional Chief Engineer and Chief Engineer, digitally.
Work and payment tracking
Milestones, completion percentage and actual-versus-planned progress, with contractor bills verified digitally against approved budgets.
Role-specific dashboards
Package-level and contractor-wise reports for Executive Engineers, up to nationwide programme dashboards for the Chief Engineer.
1CreatePackage, tender and contract entered once
→2ApproveEE → SE → ACE → CE, digitally
→3TrackPhysical and financial progress by package
→4ReportRole-specific dashboards, up to nationwide view
The advantage
One governed record, instead of a filing cabinet full of paper.
Every package's tender, contract and payment status is visible in one place, not scattered across separate files.
Executive Engineer to Chief Engineer sign-off happens inside the system, with a digital record of who approved what and when.
Physical progress, financial progress and time-extension requests sit against the same package record, not separate forms.
Evidence and framing
Grounded in each system's approved scope.
This case study describes CMS and OneRHD's Contract Management and Work & Payment Tracking modules as delivered software, grounded in each system's approved scope. No confidential data or internal system screens are reproduced here.
DPHE · official website and departmental mandate ↗RHD · official website and departmental mandate ↗Tiger Park · OneRHD case study
Representative hero illustration; no confidential operational data or contract value is reproduced.
One governed record, any agency.