Draftingstarter tier10 credits per run

Letter of Explanation

LoEs that address the officer's concern head-on, cite the rule, and close with the ask. One concern per letter.

Credits
10
Mode
Async
AI
LLM-backed
SOP Generator · output
tool_id=sop-generator

Statement of Purpose — Master of Data Science, UBC

My decision to pursue the Master of Data Science at the University of British Columbia is not a pivot. It is a continuation of a trajectory that began in my second undergraduate year, when I built a recommendation system for the campus library and

Weak spots flagged · Program rationale could name two UBC faculty. Financial ties paragraph omits spouse income.

CICC §8.1 disclaimer auto-stamped · reviewed by [RCIC name] before sending

Paste → Output

What you give it, what it gives back.

Nothing magical. A clean input surface, a clean output surface. Both visible before you hit run.

Paste inyou
  • concern:string — the exact officer concern
  • clientStory:string
  • citedRule:string — IRPR / OP manual / program criteria
Get backtool
  • letterMarkdown:string

Every output · DRAFT · FOR RCIC REVIEW

Letter of Explanation is a drafting tool, not a filing tool. Every output renders with a non-dismissable DRAFT stamp, a CICC §8.1 disclaimer, and a "reviewed by [RCIC name]" footer. The stamp is a tool registry primitive — no AI output ships without it.

How it saves time

The three ways this one pays for itself.

01

Blank-page problem, gone

You stop writing first drafts. You edit. The heavy structural work is already done by the time you open the doc.

02

Weak spots flagged for you

Letter of Explanation flags its own weak spots so you don't miss them at 11pm. Less "what did I forget" review, more focused edit.

03

CICC-defensible by default

Every output ships with the DRAFT stamp, a CICC §8.1 disclaimer, and an append-only audit log entry — so review is evidence, not overhead.

Schema

Exactly what goes in, exactly what comes out.

Inputs

concernstring — the exact officer concern
clientStorystring
citedRulestring — IRPR / OP manual / program criteria

Outputs

letterMarkdownstring

Available on the AI Portal.

Join the waitlist for cohort access, or email the founder for a firm-sized quote.

About this tool

Letter of Explanation · FAQ

Three questions we get every week on this specific tool.

The tool is built for the 80% case, but its schema accepts edge-case values. Anything the tool can't handle deterministically is either rejected with a helpful error or flagged as a weak spot. Unusual cases still benefit from the structured scaffolding; your RCIC review adds the last 20%.