Last updated 8 June 2026
Projects / Requests Feature Intake

Requests Feature Intake

Initiative / Delivery Clarity and Flow

Create a structured intake process so feature requests are well-formed, validated, steward-led, and clearly routed from the start.

Open in Linear

Standardise how product feature requests (excluding bugs and operational requests) enter delivery through clearer submission rules, stronger validation, and steward-led triage.

This project ensures feature requests come through the right intake path by making stewards the primary source of submission, improving structural validation, and giving clearer guidance on how to write strong requests. It also reduces noise and duplication through better request shaping and duplicate detection, so ideas are easier to assess before they move into discovery or delivery.

The goal is to reduce incomplete or low-quality requests, improve prioritisation, and create a more reliable front door for change so requests are properly formed before they move into discovery, planning, or delivery.

Status

Backlog

Lead

Ian Lovell

Teams

Platform

Resources

Linked Linear docs and external resources.

1 total

Project updates

Recent status notes posted directly on this project in Linear.

0 shown

No project updates have been posted in Linear yet.

Initiative updates

Recent updates shared from Delivery Clarity and Flow because this project has limited direct update history.

3 shown

Ian Lovell

16 Apr 2026

We’ve now closed both Delivery Workflow and Delivery Reporting projects, marking the completion of a key set of improvements to how work is defined, prepared, and tracked across delivery.

The Work site now includes issue readiness guidelines, giving the team a shared standard for when work is ready to move forward from request through to completion. We’ve also introduced issue-writing guidance to support clearer, more structured requests.

We’ve added Requests - Tracking as the next area of focus. This project covers creating clearer visibility into what happens after a request is accepted, from review and discovery through planning, delivery, parking, cancellation, or conversion into projects. The aim is to make request status, ownership, and outcomes easier to follow in Linear and on the work site, giving teams and requesters a more transparent and reliable view of progress across the full lifecycle.

Maria Kudriavtseva

27 Mar 2026

We’ve continued improving both workflow efficiency and visibility across the initiative this sprint.

As part of the broader cleanup and simplification of work organisation, the New Features team has been removed from Linear. All new issues are now routed to the TEC team for validation and further action.

Work on documenting issue readiness guidelines is in progress, aiming to establish a clear, shared standard for when work is ready to enter delivery.

Forecasting has been introduced on the Work site to improve visibility into upcoming delivery and support more confident planning.

A dedicated Linear view for Clinic & Support teams has been created in test mode to explore the most effective approach for department-level visibility, sprint prioritisation, and allocation.

Ian Lovell

4 Mar 2026

We’ve rolled out structured issue templates, ensuring tickets include clear context such as patient/order details and supporting media. This standardisation not only speeds triage and reduces duplicates but also ensures that if issues evolve into larger projects, the requirements and context are already well-documented, making subsequent work more efficient and easier to plan.

Issues

Grouped by current Linear workflow status.

2 total

Todo

2

  • PLT-198 - Investigate Linear issue duplication detection
    Todo
  • PLT-63 - Create online form for Linear requests
    Todo