Why I Built It — Mehraz Negar

I built a construction-management platform. But the real design problem was not the dashboard.

It was the gap between having information and making a decision someone can act on.

Consider a revised drawing that changes an installation detail. The design team has issued it. Procurement is working from an earlier specification. The programme still assumes the original sequence.

Each team may have an update. The project still needs a coordinated decision.

I designed and developed Mehraz Negar, my bilingual web-based construction-management platform, around that problem.

Its purpose is to connect the work breakdown structure, programme controls, design coordination, documents, risks and named decisions within project-specific workspaces.

The question behind the interface is practical: what does the person responsible for delivery need to see before agreeing the next step?

For that revised detail, I would want the affected package identified, the programme and procurement implications reviewed, and the required approval made explicit. Then someone needs responsibility for communicating the decision and checking that the right information reaches the site.

A dashboard can make an issue visible. It cannot, by itself, resolve that handover.

That distinction matters to me as a Construction Project Manager. The objective is not to bring every discipline into every meeting. It is to bring the right people and evidence together at the point a decision is needed.

Building Mehraz Negar is one way I have made that management approach tangible.

I want the answer to “What happens next?” to include an action, an owner and a clear basis for proceeding.

Where does information most often lose its connection to the next action on your projects?