Learn the workspace, connect the tools you need, and complete one classification with your onboarding lead.
The finish line
You can find the right queue, follow the run in My Work, review the evidence, and show your lead the final result or exact stopping point.
Progress is saved in this browser.
Learn the workspace, connect the tools you need, and complete one classification with your onboarding lead.
The finish line
You can find the right queue, follow the run in My Work, review the evidence, and show your lead the final result or exact stopping point.
Progress is saved in this browser.
Longhand at a glance
Longhand is the desktop app where you start approved classification work, follow each run, and review results before they continue.
01
Shared work that is waiting to be started. Your lead tells you which queue to use.
02
The runs you have started and the current state of each one.
03
The evidence and field-level controls you use when a run needs your decision.
How analyst work moves
Longhand tracks the run. You check the evidence and decide whether the result can continue.
Stage 1
Shared work that is ready to start. Use only the queue your lead approves.
Stage 2
The runs you started, grouped by Running, Failed, Needs Review, and Done.
Stage 3
Where you check each field against its evidence and record corrections.
Stage 4
The destination for a reviewed result when submission is allowed.
The onboarding stop rule: do not start a batch until your lead names the practice queue, and do not submit a record whose evidence does not support your decision.
What you'll be able to do
Sign in to the LegitScript workspace
Connect Google Workspace and the Browser Agent
Find My Work and the Classification queues
Start only the queue your lead approves
Review each field against its evidence
Record the outcome or the exact point where work stopped
This is a guided first run, not a full tour of Longhand. The goal is to complete the basic setup and know what to do when a run needs your attention.
The guide
Step 1 of 10 · 3 min
Confirm the account, queue, and stopping point for your first session.
The invitation is tied to one email address. Before you open Longhand, confirm the account you will use, the practice queue, and where the first run should stop.
Do this
Remember: Do not use a personal email or a different work alias. Longhand accepts the pending organization invitation when the invited identity signs in.
What you leave with
Step 1 checkpoint
Practice evidence target
You can name the invited work email, the designated practice queue, the person supervising the session, and the approved stopping point for the first run.
Recording this checkpoint saves self-reported lesson practice in this browser. It is not evidence of certified competency; certification requires a separately submitted artifact and qualified human evaluation.
Step 2 of 10 · 5 min
Open Longhand from the invitation. Use the download page only if the app is not installed.
The invitation opens the desktop app and carries the sign-in context with it. If Longhand is not installed, download it, then return to the invitation.
Do this
Installation paths
| Platform | Install | Open from |
|---|---|---|
| macOS | Open the downloaded disk image and install Longhand | Applications |
| Windows | Run the downloaded installer | Start menu |
Step 2 of 10 · 5 min
Open Longhand from the invitation. Use the download page only if the app is not installed.
Do this
Step 2 checkpoint
Practice evidence target
Longhand opens as a desktop app on your computer, and clicking the invitation's Open Longhand button brings the app to the foreground.
Recording this checkpoint saves self-reported lesson practice in this browser. It is not evidence of certified competency; certification requires a separately submitted artifact and qualified human evaluation.
Step 3 of 10 · 5 min
Sign in with the same work email that received the invitation.
LegitScript has already set up the workspace for you. Signing in with the invited email connects this installation to the right organization.
Do this
Remember: Do not paste a LegitScript, Anthropic, OpenAI, or other organization secret into the app. LegitScript access comes from your signed-in workspace.
What each outcome means
| What you see | What to do |
|---|---|
| Home with the LegitScript experience | Continue to the workspace check. |
| A browser sign-in loop | Stop and capture the exact browser or app message. |
| The general Connect an AI Provider wizard | Do not add a personal key; stop and contact your onboarding lead. |
| A different organization | Stop. Confirm the invited email before trying again. |
Step 3 of 10 · 5 min
Sign in with the same work email that received the invitation.
Do this
Step 3 checkpoint
Practice evidence target
The sign-in finishes, Longhand returns to Home, and you are not being asked to configure a personal AI provider as part of a general first-run wizard.
Recording this checkpoint saves self-reported lesson practice in this browser. It is not evidence of certified competency; certification requires a separately submitted artifact and qualified human evaluation.
Step 4 of 10 · 5 min
Connect the approved work account Longhand will use during onboarding.
Longhand uses this connection to work with Gmail, Calendar, Drive, Sheets, and Docs. Set it up now so your first workflow doesn't stop when it needs a Google tool or open the wrong account.
Do this
Remember: Not sure which account to use? Stop and ask your onboarding lead. Don't connect a personal account or guess.
Make sure the right account is connected
| Expected | Stop signal |
|---|---|
| The work Google account your lead approved | A personal account or another work identity |
| Google Workspace says Connected | Sign-in required, disconnected, or authorization error |
| All five Google services are listed | A service is missing after Test Connection |
Step 4 of 10 · 5 min
Connect the approved work account Longhand will use during onboarding.
Do this
Step 4 checkpoint
Practice evidence target
Google Workspace shows Connected in Settings → Tools. Test Connection also succeeds for the approved work account.
Recording this checkpoint saves self-reported lesson practice in this browser. It is not evidence of certified competency; certification requires a separately submitted artifact and qualified human evaluation.
Step 5 of 10 · 7 min
Install the Longhand Agent Chrome extension, then make sure Longhand can see it.
The Browser Agent lets Longhand work on approved sites you're already signed into. Chrome provides the connection. Longhand keeps the approvals and allowed-site rules.
Do this
Remember: Connected doesn't mean every site is available. LegitScript manages the pre-approved domains. Only add another site through the approved onboarding process.
Make sure Chrome and Longhand are connected
| Expected | Stop signal |
|---|---|
| Chrome and Longhand are open on the same computer | Another browser, phone, or computer |
| The Extension card says Connected | Disconnected or still waiting after install |
| Approvals stay in Longhand | A browser prompt asks you to widen access outside the approved flow |
Step 5 of 10 · 7 min
Install the Longhand Agent Chrome extension, then make sure Longhand can see it.
Do this
Step 5 checkpoint
Practice evidence target
Settings → Browser Agent shows Connected. You can also explain the rule: approvals happen in Longhand, and the agent only works on approved domains.
Recording this checkpoint saves self-reported lesson practice in this browser. It is not evidence of certified competency; certification requires a separately submitted artifact and qualified human evaluation.
Step 6 of 10 · 4 min
Confirm you're in the LegitScript analyst view before starting work.
You can sign in successfully and still be in the wrong organization or view. Check the branding, My Work, and Classification queues before you start.
Do this
Workspace acceptance check
| Expected | Stop signal |
|---|---|
| LegitScript wordmark and dark-blue accent | Stock Longhand branding only |
| Agents navigation | A generic Projects-first workspace |
| My Work above Classification queues | Either surface missing |
| No personal organization secret requested | A request for a LegitScript or team API key |
Step 6 of 10 · 4 min
Confirm you're in the LegitScript analyst view before starting work.
Do this
Step 6 checkpoint
Practice evidence target
You can point to the LegitScript brand, the My Work board, and the Classification queues in the Analyst view.
Recording this checkpoint saves self-reported lesson practice in this browser. It is not evidence of certified competency; certification requires a separately submitted artifact and qualified human evaluation.
Step 7 of 10 · 5 min
Know where new work appears and where to follow the runs you started.
Classification queues show shared work that's ready to start. My Work shows the runs you've started and whether each one is Running, Failed, Needs Review, or Done.
Do this
Where each action happens
| Surface or state | Meaning | Your next action |
|---|---|---|
| Classification queues | Shared work available to the team | Start only the queue your lead approved |
| Running | Longhand is executing the workflow | Let it run; inspect only if it stalls |
| Needs Review | The run is deliberately waiting on a person | Open the review console |
| Failed | The run stopped before completion | Read the cause before retry or re-drive |
| Done | The run reached its terminal result | Verify the supervised outcome, then clear only if appropriate |
Step 7 checkpoint
Practice evidence target
Given any item on screen, you can say whether it is waiting to start, running, waiting on your judgement, failed, or finished. You can also say which surface owns the next action.
Recording this checkpoint saves self-reported lesson practice in this browser. It is not evidence of certified competency; certification requires a separately submitted artifact and qualified human evaluation.
Step 8 of 10 · 8 min
Take the next items from the queue your lead approved.
Starting from a queue takes the next available items and adds the runs to My Work. You don't need to select or start each record one at a time.
Do this
Remember: This is the first action that starts real processing and may eventually write to the LegitScript database. Do not perform it unsupervised during onboarding.
What happens when you start a batch
| You do | Longhand does |
|---|---|
| Choose the approved queue | Takes work only from that queue |
| Click the queue's Start next N button once | Claims up to the number shown and avoids duplicate work |
| Keep the app open | Starts the matching runs |
| Watch My Work | Shows the current state of each run |
Step 8 of 10 · 8 min
Take the next items from the queue your lead approved.
Do this
Step 8 checkpoint
Practice evidence target
One authorized click on the designated queue creates the expected runs in My Work, with no duplicate manual starts and no work taken from a different queue.
Recording this checkpoint saves self-reported lesson practice in this browser. It is not evidence of certified competency; certification requires a separately submitted artifact and qualified human evaluation.
Step 9 of 10 · 12 min
Check each field against the evidence before the run continues.
Longhand pauses a run in Needs Review so you can check each field. Your decision and any correction are recorded before the workflow continues.
Do this
Remember: Submitting the review lets the workflow continue toward the LegitScript database. A quick skim doesn't count as a completed review.
Review decisions
| Decision | Use it when | Required follow-through |
|---|---|---|
| Correct | The evidence supports the proposed value | No edit; continue to the next field |
| Incorrect | The proposed value is wrong or incomplete | Enter the corrected value or missing detail |
| Stop and escalate | The evidence is missing, conflicting, or outside your authority | Do not guess or submit; capture the record and question |
Step 9 of 10 · 12 min
Check each field against the evidence before the run continues.
Do this
Step 9 checkpoint
Practice evidence target
You complete one field-by-field review using the evidence, record any necessary correction, and submit only after every displayed field has been deliberately checked.
Recording this checkpoint saves self-reported lesson practice in this browser. It is not evidence of certified competency; certification requires a separately submitted artifact and qualified human evaluation.
Step 10 of 10 · 5 min
Confirm the final state and give your lead a clear handoff.
A Done run gives you the expected result. A Failed run gives you a reason to investigate. In either case, record the final state and give your lead enough information to approve the next step.
Do this
Recovery rule
| State | Safe response |
|---|---|
| Done | Record the result and ask for sign-off |
| Needs Review | Finish or escalate the field-level decision |
| Failed with a clear transient cause | Retry only with lead approval |
| Failed because the run no longer owns its item | Use Re-drive when the app offers it |
| Unknown or repeated failure | Stop; send the exact state, run, and error |
Step 10 of 10 · 5 min
Confirm the final state and give your lead a clear handoff.
Do this
Step 10 of 10 · Final check
Check each item as you finish it. Your progress is saved in this browser.
0 of 8 complete
Finish the checklist with your onboarding lead before you begin independent queue work.
Step 10 checkpoint
Practice evidence target
Your onboarding lead receives the workspace evidence, practice run, final state, review status, and any exact error. Your lead then approves the next step or assigns one.
Recording this checkpoint saves self-reported lesson practice in this browser. It is not evidence of certified competency; certification requires a separately submitted artifact and qualified human evaluation.