Follow the steps and red lettered screenshots below. Some controls vary by installed version; confirm a send, purchase, license decision, or saved record in your app.

How to Use ScopeStamp — the complete guide

ScopeStamp for Windows · JE Horizon · updated 2026-09-27

Help center · Product page · Microsoft Store

1. What this app is

ScopeStamp is a Windows desktop app for small contractor offices that need to document work added after the original quote — the "extras" — and keep the evidence for that work beside the bill. You create a job (customer, original quote reference, scope, one currency), add line items for the extra labor and material, attach the photos, PDFs and exported customer messages your office already has, and see clearly which items still lack customer approval evidence before the bill goes out. When the packet is ready, you export a numbered PDF packet plus a CSV of the line items plus a file-hash manifest into a folder of your choosing.

The scenarios ScopeStamp is built for: a plumber reroutes a drain mid-job and the customer texts "go ahead"; an electrician wires an extra sub-panel and photographs the work; an office manager assembles the change-order packet before invoicing. The photos and the text were already on a phone — ScopeStamp gives them a home next to the exact dollar amount they support.

Everything runs locally on one Windows PC. Job data stays in a local workspace folder; nothing is uploaded automatically.

What this app is NOT

• It is NOT a signature service. The packet's status is an office record — not an electronic signature, not a legal approval determination. The app does not obtain approval for you.
• It is NOT an invoicing or payment system. It does not collect payment, send invoices, or process card payments. You document the work here, then bill through whatever you already use.
• It is NOT a phone app, a customer portal, or a dispatch/scheduling system. There is no phone app for crews.
• It is NOT an estimator. There is no AI, no auto-margin, no automatic receipt matching — amounts are what you enter.
• It is NOT cloud software. There is no cloud upload and no account required for the Free tier.

2. Before you start

What you need, at a glance:

Plans & pricing — copied exactly from the ScopeStamp site (jehorizon.com/scopestamp, verified 2026-09-27):

Free — $0

"The permanent Free tier covers one active job at a time with complete line-item documentation, evidence linking, and tamper-evident packet exports — no credit card, account, or time limit required."

• Complete approval, billing-record and export workflow
• One active job at a time; archive to start another
• No account, card or time limit — archived jobs stay readable and exportable

Pro — $1.99 / mo · $19.99 / yr (flat, zero per-seat)

The Store submission materials describe an optional Pro subscription through JE Horizon website checkout, with zero per-seat fees. Confirm the current purchase flow in the app before paying.

• Multiple/unlimited concurrent active jobs
• Existing active jobs remain usable if Pro ends
• Flat one price regardless of how many people touch the job — no per-tech pricing, no annual contract, no implementation fees

Pro is a subscription, not a one-time purchase. There is no account on the Free tier. The Store submission describes JE Horizon website checkout for Pro; if the in-app "Subscribe…" action does not open a checkout you can complete, ask support to verify the current purchase path before paying.

3. Install & first launch

1. Open the Microsoft Store on your PC (the Store app is built into Windows).
2. Search for ScopeStamp.
3. Click Get (or Install). The listing title is "ScopeStamp - Free download and install on Windows". You may be asked to sign in with your Microsoft account — that is the Store's sign-in, not a ScopeStamp account.
4. Wait for the download and install to finish, then click Open (or find ScopeStamp in the Start menu).
5. The app opens on the main window — a light background with the word ScopeStamp at the top-left of a grey side panel, and a mostly empty area to the right.

What you see on first launch is the empty state: a big heading "Start with the job you need to document" and the line "Select New job to add extra work and attach the files your office already has." Nothing is set up, nothing is registered, no account is created. You can start working immediately.

Reviewed product or Store capture. It shows the named control only; it does not prove that a later action completed.

4. Quick start

Your first win in about 10 minutes:

This gets a brand-new user from zero to a finished exported packet. Every button below is on the screen in front of you; the 🔴 marks the button to press at each step.

1. Click 🔴 "New job…" (lower-left side panel). A "New job" dialog opens.
2. Fill in the form: Customer label (required — something like "Demo Plumbing Co"), Quote / reference (optional — e.g. "Q-2026-0417"), Currency (pick the currency of the job), Original scope (what the original quote covered). Then click OK. The job appears in the job list on the left and its page opens on the right.
3. On the job page, click the "Extra work" tab (second tab). Click 🔴 "Add item…". In the "Line item" dialog choose a Category (labor / material / other), type a Description, a Quantity (default "1"), and a Unit price (for example 150.00 — decimals must match the currency), then click OK. Do this for each extra item.
4. Click the "Evidence" tab (third tab). Click 🔴 "Add files…" (or drag files onto the window) and pick the photos, PDFs or exported messages for this job. For each file a small "Attachment" dialog opens — set Authored by to customer for customer messages, type a Source label like "Customer: ok, go ahead", and click OK.
5. Go back to the "Extra work" tab, click a row to select an item, then click 🔴 "Link evidence…" and choose the attachment that backs that item. Link customer messages/documents to every item.
6. Watch the banner at the top of the page. When it says "Approval evidence missing: 0", click 🔴 "Verify approval (operator)" in the Packet actions row. This is your explicit "I checked the evidence" step. If it is refused, read the message — some item still lacks qualifying evidence (a photo alone never counts; see section 7).
7. When the state reads "Approval verified by operator" and the button "Record invoice reference…" lights up, click it and type the external invoice number (this records "billed").
8. Click 🔴 "Export packet (PDF + CSV + manifest)…" (wide teal button at the bottom). Choose a folder. The app writes three files (PDF + CSV + JSON). Read the Integrity check result before sharing anything. The published 0.1.9.0 build has returned PROBLEMS on a synthetic export; if you see that result, do not describe the packet as verified or send it as a verified packet. See section 5.10 and troubleshooting below.

5. The tour

Every screen, every button — in the order you meet them.

5.1 The main window — layout and navigation

The main window has two parts. On the left is a grey side rail; on the right is the working area that shows either the empty page or the page of the job you selected.

The side rail (from top to bottom): the ScopeStamp wordmark; the heading Jobs; a count line ("1 job" or "N jobs"); the job list (one entry per job — each shows the customer label and the currency in parentheses, e.g. "Demo Plumbing Co — 455 Acorn St (USD)"; an archived job adds " — Archived"); the "New job…" button (teal); the "Archive selected job" button; the "Reopen selected job" button; and a small license status line at the bottom.

At the very top of the window are two menus: Help (contains "Suggest a Feature…") and License (contains "Free and Pro access…").

Click a job in the list to open it. The right side switches to that job's page.

5.2 Create a job — the "New job" dialog

Click "New job…" in the side rail. A small "New job" dialog opens with four fields and OK / Cancel buttons.

Reviewed product or Store capture. It shows the named control only; it does not prove that a later action completed.

5.3 The job page — status line, review banner, amounts

Opening (or creating) a job shows its page on the right. From top to bottom: the job title (customer — quote reference); a grey state line ("State: … • Currency: … • Revision 1"); the review banner (a coloured panel); the amounts line ("Subtotal: … • Tax: … • Total: …"); the Packet actions row; the four tabs; and the wide teal "Export packet (PDF + CSV + manifest)…" button at the very bottom.

The review banner is the app's most important screen element. It states the approval status in one sentence, for example:

"Extra work: 4 items. Approval evidence missing: 1. Ready for billing review: 3."

Under it runs a next-action line such as "Review 1 item missing customer approval evidence before operator verification." When everything has qualifying evidence the banner turns green and reads "Extra work: N items. Approval evidence missing: 0. Ready for billing review: N."

The job page also carries a permanent note you should trust: "Internal status is not an authenticated electronic signature. Approval is only as good as the attached evidence."

Reviewed product or Store capture. It shows the named control only; it does not prove that a later action completed.

5.4 "Job & scope" tab — editing job details and the flat tax

This tab holds the same fields you entered when creating the job, plus one extra: the revision tax. The tax on this screen is a flat amount in the job currency (for example "45.00"), not a percentage — the app deliberately has no percentage engine.

5.5 "Extra work" tab — line items and linking evidence

This tab is where the money lives. The intro line says: "Add the work and amounts, then link evidence to each item that needs approval." The items table has seven columns: # (line number), Kind, Description, Qty, Unit price, Amount, Approval review.

The Approval review column color-codes each item: green "approval evidence linked" (or "operator verified" once verified) when qualifying customer evidence is linked; yellow "missing" when there is no qualifying approval evidence; "evidence only" when files are linked but none qualifies as approval.

Below the table: "Add item…", "Edit item…", "Remove item" (all Draft-only). Below that, the linked-evidence panel for the selected item: a status line, a list of linked attachments (double-click to open the file), and four buttons — "Link evidence…", "Add evidence files…", "Unlink selected evidence", "Open selected evidence" (these stay enabled through "Approval evidence attached").

The line-item dialog ("Line item" / "Edit line item"): choose Category (labor, material, other), Description (required), Quantity (default "1", up to 4 decimal places), and Unit price (in major units of the job currency — placeholder shows e.g. "12.50"; decimals must match the currency's minor units). The amount is quantity × unit price, rounded half-up to the smallest unit; click OK to add/update.

Reviewed product or Store capture. It shows the named control only; it does not prove that a later action completed.

Reviewed product or Store capture. It shows the named control only; it does not prove that a later action completed.

5.6 "Evidence" tab — importing and labeling files

The Evidence tab is the heart of the product. The hint at the top states the rules you will live by: "Drag JPG, PNG, PDF, or exported message files here. Original files stay untouched; ScopeStamp records a SHA-256 hash of each copy. A photo alone is never approval evidence; an employee note is never customer consent."

Import in three ways: drag files onto the table area, or click "Add files…" and pick them, or click "Add evidence files…" on the Extra work tab. For every imported file a small Attachment dialog opens (SHOT 7) asking you to label it.

The evidence table has seven columns: Source label, Kind, Author, Source note, Approval evidence? (YES/no), SHA-256 (first 16 characters shown), File. Below the table, the "Selected evidence" panel spells out the full story for the highlighted row: the source label, whether it qualifies as customer approval evidence (and why), which item numbers it is linked to, the original file name, the source note, and the full SHA-256.

🧠 SHA-256 (first use): a fingerprint computed from a file's exact bytes. Two files with different content get different fingerprints, so anyone can re-hash a file and prove whether its bytes changed since import.

The Attachment dialog (one per imported file): set Kind (photo / document / message / receipt), Authored by (customer / employee / supplier — defaults to employee, never pre-selects "customer"), Source label * (required; placeholder "Customer: ok, go ahead"), and Source note (optional). The dialog warns: "Approval evidence = customer-authored message/document. A photo alone or an employee note never counts as approval, whatever the label says."

Three hard facts about this dialog: (1) the Kind you pick must match what the file's bytes actually are — name it "message" and the bytes are a PNG, the import is refused; (2) only kind document or message with author customer can ever become approval evidence; (3) the source label is an office note, never a proof of identity.

Reviewed product or Store capture. It shows the named control only; it does not prove that a later action completed.

Reviewed product or Store capture. It shows the named control only; it does not prove that a later action completed.

5.7 Approvals & the state machine

Every packet moves through five states. The current state is always on the state line under the job title:

1. Draft — the packet is being assembled.
2. Sent (operator-reported) — you clicked "Mark sent (reported)"; you are telling the record the packet was sent to the customer.
3. Approval evidence attached — at least one qualifying customer message/document is attached.
4. Approval verified by operator — you clicked "Verify approval (operator)" after checking every item.
5. Billed (external invoice recorded) — you typed an external invoice reference.

The six Packet actions buttons and exactly when they work (greyed = refused in that state):

Three rules that protect the record: a photo is never approval — even a photo of a signed form; the operator must attach the actual customer-written message/document. Partial approval blocks verification — if any item lacks qualifying evidence, verification is refused and the banner keeps the honest count. Billed is terminal — once billed, the packet cannot be edited or moved back; to change anything you create a new revision.

If the button "Verify approval (operator)" is pressed while items are still missing, the app asks "Approval evidence missing for N item(s). Verification will be refused — attach customer messages/documents first and link them to every item. Continue?" — clicking Yes just shows the refusal; nothing is lost.

The invoice-reference dialog has the title "Record external invoice reference" and asks: "External invoice reference (required to mark billed):". Type your own invoice number (max 200 characters) and click OK. The state line changes to "Billed (external invoice recorded)".

Reviewed product or Store capture. It shows the named control only; it does not prove that a later action completed.

Reviewed product or Store capture. It shows the named control only; it does not prove that a later action completed.

5.8 Revisions — "Revise packet…"

A revision is a frozen snapshot of the packet. Clicking "Revise packet…" opens the "Revise packet" dialog, which explains the contract in its own words:

"Create revision N+1 from revision N? (Content is snapshotted; a new revision always starts as draft — approval is never carried over.) Operator note:"

Type an operator note (optional) and click OK. The new revision copies the items, attachments, links, scope, and tax, but it always starts as a Draft with zero approval recorded — a history event records that re-verification is required. The old revision is untouched.

Why this rule matters: "we approved revision 1" can never be stretched to cover a changed revision 2. Every version of the packet keeps its own approval status.

Reviewed product or Store capture. It shows the named control only; it does not prove that a later action completed.

5.9 "History & exports" tab — prior revisions and the export register

This tab keeps the audit trail. Intro line: "Open an earlier revision to inspect its original details. Earlier revisions are read only."

The revisions table lists every revision with columns Revision, State, Items, Missing approval, Invoice ref, Created (UTC). The exports tree lists every export ever made, grouped by revision, with columns Export file, Kind, SHA-256 — the file names follow the pattern <customer>-r<n>-<kind>-<timestamp>-<random>.<ext>, so no two exports can ever collide or overwrite.

The read-only revision viewer (title "Revision N — read only") shows the heading line with the revision's state, the note "Historical packet · Read only · Values and evidence as recorded for this revision", a details box (Customer, Quote/reference, Original scope, State, External invoice reference, Operator revision note), the amounts, the "Extra work and linked evidence" table (with a Linked evidence column), the "Evidence in this revision (select to open verified bytes)" table and detail line, a "Recorded exports" list when exports exist, and the buttons "Open selected evidence" and Close. Nothing in this dialog can be edited — that is the point.

Reviewed product or Store capture. It shows the named control only; it does not prove that a later action completed.

Reviewed product or Store capture. It shows the named control only; it does not prove that a later action completed.

5.10 Export the packet

Click "Export packet (PDF + CSV + manifest)…" (the wide teal button at the bottom of every job page). The app asks you to choose a folder ("Choose an explicit export folder"). Inside that folder it writes three brand-new files:

• <customer>-r<n>-packet-<timestamp>-<random>.pdf — the numbered packet ("Page X of Y"), with the job/quote/currency/invoice table, original scope, the approval banner, the extra-work amounts, the evidence behind each item (photos re-encoded, GPS stripped), the attachment register, and the printed note that internal status is not a signature. It opens on any machine with no ScopeStamp account.
• <customer>-r<n>-line-items-<timestamp>-<random>.csv — a deterministic CSV (UTF-8 with byte-order mark for Excel): revision_number, line_number, kind, description, quantity, unit_price_minor, unit_price, currency_code, amount_minor, amount, approval_status (operator_verified / approval_evidence_linked / evidence_only / no_evidence). Cells starting with spreadsheet-formula characters are neutralized.
• <customer>-r<n>-attachment-manifest-<timestamp>-<random>.json — the manifest: every attachment's original filename, source label, kind, author, approval status, byte count, SHA-256, and workspace path.

After writing, the app shows a confirmation box listing the three files plus an Integrity check line. An OK (missing 0, changed 0, invalid 0) result is the intended result when the files match the manifest. Every export is recorded in the exports table with its hash; the next export gets new file names and never touches the old ones.

Published-build release hold: the current Store 0.1.9.0 build reported PROBLEMS (missing 0, changed 0, invalid 1) on a second synthetic export, while an independent check of the same manifest found no invalid file. A source repair is staged but is not in the published build. Treat any PROBLEMS result as unresolved and do not tell the customer that integrity passed or advise sending the packet until a corrected Store build passes a fresh export test.

5.11 License / Pro window — "ScopeStamp Free and Pro"

Open it via License → "Free and Pro access…" in the menu bar. The dialog shows your current status message, an explanation note, a read-only Device request field ("share only with ScopeStamp support"), and four buttons: Subscribe…, Refresh subscription, Import signed license…, Close.

Free-plan behaviour: one active job at a time with the complete approval, billing-record and export workflow — no account, card, time limit or network call. If Pro ends later, jobs that are already active stay usable and editable; only creating or reopening jobs follows the Free capacity rule.

Reviewed product or Store capture. It shows the named control only; it does not prove that a later action completed.

5.12 In-app feedback — "Suggest a Feature…"

Open it via Help → "Suggest a Feature…". The dialog has Subject (placeholder "One line, what you would like added"), Description * (required — "What problem does it solve for you?"), Your email (optional — leave blank to stay anonymous), and a checked-by-default checkbox "Include system info: app name/version, Windows version, CPU architecture, time. No files, no paths, no job or customer data." The status line tells you where the local copy is saved. Buttons: "Send by email…", "Save copy…", Close.

Reviewed product or Store capture. It shows the named control only; it does not prove that a later action completed.

5.13 Archive & reopen — the Free-tier job cycle

When a job is finished, click "Archive selected job" in the side rail. The job stays in the list with " — Archived" after its name; you can still open it, read everything, view its history and export the packet — every edit button greys out. Archiving frees the active-job slot so you can create the next job on the Free tier.

To work on an archived job again, select it and click "Reopen selected job" (visible only for archived jobs). The store refuses reopening if no slot is free — on the Free tier that means zero other active jobs — and shows the message "Free allows one active job. Archive the current job or upgrade to Pro."

Reviewed product or Store capture. It shows the named control only; it does not prove that a later action completed.

6. What's supported

Platforms and formats

Feature per plan

Not yet available (honest list) — none of these exist in the current build, so do not look for them:

• Phone app, customer portal, crews logging in remotely
• Hosted e-signatures, and any claim that the packet is a legal or authenticated signature (in fact the app prints the opposite)
• Invoicing, payment collection or card processing, accounting/QuickBooks sync
• Automatic receipt-to-job matching and automatic margin/markup calculation
• Sending SMS or quoting by text (the app only imports exported messages)
• Cloud upload, cloud backup or any automatic sync (data stays local by design)
• Per-seat plans of any kind (there are no user tiers even on Pro)

7. Edge cases & gotchas

1. Symptom: a photo of a signed form doesn't approve the item. Why: the honesty engine allows only customer-authored messages or documents (real text/PDF bytes) as approval evidence; a photo is never approval — whatever its label says, even a photo of a signed form. What to do: attach the actual written acceptance (a scan/PDF of the signed document, or the exported message) with author customer, link it, then verify.

2. Symptom: an employee note or supplier receipt doesn't count as approval. Why: kind message/document with author customer is the only combination that qualifies; employee and supplier material is filed as evidence but can never authorise an item. What to do: label files truthfully — the dropdown cannot override the rule, and choosing a wrong kind for the bytes is refused outright.

3. Symptom: "Verify approval (operator)" is refused, or verification is blocked. Why: the guard requires EVERY extra-work item to have linked qualifying evidence — partial approval is never enough. What to do: read the banner ("Approval evidence missing: M"), open each missing item via "Review missing item", link a customer message/document to each, then verify again.

4. Symptom: after billing you cannot edit anything, and "Return to draft" is refused. Why: billed is terminal by design — the record must not be silently changed after the fact. What to do: click "Revise packet…" to create a new draft revision; the old billed revision stays frozen and readable.

5. Symptom: the new revision shows approval as missing again after you approved revision 1. Why: revisions never inherit approval — a new revision always starts as Draft and requires fresh evidence review and a fresh verify step. This is deliberate. What to do: re-check the linked evidence and verify again; every old revision keeps its original approval status.

6. Symptom: exporting twice produces four files, not an overwrite. Why: every export is a brand-new file (<customer>-r<n>-<kind>-<utc>-<random>.<ext>) and the old one is never touched. What to do: nothing — this is the guarantee. The exports tree in "History & exports" lists every file with its hash so "which PDF is current" is always answerable.

7. Symptom: "12.5" is refused when the job currency is JPY (or any 0-decimal currency). Why: currency decimals are looked up, never assumed — JPY has 0 decimals, KWD has 3, and a price with the wrong number of decimals is refused rather than quietly rounded. What to do: enter whole amounts for 0-decimal currencies (12, not 12.5) and three decimals for KWD-style currencies; unknown currency codes are refused too.

8. Symptom: the Currency dropdown shows AED when you open "New job". Why: the list is alphabetical, so it does not default to USD. What to do: always set the currency before saving; a job's currency can never be changed after line items exist (mixed currencies are structurally impossible).

9. Symptom: the total shows "OVER LIMIT". Why: safety caps — unit price ≤ 1×10¹² minor units, line amount ≤ 1×10¹⁵, packet total ≤ 1×10¹⁵, quantity ≤ 4 decimal places. The app renders "OVER LIMIT" instead of fabricating a figure. What to do: check your quantities/prices; a number is never invented.

10. Symptom: "New job…" is greyed out and archiving is required. Why: the Free tier allows one active job at a time. What to do: click "Archive selected job" on the finished job (data stays readable/exportable), then create the next job — or upgrade to Pro for multiple concurrent active jobs.

11. Symptom: a Pro subscription ended and you worry about your data. Why: Pro-expiry grandfathering means existing active jobs remain usable and editable — only creating or reopening jobs follows the Free capacity rule. What to do: keep working; archives and exports stay intact; subscribe again only if you need new concurrent jobs.

12. Symptom: you cannot find your data / you want a backup. Why: everything lives in one local SQLite workspace: %LOCALAPPDATA%\JE Horizon\ScopeStamp\workspace (the folder contains scopestamp.db plus the attachments/ store). What to do: to back up, copy that whole folder while the app is closed; nothing is uploaded anywhere, and exporting the packet to your own folder is the standard way to share.

13. Symptom: the exported PDF's photos have no GPS. Why: derived report images are re-encoded with ALL metadata (GPS included) stripped by default; the originals on your drive stay untouched. What to do: nothing — that is the privacy rule. The manifest hashes always refer to the preserved originals.

14. Symptom: importing a file is refused with a media-class message. Why: the app sniffs the file's bytes, not the name — a PNG cannot be recorded as kind message or document (a picture is never an exported message), and files over 50 MiB, binaries, or unsupported extensions are refused. What to do: export the message as TXT/EML/HTML/JSON/MD or scan the document as PDF, then import.

15. Symptom: an HTML/EML message opens as boring plain text, not a web page. Why: by design, text/HTML/JSON message evidence opens in an in-app read-only text viewer (first 1 MiB) so remote images or links embedded in the export can never load. What to do: read the text; the stored bytes are unchanged. Photos and PDFs open in the normal Windows viewers.

16. Symptom: closing the app mid-task loses your work. Why: each form saves only when you click its save/OK button — the Line item, Attachment, New job and invoice dialogs commit on OK, and the Job & scope fields commit on "Save job details". What to do: commit early and often; already-created jobs and their saved records persist across restarts (the data is in the local database).

17. Symptom: an archived job's edit buttons are all grey. Why: archives are read-only by design (still fully exportable). What to do: "Reopen selected job" when a slot is free; mutations on archived jobs are refused with "This job is archived. Reopen it before changing the packet."

18. Symptom: the app says it can't open your mail app for a suggestion. Why: ScopeStamp hands a mailto draft to the OS; if no mail handler is registered it reports honestly ("your mail app did not open … Nothing was sent"). What to do: use "Save copy…" and attach the .txt to an email yourself, or write directly to [email protected].

8. Troubleshooting

The app won't install or won't open. 1. Confirm your PC is Windows 10 or 11 (64-bit) and you are signed into the Microsoft Store with a Microsoft account. 2. Reinstall from the Store: search "ScopeStamp", click Get. 3. If it installed but won't start, restart the PC and try again. 4. If it still fails, note the exact error and app version shown on your PC, then write to [email protected] with the text of the error.

The "New job…" button is greyed out. 1. Look at the license line at the bottom of the side rail. 2. On Free, one active job is the limit — select the active job in the list and click "Archive selected job", then try "New job…" again. 3. If you want concurrent jobs, open License → "Free and Pro access…" and subscribe.

A button you expect is missing or greyed. 1. Read the state line: each Packet action is enabled only in the states listed in section 5.7. 2. Items/evidence edits need Draft (content) or up to "Approval evidence attached" (evidence). 3. If the job is archived, edit buttons are intentionally off; reopen it or export instead.

Verification is blocked / "Verification will be refused". 1. Note the banner's "Approval evidence missing: M". 2. Click "Review missing item", select the item, open its linked evidence, and confirm the file is a customer-authored message/document (author customer). 3. Link qualifying evidence to every item, then click "Verify approval (operator)" again.

The invoice/reference step won't complete. 1. "Record invoice reference…" is enabled only in state "Approval verified by operator" — verify first. 2. The reference cannot be empty and is capped at 200 characters.

Export produces a warning or "Integrity check: PROBLEMS". 1. The three files were still written — the check re-hashes the stored attachments against the fresh manifest. 2. A missing or changed result can indicate that a stored copy was deleted or altered. The current published build has also reported invalid 1 on a synthetic export whose manifest passed an independent check, so do not assume every invalid result proves a bad source file. 3. Preserve the files and result, do not send the packet as verified, and contact support. If a source file really is missing or changed, restore the workspace from backup (section 7 entry 12) or re-import the original before exporting again.

The totals look wrong. 1. Tax is a flat operator-entered amount per revision — not a percentage; check the "Revision tax (flat amount)" field. 2. Amounts are quantity × unit price in the job currency, rounded half-up to the smallest unit; if a value is refused, check the currency's decimal rule (entry 7 in section 7). 3. "OVER LIMIT" means a safety cap was hit; correct the numbers, no fabricated total is shown.

Subscribe / refresh behaves unexpectedly. 1. "Subscribe…" opens the JE Horizon checkout in your default browser and needs internet. 2. After checkout, click "Refresh subscription" — the app then contacts the claim endpoint once; possible honest messages: "Payment is still being confirmed…", "This checkout pairing was not found…", "Pro is inactive…", or "Subscription status is temporarily unavailable…". None of those delete your jobs. 3. If checkout never opens or you cannot complete it, contact support — the checkout flow was being finalized at guide-writing time.

A license file says "This license belongs to another computer" or "could not be verified". 1. Pro is device-bound; the file was issued for a different machine. 2. Check your Windows date and time (a clock rollback also blocks verification). 3. Download a fresh license from your account and import it via "Import signed license…".

The app seems stuck on a screen. 1. Check for an open dialog behind the window (message boxes, the "Record external invoice reference" input). 2. Every write is committed to the local database immediately; restarting the app cannot corrupt the packet. 3. If a window truly freezes, close the app from the taskbar and reopen — the workspace is safe.

9. FAQ

Common questions:

I don't see the "Verify approval (operator)" button. The Packet actions row is on every job page, but buttons grey out by state. If verification is not allowed yet, the banner shows how many items are still missing approval evidence — link customer messages/documents to all of them first.

Can I undo that? Currently only by editing while in Draft: "Return to draft" moves linked evidence back up to Draft only from non-billed states, and once billed the only way to change the packet is "Revise packet…" (a new draft revision). There is no general undo history; remove-item and unlink actions are immediate.

Where is my data saved? In one local workspace: %LOCALAPPDATA%\JE Horizon\ScopeStamp\workspace (database scopestamp.db plus the attachments/ store). Back it up by copying that folder while the app is closed. Nothing is uploaded automatically.

Will this touch my files? Your originals are never modified, moved or deleted. Imported files are COPIED into the workspace, hashed, and the originals are left exactly as they were. Even the exported packet strips GPS from photos — but only from the derived copies, never from your originals.

Do I need to pay? No. The permanent Free tier does the complete workflow — one active job at a time, no card, no account, no time limit. Pro ($1.99/mo or $19.99/yr) only adds multiple concurrent active jobs.

Can I use it offline? Yes. Free-tier work, evidence, history and exports are fully local — no network call at all. Only the optional Pro actions (subscribe, refresh subscription) and the Store download itself need internet.

What happens if I close it mid-task? Anything already saved (a created job, added items, imported evidence, exports) stays in the local database. Only unfinished forms are lost — a dialog you had not clicked OK/Save on. Commit early and often.

Does ScopeStamp approve my change orders for me? No. The app shows what is missing and lets you record that an operator verified the evidence; a photo or staff note never counts by itself, and the packet states it is an office record, not an electronic signature or legal determination.

Can the customer open my PDF without the app? Yes — the packet is a standard numbered PDF that opens in any PDF reader, with no ScopeStamp account needed. The CSV and manifest ride alongside it.

Will my old revision be overwritten? Never. Every revision and every export stays available; new revisions start as drafts, and exports are always new files.

10. Privacy & data

The claims below are the app's own, copied from the ScopeStamp site and build documentation (verified 2026-09-27).

• "One local workspace. Nothing is uploaded automatically." Job data never leaves the machine unless you export it. There is no cloud-upload path and no network code in the core.
• "Job data is not automatically uploaded. File checks and packets are local by design; any optional Pro licensing check is an explicit, user-initiated action." The only network request in the app is the subscription refresh, triggered by you, which sends device-pairing data only — never customer, job, attachment or evidence content.
• Originals stay untouched. Imported files are copied into the local workspace; the source files (the crew's photos, the exported text) are never modified, moved or deleted.
• GPS/EXIF is stripped from packet images by default. Photos embedded in the exported PDF are re-encoded and all metadata — GPS included — is dropped. Originals keep their metadata.
• Feedback is honest and minimal. If you use "Suggest a Feature…", the volunteered system info is only app name/version, OS/arch and a UTC timestamp — deliberately no file paths, no job or customer content, no license keys, no network state. The app writes the request to a local state database and only ever hands a draft to your own mail app; it never claims it sent anything.
• No AI, no GPU, no third-party data processing. Everything runs locally on the office PC.

11. Getting help

• Support email: [email protected]
• Support page: https://jehorizon.com/support/ — help articles at https://jehorizon.com/help/#scopestamp
• Feature requests: [email protected] (or use Help → "Suggest a Feature…" in the app — it saves a local copy and opens a pre-filled draft for you); general feedback goes to [email protected]
• When you write in, include: which app (ScopeStamp), the Windows version, what you clicked and what happened, and any exact error text. To attach system info without emailing anything from inside the app: open Help → "Suggest a Feature…", leave the diagnostics checkbox ticked, click "Save copy…", and attach the saved .txt to your message. If support asks for your device pairing, it is shown under License → "Free and Pro access…" (Device request field).

Back to guide contents