Blindsmiths

1

Jobs directory and entry point

Start from the jobs directory so the new record lands in the standard search and handoff flow.

Open Create job from the jobs directory

The jobs directory is the normal entry point for new work. Start there so the record is immediately searchable and visible to the rest of the office flow.

Overview

Open full size for readable detail

Detail views

Expected result

A clean new-job flow opens from the standard jobs directory, not from an ad hoc shortcut.

Last verified 2026-04-10

2

New job form

Capture customer details, operator fields, and notes before entering windows.

/jobs/new

Create the base job record

Enter the customer, operator, and note details first. The job record should exist before you start adding windows or uploads.

Overview

Open full size for readable detail

Detail views

Expected result

The job is created and routes directly into the job workspace with the main details already attached.

Last verified 2026-04-10

3

Job overview

The job header, status/menu, and meta cards are the persistent shell for entry, quote, and production work.

/jobs/{jobId}

Confirm the job shell before editing rows

Once the job opens, the header and meta cards become the shared context for window staging, quoting, and production actions.

Overview

Open full size for readable detail

Detail views

Expected result

The operator can confirm they are on the correct job before adding or committing any rows.

Last verified 2026-04-10

4

Entry tabs overview

Form, Voice, and Upload are all staging tools. Nothing durable reaches the sheet until Commit.

/jobs/{jobId}

Understand the staging model

Form, voice, and upload all feed the staged rows review. They are entry modes, not separate durable sources.

Overview

Open full size for readable detail

Detail views

Expected result

Operators know that Form, Voice, and Upload all lead into the same staged review and commit path.

Last verified 2026-04-10

5

Form entry workflow

Use Form when you are typing one row at a time and want the cleanest office-first capture path.

/jobs/{jobId}

Add rows to staging from Form

Form mode is the clearest way to capture one blind at a time. It stages rows locally first so you can review them before the live sheet changes.

Overview

Open full size for readable detail

Detail views

Expected result

The operator can add windows into staging without mutating the live sheet immediately.

Last verified 2026-04-10

6

Sheet-entry workflow

Use Sheet entry when the operator needs faster spreadsheet-style editing while still staying inside staged review.

/jobs/{jobId}

Capture rows in sheet mode without committing yet

Sheet entry is for faster grid-style capture and review. It still feeds the staged model, so you are not bypassing validation or Commit.

Overview

Open full size for readable detail

Detail views

Expected result

Operators can enter rows quickly in a grid while keeping the same staged review and commit rules.

Last verified 2026-04-10

7

Voice workflow

Voice capture is another entry mode feeding staging. Review is still required before anything becomes durable.

/jobs/{jobId}

Capture by voice, then review the staged result

Voice is for faster spoken capture in the field or office. The transcript and parsed rows still need human review before Commit.

Overview

Open full size for readable detail

Detail views

Expected result

Spoken capture lands in staging and is reviewed before the live sheet or windows list changes.

Last verified 2026-04-10

8

Upload workflow

Upload parses source files into staged rows. Warnings and review still happen before the live job is changed.

/jobs/{jobId}

Upload, parse, and review before commit

Upload is the faster bulk path for external files. The parse result still lands in staging first, where warnings and review happen before Commit.

Overview

Open full size for readable detail

Detail views

Expected result

Uploaded source rows are staged, reviewed, and only then committed into the durable job record.

Last verified 2026-04-10

9

Draft rows review

Staged rows are the review point for validation errors, edits, clears, and the final commit decision.

/jobs/{jobId}

Review staged rows before they become durable

Staged rows are where Form, Sheet, Voice, and Upload converge. Review validation issues, fix rows, and decide whether to clear or commit.

Overview

Open full size for readable detail

Detail views

Expected result

Only reviewed, validated rows are promoted from staging into the committed windows list.

Last verified 2026-04-10

10

Save flow

Commit is the moment staged work becomes durable. Before that point, the live sheet and committed windows stay unchanged.

/jobs/{jobId}

Commit only after staged review is complete

Commit turns reviewed staged rows into durable job data. Until it runs, the live sheet and committed windows list should still reflect the previous durable state.

Overview

Open full size for readable detail

Detail views

Expected result

Operators understand exactly when staged work becomes durable and what remains local before that point.

Last verified 2026-04-10

11

After-save edits

After commit, use the committed windows list to edit or delete durable rows instead of treating staging and committed data as the same thing.

/jobs/{jobId}

Edit committed rows after they reach the windows list

Once rows are committed, they move into the durable windows list. Post-commit edits belong there, while new draft work still belongs in staging.

Overview

Open full size for readable detail

Detail views

Expected result

Operators can distinguish staged edits from committed-row edits and work in the correct surface for each.

Last verified 2026-04-10