How a Biotech Leader Automated Project Tracking in a Regulated Environment

A world-leading biotechnology company was tracking its project epics and realization measures by hand. Records were typed in with nothing checking them, status updates arrived late, and every report had to be compiled from whatever copy of the data someone had taken that week. OnPoint Insights replaced the manual entry with a Power Apps application, automated the status updates through Power Automate and SharePoint, and moved the reporting into a Tableau dashboard.

Manual entry replaced by an app

A Power Apps application with validation built in, so task and epic records meet the standard at the point of entry instead of being corrected afterwards.

Status updates itself

Power Automate and SharePoint keep task and epic status current automatically, so stakeholders see progress without asking anyone for it.

Reports opened, not assembled

A Tableau dashboard replaced the manual compilation that every report used to start with.

The problem

Manual tracking fails quietly

Manual project tracking does not break all at once. A field gets filled in differently, a status is updated two days late, a report is built from a copy someone took on Tuesday. Each one is small. Together they mean the project status everyone is working from is approximately true, and in a regulated environment approximately true is a different kind of problem.

Our client was tracking project epics and realization measures this way across fragmented reporting processes. The errors were predictable, the visibility was poor, and the reporting took long enough that the teams producing it had little time left for the work it was supposed to inform.

What was getting in the way

  • Manual data entry produced frequent errors and inconsistent task records, which undermined the reliability of project tracking.
  • Teams had no real-time view of project status, so stakeholders could not track progress or respond quickly.
  • Reporting required manual data compilation, which slowed turnaround and took time away from strategic work.
  • The process was not flexible enough to absorb new workflows or changing business requirements.

Our approach

Standards at the point of entry, not after the fact

What we found

Every item on the client’s list traced back to the same place: data typed in by hand with nothing checking it. Reporting was slow because the records had to be reconciled first. That meant the fix had to start at data entry, not at the dashboard.

What we did

An application instead of manual entry. A custom Power Apps application removes manual input, enforces data standards and validates records as people work rather than after they submit.

Status that maintains itself. Power Automate and SharePoint keep task and epic status current automatically, so visibility is a by-product of doing the work instead of a separate reporting exercise.

Reporting that is already compiled. A Tableau dashboard presents the key metrics, so producing a report means opening it.

Built to be extended. The design accommodates new workflows and features as the business process changes, which in a regulated environment it reliably does.

The choice we made

We put the validation in the form rather than in a cleanup process afterwards. A form with rules is more constraining than a spreadsheet and people notice it will not accept a half-finished record or a date that cannot be right. That friction is the point. It is the difference between an error being prevented and an error being discovered in a report, and in a regulated environment the second one is expensive.

BUILT ON
  • Power Apps Power Apps
  • SharePoint SharePoint
  • Tableau Tableau
  • Power Automate Power Automate

The results

What changed for the teams

Project status stopped being something the business assembled and became something it could look at.

Fewer errors, because fewer chances to make one

Validation and consistency checks inside the application catch problems at entry, so the records behind the reporting are consistent rather than reconciled.

Status without asking for it

Stakeholders see project and epic status immediately rather than requesting an update, which shortens the gap between something changing and someone acting on it.

Reporting time back to the team

Report turnaround fell, so the people who used to spend their week compiling data spend it on the priorities the reports were meant to serve.

Let's Connect

Facing a similar challenge?

Talk to our data and AI team about where you are today and what good looks like. 30 minutes, no obligation.

Book a consultation
Professional customer service agent on a support call
More Case Studies
Next Case Study
Contact Us

Collaborate with us

We're here to answer your questions and help you find the right solution.

Client-oriented
Results-driven
Problem-solving
Transparent

"*" indicates required fields

This field is for validation purposes and should be left unchanged.