Quick answers #
Short, practical answers to common how-to questions. These power the Ask AI help bubble.
Everything Big Sky does, in the order your shop will use it. Skim the sidebar, search any topic, both the navigation and the article content filter as you type, or follow the workflow top-to-bottom.
Last refreshed May 2026. Includes parts checkouts, multi-warehouse stock, Travel Flags, BSAP wholesale, 2FA, Microsoft SSO, and everything else that shipped this spring.
Everything that's shipped recently, newest first. Check back here to see what's changed across the platform.
Big Sky is the complete shop platform, work orders, FAA-compliant logbook entries, parts inventory and POs, quotes, invoicing with built-in Stripe payments, time tracking, accounting export, and a real-time shop floor view. This guide is the manual.
Use the search box at the top of the sidebar to find any topic in seconds. Every section has a #anchor link in the heading: copy it to share a deep link with another tech in the shop, or with us in support.
Big Sky is built around the lifecycle a job actually moves through. Knowing this map makes the rest of the platform self-explanatory.
Status moves freely between the first four. Only sign-off transitions to released, which locks the WO and produces the LBE.
Drafts are fully editable. Once sent, line items lock; only payment status, due date, and notes can change.
Receiving against a PO updates inventory and rolls cost into the linked WO automatically.
Big Sky has five roles. Permissions are layered, Owner can do everything, each role below has progressively narrower access.
Top-level admin. Created automatically for the first user on a fresh deploy. Can promote and demote any other role, including Admin. Only Owner can grant Owner. The shop's identity, billing, Stripe Connect, and outbound email routing are Owner-controlled.
Day-to-day shop management. Creates / edits / closes work orders, invoices, POs. Can manage users (create, edit role within Admin / Management / Tech, deactivate). Can sign off LBEs if they're an A&P. Cannot promote anyone to Owner.
Same operational rights as Admin minus user management. Useful for shop foremen and lead techs who need to coordinate work and read reports but shouldn't be moving people in and out of the system.
Default for new mechanics. Can punch in / out, view assigned WOs, log labor and parts on discrepancies, write resolutions, and sign off LBEs (when they hold an A&P or IA cert). Cannot edit invoices, POs, or shop settings.
Read-only access to the Accountant page (A/R aging, payments, vendor bills) plus QuickBooks CSV export. No access to maintenance records or sign-off. Use this for an outside bookkeeper.
Customers are the owners of aircraft. One customer can own many aircraft. Manage them on the Customers page.
/customer-profile.html?id=… showing aircraft, WOs, invoices, and balance.Click any customer row to land on their profile, which surfaces:
Use this view when a customer calls, fastest way to pull up everything tied to them.
Aircraft are owned by customers. Manage them on the Aircraft page.
The aircraft's engine count drives whether the WO sign-off prompts for separate engine LBEs. Single-engine aircraft sign one airframe LBE that covers airframe + engine; multi-engine aircraft can sign separate LBEs per engine, plus APU if equipped. Tag has_apu on the aircraft to enable APU sign-off.
Click any tail to land on the aircraft detail page. Shows:
This is your one-stop view when a customer asks "what was done last annual?", every LBE links to its source WO with the full discrepancy + parts breakdown.
A work order is the central object. Discrepancies, parts, time, the eventual LBE, the eventual invoice, all hang off it.
The WO opens in open status. Move it to in progress when you start touching the aircraft.
Sometimes the customer paying for the work isn't the aircraft's registered owner - a management company, a lessee, or a buyer during a pre-purchase. Pick the billing customer first, then click 🔍 Search all aircraft… at the bottom of the tail dropdown and type the tail. Picking another owner's aircraft opens a deliberate acknowledgment step confirming that the selected customer takes on payment and the RTS handoff while the aircraft stays on its owner's profile.
A discrepancy is a single squawk, one defect or task. Most WOs have several. Each one rolls up its own labor + parts cost.
Each discrepancy can have any number of parts. Pull from inventory or enter free-text parts you don't stock.
Pulling a part from inventory automatically decrements the on-shelf count. Removing the part from the disc reverses the decrement.
Type a part number that doesn't match anything in inventory and the system saves it as-is. No inventory_id is captured: so stock isn't decremented. Useful for one-off parts.
When a part is applied to a discrepancy (manual add, checkout, lot pull, customer-owned part, or scanner), any cert on file for that part - an 8130-3 PDF or a photographed cert uploaded to the part with document type Cert - is automatically copied into the WO's Documents as an 8130, tagged for the RTS package, with a note recording which discrepancy it was used on. Use the same part on a second discrepancy and the note gains an "also used on…" line instead of duplicating the document.
Hours go on each individual discrepancy in the Actual Hours field: that's what shows up on the LBE and the invoice. For shop-wide time tracking that aggregates payroll, see the Time Clock.
Two ways to log:
Set status from the WO header. Available transitions:
Big Sky has soft edit locks, when a user opens a WO for editing, no one else can edit the same WO at the same time. Prevents two techs blowing away each other's changes.
If you see "Bob is currently editing this work order":
Locks expire automatically after 30 minutes of inactivity, so abandoned tabs don't permanently block anyone.
From the WO header, click 🖨 Print WO. A clean printable view loads with all discrepancies, parts, and totals laid out for paper. Customer-facing, no internal notes or labor rates by default.
This is what tech writeup, customer copy, and the work-on-the-aircraft printout all look like. Same template; toggle "Show internal notes" if you want it for shop floor use.
Sign-off creates a logbook entry (LBE), locks the WO, and produces a tamper-evident PDF that's ready to hand to the customer or paste into the airframe logbook.
released, every disc is signed and locked, an LBE row is created with a SHA-256 record hash, and the LBE PDF auto-attaches to the WO Documents library.Use for any maintenance or alteration work: R&R, troubleshooting, AD compliance, repairs, modifications. The vast majority of work orders.
Use for the airworthiness inspection itself: annuals, 100-hour, progressive, pre-purchase. The inspection record cites 43.11 and includes the inspection type. If your annual also includes a list of items repaired, you can sign one 43.11 (the inspection) and one 43.9 (the work that fell out of the inspection), that's standard practice.
When you've worked on more than one logbook (airframe + engine 1 + engine 2 + APU), each gets its own LBE.
The WO sign-off flow lets you sign each section separately. The WO doesn't transition to released until every eligible section is signed. Engine LBEs surface engine make/model/serial in the meta grid (frozen at sign time). APU LBEs do the same for APU identity.
Made a typo or need to correct after sign-off? Use Void & Revise. Available from the WO detail page (when status=released) and the LBE detail page itself.
in progress, every discrepancy is unsigned and editable, the LBE row is deleted. An immutable audit-log entry preserves the original SHA-256 hash and your reason. After corrections, re-sign to produce a new LBE.Every signed LBE includes a SHA-256 hash computed over the canonical record at sign time. The hash is printed on the LBE PDF and stored in the database.
Click Verify Hash on the LBE detail page to recompute and compare. Match → record intact. Mismatch → flag immediately, the record has been modified since sign time.
Per AC 120-78B, this is the tamper-evidence mechanism that lets you defend the LBE in any FAA audit.
The Documents library is your shop's complete paperwork archive, 8130-3s, signed LBE PDFs, training records, manuals, photos, customer-supplied PDFs.
Each document can be tied to a customer, an aircraft, a WO, or none of those (general shop docs). Filter by type, search by name / part number / serial number.
From any WO detail page, click 📎 Documents. The upload modal opens with a tile-grid type picker.
After sign-off, the green 📦 Generate RTS Package button appears. Click it to produce a single merged PDF with everything the customer needs.
The merged PDF downloads with archival metadata. Hand it to the customer; they have a single document with every airworthiness record for this trip through the shop.
Quotes are estimates you send before work begins. Build them on the Quotes page.
From the quote detail page, click Send Quote. The customer receives an email with the quote attached as a clean PDF + an Accept link.
Once the customer says yes, click Convert to Work Order. A new WO is created with the quote's items pre-populated as discrepancies and parts. The quote is marked accepted with a link back to the new WO.
After sign-off, click Create Invoice on the WO page (or in the Accountant page's billing pipeline).
The invoice opens as draft. Adjust line items, add tax, set due date, then move to sent.
While the invoice is in draft, every line is editable.
From the invoice detail page, click Send Invoice. We email the customer the invoice PDF + a Pay Now link.
The Pay Now link takes them to /pay?invoice=…: a public page where they can view the PDF, pay with a card, or read your wire/check instructions for offline payment. Invoice flips to sent.
From the invoice detail page, click Download PDF. A clean printable PDF generates server-side with shop letterhead. For paper invoices, hit Print directly, same template renders cleanly on letter-size paper.
When a customer hits Pay Now, Stripe collects their card and processes the charge. As soon as Stripe confirms, the invoice flips to paid automatically.
You'll see the payment in the Stripe dashboard within seconds and on the Accountant page's payments view immediately. Stripe pays out to your bank on whatever schedule you've configured (daily / weekly).
If the customer pays you offline, mark the invoice paid by hand.
Invoice flips to paid. The reference number is saved for your records.
Issue refunds in the Stripe dashboard, full or partial. The Big Sky invoice updates to reflect the refunded amount automatically via webhook.
For check / wire payments that need to be reversed, void the manual payment record first, then issue the refund out-of-band and record it as a separate credit memo.
The Payments page is the master ledger, every payment received (Stripe, check, wire, cash) with the invoice it applied to.
Use this when reconciling at month-end. Filter by date range, payment method, or customer. Export to CSV for the bookkeeper.
The Parts Manager is your parts shelf. Each row is a part number with description, on-shelf count, unit cost, sale price (or markup %), and optional reorder threshold.
Parts are searchable from the WO Add-Part typeahead, which makes adding them to discrepancies a one-click affair.
When a PO arrives, use Parts Receiving to bump inventory + capture the 8130-3.
Receiving updates inventory in real time and rolls cost into the linked WO if the PO has a WO target.
Big Sky generates QR codes for every part in inventory. The Parts Scanner page uses the device camera to scan them.
This is what changes parts from a spreadsheet into a real shop-floor system.
The QR Generator prints sticker labels for every part. Each label has the part number, description, and a QR code the scanner can read.
Tip: print labels in batches of ~30 when receiving a big shipment.
For parts that need serial-number traceability (life-limited engine components, avionics, anything tagged), enable serialized tracking on the part. Each individual unit gets its own serial stored alongside inventory.
When you add the part to a discrepancy, the serial-number field becomes a typeahead of in-stock serials. Pick one; that specific unit gets pulled from inventory and stamped onto the LBE.
When you swap a unit and the old one goes back to the vendor for core credit, log it on the Cores page.
The system tracks expected return dates, credit amounts, and which WO/PO the core came from. The dashboard surfaces overdue cores so they don't fall off the radar.
The Tags page tracks the status of parts on the shelf or in process.
Tags can tie to a specific part, WO, or aircraft. When the FAA asks "where did this part live?", this is your audit trail.
POs track money you owe vendors. Create them on the Purchase Orders page.
From the PO detail page, click Receive. Same flow as Parts Receiving, confirm quantities, upload the 8130-3, save. Inventory updates and cost rolls to the WO.
POs auto-close when fully received. To reopen a closed PO (received quantity wrong, vendor sent more, etc.), an Admin or Owner can Unlock or Reopen the PO from its detail page. Tech / Management cannot, preserves audit trail integrity.
The Status Board is a live read of the shop floor. Cast it to a wall-mounted TV or a lobby monitor.
Shows every active WO grouped by status (Open / In Progress / Waiting Parts / Complete) with the tail number, customer, assigned tech, and time-in-shop. Auto-refreshes, no manual reload.
The Shop Manager is the operational dashboard for whoever's running the day, usually a foreman or the owner.
Punch in / out against a specific WO and (optionally) a specific discrepancy. Hours roll up to weekly timesheets.
Open punches show at the top of the page in real time so you don't forget to clock out. Each tech's weekly hours roll up; Management approves; payroll exports to CSV with FLSA-aware overtime calc.
Work Authorization is the customer-signed pre-work contract. Generates a clean PDF the customer can sign on-screen (touchscreen or mouse), in person or remotely.
Tool Calibration tracks every torque wrench, multimeter, and gauge with their cal date, due date, and certificate number.
The dashboard surfaces tools with cal due in the next 30 days. Never get caught with an out-of-cal tool on a big job.
Inspection Library holds reusable inspection checklists keyed to aircraft make/model.
Build a template once for the C172 annual; pull it into every C172 annual WO with one click. Templates are the difference between an annual taking 8 hours of paperwork prep and 30 seconds.
Reports surfaces shop-wide metrics for any date range:
Use the date pickers or canned ranges (Last 7 / 30 / 90 days, MTD, YTD). CSV export on every report.
The Accountant page is the bookkeeper's home base. Built for an outside accountant or in-house finance person who shouldn't have access to maintenance records.
From the Accountant page, the QB Export card produces a CSV in QuickBooks Desktop's import format.
Pick a date range, choose what to include (invoices / payments / vendor bills), download. Import into QB once a week or once a month, whatever your bookkeeper prefers.
The export includes customer names, invoice numbers, line-item GL codes (mapped on My Shop → Accounting), payment methods, and reference numbers. Bookkeeper-friendly.
My Shop is the shop's identity record. Owner-only.
Admin is where Owner and Admin manage the user list. Add new users, change roles, deactivate.
Each user has their own signature, cert info, and password. LBEs are signed under the certifying mechanic's name + cert, not the shop's.
My Account is the personal settings page for the currently logged-in user.
Big Sky sends invoice emails, quote emails, and Work Auth links from a domain you control. Configured under My Shop → Outbound Email Routing.
[email protected] (you set this).If you skip this, emails fall back to a generic [email protected] sender: which works but looks unprofessional.
Every part can have a free-text shelf label, "B-12, Bay 3" or "Rack 4, Avionics", separate from which warehouse it lives in. Set it in the Edit Part modal under Bin Location.
The label shows up as a 📍 chip on the Parts Manager row so a mechanic can find the bay without asking parts admin. This is per-part metadata, not per-warehouse, use Stock Locations (below) to track which warehouse a part is in.
Mechanics can pull parts off the shelf before they've opened a work order. The system tracks every checked-out unit until it's either scanned onto a WO or returned to the shelf.
Stock_levels stay the single source of truth for what's physically on the shelf. Checkouts are an overlay: separate ledger that says "Jane has 2 of these in her toolbox right now." Nothing decrements stock until a part actually gets consumed on a WO.
When you later scan the part onto a WO via the normal flow, the system FIFO-decrements your open checkouts for that part. Any leftover qty stays in your list until you return it. If you consume more than you checked out, the extra "falls through" as a normal consume, no harm.
Parts Manager rows show how many units are currently checked out across all mechanics. Hover the chip to see who has what.
My Checkouts is the mechanic-facing list of every part currently in your possession. Tile is on the dashboard for everyone.
Stock Locations tracks WHICH warehouse each unit of stock lives in. Big Sky uses three: PBI, MLB, GRANT.
One location, WHOLESALE, is walled off from maintenance, it's the wholesale-only stock for BSAP. Only Owner and Grant parts users see it. See Wholesale & Hidden inventory.
Transfers moves stock between warehouses, and absorbs customer-supplied parts into BSA inventory.
When a customer brings a serviceable part to a WO and it gets used elsewhere, transfer it into BSA stock under a customer-credit. Recorded as a denial-reason if the customer later asks for it back.
Parts Requests is the tech-submitted requisition flow. Tech needs a part that isn't on the shelf, submits a request; parts admin approves and turns it into a PO.
The dashboard tile shows a count badge of requests awaiting your action.
BSAP is the wholesale parts arm. Separate Stripe account, separate invoice numbering (BSAP-YYYY-NNNN), separate dashboard.
BSAP-2026-0001… with the BSAP branding and bank details.Parts Sales is the BSAP-specific dashboard. Owner and Grant parts users only: admin is denied here, and the page returns 404 to make BSAP's existence private to anyone without access.
Cycle Counts runs spot inventory audits without shutting the shop. Pick N parts, count them, adjust, log the variance.
Best practice: 10-20 parts per cycle count, weekly. Catches shrinkage and miscount before the annual audit.
RMAs tracks parts you're returning to a vendor, wrong part shipped, defective, etc. The dashboard surfaces open RMAs so credits don't fall off the radar.
Core Search Requests is where techs and parts admins can ask the system to scan for a sourceable core internally before going to an outside vendor.
The search includes Wholesale, so a needed core might already be sitting in wholesale stock waiting to be re-routed to maintenance. Saves the shop hundreds when it hits.
Parts Manager rows surface data-quality issues as small chips so admin can fix them in-line.
Max Qty on a part caps reorder suggestions (so the dashboard doesn't auto-suggest 50 of a part you only need 5 of). Scrap fee auto-adds a per-WO disposal charge for hazmat / oil consumables, see My Shop → Default scrap fee.
Inventory Audit Log records every change to every stock_level in chronological order. Receive, consume, transfer, cycle-count, checkout, write-off, every event with who, when, before, after.
Filter by part, user, action type, or date range. CSV export for the annual audit binder.
Receiving Log is the chronological view of every parts-receiving event. Cross-references every line received against the PO and the WO (if linked).
Cleaner for FAA "show me what came in on 4/15" questions than scrolling through PO detail pages.
When a tech saves a note on a WO discrepancy, they re-enter their password. The system stamps name + cert + timestamp onto the note so it can serve as evidence of work performed.
You can't clock out of a WO unless you've saved at least one note on that WO during the punch. Forces a habit of documenting findings before walking away. Bypass: clock to Shop (indirect) instead of a WO.
When a tech clocks out of a WO, their labor hours push to the WO instantly. When admin later approves the time on the Time Clock Manager, the WO re-syncs with the approved (billable) hours.
If admin rejects (rare) or trims hours, the WO updates back to the trimmed total.
Big Sky services aircraft at every airport in Florida. Travel Baselines defines the expected drive time + miles to each airport. When a tech logs travel that significantly exceeds the baseline, the system auto-flags it for admin review.
A Parts Sale WO is a non-maintenance WO where Big Sky just sells parts (no labor, no airworthiness). Lower-touch than a full MX WO.
When you close a Non-MX Parts Sale WO, the system auto-generates the BSA Certificate of Conformity form, the document the customer needs for their records. Attaches to the WO Documents library automatically. No more hand-filling COCs.
Parts Sale WOs are the only WO type that can pull from Wholesale. Combined with Payee: bsap, this is the BSAP wholesale flow.
Time Clock Manager is the admin view for reviewing and approving time. Admin / Owner / Management only.
Admin approves time → labor on the WO updates to the approved hours (see Live labor sync). Approved-only is the default; admin rarely rejects.
For international customers, generating a standard invoice isn't enough, customs requires a commercial invoice with HTS codes, country of origin, and a value declaration.
Standard invoice still generates in parallel for the customer's accounting.
Tooling tracks every shared tool in the shop, calibrated and uncalibrated alike. Different from Tool Calibration: Cal tracks the gauge / wrench cal-due dates, Tooling tracks who has it right now.
2FA is admin-enrolled, SMS-based, mandatory for Owner and Admin accounts. Users can't turn it on or off themselves, only Admin / Owner can enroll or disable.
+15615550100).Normal password sign-in → second screen prompts for the SMS code. Code is valid for 5 minutes. Recovery codes can be used in place of an SMS code if the phone is lost.
Admin / Owner can disable 2FA on a user's account (e.g., phone lost permanently). They should re-enroll under a new number rather than leave it off long-term.
Users can sign in with their work Microsoft / Azure AD account instead of a JMGMT password. Alternative to (not replacement of) password sign-in.
SSO-signed users still hit the 2FA gate if they have 2FA enrolled. Most shops just rely on Microsoft's MFA at that point and turn off the JMGMT-side 2FA for SSO users, your call.
Every login attempt, success or failure, captures coarse geolocation (from the browser, with permission), IP address, and user agent. Visible on the Time Clock Manager → Login Locations card.
The geo permission is requested at the login page so it's there before sign-in. If the user denies geolocation, login still works, just no map pin.
JMGMT publishes /privacy.html and /terms.html as public pages, reachable without sign-in. They're linked from the login page footer and used by Twilio for A2P 10DLC SMS campaign registration.
Update text in the HTML files. Both pages cover JMGMT operationally + the specific SMS data-sharing language Twilio carriers require. Don't edit the "We do not sell, share, transfer…" mobile-number paragraph without re-registering the SMS campaign.
Multi View turns one browser window into a workspace of up to four panes, each pane a full, live section of the platform. Keep a work order open next to Parts Manager, or watch the Status Board while receiving against a PO, without juggling tabs or bouncing through the dashboard.
The workspace arranges itself automatically as you add panes: 1 pane fills the window, 2 sit side by side, 3 gives you two on top and one full-width below, 4 makes a 2×2 grid.
Each pane has a slim title bar with five controls:
Panes navigate like normal pages, click a row in Work Orders and that pane goes to the WO detail. The other panes don't move. Use the pane's ← Back (or the page's own Back button) to retrace your steps in that pane, or ⇄ Swap to jump straight back to the section picker. The browser's own Back button is deliberately kept out of pane navigation - it exits Multi View instead of moving panes around.
Multi View saves your panes, including where you navigated inside them, on this browser. Close the tab, come back tomorrow, open Multi View: your layout is restored. Opening via the ⊞ button puts the current page first and restores the rest of your last session after it.
Panes count as separate "editors" for the edit-lock system. Two panes on different records: totally fine. Open the same WO in two panes and the second gets the normal "currently editing" prompt with a View-Only option, exactly as if a coworker had it open. That's intentional: it protects your own unsaved edits from yourself.
Sign out from the Multi View header (or from inside any pane) and the whole window returns to the login page, panes are never left half-signed-in.
Two different "locked" states exist:
Almost always: at least one discrepancy is missing a resolution. Open each disc, fill in the resolution text, save. The button activates as soon as every unsigned disc has resolution text.
Other reasons: you don't have a signature or cert number on file (My Account), or you're a role that can't sign (Tech without an A&P / IA cert, Accountant always).
See Edit locks (multi-tech safety). Soft lock prevents two people overwriting each other's changes. Auto-expires after 30 minutes of inactivity.
Cmd / Ctrl + K: open global search anywhere in the app.Cmd / Ctrl + F on this guide: focus the search box at the top of the sidebar.Esc: close any open modal, or clear the guide search.Tab through any form: every input is keyboard-reachable.F: fullscreen the board for wall-mount displays.Any checkout open longer than 7 days gets an amber "Stale" tag on My Checkouts and shows up on the admin's Time Clock Manager → Stale Parts Checkouts card.
If the parts are still in your toolbox waiting on a job: ignore, the tag is informational. If you used them but didn't scan onto a WO: scan now, the auto-close will clear it. If you don't know where they are: tell admin so they can write it off rather than leave it open.
Multi View is desktop-only by design, splitting a tablet screen into 2-4 panes leaves each pane too narrow to work in safely (think: fat-fingering a parts quantity in a 300px pane).
Below 900px of screen width, the dashboard tile and the ⊞ header button are hidden, and /workspace.html shows a notice instead of panes. On a desktop, if the tile seems missing, your browser window is probably snapped to a narrow half-screen: widen it. Full guide: Multi View: your split-screen workspace.