[ Project name — e.g. Hyperscale data centre, Jakarta ]
- Problem
- [ What was going wrong, in one or two sentences. ]
- Action
- [ What you actually did — the decision, not the duty. ]
- Result
- [ The measurable change. A number you can source. ]
Project Controls & Scheduling
Project coordinator working in enterprise scheduling, advanced project controls, and data-driven execution for mission-critical infrastructure. When the reporting tools could not answer the question, I built the ones that could.
Selected work
Not a list of job titles — what was broken, what I did about it, and what measurably changed.
Built, not just used
Five project-control modules sharing one project master and one sign-in. The strongest thing on this page is not a description of my skills — it is a platform you can go and look at.
Document control with a real audit trail, role-based access scoped per project, and an approval workflow that survives contact with a live site. Node and Express on the back, Prisma over PostgreSQL, a React front end.
Capabilities
Oracle Primavera Cloud and P6. Baseline development, critical path, look-ahead planning, and recovery scheduling.
WBS design, weighted progress measurement, earned value, and variance analysis that traces back to the activity.
Deliverable registers, review cycles from IFR to IFC, and approval trails that hold up under audit.
Mission-critical infrastructure delivery, where a slipped commissioning date is not a rounding error.
When the reporting stack cannot answer the question, I build what does — full stack, in production, used on real work.
Turning a week of spreadsheet reconciliation into a dashboard the project actually trusts.