Four functions, one record per applicant

Every applicant's assessment moves through four stages, each owned by a distinct function on the team:

• Company Profile Analyst — structures the applicant's intake into a standard profile, flagging any field it cannot confidently fill rather than guessing.
• Readiness Assessor — scores the profile against the program's own readiness dimensions, with a stated rationale for every rating.
• Program Fit & Pathway Analyst — drafts a recommended pathway and next step, grounded only in the profile and assessment already on record.
• Assessment Reviewer — the human sign-off. No assessment becomes final without a named reviewer's recorded approval.

How an assessment actually gets worked

Nothing here starts because someone clicked a button on this screen — this surface is for reviewing finished work, not kicking it off. An assessment starts the moment an applicant's intake (their profile and any supporting documents) lands in the Assessment Team's queue. From there the four functions above run in a fixed sequence, each one picking up exactly where the last left off:

1. The Company Profile Analyst structures the raw intake first — nothing downstream starts until a profile exists.
2. The Readiness Assessor scores that profile once it's structured.
3. The Program Fit & Pathway Analyst drafts a pathway once a score exists.
4. The Assessment Reviewer signs off once a pathway has been drafted.

That run produces one complete version, which lands here as “Ready for review.” If you request a revision, the same four-function sequence runs again on your feedback and produces a new version — it does not resume mid-sequence or patch the old one.

Every finding is evidence-backed

A rating is never asserted on its own — each one is tied back to the specific source document, checksummed and logged, that supports it. When the available evidence is not enough to rate something fairly, that dimension is marked as a gap instead of a guess. You can trace exactly what a finding is based on from the Detail screen.

Nothing is ever overwritten

A requested revision never edits the prior version — it produces a new, complete version that explicitly names the one it replaces. Every version ever delivered stays retrievable on the Version History screen, exactly as it was at the time.

Two separate approvals, on purpose

An assessment's internal readiness sign-off (by Bowie BIC's own COE reviewer) and your acceptance of the delivered output here are deliberately kept as two distinct records. Accepting a deliverable on this screen is your organization's own record of review — it does not alter the underlying assessment.

What your access level lets you do

Everyone invited can browse every assessment for Bowie BIC — the full findings, evidence, and version history. What differs by level is who can make this organization's official decision on a deliverable, and who sees the aggregate Insights view:

• Viewer Read-only. Can open any assessment and read everything on it — findings, evidence, rationale, full version history. Cannot accept a deliverable, request a revision, or open Insights.
• Editor Everything a Viewer can do. On this specific surface that's currently the same set of actions as Viewer, since there's no submission form here to edit — the extra capability (submitting new requests and clarifications) exists on Compound Leverage's broader portal, not on this review-only screen. Still cannot accept a deliverable or request a revision on your organization's behalf.
• Approver Everything an Editor can do, plus the authority to make Bowie BIC's official call on a deliverable: Accept it, or send it back with “Request a revision.” Also the first level that can open Insights, the aggregate view across all of Bowie BIC's assessments.
• Admin Everything an Approver can do. Reserved for whoever should ultimately be accountable for this workspace; it doesn't unlock any additional action on this screen today.