Cross-Asset PDCA Control Ledger Template
A spreadsheet-ready control ledger for deciding when to increase, repair, bundle, hold, or kill blogs and backlink assets without duplicate work.
Portfolio Operating Dashboard
Spreadsheet-first scorecards for deciding what to kill, hold, repair, bundle, scale, monitor, or measure next across a mixed asset portfolio.
How To Use This Library
This library is a working shelf for operators who need a usable artifact before a sales conversation. Start with the checklist, scorecard, or worksheet that matches the defect you can actually observe. Fill the artifact first, then decide whether the next step is self-repair, diagnostic review, implementation, monitoring, or hold.
The pages in this hub are designed to be useful without buying anything. They define the failure mode, give a copyable table, and name the route boundary. They do not ask for private credentials, customer records, account creation, payment setup, DNS changes, outreach sends, or public publishing actions.
For backlink value, the page should be citable because the artifact helps another operator finish a job or defend a decision. If the artifact cannot stand alone, the page should be revised before it receives more internal links.
The Weekly Portfolio Scorecard Template
A weekly scorecard schema that turns asset reporting into kill, hold, repair, bundle, scale, and monitor decisions.
Batch A Fit
Use this hub when a mixed portfolio has too many assets and too few decisions. The scorecard should not reward page count, row count, or report complexity. It should force one weekly operating choice for each important asset: kill, hold, repair, bundle, scale, monitor, or needs measurement. Keep the field set small, spreadsheet-friendly, and tied to proof, qualified clicks, inquiries, cash bands, maintenance cost, and a named owner.
Route Links
Use these links when the artifact has clarified the next operating state. Keep diagnostic work separate from implementation until the defect is visible.
Publication Boundary
This staged hub is a local public-candidate surface only. It does not deploy, send, publish, create accounts, change DNS, connect payments, or run paid tools.
When this library becomes a Diagnostic Sprint
If several pages in this library point to the same missing evidence, broken route, or measurement gap, turn the finding into a scoped diagnostic note before adding more pages.