Quick Start — Your First 30 Minutes

Sign in, load a project, convert a customer label specification into a standard, and download a signed, verifiable label package. Everything below produces real output from your own data.

This is the shortest path from a fresh sign-in to a branded label package you can hand to a customer. Budget about half an hour. Every step ends in something you can see, and the last one leaves you with a downloadable file and a public verification link.

You need one thing before you start: a fiber assignment spreadsheet for a real project, and ideally the label specification your customer gave you. If you would rather try the flow before committing your own data, ask your support contact for the sample pack.

Before you begin

Spanish is still under review. Some screens fall back to English and a few strings are wrong. Use English for production work in this release.

1. Sign in and change your password (0–4 min)

1. Open https://app.tsmartlabel.com and sign in with the email and temporary password you were sent.
2. Go to Settings → Security and set a password of your own. The temporary one was readable by whoever passed it to you, so treat this as part of signing in rather than something to do later.
3. Confirm your workspace name appears at the top of the left sidebar. If it says anything else, stop and contact support before loading data.

If you ever lose your password, use Forgot password? on the sign-in page. The link is good for 60 minutes and works once.

You should see: the Overview page, with counters for netbuilds, documents, open conflicts and evidence gaps, plus a map of your sites.

2. Get your bearings (4–7 min)

The left sidebar has two groups:

• Core — Studio, Labels, Documents, Output, Tables, Data, Inventory
• Fiber Ops — Netbuilds, Topology, Conflicts, Field Observations, Analytics, Visualization, Evidence Explorer, Gap Analysis

Press Ctrl+K (⌘K on Mac) anywhere to search netbuilds, sites, fibers and documents.

Two things float above the page: the feedback pill and the asset search pill. They can cover a button near the edge of the window — scroll slightly to reach anything underneath.

Navigate with the sidebar and in-app links rather than typing URLs. An unknown address renders an unstyled error page in this release.

3. Create a netbuild (7–11 min)

A netbuild is one construction scope — the unit everything else hangs off.

1. Netbuilds → New.
2. Use your real project code (for example N1014444) and a name your crew will recognise.
3. Save.

You should see: the new netbuild in the list. If it does not appear, reload before creating it again — the first save usually succeeded even when the list does not refresh.

Your plan allows 25 active netbuilds and 5,000 fibers per netbuild.

4. Upload your fiber assignment (11–16 min)

1. Open the netbuild and use Upload document.
2. Drop in your fiber assignment spreadsheet. DFSA scope and SOW .docx, OTDR .sor traces and site photos all belong here too, but the spreadsheet is what unlocks the next step.
3. Watch the status move UPLOADED → QUEUED → PARSING → PARSED.

FAILED almost always means an unexpected header row — fix the sheet and upload again.

The Documents list shows the most recent 500 documents per view in this release. Use the project selector to narrow it rather than scrolling.

You should see: at least one document at PARSED, and the netbuild’s span and fiber counts filled in.

5. Convert the customer’s label spec in Studio (16–23 min)

Conversion Studio turns a customer’s label specification into a machine-readable standard your team can produce against. It is a six-step wizard.

1. Studio → New Conversion. Fill in all five fields.

   If you fill the form from a saved template chip, the red validation messages may stay on screen even though the fields are correct. Click Create anyway.

2. Step 1 — Upload Label. Attach the customer’s label sample, or paste the label text into the box. Continue stays dim until one of the two is present, and pasted text needs at least 20 characters.

3. Step 2 — Generate Rules. The engine reads your sample and proposes naming rules.

4. Step 3 — Approve Rules. Accept or override each rule. This is the step worth slowing down on — everything downstream is produced from what you approve here.

5. Step 4 — Generate Template. The approved rules become a label template.

6. Step 5 — Submit for Review, then have a Project Manager Approve. Approval is what unlocks PDF and DOCX export; without it those buttons stay disabled.

7. Step 6 — Generate Labels.

You should see: the status badge reading Approved, a Quality Score on the preview, and a generated label set.

6. Download the package (23–29 min)

Go to Output. This is your download surface — Studio’s step 6 offers a shortcut with a narrower set of formats.

Download the PDF and the CSV. The PDF carries the corporate sheet and the ● powered by tsmartlabel · A Yupana Solution footer.

ZPL for Zebra and Brady printers is available on your plan through the export API rather than a button — ask support to set up a printer profile.

A successful PDF or DOCX export moves the conversion to Exported. Producing another formal export after that requires re-approval, so download everything you need in one go.

You should see: a real, branded label package on your disk.

7. Verify it (29–30 min)

Open the release verification link for the package you just produced. The verifier recomputes the SHA-256 hash and tells you whether the file matches what was signed.

You should see: a verdict of VERIFIED with a hash.

That link is public and needs no account, so you can send it to a customer as proof that the package they hold is the package you released.

Where to go next

The full guide for every screen is in the app under Usage Guide.

Known limitations in this release

Worth knowing before they surprise you:

• Gap Analysis totals are workspace-wide. The Span gaps and Fiber SOR gaps lists are correct; the large TOTAL FIBERS and MISSING SOR numbers above them are not scoped to the selected netbuild. Trust the lists.
• Some screens do not refresh after you add a record. Reload before creating it again — the first write usually succeeded.
• Site CLLI codes are not validated. They are 8 characters (for example BOISID96). A short code creates a site that shows as CLLI unresolved on the map permanently.
• OTDR PASS/FAIL is not scored automatically. Traces are stored and viewable, and sign-off is manual for now.
• The label design editor is incomplete. Font size and grid controls do not yet affect output. Choose an existing template rather than designing one.
• Field Observations rows are titled with an internal record ID, with the span, port and document on the second line. The summary counts above the list ignore your filters.
• If a draft profile sits at Pending, processing is queued. Contact support if it has not cleared within an hour.

Report anything else through the feedback button in the bottom-right corner — it captures the page you were on automatically.