Deliverable
Preflight V1.0 · WINDOWS

A final check for document handovers

Your register says what should be there. Preflight checks what is.

Import a CSV or XLSX register, scan a local delivery folder, and see exactly which files are ready, missing, unexpected or ambiguous—before the package leaves your hands.

Microsoft StoreGet Deliverable Preflight →Inspect the real workflow ↓
02 / WORKFLOW

Four deliberate steps. One defensible result.

Deliverable Preflight stays close to the workflow document controllers already use. It does not replace the register, rename files or invent matches.

  1. 01

    Register

    Open a CSV or XLSX register, choose the header row and map document number, revision and filename.

  2. 02

    Delivery folder

    Select the folder to inspect and decide whether subfolders should be included.

  3. 03

    Matching mode

    Compare exact filenames or locate complete document-number tokens inside filenames.

  4. 04

    Report

    Review every outcome, inspect candidate paths and export the complete result to CSV or XLSX.

03 / ACTUAL PRODUCT

No mock-ups

The tested Windows application.

These are the same release-candidate screens used for the Microsoft Store listing. Select a stage to inspect the workflow.

Deliverable Preflight with a CSV register imported and a delivery folder scan completed
Register and folder ready. Six valid register rows imported; eight local files scanned.
04 / RESULT LOGIC

Four outcomes. Nothing vague.

R

Ready

Exactly one scanned file matches the register expectation.

M

Missing

No scanned file matches the register expectation.

U

Unexpected

A scanned file does not correspond to any register expectation.

A

Ambiguous

More than one candidate file matches a single expectation.

05 / MATCHING

Choose the rule that matches the handover.

Both modes are deterministic and explain what they matched. There is no fuzzy scoring, AI interpretation or cloud processing.

MODE A

Exact Filename

Compares the complete expected filename from the register with scanned filenames, ignoring letter case.

Best for
Controlled packages with an agreed filename field
Revision
Included only when it is part of the expected filename
MODE B

Document Number in Filename

Finds the mapped document number as complete filename tokens separated by hyphens, underscores, dots or spaces.

Best for
Packages where descriptive filename text varies
Revision
Not validated; the report states this clearly

Privacy by architecture

The register and delivery stay on the device.

The application reads only locations selected by the user. It does not upload files, create accounts, collect telemetry, show advertising, rename files, move files or delete source content.

Read the full privacy policy →
06 / FIELD NOTES

Practical document-control guides.

View all field notes →
GUIDE 04What should a master document register include?Essential fields · revisions · final file checks GUIDE 01How to check a document register against a delivery folderRegister preparation · folder scan · exception review GUIDE 02A practical document handover checklist before issueScope · revisions · naming · package evidence
DELIVERABLE PREFLIGHT · V1.0

Check the package before it leaves your hands.

Now availableMicrosoft StoreView product →