Oravelin's programme documentation follows a defined process from source review through session brief publication. Each stage of that process is described here.
Each programme cycle begins with a structured review of published exercise science literature. Sources are selected based on peer-review status, publication date, and relevance to the target movement category. Sources are logged in an internal reference archive.
The review process distinguishes between primary research, systematic reviews, and meta-analyses. Programme parameters — including volume ranges, rest intervals, and movement sequencing principles — draw from sources where the evidence base is consistent across multiple studies.
Reviewed sources inform the structural architecture of each programme block. Session design maps movement patterns across a defined weekly structure, ensuring that volume distribution follows established progressive overload principles.
Each session is built around a primary movement, a secondary movement, and an optional accessory sequence. Rest intervals are indexed by intensity tier rather than fixed duration, allowing adaptation across fitness levels. The sequencing model is logged as a structured table within each programme file.
Before a programme is published, each session brief undergoes an internal consistency review. The review checks that movement sequences do not introduce conflicting stimulus patterns, that volume across the week falls within documented safe ranges, and that the progression criteria between sessions are achievable.
Verification also covers the session brief text itself — checking that execution notes are unambiguous, that alternatives are listed where the primary movement requires equipment substitution, and that difficulty ratings are calibrated against the programme level index.
Programmes are published to the Oravelin index once verification is complete. Each programme entry carries a publication date, a programme code, and a revision number. When a session within a programme is updated, the revision number increments and the previous version is archived.
The publication index groups programmes by fitness level, training objective, and average session duration. New programme blocks are added on a quarterly publication cycle. Archived versions remain accessible through the index for reference purposes.
Every session is accompanied by a brief that states the session purpose, primary movement, secondary movement, volume parameters, rest intervals, and a note on common execution errors. The brief is written for practical reference — concise, specific, and unambiguous.
Each programme block includes a progression table mapping the expected volume and intensity trajectory across the block's weeks. Progression increments are expressed as percentage-of-baseline increases, allowing individuals to calibrate relative to their starting point rather than a fixed absolute load.
When a session brief is revised, the change is documented within the brief itself. The revision log records the date, the nature of the change, and the version number. This practice maintains a transparent history of all methodological updates across the programme library.
Oravelin does not produce original research. The programme documentation is derived from published exercise science literature, with sources selected and screened according to the criteria described in Stage 01 of the methodology. No proprietary research is claimed.
The primary source categories include peer-reviewed strength and conditioning journals, published meta-analyses on bodyweight training outcomes, and systematic reviews of HIIT protocols in non-gym settings. Where multiple sources address the same parameter — such as optimal work-to-rest ratios — the methodology notes the range of published positions and selects the approach most applicable to a home training context.
All source references used in programme development are logged internally. The reference log is updated at each quarterly review cycle. Individuals who wish to consult the primary sources for any documented programme parameter may submit an enquiry through the contact page.