Setup requests now cover more starting points
Protocol added more public setup paths for lifters coming from spreadsheets, notes, other apps, or existing written plans.
Shipped
- Added a public path for people who want to move an existing training setup into Protocol.
- Made routine conversion and platform migration requests easier to find from the Resources area.
- Clarified that request paths are for setup help, not a guarantee that every plan can be converted.
- Added safer public forms and clearer confirmation behavior around setup requests.
- Connected more public pages back to the app handoff without making the site overclaim what the app can import automatically.
Why
Most serious training history does not start inside a new app.
It starts in a spreadsheet, a notes file, a coach message, another tracker, or a program PDF. That does not mean the lifter wants to rebuild every week from scratch. It means the first product question is often: can I bring what I already do into a structured place?
The new request paths are meant for that moment. They give someone a public way to explain what they are trying to move, while keeping the boundary honest. Protocol is not promising automatic import for every format. It is making setup friction visible so the product can keep improving around real routines.
This matters because routine setup is part of the workout experience. If the app only works for people who start from a blank canvas, it misses the lifters who already have a plan.
Notes
- Requests are reviewed selectively and may not be converted.
- Protocol does not provide medical, nutrition, or coaching advice through these forms.
- Imported routines still need user review before training.
Next
- Keep using setup requests to find the routine families and migration paths worth supporting first.
- Keep public Resources pages aligned with the app's actual routine support.