Digital intake and scoping tool
A browser-based tool that guides requesters through the information agreed for scoping new work, built for a global biopharmaceutical company.
- Client
- Global biopharmaceutical company, Europe
- Services
- Process design, tool build
- Area
- Development and automation
Context
The wider situation.
Teams that deliver project work depend on clear requests. When a request arrives without key details, such as its purpose, audience, deliverables or deadlines, the team has to go back to the requester before it can scope or estimate the work. Each round of follow-up adds delay, and the information that eventually arrives is often recorded in different places and formats, which makes it harder to use.
The problem usually grows with volume. Requesters describe their needs in their own way, by email, in documents or in conversation, and the receiving team spends time interpreting and reformatting them. Without an agreed set of information, it is also difficult to compare requests or to estimate consistently. A structured intake step addresses this by asking for the right details at the point a request is made.
The challenge
What needed to change.
Requests for new work arrived incomplete and in different formats.
Missing details meant repeated follow-up before work could be scoped or estimated.
What we did
Our approach.
Identified the details every request needs before it can be scoped
Built a simple browser-based tool that guides requesters through each one
Produced a consistent, structured request that feeds straight into scoping
The work started with the scoping process itself. The details every request needs before it can be scoped were identified first, so that the tool would ask for the right information. A simple browser-based tool was then built to guide requesters through each of those details in turn. The tool produces a consistent, structured request that feeds straight into scoping, giving the team a single format to review in place of incomplete requests that need repeated follow-up.
Delivery perspective
The tool produces a consistent request format for the team to review and scope.
Planning similar work
What similar organisations should consider.
Agree what scoping requires
Before designing any form or tool, agree with the people who scope work which details they genuinely need. The list should be as short as possible while still allowing a reliable estimate. Asking for information that is never used discourages requesters and adds nothing to the scoping process, so each item should earn its place.
Guide requesters step by step
Many requesters submit work only occasionally and are not familiar with what the delivery team needs. Guiding them through each item, with plain explanations of why it matters, helps them provide complete answers the first time. A tool that runs in the browser also avoids the need for software installation or special access.
Produce a consistent output
The value of an intake tool lies in what it hands to the receiving team. A request in a consistent, structured format can be reviewed quickly, compared with others and taken straight into scoping. Agreeing that output format early makes it easier to connect the tool to the steps that follow.
Keep the tool simple
Intake tools work best when they are easy to use and easy to change. A simple tool can be adjusted as the team learns which details matter most, without a lengthy development cycle. Complexity can be added later if it proves necessary, but it is difficult to remove once requesters have become used to it.
Discuss a similar project.
Tell us about your project.