The Weekly Portfolio Scorecard Template
A weekly scorecard schema that turns asset reporting into kill, hold, repair, bundle, scale, and monitor decisions.
Search Intent
weekly portfolio scorecard template. This page is for operators who need a practical decision artifact before they buy traffic, rebuild pages, request implementation, or scale production.
How To Use This Page
A weekly portfolio scorecard should be small enough to use and strong enough to change decisions. If the field set is too thin, it becomes traffic reporting. If it is too large, it becomes dashboard maintenance. The useful middle is a row per asset per week with enough information to decide what happens next.
Start with asset and route context, then capture attention, route movement, inquiry quality, proof, cash band, maintenance cost, defect count, and one explicit decision. If the weekly review cannot fill those fields, the dashboard is not ready for scale.
Practical Artifact
Weekly Portfolio Scorecard. Copy the table into a spreadsheet or operating note. Use the status fields to separate visible defects from unknowns before choosing a service route.
| Field | Required? | Why it exists | Example value |
|---|---|---|---|
| asset_id | Yes | Links score to inventory | INFO-W3-30-A02 |
| route_family | Yes | Prevents comparing unlike routes | info_asset |
| sessions_or_views | Yes | Measures attention | 420 |
| qualified_clicks | Yes | Measures route movement | 18 |
| qualified_inquiries | Yes | Separates fit from noise | 2 |
| cash_amount_band | Yes | Tracks cash without private detail | 50000-199999 |
| owned_audience_action | Yes | Tracks note, LINE, email, product, or repeat-reply movement | fit reply |
| proof_signal | Yes | Captures trust and citation value | citation |
| maintenance_minutes | Yes | Prevents hidden cost | 35 |
| defect_count | Yes | Shows repair pressure | 2 |
| decision | Yes | Forces operating effect | repair |
| decision_owner | Yes | Prevents passive reporting | PM lane |
| next_action | Yes | Converts review into work | Fix CTA mismatch |
Decision Rule
| Scorecard state | Decision | Rule |
|---|---|---|
| Fields are mostly blank | needs_measurement | Define fields before scaling work |
| Traffic exists but route movement is weak | repair | Fix CTA, proof, or inquiry route before more production |
| Proof and qualified movement exist | bundle or scale | Scale only if maintenance and risk gates pass |
| No decision changes after two cycles | simplify | Remove fields that do not affect work allocation |
The score or checklist result is a triage tool, not a guarantee. It should make the next review easier to explain and easier to audit.
Internal Links
Natural Next Step
Use a Dashboard Setup Sprint when you cannot fill the fields needed for a weekly decision.
Review the services route after the artifact has clarified the problem state.
Next Diagnostic Step
If this checklist exposes repeated unknowns, turn the artifact into a short scope note. The first useful next step is a diagnostic read, not a redesign, ad spend, or paid tool.