· Theals · Practice · 2 min read
Project intake tracks and what to send first
Pick a track, send the minimal inputs, and get a first pass output quickly without scope drift.
Most wasted time comes from unclear requests. This page is a fast scoping layer so work starts correctly.
Choose one track to start. Mixed requests are fine, but they should be sequenced.
Track 1. Manuscript or review
Best for:
- a draft that feels incoherent or repetitive
- methods and results that need tightening
- a revision cycle that is stuck
Send:
- latest draft
- figures and tables, even if rough
- target journal or audience
- deadline if real
You receive:
- revised draft with tracked changes
- change log explaining why changes matter
- optional response-to-reviewers draft
Track 2. Grant polishing
Best for:
- aims that are not crisp
- approach sections that invite reviewer attack
- resubmission strategy
Send:
- call text or funder criteria
- aims page
- research strategy outline or draft
You receive:
- tightened narrative aligned to criteria
- risk register style critique of reviewer objections
- prioritized edit plan
Track 3. Clinical data and ML
Best for:
- cohort definition and validation
- reproducible analysis pipelines
- figure and table generation with an analysis memo
Send:
- schema and table list, or a small representative extract
- cohort definition in plain language
- outcomes and key covariates
- constraints including PHI handling
You receive:
- cohort logic implemented and validated
- reproducible pipeline outputs with versioned folders
- summary tables and plots
- short analysis memo stating assumptions and limitations
Track 4. Tools and infrastructure
Best for:
- eliminating repeated manual work
- small internal tools for teams
- structuring documentation and content systems
Send:
- current workflow and pain points
- example inputs
- desired outputs
You receive:
- working tool
- minimal documentation
- handoff instructions
If you want work to move fast, pick the track first.
