wiki content export 2026-03-24
This commit is contained in:
parent
8549cb0252
commit
f5a69b8683
97 changed files with 4918 additions and 393 deletions
57
content/wiki/hub/reviewer/00-your-dashboard.md
Normal file
57
content/wiki/hub/reviewer/00-your-dashboard.md
Normal file
|
|
@ -0,0 +1,57 @@
|
|||
# Your Dashboard
|
||||
|
||||
The **My Reviews** dashboard is your home base. It shows every application assigned to you, organized by urgency so the most important items surface first.
|
||||
|
||||
## Getting There
|
||||
|
||||
Click **My Reviews** in the top navigation bar. This takes you to `/reviews`. A badge on the nav link shows how many assignments need your attention.
|
||||
|
||||
## Card Grid Layout
|
||||
|
||||
Active assignments appear as a card grid -- one, two, or three columns depending on your screen width. If you have assignments across multiple cohorts, cards are grouped under cohort headers. When you only have one cohort, the header is suppressed.
|
||||
|
||||
Each card shows:
|
||||
|
||||
- **Studio name** -- the applicant's studio or team name
|
||||
- **Progress bar** -- small block indicators showing how far through the review stages this application has progressed
|
||||
- **Stage name** -- which stage this assignment belongs to (e.g., "1st Interview", "2nd Interview"), plus the interview date if applicable
|
||||
- **Status text** -- contextual information like "In progress" for drafts, "View only" for read-only assignments, or pipeline status
|
||||
- **Action button** -- the primary action available to you
|
||||
|
||||
## How Cards Are Sorted
|
||||
|
||||
Cards are sorted by urgency, not alphabetically. The order is:
|
||||
|
||||
1. **Overdue** -- interview stages past their due date (shown in red)
|
||||
2. **In progress** -- reviews you have started but not submitted (drafts)
|
||||
3. **Ready to score** -- non-interview stages waiting for your input
|
||||
4. **Post-interview ready** -- interview stages where the interview has already occurred
|
||||
5. **Scheduled** -- upcoming interviews (future date)
|
||||
6. **Awaiting scheduling** -- interview stages with no date set yet
|
||||
7. **View only** -- assignments where you have read-only access
|
||||
8. **Pipeline** -- applications not yet at this stage (shown dimmed)
|
||||
|
||||
## Action Buttons
|
||||
|
||||
The button on each card reflects the most relevant action:
|
||||
|
||||
- **Score Now** -- the application is ready for you to score
|
||||
- **Continue** -- you have a draft in progress
|
||||
- **Prepare** -- an interview stage where you can review materials before the interview
|
||||
- **View** -- view-only access to the application
|
||||
|
||||
Clicking the card or its action button opens the guided scoring interface.
|
||||
|
||||
## Search
|
||||
|
||||
When you have 10 or more active assignments, a search field appears at the top. Type a studio name to filter the visible cards.
|
||||
|
||||
## Completed Reviews
|
||||
|
||||
Below the active grid, a **completed** section lists reviews you have already submitted. Click the toggle to expand or collapse it. If you have no active assignments, completed reviews display automatically.
|
||||
|
||||
Each completed row shows the studio name, stage, your score percentage, and the date you submitted. Click **View** to revisit a completed review in read-only mode.
|
||||
|
||||
:::info
|
||||
The count shown next to "My Reviews" in the navigation bar reflects actionable assignments only -- it excludes view-only and pipeline items.
|
||||
:::
|
||||
60
content/wiki/hub/reviewer/01-scoring-an-application.md
Normal file
60
content/wiki/hub/reviewer/01-scoring-an-application.md
Normal file
|
|
@ -0,0 +1,60 @@
|
|||
# Scoring an Application
|
||||
|
||||
The guided scoring interface walks you through each rubric criterion one at a time, then asks for your overall recommendation. This is where you do the actual work of evaluating an application.
|
||||
|
||||
## Opening the Scoring Interface
|
||||
|
||||
Click any active card on your **My Reviews** dashboard (or its **Score Now** / **Continue** button). This opens the guided scoring page at `/review/[cohortSlug]/guided`.
|
||||
|
||||
The page has a two-column layout:
|
||||
|
||||
- **Left column** -- background information about the application
|
||||
- **Right column** -- the scoring form
|
||||
|
||||
## Left Column: Background Tabs
|
||||
|
||||
The left column has several tabs depending on the stage:
|
||||
|
||||
- **Application** -- the applicant's submitted answers, attachments, and links. Eligibility questions are filtered out. File attachments can be downloaded; URLs open in a new tab.
|
||||
- **Reviews** -- completed reviews from earlier stages (hidden on the first stage). If blind review is enabled, reviewer identities are hidden.
|
||||
- **Assessments** -- self-assessment results from team members (second-round stages only).
|
||||
- **Script** -- interview questions configured for this stage, rendered from markdown. Use this to guide your interview conversation.
|
||||
- **Notes** -- a private text area for your own interview notes. These auto-save and are tied to the specific stage. Only you can see them.
|
||||
|
||||
## Right Column: Scoring
|
||||
|
||||
By default, you score one criterion at a time in **focused mode**. A **Show all** toggle in the upper right switches to a view where every criterion is visible at once.
|
||||
|
||||
In focused mode, each criterion shows:
|
||||
|
||||
1. **Criterion number and name** (e.g., "Criterion 1/5 -- Mission Alignment")
|
||||
2. **Description** of what to evaluate
|
||||
3. **Score options** -- either threshold cards with descriptions (click to select), named levels, or numeric buttons depending on how the rubric is configured
|
||||
4. **Notes field** -- optional per-criterion notes
|
||||
|
||||
Use the **Next Criterion** and **Previous** buttons to navigate. You can also use the **Jump to...** dropdown to skip to any criterion. A criterion must be scored before you can advance to the next one.
|
||||
|
||||
### Keyboard Shortcuts
|
||||
|
||||
In focused mode, you can score without touching your mouse:
|
||||
|
||||
- **Up/Down arrows** -- navigate between threshold or level options
|
||||
- **Enter** -- select the focused option and advance to the next criterion
|
||||
- **Left/Right arrows** -- move to the previous or next criterion
|
||||
- **Number keys (1-9)** -- set a numeric score directly (when simple score buttons are shown)
|
||||
|
||||
## Saving and Submitting
|
||||
|
||||
Your work auto-saves every 1.5 seconds after you make a change. A "Saving..." / "Saved" indicator appears near the top right. You can also click **Save Draft** manually at any time.
|
||||
|
||||
Once all criteria are scored, click **Proceed to Recommendation** to move to the final screen. This shows your score summary, lets you select a recommendation, and provides space for overall notes.
|
||||
|
||||
Click **Submit Review** when you are ready. A confirmation dialog explains that submission locks your scores and notes. After confirming with **Submit & Lock**, your review is complete and you are redirected to the dashboard.
|
||||
|
||||
:::warning
|
||||
After submission, your scores and notes are locked. You can still change your recommendation if the review is for the application's current stage, but scores cannot be edited.
|
||||
:::
|
||||
|
||||
:::tip
|
||||
For interview stages, the **Submit Review** button is disabled until after the interview has occurred. You can still prepare by reviewing the application and scoring criteria beforehand.
|
||||
:::
|
||||
52
content/wiki/hub/reviewer/02-understanding-rubrics.md
Normal file
52
content/wiki/hub/reviewer/02-understanding-rubrics.md
Normal file
|
|
@ -0,0 +1,52 @@
|
|||
# Understanding Rubrics
|
||||
|
||||
Rubrics define the criteria you score applications against. They are created and managed in Flywheel, the external assessment engine, and loaded automatically when you open the scoring interface.
|
||||
|
||||
## What a Rubric Contains
|
||||
|
||||
Each rubric has a title and a list of **criteria**. A criterion is a single dimension you evaluate -- for example, "Mission Alignment" or "Team Dynamics." Every criterion includes:
|
||||
|
||||
- **Name and title** -- what the criterion is called
|
||||
- **Description** -- what you should be evaluating
|
||||
- **Maximum points** -- the highest score possible for this criterion
|
||||
- **Weight** -- how heavily this criterion counts in the overall score (used in consensus calculations)
|
||||
|
||||
## Score Levels and Thresholds
|
||||
|
||||
Depending on how the rubric is configured in Flywheel, scoring guidance appears in one of three formats:
|
||||
|
||||
### Thresholds
|
||||
|
||||
Each criterion has named scoring bands with a title, description, and score range. For example:
|
||||
|
||||
- **Exceptional** (4-5): "Strong and nuanced understanding of their specific challenges..."
|
||||
- **Competent** (2-3): "Basic recognition of some of their main challenges..."
|
||||
- **Developing** (1): "Unaware of or defensive about their challenges..."
|
||||
|
||||
When you click a threshold, the score is set to the midpoint of that range.
|
||||
|
||||
### Named Levels
|
||||
|
||||
Each level has a fixed score value, a name, and a description. You click the level that best matches the applicant. The score is assigned directly from the level definition.
|
||||
|
||||
### Numeric Scores
|
||||
|
||||
When no thresholds or levels are configured, you see simple numbered buttons from 1 to the maximum. You select the number that best reflects your assessment.
|
||||
|
||||
## How Criteria Map to Application Questions
|
||||
|
||||
Each review stage has a rubric assigned through its Flywheel configuration. The scoring profile for a cohort defines a **map** that connects rubric criterion keys to application question keys. For example, a criterion called `gov_readiness` might map to the question `Q.GOV_PLAN`, meaning the applicant's answer to that question is what you should consider when scoring that criterion.
|
||||
|
||||
In practice, you see this mapping reflected in the scoring interface: the left column shows the applicant's answers, and the right column shows the corresponding criterion to score. The interface is designed so you can read the relevant answer and score it in the same view.
|
||||
|
||||
## Per-Stage Rubrics
|
||||
|
||||
Different review stages can use different rubrics. An application review stage might focus on written application quality, while an interview stage might use criteria like "Openness to Feedback" or "Cohort Fit." The rubric is loaded automatically based on the stage configuration -- you do not need to select one.
|
||||
|
||||
:::info
|
||||
Rubrics are managed by administrators in Flywheel. If a rubric is missing or misconfigured, you will see a "Rubric Not Available" message when you try to open the scoring interface. Contact your cohort administrator if this happens.
|
||||
:::
|
||||
|
||||
## Score Calculation
|
||||
|
||||
Your total score is the sum of all individual criterion scores. The percentage is calculated as total score divided by the maximum possible total. This score, along with your recommendation, feeds into the consensus view that administrators use when making decisions.
|
||||
49
content/wiki/hub/reviewer/03-recommendations.md
Normal file
49
content/wiki/hub/reviewer/03-recommendations.md
Normal file
|
|
@ -0,0 +1,49 @@
|
|||
# Recommendations
|
||||
|
||||
After scoring all criteria for an application, you select a recommendation. This is your overall judgment on what should happen next with the applicant.
|
||||
|
||||
## The Four Options
|
||||
|
||||
You choose one recommendation from a dropdown on the **Final Recommendation** screen:
|
||||
|
||||
- **Advance to Next Stage** -- you believe this applicant should move forward in the process. Use this when the application or interview performance meets or exceeds the bar for the current stage.
|
||||
|
||||
- **Hold for Further Review** -- you are not ready to recommend advancing or declining. Use this when you see potential but have concerns that need committee discussion, or when the applicant falls in a borderline zone where additional input from other reviewers would help.
|
||||
|
||||
- **Decline Application** -- you believe this applicant should not continue. Use this when the application clearly does not meet the criteria for the cohort, or when significant concerns emerged during the review.
|
||||
|
||||
- **Undecided** -- you have not formed a recommendation yet. This is the default state. You must change it to one of the other three options before you can submit your review.
|
||||
|
||||
:::warning
|
||||
You cannot submit your review while the recommendation is set to **Undecided**. All criteria must be scored and a recommendation selected before the **Submit Review** button becomes active.
|
||||
:::
|
||||
|
||||
## The Recommendation Screen
|
||||
|
||||
When you click **Proceed to Recommendation** after scoring, you see:
|
||||
|
||||
- **Your total score** and percentage in the top right
|
||||
- **Recommendation dropdown** -- select your choice here
|
||||
- **Score summary** -- a breakdown of each criterion with your score
|
||||
- **Overall notes** -- a free-text area for your overall assessment of the applicant
|
||||
|
||||
The score summary is read-only at this point (go back to scoring to change individual scores). The recommendation and overall notes can be edited freely before submission.
|
||||
|
||||
## Changing Your Recommendation After Submission
|
||||
|
||||
Once you submit, your scores and notes are locked. However, if the review is for the application's current stage, you can still change your recommendation. On the read-only review screen, click the **Change** button next to your current recommendation. A modal asks you to:
|
||||
|
||||
1. Select a new recommendation
|
||||
2. Provide a reason for the change
|
||||
|
||||
The change is recorded with a timestamp and your reason. A full history of recommendation changes is visible below the current recommendation.
|
||||
|
||||
:::info
|
||||
Recommendation changes are only available while the application is still at the stage you reviewed. Once the application advances to a later stage, your earlier recommendation becomes fully locked.
|
||||
:::
|
||||
|
||||
## How Recommendations Factor Into Decisions
|
||||
|
||||
Your recommendation is one input among potentially several reviewers. Cohort administrators see all reviewer recommendations alongside consensus scores when making decisions on the **Decisions** tab. A pattern of "advance" recommendations supports moving an applicant forward, while mixed recommendations (some "advance," some "hold") typically trigger committee discussion.
|
||||
|
||||
The final decision -- accept, waitlist, or decline -- is made by the cohort admin, not determined automatically by reviewer recommendations.
|
||||
56
content/wiki/hub/reviewer/04-interviews.md
Normal file
56
content/wiki/hub/reviewer/04-interviews.md
Normal file
|
|
@ -0,0 +1,56 @@
|
|||
# Interviews
|
||||
|
||||
Interview stages follow the same scoring workflow as application review stages, with additional features for preparing, taking notes, and working with scheduled interview times.
|
||||
|
||||
## The Dashboard for Interview Stages
|
||||
|
||||
Your **My Reviews** dashboard at `/reviews` handles both application reviews and interview assignments in a single view. Interview stage cards show additional information:
|
||||
|
||||
- **Stage label** -- displayed as "1st Interview" or "2nd Interview" instead of the raw stage name
|
||||
- **Interview date** -- shown next to the stage name if an interview has been scheduled
|
||||
- **"Unscheduled"** -- shown if the interview has not been booked yet
|
||||
- **Due date** -- if a due date is set, it appears on cards where the interview has already occurred. Overdue items show the date in red with an "OVERDUE" label.
|
||||
|
||||
Interview cards sort by urgency alongside non-interview cards. Overdue interview reviews appear at the very top. Unscheduled interviews appear lower since there is nothing to act on yet.
|
||||
|
||||
## Preparing for an Interview
|
||||
|
||||
Before the interview takes place, you can open the scoring interface to prepare. Click **Prepare** on the card. Inside, you have access to:
|
||||
|
||||
- **Application tab** -- review the applicant's full submission
|
||||
- **Reviews tab** -- read completed reviews from earlier stages to understand how the applicant has been evaluated so far
|
||||
- **Script tab** -- view the interview questions configured for this stage (rendered from markdown). Use these to guide your conversation.
|
||||
- **Notes tab** -- start writing private notes before, during, or after the interview
|
||||
|
||||
You can score criteria and save drafts during preparation, but you cannot submit the review until after the scheduled interview time has passed.
|
||||
|
||||
:::tip
|
||||
Open the scoring interface on a second screen during the interview itself. The **Script** tab gives you your question guide, and the **Notes** tab lets you capture observations in real time.
|
||||
:::
|
||||
|
||||
## Taking Interview Notes
|
||||
|
||||
The **Notes** tab provides a private text area tied to the specific stage. Your notes auto-save as you type (with a short delay). Only you can see these notes -- they are not visible to other reviewers or the applicant.
|
||||
|
||||
Notes are stored separately from the review itself. Even if you have not started scoring, you can use the notes tab to capture thoughts during or after the interview.
|
||||
|
||||
## Scoring After the Interview
|
||||
|
||||
Once the interview time has passed, the scoring workflow is identical to a regular application review. Score each criterion, select your recommendation, write your overall notes, and submit.
|
||||
|
||||
For second-round interview stages, an additional **Assessments** tab appears in the left column, showing self-assessment results from the applicant's team members. This gives you context on how the team views its own strengths and challenges.
|
||||
|
||||
## What Happens After You Submit
|
||||
|
||||
After submission:
|
||||
|
||||
1. Your review is locked (scores and notes become read-only)
|
||||
2. You are redirected back to the dashboard
|
||||
3. The assignment moves to the **completed** section
|
||||
4. Your recommendation can still be changed if the application remains at this stage
|
||||
|
||||
The cohort administrator is notified when enough reviewers have completed their reviews for a stage. They will then review the consensus scores and make a decision on each application.
|
||||
|
||||
:::info
|
||||
Interviews are scheduled through Cal.com by the cohort administrator. You do not book interviews yourself. If your dashboard shows "Unscheduled" for an interview assignment, the booking has not been created yet -- no action is needed from you.
|
||||
:::
|
||||
Loading…
Add table
Add a link
Reference in a new issue