Framework
Read the public CDOR methodology, assumptions, boundaries, and validation status.
Methodology →About the project
Built to make hidden milestone risk visible before it becomes last-minute work.
Clinical teams are usually strong within their individual functions. The harder problem is seeing the unresolved decisions, dependencies, handoffs, risks, and evidence gaps that sit between functional work and a critical milestone. CDRN makes that operational readiness knowledge explicit and reusable.
Why this exists
Teams can be almost complete and still not be ready.
Trackers can show progress and standards can define requirements, but neither consistently surfaces the cross-functional decision, dependency, handoff, review, or evidence gap that can still stop a milestone.
CDRN is intended to complement—not replace—sponsor procedures, approved study documents, statistical judgment, validated systems, or accountable cross-functional decisions.
The platform has two parts that share one method. The Navigator applies it: build a dated readiness plan, analyze a change, test a scenario, estimate capacity, and track actions in a private local Workspace. The Handbook explains it: why a checkpoint exists, how to decide, and what changes when conditions change. The two are meant to be used together, and each is useful alone.
The operating problem
Fragmented knowledge
SOPs, trackers, shells, standards, and unwritten team practices describe different parts of execution.
Cross-functional milestones
Database lock, interim analysis, and submissions require coordinated decisions across functions.
Experience does not scale automatically
Senior practitioners develop strong instincts that are rarely documented in reusable form.
The Handbook
A practical leadership handbook, built into the platform.
Clinical Statistical Programming Operations: A Practical Leadership Handbook has twelve planned chapters. Three are written in full as author drafts (capacity planning, dry run and database lock readiness, and dependency, risk and escalation management). The other nine are shown as clearly labelled outlines, not as finished text.
Each written chapter follows one pattern and links to a matching Navigator tool and a template. The Handbook does not repeat the Field Guide: the Field Guide gives the short answer, and the Handbook gives the reasoning.
Where it stands
Author drafts
Written from statistical programming leadership practice. Worked examples use a fictional study.
No independent review yet
Practitioners are invited to review chapters using synthetic scenarios. The review page shows the current count, which is zero.
Source files
Chapters are version-controlled source files that generate the web pages, so they can later feed a PDF or a book without being rewritten.
Creator & maintainer
Developed from clinical data and analysis delivery practice.
Shiva Kumar
Developed by a clinical statistical programming leader with more than 13 years of experience supporting clinical development, regulatory submissions, integrated analyses, database locks, safety updates, programming standards, and cross-functional delivery. The platform broadens that experience into shared readiness views for Programming, Biostatistics, Data Management, Regulatory, and Clinical stakeholders.
The public project intentionally avoids sponsor-specific study details and is designed as a generalized professional resource. Independent review, external practitioner contributions, and transparent versioning are intended to improve the methodology over time.
Project governance
Credibility should be inspectable.
The project keeps methodology, version history, accessibility commitments, contribution rules, and citation guidance visible rather than relying on unsupported claims.
Version history
Material product, content, methodology, and standards-reference changes are visible on the public changelog.
Changelog →Accessibility
Read the public WCAG-oriented design and quality statement.
Accessibility →Citation
Use the public citation page and version information when referencing CDRN or CDOR.
Citation →Content validation status
Author-created guidance and independent review are kept distinct.
The current public content is an editorial baseline rooted in clinical statistical programming leadership and cross-functional delivery experience. CDRN does not present other functions as independently validated until that review can be documented.
When independent reviewers are added, the site will identify the function, reviewed content/version, review date, and permission to name the reviewer or organization where applicable.
Use & adoption
How CDRN's use is documented.
CDRN documents meaningful professional use through privacy-conscious interaction counts, structured practitioner feedback, reported team adoption, external references, and traceable product changes. No adoption total is published until it can be substantiated.
Meaningful use
Readiness plans generated, calendar exports, resource and template downloads, Handbook chapters opened, guide use, and returning sessions are measured as aggregate activity rather than as vanity page views. Reading progress is also kept on your own device, where only you can see it.
Practice outcomes
Practitioners can document what CDRN helped clarify, identify, improve, or change in generalized professional work.
Reported adoption
Feedback distinguishes individual reference, repeated use, team sharing, internal workflow use, and training use.
External reference
Independent citations, links, presentations, teaching, publications, and professional references are listed only when they are verifiable.
Measurement status
Evidence collection is designed for public deployment. Verified adoption metrics will appear only after real use exists.
How measurement protects privacy →
Independent external references
None are listed yet. This section will remain empty until a citation, presentation, article, teaching reference, or professional link can be independently verified.
View the documented framework →
Independent-use feedback
Tell us how CDRN changed the work.
Specific use is more useful than praise. Share the role, how you used CDRN, and what changed. Optional details can document repeat or team use without exposing confidential study information.
Why these questions are asked
They distinguish browsing from practical use, repeat use, team adoption, and documented improvement. Responses are not presented publicly as evidence unless they can be substantiated and any required permission is obtained.
Evidence governance
Claims should be traceable to source evidence.
CDRN separates self-reported use, verified adoption, and independent external references. Public metrics are not upgraded from one category to another without supporting documentation.
Feedback IDs
Accepted practitioner submissions receive a unique FB evidence identifier and UTC timestamp.
Change traceability
Material product changes can be linked internally to the feedback or recurring problem that prompted them.
Verification levels
Anonymous aggregate use, self-reported adoption, corroborated adoption, and independent external reference are kept distinct.
No manufactured impact
CDRN does not infer organizational adoption from page views, downloads, or generic compliments.