Skip to main content
A fractional practice runs on documents: the engagement letter that starts a client, the status report that proves the work, the diagnostic that frames the problem. TorchRunner produces these from what it already knows about the engagement, so you are editing a real draft instead of starting from a template.

​
Documents you edit in place

These are produced inside TorchRunner and edited right there, with the engagement’s context already filled in:

Engagement letter

The agreement that opens a client relationship.

Statement of work

Scope, deliverables, terms.

Change order

When the scope moves, on the record.

Retainer invoice

Billing that reflects the engagement.

Status report

The recurring proof of work for the client.

Diagnostic report

The framing document that scopes a problem.
These open in a rich editor inside the workspace. The draft arrives populated from the engagement record, you shape it, and it stays linked to the client it belongs to.

​
Documents generated into your other tools

Some deliverables belong in formats their readers already expect: a board deck, a complex financial model. For those, TorchRunner generates into the standard tools, so a spreadsheet model lands as a real spreadsheet and a slide deck lands as real slides, ready to open where your client opens them.
Whether a document is edited in place or generated outward depends on the artifact. Narrative deliverables live in TorchRunner. Heavy spreadsheets and decks generate into the tools built for them.