Criteria,Weight,Score (0-5),Weighted Score (W*S),Total WS Possible

FINDABILITY
Findable in search,,,=(B*C),=(B*5)
Release notes present,,,=(B*C),=(B*5)
Site-specific search available,,,=(B*C),=(B*5)
Developer portal hub context,,,=(B*C),=(B*5)
UI pages link to docs,,,=(B*C),=(B*5)
Main organization isn't an FAQ,,,=(B*C),=(B*5)
Version selection is available,,,=(B*C),=(B*5)
Easy path to top 5 pages,,,=(B*C),=(B*5)
Topics have article-like length,,,=(B*C),=(B*5)
Content follows task-based organization,,,=(B*C),=(B*5)
Developer portal has IA flow,,,=(B*C),=(B*5)

ACCURACY
Steps are accurate,,,=(B*C),=(B*5)
Code samples work,,,=(B*C),=(B*5)
Content reviewed within past year,,,=(B*C),=(B*5)
Timestamps are visible,,,=(B*C),=(B*5)
No broken links,,,=(B*C),=(B*5)
Instructions are consistent,,,=(B*C),=(B*5)
Screenshots are up to date,,,=(B*C),=(B*5)
Deprecated features are noted,,,=(B*C),=(B*5)
App code matches doc code,,,=(B*C),=(B*5)

RELEVANCE
Key use cases are documented,,,=(B*C),=(B*5)
Code samples exist,,,=(B*C),=(B*5)
Support options noted,,,=(B*C),=(B*5)
Reference material is interactive,,,=(B*C),=(B*5)
Feedback options available,,,=(B*C),=(B*5)
Docs are published when features released,,,=(B*C),=(B*5)
GitHub is actively monitored,,,=(B*C),=(B*5)

CLARITY
Product overview page answers "wh" questions,,,=(B*C),=(B*5)
Access and authorization explained,,,=(B*C),=(B*5)
Overview addresses use cases,,,=(B*C),=(B*5)
Overview has architectural diagram and explanation,,,=(B*C),=(B*5)
Overview has index of assets that the product offers,,,=(B*C),=(B*5)
Subsystems have their own overview pages,,,=(B*C),=(B*5)
Getting started tutorial exists,,,=(B*C),=(B*5)
Sandbox environment available,,,=(B*C),=(B*5)
README file exists in code repo,,,=(B*C),=(B*5)
Tasks have prerequisites sections,,,=(B*C),=(B*5)
Tasks have numbered steps or sections,,,=(B*C),=(B*5)
Sample app available,,,=(B*C),=(B*5)
Code sample has inline comments,,,=(B*C),=(B*5)
Any role-based permissions are noted,,,=(B*C),=(B*5)
Steps are detailed rather than general,,,=(B*C),=(B*5)
Workflow maps connect topics in larger flows,,,=(B*C),=(B*5)
Visuals aid in areas of confusion,,,=(B*C),=(B*5)
Support cases are minimal for the product,,,=(B*C),=(B*5)
Technical level is appropriate to audience,,,=(B*C),=(B*5)
Experiential learning paths are available,,,=(B*C),=(B*5)
Doc recommend the simplest path when multiple options exist,,,=(B*C),=(B*5)
Docs call out relevant sections in a sample app,,,=(B*C),=(B*5)

COMPLETENESS
Reference docs follow industry standards,,,=(B*C),=(B*5)
Parameter docs have complete info,,,=(B*C),=(B*5)
Reference content has consistent structure,,,=(B*C),=(B*5)
Error messages are documented,,,=(B*C),=(B*5)
Responses includes both sample and schema (REST APIs),,,=(B*C),=(B*5)
Troubleshooting section exists,,,=(B*C),=(B*5)
Limitations/thresholds documented,,,=(B*C),=(B*5)
Locale limitations noted,,,=(B*C),=(B*5)
Unhappy paths are documented,,,=(B*C),=(B*5)

READABILITY
Grammar isn't distracting,,,=(B*C),=(B*5)
Placeholder text in code is visually apparent,,,=(B*C),=(B*5)
Sidebar nav has consumable organization at a glance,,,=(B*C),=(B*5)
Sidebar nav highlights the current topic,,,=(B*C),=(B*5)
Context remains consistent when navigating,,,=(B*C),=(B*5)
Doc types have consistent names across product docs,,,=(B*C),=(B*5)
Subheadings are descriptive,,,=(B*C),=(B*5)
Topics start with summaries,,,=(B*C),=(B*5)
Glossary exists,,,=(B*C),=(B*5)
Glossary entries match the actual terms used in the content,,,=(B*C),=(B*5)
Code samples have proper formatting and highlighting,,,=(B*C),=(B*5)
Responsive view presents content in a readable way,,,=(B*C),=(B*5)
Navigation mechanisms are consistent across docs,,,=(B*C),=(B*5)
Sentences and paragraphs are somewhat short,,,=(B*C),=(B*5)
Language uses active voice,,,=(B*C),=(B*5)

TOTALS,--,--,=SUM(D4:D60),=SUM(E4:E60),=ROUND(((D61/E61)*100),0)&"%"