From redline to drawn, with you holding the pen

The four steps

1. Drop the redline on the palette.

   Drag the markup PDF onto the palette. Before it reads a page, SparkFlow asks whether there is anything it should know about this markup, and your line travels with the job. SparkFlow matches each page to the drawing you actually have open using the sheet number, title block, revision and the geometry itself. If the evidence is thin or contradictory, it asks instead of guessing.

2. Read every instruction in context.

   The page is split into independent instructions. Each one is interpreted against your approved standards, symbol libraries and drafting conventions, including separate treatment for legacy and current project generations. A page with no text layer, such as a handwritten one, is read page by page.

3. Review the proposal, with its evidence.

   Each card shows the note as SparkFlow read it, the sheet and revision it is bound to, the validators’ result and the reference shown. Clear items become reviewable right away; unclear ones wait for clarification instead of blocking everything.

4. Accept, reject or teach.

   Accepting a proposal triggers a final check of the drawing, its version, the lock and your permissions. The change then runs as one native AutoCAD transaction with a discrete undo group, and an audit entry records the decision. Reject applies nothing. Teach tells SparkFlow what that markup means for your firm.

The proposal card

The palette docks beside the drawing you have open. Every proposal waits there for you, and nothing runs behind your back. Each card carries its own evidence: the note as SparkFlow read it, the sheet and revision it is bound to, the validators’ result and the reference shown. Nothing is drawn on the sheet while you review; the change is drawn when you accept.

StartE-001*E-101*E-102*

PROJECT MANAGER

SAMPLE PROJECT

SparkFlowAssistant

Proposal 1 of 1 · Bound to E-101 Rev 3

Replace the receptacle in the sink zone with a GFCI receptacle on circuit LP-4-12

Standard S-E-09 · 12 validators passed

Reference shown: OESC Rule 26-700(11) (illustrative)

Accept Reject Teach

Ask SparkFlow or describe a change

SAMPLE PROJECTE-001.DWGE-101.DWGE-102.DWGLP-4.DWG

ProjectsLocation View

[-][Top][2D Wireframe]

Command:

Your codes and standards, under your licence

SparkFlow buys no code or standard and shares none between firms. The books your engineers ask about are your firm’s own licensed copies, read inside your own environment and nowhere else. Nothing is sent to a publisher and no publisher password is kept.

1. Your firm holds the licence.

   Each book is covered by an organizational licence, or is your firm’s own document, or a public one. A single-user copy is not enough: ask the publisher for the organizational version.

2. Your administrator uploads your copy and signs the authorization.

   The authorization names SparkFlow a user of that copy on your firm’s behalf, under your licence, and records the licence’s expiry date, if it has one.

3. SparkFlow reads it for your firm alone.

   Within minutes it is indexed inside your environment. Every answer drawn from it cites the rule and the edition it relies on.

4. It stops when your licence does.

   When your licence expires, the book leaves the assistant until your administrator renews the authorization. A reminder comes 90 days before, and once a year even for a licence that never expires.

What makes a proposal trustworthy

Confidence scores don’t move drawings at SparkFlow. Deterministic checks do.

Binding before interpretation

A markup page must prove it belongs to your open drawing before any proposal is generated. Signals include:

• Sheet number, title block and project identifiers
• Revision and date agreement
• Drawing fingerprint and page geometry

An older-revision markup gets a prominent warning and needs your explicit go-ahead. Proposals from it are labelled and re-interpreted against the current drawing, never replayed blindly.

Validators that cannot be talked past

Before Accept is even enabled, every applicable check must pass:

• The target objects exist and are the right type
• The drawing is current, writable and locked to you
• Geometry, layers, blocks and connections follow your project’s profile
• The action is on the approved list, with valid parameters

No amount of model confidence, seniority or clicking through overrides a failed check.

Undo that means undo

While your markup session is open, every applied change can be reversed individually or all together, in dependency-safe order. Once you save and close, the session is finalized: the history stays visible in the archive as evidence, and recovery follows your normal document management process.

A paper trail your reviewers will like

Every proposal, decision, teaching event and applied change is recorded: who, what, where on the sheet, which evidence, which validations, before and after. Exportable by project, drawing, date or person.

Teaching

Teach once and the firm’s standard is remembered for the next sheet, across the team.

A teaching is one decision on one card. It is remembered, with the evidence of what it was taught from, for the next engineer: the next similar markup is read your firm’s way.

What SparkFlow learns stays in your firm’s environment alone. Your administrator sees it in the dashboard and can pin, narrow, quarantine or retire any item, and nothing learned from your firm is ever used for another company or for training a model.

The three assistants

Answers come from your approved standards, licensed Ontario code content and the drawing on your screen. Never from a model’s vague recollection.

Your standards, remembered

Questions about your firm’s drafting standards are answered from the standards your administrator loaded, cited to the section.

Ontario code, cited

Questions about the code are answered from the editions your firm holds a licence for, cited by edition and clause. A licensed engineer reviews an answer before anyone relies on it.

The open drawing, inspected

Questions about the drawing on your screen are answered from what the plug-in reads in it. A review of the drawing checks its electrical facts group by group, cites what it relied on, and changes nothing.

When an assistant cannot support an answer with evidence, it says so instead of guessing.

What it never does

What it never does: it never edits a drawing on its own, never sends a drawing anywhere but your firm’s own Canadian environment, and never claims a code determination. A licensed engineer decides.

Never edits closed drawings

Only the drawing you have open and writable can be changed. Batch edits across a folder don’t exist. A markup for another sheet waits until that sheet is opened and rescanned.

Never crawls your file server

No onboarding ingestion of your project history. SparkFlow reads a drawing when someone opens it, and quietly pre-reads siblings of that same project, read-only, to speed things up.

Never answers from stale memory

Historical questions like “how many receptacles did project 203 have in 2024” are refused by design. The cache that speeds up scanning is not searchable, not even by us.

Never certifies compliance

Code answers cite the exact provision and explain it plainly, then hand judgment back to your licensed engineer. There is no “engineer reviewed” button, on purpose.