Project descriptions that answerthe questions reviewers ask
- Written against the CRA criteria
- Live word limits
- Evidence linked to every claim
Write T661 project descriptions that hold up to review
What it does, up close
- 01 · Guided editor
Three sections, three clear jobs
Separate fields for technological uncertainty, work performed and technological advancement, each with prompts drawn from the questions a CRA reviewer is trained to ask.
- 02 · Live checks
Know it meets the criteria before you submit
As you write, Sredible™ flags missing hypotheses, vague outcomes and routine engineering language, and shows your word count against the form limit.
- Word limits per section
- Systematic investigation prompts
- Plain-language warnings, not jargon
- 03 · Evidence links
Every claim in the narrative points to proof
Link a sentence to the lab note, commit or test result that supports it. Reviewers see the trail, and so do you when a question comes in two years later.
Three steps, no training day
- 1Step 1
Answer the prompts
Short questions pull the technical story out of the people who did the work.
- 2Step 2
Draft and refine
Shape the answers into the three Part 2 sections with live checks.
- 3Step 3
Review and lock
A reviewer signs off, and the final text flows into the audit package.
One system, every part of the claim
Every project, document and deadline in one place
ExploreProxy or traditional, calculated for you
ExploreContemporaneous records, tagged as you go
ExploreA review-ready file, built automatically
ExploreVetted technical and financial consultants
ExploreIt helps you write it. Drafting assistance turns your answers into structured text, but the facts and final wording are yours.