Scout Manual

1. Know the account and scope before starting

• Individual Scout: use reports, notes, watchlists, unrostered prospects, and evaluation links for the sport assigned to the account.
• Single-Team access: work in one team’s roster, schedule, statistics, lineup, reports, and Game Prep context. This is a team role, not an unrestricted individual-scout account.
• Organization access: move between only the teams and seasons assigned by an organization owner or administrator.

1. Confirm the invitation or plan uses the exact email you will sign in with.
2. Finish email verification and password setup if prompted.
3. Ask the owner which sport, team, season, and role you should see.
4. Use a current browser with cookies and local storage enabled for the Kaish domain.

2. Sign in and verify the workspace

1. Open Scout Sign In and enter the assigned email and password.
2. Wait for the access check to finish and confirm the expected plan or trial belongs to the signed-in identity.
3. If more than one workspace is available, select the intended personal, team, or organization workspace.
4. Check the workspace name, sport, visible teams, and current season before entering data.
5. Open the dashboard and confirm that its next actions match your job.

A familiar email does not prove the correct role. If you can see the wrong team—or cannot see a team you expect—stop and ask an owner to verify membership rather than recreating data in another workspace.

3. Use the dashboard as the starting point

The dashboard summarizes recent reports, watchlist work, and available workflow entry points. Use it to continue current work, then return to the relevant player, game, or team record rather than making duplicate entries.

1. Review recent activity for the correct workspace and season.
2. Use the player or report entry point that matches the task.
3. Filter or search the current list before creating a new player record.
4. Confirm the player identity, team, and season before writing an evaluation.

The dashboard does not expand your access. Missing teams, sports, or tools normally indicate the selected workspace, assigned role, plan, or trial state.

4. Find the player before creating anything

1. Search by the player’s current name and use available sport, team, season, or position filters.
2. Compare roster context and other identifiers before choosing a result.
3. Open the existing player profile when it is the same person.
4. Create a new or unrostered prospect only when the player does not already exist in the permitted scope.
5. Keep spelling and identifiers consistent so reports stay attached to one record.

If two records appear to be the same player, do not delete or overwrite one casually. Record the two identifiers and ask an administrator to review the duplicate while preserving both histories.

5. Write an evaluation or report

1. Open the verified player profile or start from the intended game/team context.
2. Choose the correct report or evaluation type for the sport.
3. Enter observations in the appropriate fields instead of combining unrelated subjects in one note.
4. Add ratings or structured fields only when you can support them with the observation.
5. Check player, team, opponent, date, event, position, and season context.
6. Save, reopen, and verify the report before sharing or moving on.

Use factual language for observed actions and clearly separate it from projection or opinion. Avoid medical, disciplinary, or other sensitive claims unless your organization has an approved process for them.

6. Use notes, tracking, and watchlists deliberately

• Notes: capture a dated observation that should remain with the player context.
• Watchlists: group players who need continued attention; keep list names specific enough to avoid mistaken sharing.
• Player tracking: use consistent status and follow-up conventions across evaluators.
• Reports: use a structured evaluation when the observation should become a formal scouting record.

1. Choose the existing watchlist or create one with a clear purpose and season.
2. Add the verified player record.
3. Include the next action or reason in the available note/status fields.
4. Review old items on a regular schedule and remove only after confirming the organization no longer needs them.

7. Prepare a roster, lineup, or game

Single-Team and Organization roles may include team preparation tools. The visible tools depend on the assigned plan and role.

1. Confirm the team and season shown in the header or selector.
2. Open the roster and verify player names, numbers, positions, and active status.
3. Create or open the intended game and confirm opponent, date, and location.
4. Build the lineup, units, or formation using the sport-specific layout.
5. Review unavailable players and duplicate assignments.
6. Preview the lineup or Game Prep output before sharing.

Never create a second team merely because a roster is missing. First check workspace, season, permissions, and filters. Team records created in the wrong scope can fragment player and report history.

8. Move between teams without mixing data

1. Use the organization’s team selector rather than changing browser accounts.
2. Verify team and season after every switch.
3. Keep team-specific notes, lineups, and games inside that team’s context.
4. Use organization-wide views only when the assigned role permits them.
5. Before copying or sharing a report across teams, verify that the source and destination are authorized.

9. Verify before sharing an evaluation or lineup

1. Open the final report, public evaluation, or lineup preview.
2. Confirm it shows the intended player/team and no private draft notes.
3. Check who can open the link and whether an expiration or audience control is available.
4. Share the smallest appropriate scope.
5. Open the result in a private browser window or with a test recipient before sending widely.

Available share and export controls vary by plan and role. If the current interface does not show a control, do not work around access with screenshots or copied private data; ask the workspace owner.

10. Keep records durable and recoverable

• Save before leaving a long report or changing workspace.
• Keep source notes or approved scouting documents according to the organization’s retention policy.
• Do not treat browser history as a backup.
• Do not export or download more player data than the recipient needs.
• When a page looks stale, refresh once and verify the workspace before re-entering information.

If a save appears to fail, copy unsaved text to a temporary private note before refreshing, record the exact error, and verify whether a new or updated record exists. Avoid clicking Save repeatedly if that could create duplicates.

11. Run a short readiness check

1. Sign in with the exact role you will use.
2. Confirm the correct workspace, sport, team, and season.
3. Find a known player without creating a duplicate.
4. Create a clearly labeled test note or report, save it, and reopen it.
5. Add that player to a test watchlist and verify the entry persists.
6. For team roles, open the roster and preview a lineup without publishing it.
7. If sharing is part of the role, verify one approved test link and then remove or expire it.
8. Delete only the test content you created and only when the role offers a safe delete action.

12. Fix the boundary that failed

13. Know the access boundaries

• Plan names, prices, and exact role permissions can change; the signed-in product and current pricing page are authoritative.
• Main Kaish and Scout use separate login and entitlement paths, and Hockey remains separate.
• A Team or Elite description that includes Scout does not confirm the Scout account is ready; sign in to Scout directly.
• Search covers the records and fields exposed by the current Scout interface; it is not video, audio, or OCR search.
• Public sharing should not be treated as a private data vault.
• Features visible to an owner may be intentionally unavailable to members or evaluators.

Go deeper