[{"data":1,"prerenderedAt":471},["ShallowReactive",2],{"guide:en:getting-started/how-it-works":3},{"id":4,"title":5,"body":6,"description":463,"extension":464,"meta":465,"navigation":466,"path":467,"seo":468,"stem":469,"__hash__":470},"guide_en/en/user/getting-started/how-it-works.md","How Aptli Fits Together",{"type":7,"value":8,"toc":449},"minimark",[9,13,42,45,50,61,73,77,83,90,94,100,132,135,140,147,174,177,181,195,201,211,223,227,234,240,278,282,285,291,305,308,312,315,348,352,355,413,416,441],[10,11,5],"h1",{"id":12},"how-aptli-fits-together",[14,15,16,17,21,22,25,26,29,30,33,34,37,38,41],"p",{},"Before you touch any single page, it helps to see how the pieces relate. Almost everything in Aptli hangs off one spine: a ",[18,19,20],"strong",{},"project"," holds ",[18,23,24],{},"jobs",", each job has a ",[18,27,28],{},"material side"," and a ",[18,31,32],{},"work side",", and both sides come back together in a ",[18,35,36],{},"report"," that a ",[18,39,40],{},"validation"," signs off on. Inventory moves underneath all of it.",[14,43,44],{},"This page is the map of that spine. Every box here has its own detailed guide later — this is just how they connect.",[46,47,49],"h2",{"id":48},"the-big-picture","The big picture",[51,52,57],"pre",{"className":53,"code":55,"language":56},[54],"language-text","                          ┌─────────────┐\n                          │   PROJECT   │   optional umbrella\n                          └──────┬──────┘\n                                 │  groups many\n                                 ▼\n                          ┌─────────────┐\n                          │     JOB     │   one unit of planned work\n                          └──────┬──────┘\n                ┌────────────────┴────────────────┐\n                │                                  │\n         MATERIAL stream                      WORK stream\n       \"what gets used\"                    \"what gets done\"\n                │                                  │\n                ▼                                  ▼\n       ┌─────────────────┐               ┌──────────────────┐\n       │ Resource lines  │               │   Work Orders    │\n       │   on the job    │               │  (the dispatch)  │\n       └───────┬─────────┘               └────────┬─────────┘\n               │                                  │\n        ┌──────┴───────┐                  ┌───────┴───────┐\n        ▼              ▼                  ▼               ▼\n   Registered      Ad-hoc           Registered        Ad-hoc\n   RESOURCE      (typed in by      ACTIVITY         (typed in by\n  (from your       hand, not       (from your        hand, not\n   catalogue)     registered)       catalogue)       registered)\n","text",[58,59,55],"code",{"__ignoreMap":60},"",[14,62,63,64,67,68,72],{},"The shape repeats deliberately. ",[18,65,66],{},"Both streams give you the same choice:"," pull from a catalogue of registered things, ",[69,70,71],"em",{},"or"," type something in ad-hoc. You are never forced to pre-register everything to get work moving.",[46,74,76],{"id":75},"a-project-holds-jobs","A project holds jobs",[14,78,79,80,82],{},"A ",[18,81,20],{}," is an optional umbrella — a campaign, a site rollout, a phase of work. It groups related jobs and rolls their progress up so you can watch the whole effort in one place.",[14,84,85,86,89],{},"A job does ",[18,87,88],{},"not"," have to belong to a project. Plenty of work is a one-off job with no umbrella. The project is there when you want the rollup, not as a hoop to jump through.",[46,91,93],{"id":92},"a-job-has-two-streams","A job has two streams",[14,95,79,96,99],{},[18,97,98],{},"job"," is the core unit of planned work. Think of it as having two independent sides:",[101,102,103],"callout",{},[14,104,105,108,109,112,113,116,117,108,120,123,124,127,128,131],{},[18,106,107],{},"Material side"," — ",[69,110,111],{},"what the work consumes."," These are the ",[18,114,115],{},"resource lines"," on the job: the cable, the screws, the adhesive, the labour hours. ",[18,118,119],{},"Work side",[69,121,122],{},"what actually gets done."," This is dispatched as ",[18,125,126],{},"work orders",", each carrying an ",[18,129,130],{},"activity"," (the splice, the inspection, the dig).",[14,133,134],{},"The two streams run in parallel and don't depend on each other. A job can have material with no formal activity, or an activity with no tracked material. You add structure to each side only where it earns its keep.",[136,137,139],"h3",{"id":138},"registered-vs-ad-hoc-the-recurring-choice","Registered vs. ad-hoc — the recurring choice",[14,141,142,143,146],{},"On ",[18,144,145],{},"both"," streams you pick one of two paths for every line:",[148,149,150,168],"ul",{},[151,152,153,156,157,162,163,167],"li",{},[18,154,155],{},"Registered"," — chosen from a catalogue you maintain (",[158,159,161],"a",{"href":160},"/guide/inventory-management/resources/","Resources"," for materials, ",[158,164,166],{"href":165},"/guide/work-fulfillment/activities/","Activities"," for work). Registering buys you consistent names, units, stock tracking, and pickup rules.",[151,169,170,173],{},[18,171,172],{},"Ad-hoc"," — typed in by hand, on the spot. Nothing pre-registered. Use it for the one-time material or the unusual task that isn't worth a catalogue entry.",[14,175,176],{},"The same record can mix both. This is the \"looser reference system\" — registration is an option that adds tracking, never a gate that blocks work.",[46,178,180],{"id":179},"both-streams-meet-in-a-report","Both streams meet in a report",[14,182,183,184,187,188,190,191,194],{},"Planning describes what ",[69,185,186],{},"should"," happen. A ",[18,189,36],{}," captures what ",[69,192,193],{},"actually"," happened — and it's where the two streams converge:",[51,196,199],{"className":197,"code":198,"language":56},[54],"        WORK stream                       MATERIAL stream\n            │                                   │\n     work performed                     material consumed\n   (against the activity)              (against the resources)\n            │                                   │\n            └────────────────┬──────────────────┘\n                             ▼\n                        ┌─────────┐\n                        │ REPORT  │   what was actually done + used\n                        └────┬────┘\n                             ▼\n                      ┌──────────────┐\n                      │  VALIDATION  │   sign-off\n                      │  pass / fail │\n                      │  needs-revision / approved-with-notes\n                      └──────────────┘\n",[58,200,198],{"__ignoreMap":60},[14,202,203,204,207,208,210],{},"A report records the work completed ",[18,205,206],{},"and"," the material consumed in one place. A ",[18,209,40],{}," is the quality gate on top of it: a reviewer signs off with a status, and that status is what releases the work as accepted. Reports and validations are the audit trail of the job — they stay on the record even after the underlying infrastructure changes.",[101,212,213],{},[14,214,215,218,219,222],{},[18,216,217],{},"Validations aren't a separate menu item."," They live as traffic-light badges on the ",[18,220,221],{},"Reports"," page — click a badge to view, edit, or create a validation without leaving the report.",[46,224,226],{"id":225},"the-inventory-side","The inventory side",[14,228,229,230,233],{},"Everything on the material stream is backed by an inventory ledger. The ",[18,231,232],{},"Inventory"," menu has four views, and they relate to each other like this:",[51,235,238],{"className":236,"code":237,"language":56},[54],"   RESOURCE  ──┐\n  (what it is, │\n   the         ├──►  STOCK ITEM   the live balance:\n   catalogue)  │    \"X of this resource, at this site\"\n               │           │\n   SITE  ──────┘           │ every change is written as a\n  (where stock lives:      ▼\n   warehouse, depot,  TRANSACTION   receipt · transfer · pickup ·\n   or a person)                     consumption · adjustment · return\n",[58,239,237],{"__ignoreMap":60},[148,241,242,252,266,272],{},[151,243,244,247,248,251],{},[18,245,246],{},"Resource"," — the catalogue entry: what the material ",[69,249,250],{},"is"," (also covered above as the registered material option).",[151,253,254,257,258,261,262,265],{},[18,255,256],{},"Site"," — a place that holds stock. A ",[69,259,260],{},"location"," (warehouse, depot, field site) or a ",[69,263,264],{},"personal"," site (a worker's own inventory).",[151,267,268,271],{},[18,269,270],{},"Stock Item"," — how much of a given resource sits at a given site. The balance only ever changes through a transaction.",[151,273,274,277],{},[18,275,276],{},"Transaction"," — the immutable record of every movement in or out. This is the audit trail; you correct mistakes by adding an adjustment, never by editing history.",[46,279,281],{"id":280},"what-happens-to-consumed-material","What happens to consumed material",[14,283,284],{},"When a report says material was used, that consumption doesn't just vanish from a form — it moves real stock. Consumed material goes one of two ways:",[51,286,289],{"className":287,"code":288,"language":56},[54],"   ┌──────────┐   consumed       ┌────────────────────────────┐\n   │   SITE   │ ───────────────► │ Used up at the job          │\n   │ (stock)  │                  │ Gone — but recorded forever │\n   └────┬─────┘                  │ as a consumption record     │\n        │                        └────────────────────────────┘\n        │ transferred / picked up\n        ▼\n   ┌──────────────┐\n   │ Person or    │   Carried out as tracked inventory —\n   │ another site │   still on the books, just moved\n   └──────────────┘\n",[58,290,288],{"__ignoreMap":60},[148,292,293,299],{},[151,294,295,298],{},[18,296,297],{},"Consumed at the job"," — the material is spent. The stock balance drops and a permanent consumption record is written. You can't erase usage; corrections are made by adding an adjustment, never by deleting history.",[151,300,301,304],{},[18,302,303],{},"Pulled out of the site as tracked inventory"," — the material leaves the warehouse but isn't gone. It's transferred to another site or picked up by a worker, so it stays on the books in a new location until it's actually used.",[14,306,307],{},"Either way, the inventory ledger always reconciles: stock that left a site was either consumed or is now sitting somewhere else that the system can point to.",[46,309,311],{"id":310},"putting-it-together","Putting it together",[14,313,314],{},"A typical flow, end to end:",[316,317,318,324,330,336,342],"ol",{},[151,319,320,323],{},[18,321,322],{},"Plan"," — create a job (optionally under a project). Add resource lines for the materials and dispatch work orders with their activities.",[151,325,326,329],{},[18,327,328],{},"Authorize & pick up"," — workers draw the registered materials they need from a site.",[151,331,332,335],{},[18,333,334],{},"Do the work"," — out in the field, against the work order's activity.",[151,337,338,341],{},[18,339,340],{},"Report"," — capture the work completed and the material consumed.",[151,343,344,347],{},[18,345,346],{},"Validate"," — a reviewer signs off, which accepts the work and finalizes the consumption.",[46,349,351],{"id":350},"where-to-go-next","Where to go next",[14,353,354],{},"Each box on this page has a full guide:",[148,356,357,364,371,378,386,396],{},[151,358,359,363],{},[158,360,362],{"href":361},"/guide/work-fulfillment/projects/","Projects"," — the umbrella that groups jobs",[151,365,366,370],{},[158,367,369],{"href":368},"/guide/work-fulfillment/jobs/","Jobs"," — planning work with resource lines",[151,372,373,377],{},[158,374,376],{"href":375},"/guide/work-fulfillment/workorders/","Work Orders"," — dispatching the work side",[151,379,380,382,383,385],{},[158,381,161],{"href":160}," and ",[158,384,166],{"href":165}," — the two catalogues",[151,387,388,382,391,395],{},[158,389,221],{"href":390},"/guide/work-fulfillment/reports/",[158,392,394],{"href":393},"/guide/work-fulfillment/validations/","Validations"," — capturing and signing off",[151,397,398,402,403,407,408,412],{},[158,399,401],{"href":400},"/guide/inventory-management/stock-items/","Stock Items",", ",[158,404,406],{"href":405},"/guide/inventory-management/sites/","Sites",", and ",[158,409,411],{"href":410},"/guide/inventory-management/transactions/","Transactions"," — the inventory ledger underneath",[14,414,415],{},"Three menu items sit alongside this spine rather than inside it:",[148,417,418,424,435],{},[151,419,420,423],{},[18,421,422],{},"Home"," — a dashboard of progress and inventory rollups across everything above.",[151,425,426,429,430,434],{},[18,427,428],{},"Field Records"," — the map. Jobs and features have a geographic presence there; see ",[158,431,433],{"href":432},"/guide/getting-started/map-concepts/","Map Concepts",".",[151,436,437,440],{},[18,438,439],{},"Help Requests"," — ask for and track support on any record.",[14,442,443,444,448],{},"Next up: ",[158,445,447],{"href":446},"/guide/getting-started/access-and-controls/","Who Can See and Change What"," — how Aptli decides what each person is allowed to view and edit.",{"title":60,"searchDepth":450,"depth":450,"links":451},2,[452,453,454,458,459,460,461,462],{"id":48,"depth":450,"text":49},{"id":75,"depth":450,"text":76},{"id":92,"depth":450,"text":93,"children":455},[456],{"id":138,"depth":457,"text":139},3,{"id":179,"depth":450,"text":180},{"id":225,"depth":450,"text":226},{"id":280,"depth":450,"text":281},{"id":310,"depth":450,"text":311},{"id":350,"depth":450,"text":351},"The big picture: how projects, jobs, work, materials, reports, and validations relate to each other — and how consumed inventory is tracked.","md",{},true,"/en/user/getting-started/how-it-works",{"title":5,"description":463},"en/user/getting-started/how-it-works","YWUOI7UA6LUyuJg7xAwFXzFtSV8d3SDx1O-p_aZdI44",1781607714702]