Step-by-step guide
MeginLoad
Combine personal task recipes into one loading and obtain list, with visible quantities and contributing jobs.
Use this for desktop preparation before sequential service visits by one operator. You supply the requirements and inspect the counts. Reusable tools must return between jobs; consumables add across all tasks.
See it in use
Prepare a loading packet for three visits
A screenshot walkthrough with fictional practice data. Select a step to explore.
1. Start with
Prepare a loading packet for three visits
Maple has three fictional jobs, vehicle stock and store stock.
Sample files and contents
Jobs A/B/C need DRILL 1/1/2, BIT 1/1/0 and PAD 4/6/2. Vehicle counts are DRILL 1, BIT 1, PAD 3; storage counts are 1, 0 and 5.
Practice files and guides are free. The complete app is included only where the product page says so.
2. In the app

Try it in three steps
- Load the example and open Review & export.
- Inspect reusable MAX and consumable SUM contributions.
- Save the project and open the printed packet.
Show every click and setting
- Use Try fictional example and open Review & export.
- Expand each contribution list: reusable equipment uses MAX, consumables use SUM.
- Compare the loading and obtain quantities, save JSON and open the downloaded packet.
3. The result
Inspect the result
The packet lists item totals, load and obtain actions, and job contributions. The fictional PAD need totals 12 units across visits.

What to check in the practice result
DRILL required 2, load 1, obtain 0. BIT required 1, load 0, obtain 0. PAD required 12, load 5, obtain 4. Removing Bench visit changes DRILL to 1 and PAD to 10. These are fictional arithmetic results, not field or trade guidance.
This fictional example is shown in the working interface and in the supplied result. Review the guide before using your own files.
See the workflow at a glance
Choose a short explanation, then follow the worked example below. Check the requirements and compatibility before using your own files.
Two drills, twelve pads: show where the totals came from.
Three sequential visits do not need three separate sets of reusable tools. MeginLoad's fictional Maple example takes the maximum drill requirement and sums consumable pads, then compares the totals with vehicle and storage counts. The result asks for one drill to load, five pads to load and four pads still to obtain. Requirements come from you, and reusable equipment must return between jobs. This is planning, not proof that anything was loaded or a trade-completeness checklist. The guide shows the arithmetic and saved project workflow in Linux Chrome.
View the illustrated card

Choose the quantity rule before loading the vehicle
The Maple example is one operator visiting jobs sequentially, with reusable equipment returning between visits. Check that assumption before choosing MAX.
The same equipment returns between visits
Use MAX for the reusable drill and bit requirements. Drill quantities 1, 1 and 2 require two drills, not four. With one already in the vehicle and one in storage, load one and obtain none.
Supplies are used up on each visit
Use SUM for the pads: 4 + 6 + 2 = 12. With three in the vehicle and five in storage, load five and obtain four. Do not apply MAX to consumables just because the visits are sequential.
Jobs overlap, or stock is unknown
Represent simultaneous demand together; separate MAX lines do not model concurrent crews. A blank stock count is unknown, not zero. Check physical quantities before marking loading complete; the calculation does not prove the vehicle is loaded.
Before you start
- Desktop Google Chrome on Linux; Chrome 152 on Linux x86_64 was verified. Other environments and mobile field use are unverified.
- Extract the whole ZIP. Keep MeginLoad.html beside app, manual, screenshots and examples; open it outside the ZIP preview.
- Your own item IDs, units, counting rules, task requirements and inspected vehicle/storage counts. The fictional examples are arithmetic demonstrations.
Your first result
Try the fictional Maple example
Open
MeginLoad.htmland choose Try fictional example. Go to Review & export. Expect DRILL 2, BIT 1 and PAD 12 required. Expand the pad contributions to see 4 + 6 + 2. The prefilled counts and checkmarks are practice data.Compare the loading result
With the example counts, DRILL needs 1 loaded and 0 obtained; BIT needs 0 and 0; PAD needs 5 loaded and 4 obtained. Remove Bench visit under Jobs to prepare: DRILL becomes 1 and PAD becomes 10. Affected physical marks clear.
Create your own item and recipe library
Choose Start blank, acknowledge sequential use and name the session. Under Items & recipes, add stable IDs, names, units, bins and either Reusable/MAX or Consumable/SUM. Create a recipe, use Add line, then Save recipe. Identical names with different IDs stay separate.
Copy recipes into jobs
Choose Jobs to prepare → Add job. Enter its label and notes, select a recipe and choose Insert copy, or add task lines manually. Save the job. Future recipe changes do not alter existing copies. Enter simultaneous needs together on one combined line.
Inspect the actual counts
In Review & export, use Inspect, Obtain and Load from storage to find the next item, then select it to reach its counts and task contributions. Enter vehicle and storage quantities and choose Apply counts. Blank means unknown. Typed edits show UNAPPLIED COUNTS; save, export, navigation and physical marks wait until you apply or correct them. One Apply action validates all pending item counts together. Invalid values stay visible. Inspect changed items again, then mark physical loading separately.
Save a project and printable packet
Choose Save project and keep the downloaded JSON; there is no autosave. Open project restores it. The printable HTML includes the same inspect, obtain and load lists, plus per-job details and return checks. Open it in desktop Chrome and print to A4 or Letter, or save as PDF. CSV is a review table, not a project backup. Use New session from library for another trip and inspect again.
A worked example
Maple: three fictional visits
Input: Jobs A/B/C need DRILL 1/1/2, BIT 1/1/0 and PAD 4/6/2. Vehicle counts are DRILL 1, BIT 1, PAD 3; storage counts are 1, 0 and 5.
- Use Try fictional example and open Review & export.
- Expand each contribution list: reusable equipment uses MAX, consumables use SUM.
- Compare the loading and obtain quantities, save JSON and open the downloaded packet.
Expected result: DRILL required 2, load 1, obtain 0. BIT required 1, load 0, obtain 0. PAD required 12, load 5, obtain 4. Removing Bench visit changes DRILL to 1 and PAD to 10. These are fictional arithmetic results, not field or trade guidance.
More application screens
Know what to inspect, obtain and load
Actual version 1.0.1 screens and exports in Chrome on Linux. Maple and Studio inputs are fictional arithmetic examples.
1. See what needs attention

2. Keep edited quantities visible

3. Take the same lists with you

4. Review a compact layout

Troubleshooting
Save or export asks me to apply counts
A count was edited but not applied. Correct every pending field, then choose Apply counts once. The updated lists appear and changed items need fresh inspection. Returning a field to its saved value cancels that edit.
Unknown loading amounts
Enter both vehicle and storage counts and choose Apply counts; blank is unknown.
Quantity rejected
Use 1, 0.5 or 0.125; not 1.0, .5, signed or exponent notation.
CSV import rejected
Use exact item_id,name,kind,unit,bin headers, UTF-8 and unique IDs. Review explicit replacement mode for existing IDs.
Checks cleared
Changed items, quantities or contributing jobs/tasks require reinspection, even if totals match.
Work not saved
Use Save project and keep the downloaded JSON. The app has no autosave.
Compatibility & limits
- For one operator doing sequential tasks. Reusable equipment must return between jobs. Enter simultaneous requirements as one combined task line; separate lines use MAX.
- You enter and review every requirement. This is not a trade checklist, a completeness guarantee or evidence that an item was physically loaded or returned.
- No battery or runtime capacity, shared crews, equipment left on site, unit conversion, stock depletion, ordering, costing or device sync.
- Only desktop Google Chrome 152 on Linux was tested. Other environments, mobile field use and physical printing are unverified.
- No autosave. Download and keep the project JSON. A reopened project can retain matching historical marks; start a new session and inspect again for a new trip. Undo clears physical marks.
- Up to 500 items, 100 recipes, 20 jobs, 2,000 job lines and 5,000 recipe lines. Input and saved project limit: 2 MiB including check bindings; presentation exports: 16 MiB. Maximum counts and maximum text may not fit together.
- Quantities must use canonical decimal text with up to three decimal places and a maximum input of 999999.999. Use 1, 0.5 or 0.125; signs, exponents, leading zeros and trailing fractional zeros are refused.
- Recipes can be edited but cannot be deleted in version 1.0. Existing job copies retain their original quantities when a recipe changes.
- Presentation CSV guards formula-like text with an apostrophe; JSON retains original text. CSV is not a project backup. Unknown counts remain unknown.
- Large lists and verbose labels can produce impractical printouts. Version 1.0.1 Maple A4 and Letter PDFs are checked; maximum-size paper layouts and physical printing remain unverified.
Need a hand?
Tell us the product, host application and version, what you tried, and the exact error. Contact support with a fictional example; keep private customer files and passwords out of your message.