Your browser. Your workspace.

Document Transmittal Ledger

Freeze dated drawing issue lists with revision references, optional file fingerprints and recipient references. Print transmittal cover sheets and record acknowledgments manually.

Local browser tool. No accounts, uploads or background synchronization. Export backups for records you need to retain.

How this register works

A transmittal is a dated snapshot of the documents you intend to issue. Select individual current drawing-register rows or enter document references manually, then freeze the package. The saved document list, date and recipient reference cannot be edited through the ordinary interface. Record acknowledgment separately only when it has actually been received.

Choose an existing project workspace or use an unassigned local project. Keep different physical lots on distinct records. Up to 500 records per register and 2 MB for the combined operations backup.

Loading local records...

Reuse an existing reference

Read existing local source records, select one row and copy it into the unsaved form. Review the copy before saving. No source record is changed.

Receipt sources include all typed purchasing project references. Assembly BOM sources are the saved global plan. Workspace takeoffs and drawing registers are limited to the selected project. Repeated copying can create duplicates; reconcile the source and existing ledger first.

Add or review a record

Add a document to this issue

    Recorded work

    Examples, backups and recovery

    All four operations tools share one backup. A JSON file includes traceability, fabrication, shipments and transmittals with their linked identifiers. Loading a sample or backup replaces only this open view. An explicit record save or Save loaded view writes the entire current operations view to this browser. Export the existing saved records first before replacing them.

    Download fictional sample JSON

    If another tab changes operations, saving stops instead of overwriting its newer records. Export your current view, reload saved data, and reapply the intended change. If browser storage is full or disabled, preserve the form and export the open records before closing. These are independent local copies, not a multi-user audit system.

    Worked example

    Choose current drawing S101, revision A, from the selected workspace register. Check the issue file and optionally calculate its fingerprint. Add the document, enter issue reference T-001 and the recipient distribution reference, then freeze and save. If S101 later changes to revision B, T-001 continues to show revision A. Create T-002 for the new issue instead of rewriting the earlier record.

    Use the clearly labeled fictional sample to inspect the relationships between a six-piece material lot, its production stages, a two-piece bundle, and a one-drawing issue. None of these records describes a real customer or project.

    Troubleshooting before the next handoff

    • Confirm the workspace and mark before copying a source row. A copied snapshot will not update automatically.
    • Resolve missing or conflicting references through the responsible project team. The tools do not invent approvals.
    • Print or export the relevant record, check its quantity and revision, and retain an operations JSON backup alongside the controlled project files.

    Questions about document transmittal ledger

    Does saving a transmittal send files or email?

    No. No files, emails, messages or upload requests are sent. Print or export the cover sheet and transmit the controlled files using your established project channel. Record the acknowledgment date manually.

    Does a file fingerprint prove approval or delivery?

    No. SHA-256 identifies the selected byte sequence. It does not identify who approved a drawing, establish that it is correct, or prove that a recipient received it.

    Why does a drawing row with a blank revision need attention?

    A frozen package needs an explicit revision reference. Use the convention actually established for the project, including a meaningful initial-issue label when appropriate; never invent a revision based on the filename alone.