Skip to content
  1. Home
  2. Our work

Tillotts Pharma

Tillotts Pharma: project and risk management in Power Apps

Tillotts Pharma, a specialty pharmaceutical company focused on gastroenterology, moved its project and risk tracking out of spreadsheets and into Power Apps on SharePoint, with escalations in Power Automate and dashboards in Power BI.

Industry
Pharma and life sciences / Project and risk management
Platform
Power Apps on SharePoint
Timeline
10 weeks, in four phases
Stage
Delivered
  • 10 weeks

    Requirements workshops to full rollout

  • 3

    Projects in the pilot

  • Each update entered once and reported everywhere

The challenge

The challenge

Project and risk data sat in spreadsheets and static risk registers, so leadership often learned about an issue weeks after it appeared.

Approach

Every project manager kept a different spreadsheet

Tillotts ran its projects and risks from Excel spreadsheets and SharePoint document libraries, reviewed in regular status meetings. Each project manager kept a tracking system of their own with slightly different templates, and the risk registers lived in static documents.

Executive reports had to be put together by hand from all of those sources. Project managers spent hours on status reports, and by the time an issue showed up in a monthly report, the chance to act early had often passed.

One place for project and risk data

Project and risk data now lives in SharePoint lists, and project managers enter it once through Power Apps screens in a standard format. Before the build we agreed with the team on four things: standard risk categories and severity scales, project stage gates and approvals, the rules for escalation and notification, and which historical data to migrate or archive.

Audit trails record every change, and role-based security controls who sees what. Validation rules keep the data consistent, and the solution links to the SharePoint document libraries where project files already lived.

Escalations and dashboards

Power Automate handles the routine steps. It escalates high-priority risks and reminds owners when a risk assessment is due. It also notifies stakeholders at project milestones and starts a review when a project moves away from its baseline.

Leadership sees project health and risk exposure across all projects in Power BI dashboards embedded in the solution, and project managers and executives can check and update it from any device.

Built in two-week increments, piloted on three projects

The work ran in four phases over 10 weeks. Two weeks of workshops with the people who run and oversee projects set the requirements. We then built the solution in increments delivered every two weeks for feedback.

In weeks 7 and 8 we piloted it on three projects of different types and complexity, which ran in the new system alongside the old approach. After refining the screens, workflows and reports, we rolled it out in weeks 9 and 10, with hands-on training for project managers and IT support staff and dashboard briefings for executives.

Inside the implementation

Architecture overview

The solution uses Microsoft Power Platform on top of SharePoint. SharePoint lists hold the project and risk data, Power Apps provides the screens, Power Automate runs the routine steps and Power BI shows the dashboards.

Project and risk management

  1. 01

    Data layer

    Project and risk data in one place, with security and version control.

    • SharePoint lists
    Next: Entry
  2. 02

    Application layer

    Project managers enter data once, in a standard format.

    • Power Apps
    • Validation rules
    • Role-based security
    Next: Routine steps
  3. 03

    Automation layer

    Escalations, reminders, milestone notices and baseline reviews.

    • Power Automate
    Next: Reporting
  4. 04

    Analytics layer

    Project health and risk exposure across all projects.

    • Power BI embedded dashboards

Audit trail

Every change is recorded, which supports regulatory inspections.

Existing documents

The solution links to the SharePoint document libraries and Office 365 tools the teams already used.

Logical view of the documented architecture. Client-specific infrastructure and identifiers are omitted.

Key design decisions

  1. Fix the process before automating it

    Risk categories, severity scales, stage gates and escalation rules were agreed in workshops before the build, so the app automates a process the team had already improved.

  2. Start with the core, then add

    The first release covered the core functions. Further features were added from user feedback once people were using it.

  3. Pilot in parallel

    Three projects ran in the new system alongside the old approach before the full rollout.

How the workflow fits together

  1. A project manager updates a project

    The update goes into SharePoint lists once, through Power Apps.

  2. Rules check the update

    Validation rules keep the data consistent, and the change is recorded.

  3. Flows act on it

    Power Automate escalates high-priority risks and starts a review when a project leaves its baseline.

  4. Leadership sees it

    Power BI dashboards show the current state of every project without a manual report.

Questions for a similar implementation

Use these review points when you assess this architecture for your own environment.

  • Which risk categories and severity scales will every project use?
  • When should a risk escalate, and to whom?
  • Which historical project data should move into the new lists, and which should be archived?

Results

The outcome

Project managers enter each update once and every report and dashboard picks it up, so status reports no longer have to be compiled by hand. Leadership sees risk exposure across all projects, and the system keeps an auditable record of changes for regulatory inspections.

Stack

Technology used

  • Microsoft Power Apps
  • Power Automate
  • Power BI
  • SharePoint lists
  • Office 365

First published on our blog on 12 May 2025.

Research paper

Compliance-grade RAG: Retrieval systems a regulator can audit

How to build retrieval that a regulated reviewer can trust and audit.

Read the paper
Get the designed PDF

Start with your workflow.

We define the scope and acceptance criteria with you, in writing, before the build starts. Wider programs are scoped separately, and commercial terms are set in the statement of work.

  • Built to SOC 2, HIPAA and GDPR standards
  • EU AI Act-aligned delivery
  • Microsoft Solutions Partner