From personal lists
to one loading plan.

Know the boundary. You provide every requirement. Reusable equipment must return between jobs. For simultaneous needs, enter the combined quantity on one line. MeginLoad does not plan battery runtime, shared crews, equipment left on site, conversions, inventory depletion or orders. A checked list is not a guarantee of completeness.

Install and open

Extract the entire buyer ZIP to a folder you control. Keep MeginLoad.html next to the app, manual, screenshots and examples folders. Open MeginLoad.html in desktop Google Chrome. No terminal, server, account or internet connection is required for the app. Do not open the app from inside the ZIP preview.

Native testing: Linux x86_64 and Google Chrome 152.0.7977.82. Other operating systems and browsers are not verified. A 390-pixel layout was checked for reading; desktop preparation is the supported workflow. The separate free pack contains this guide and examples, not the editable application.

Your first result: the Maple example

1. Click Try fictional example. This creates three invented visits and prefilled example vehicle/storage counts. These are fictional numbers, not an inspection you performed.
2. In Review & export, expand the pad’s contribution list. It shows 4 + 6 + 2 = 12. The drills use MAX(1, 1, 2) = 2 because the tasks are sequential.
3. Compare the table below. Mark Physically inspected only as a practice check in this fictional example. Loading and returning are separate marks.
4. Click Save project and keep the downloaded JSON. Download the printable packet, open it in Chrome and use Print. Reopen the JSON with Open project.

Remove Bench visit under Jobs to prepare. DRILL becomes 1 and PAD becomes 10; their checks clear. BIT remains 1 and its existing inspection stays bound. Undo restores the previous data but clears all physical marks.

Make your own library and recipes

At the opening screen choose Start blank and acknowledge sequential use. Use Rename to name the session. Add an item under Items & recipes: a unique stable ID, descriptive name, counting rule, unit and optional storage bin.

• Reusable / MAX: bring the highest requirement on any one sequential task line. Two lines for the same tool with quantities 1 and 2 require 2, not 3.
• Consumable / SUM: add every task line, including duplicates. Two lines of 0.1 and 0.2 require exactly 0.3.
• Identical names with different IDs remain different items. Kind is never inferred from the name. No unit conversions occur.
• IDs cannot be renamed. To change identity, create a new item and replace its references. Removing an item fails until all job and recipe references are removed.

Create a recipe, give it a name, then add task labels, items and quantities. Add line stages a line; Save recipe commits the recipe. The ×, Escape or Cancel discards pending editor changes. Repeat for common lists you already use. Recipes have no delete button in version 1.0; edit or reuse them within the 100-recipe limit.

Build jobs from recipes

Choose Jobs to prepare → Add job. Enter a label and optional location/note. Select a recipe and click Insert copy, or add lines manually. Each inserted line retains a snapshot of the recipe name, line ID and original quantity. Edit a copied line without changing its recipe. Save the job when finished.

Changing a recipe affects future insertions only. An existing job keeps its copied quantities and provenance. Each line’s task label matters: changing a contributing task clears checks even if the item total remains equal. The app assumes all these tasks happen one after another; naming a task “simultaneous” does not change the rule.

For the next day, save the current project, then choose New session from library. This keeps items and recipes, removes jobs and clears all inspected counts and physical marks. To start completely blank, save your work, reload the app and choose Start blank.

Import your own item CSV

Only item definitions import from CSV; jobs and recipes use the project JSON. Use UTF-8 with exactly these headers in this order:

item_id,name,kind,unit,bin
CASE,Reusable case,reusable,each,Studio
FLUID,Sample fluid,consumable,litre,Studio

Choose Import items CSV. Review the preview of additions and matching IDs. Default mode rejects collisions. Explicit replacement mode replaces matching definitions after you choose Apply this import. Existing job and recipe quantities stay unchanged, so review any unit or counting-rule changes. Affected checks clear. Cancel leaves the session unchanged.

Commas, quotes and newlines inside cells must be double-quoted; escape a quote as two quotes. LF or CRLF row endings and a UTF-8 BOM are accepted. Duplicate IDs/headers, unknown columns, malformed quotes, invalid UTF-8 and missing fields reject the entire file. No rows are silently dropped. The bundled examples/items.csv is a starting point.

Review the result and inspect quantities

Each item shows its counting rule, required quantity and contributing job/task lines. Enter quantities already in the vehicle and available in storage, then click Apply counts. Blank means unknown, never zero.

deficit = max(0, required − in vehicle)
load = min(deficit, available in storage)
obtain = max(0, deficit − available in storage)

If either count is unknown, load and obtain remain unknown. Vehicle overage is displayed separately and never causes a negative load. Counts can be zero; requirement lines must be positive. Use canonical decimal strings from 0 to 999999.999, with up to three fractional digits: 1, 0.5, 0.125. Enter 1 instead of 1.0, and 0.1 instead of 0.100. Leading zeroes, signs, spaces, exponent notation and excess precision are rejected. Internally, quantities use exact integer thousandths.

Mark Physically inspected after applying both counts. Mark Physically loaded separately. Reusable items also have Physically returned. These are your records, not automatic evidence that work occurred. Any relevant item, task, job note, contributing quantity or inspected count change clears affected marks. A project stores a binding to detect stale marks after edits/imports; it is not a security signature and does not make deliberately modified files trustworthy.

A reopened project can retain marks if their binding still matches. For a new trip use New session from library and inspect again. Unknown and unchecked lists stay DRAFT; inspected lists say “Preparation inspected by user,” not “ready.”

Save, export, print and reopen

• Save project: downloads a .megin.json file containing the library, recipes, copied job lines, counts and physical marks. Use Open project to restore it. JSON preserves text exactly. No autosave or background cloud copy exists. The “Downloaded” status means the browser download was requested; verify the file in Downloads.
• Loadout CSV: a presentation table for review. Formula-like text beginning with =, +, -, @ or whitespace followed by these is prefixed with an apostrophe for spreadsheet safety. Numeric fields remain exact decimal strings. Unknown counts are the word unknown. This output is not an item-import CSV and is not a project backup.
• Printable packet: downloads standalone, script-free HTML: consolidated list grouped by sorted bin/name/ID, obtain/inspect list, per-job contributions and reusable return checks. Open it in Chrome, press Ctrl+P, select A4 or Letter, default scale, and disable browser headers/footers. Choose Save as PDF or a configured printer. Physical paper printing was not tested.

Downloads use a sanitized session name. The app only reads selected source files; it never writes back to them. Your browser controls download locations and same-name handling—keep a distinct filename when saving a new version. Closing or refreshing without a saved JSON loses your work. A browser leave-page warning is a convenience, not crash recovery.

Troubleshooting and limits

Limits: 500 items, 100 recipes, 20 jobs, 2,000 total job lines, 5,000 total recipe lines; 2 MiB input and serialized project; 16 MiB presentation exports. IDs: 1–40 ASCII letters, digits, underscores or hyphens. Names, task labels and bins: 120 characters; units: 20; notes: 1,000. Check bindings count toward the byte limit, so entry limits are not all guaranteed simultaneously for maximum-length text. Unsupported schema versions and extra fields reject atomically.

Tab/Shift+Tab move focus, Enter activates buttons and submits forms, Space toggles checkboxes, Escape closes an editor. At narrow widths, library tables scroll horizontally; review cards stack. No accessibility compliance certification or mobile field-use claim is made.

Privacy, provenance and uninstall

The app has no analytics, network calls, remote fonts, accounts or runtime dependencies. Selected files and edits remain in browser memory until you download them. Exported files contain your entered data; store and share them deliberately. No browser storage is used. Your browser or operating system may retain downloads or recent-file history independently of this app.

All included example data, code, styling and screenshots were created for MeginLoad. Maple and Studio are fictional arithmetic demonstrations; no trade procedures or customer records are bundled. See LICENSE.txt and NOTICES.md. This product does not establish field effectiveness, purchase demand, legal compliance or completeness of your list.

To uninstall, close the tab and delete the extracted folder. Keep project JSON files if you want your data, or delete your own downloaded projects and packets too. There is no service or account to cancel.