Demo preview — sample data, nothing is saved to a server

Static project assembly preview. Showing a fictional generator starter example first, so reviewers can judge the workflow before entering anything. No account, upload, backend sync, checkout, payment, live notification, or production project management is active. Planning aid only - not engineering, code, permit, final quote, or safety approval.

Project Assembly Workspace

Model the job before the crew rolls.

This is the next shape of Munda Field Planner: assemble the scope, sources, field constraints, crew sequence, materials, internal risks, and customer-safe handoff before the first truck leaves.

Fictional generator starter example is loaded.

First review the example, then start your own redacted job when you are ready. This reduces blank-page friction and shows what the workspace is supposed to produce.

Open generator starter Plan a job PM view

Scan the model

Do the source inputs, sequence, materials, and risks match how you think before rollout?

Start your job

Use redacted text only. No real names, exact addresses, access codes, files, or customer details.

Tell us what failed

The best feedback is where it feels too generic, too slow, or not realistic for field use.

Browser-local edits

Save and resume this assembly here.

This is the lightweight test version: edit redacted source inputs, save them on this device, refresh, and continue later. Nothing is uploaded or synced.

Job label

Fictional starter is active until you save a copy.

Current inputs match the saved browser-local assembly shown on this page.

Edit source inputs for the assembly

Contract / scopeWhat is included, excluded, or assumed?IFC drawings / plansEquipment, routes, schedules, or one-line references.Site measurementsPad, route, clearances, access, or field dimensions.Specs / manualsSubmittals, manufacturer notes, startup details, or model requirements.Photo / site-note summaryText only. Summarize what photos or site notes show.Timing / crewOutage window, crew plan, inspection dependency, or trade sequence.

Source hierarchy

The goal is to assemble the job from the documents and site facts that actually control the work.

Contract / scope

Ready for review

Fictional/redacted example: replace an existing standby generator before a school weekend outage.

IFC drawings / plans

Ready for review

Example plan set shows generator pad, ATS, feeder route, fuel interface, and one-line references.

Site measurements

Ready for review

Example site walk notes: pad footprint, feeder route, crane access, and gate clearance need verification.

Specs / manuals

Ready for review

Example submittals include generator set, transfer switch, startup checklist, and manufacturer notes.

Photos / notes summary

Ready for review

Example notes mention overhead lines, gate access, pad condition, fuel piping, and occupied-school constraints.

Timing / crew

Ready for review

Example sequence assumes PM review, two electricians, rigging vendor, utility/outage coordination, and inspection support.

Pre-rollout assembly stages

This is the one-page command view, split into steps so it stays usable on mobile.

Source model

Ready for review

Collect what controls the job before the crew rolls.

Scope, drawings, measurements, specs, notes, timing.

Site / access model

Ready for review

Make the job visible: access, route, pad, equipment, constraints.

Pad, rigging, feeder route, fuel/ATS interfaces.

Crew sequence

Verify

Turn the plan into ordered work the foreman can follow.

Tasks, rough durations, dependencies, owner/crew notes.

Material readiness

Verify

Separate planned, ready, long-lead, and verify-before-order items.

Draft categories, examples, and verification notes.

PM / field / customer handoff

Ready for review

Keep internal risk separate from customer-safe progress language.

PM notes, field checklist, customer-safe update, print packet.