Each guide is short and starts from what you want to do. The reference has every detail.
Guides
Writing a planThe plan is a page with forms. Each choice is a block that quotes the protocol, and the compiler checks every line with a fix.The decision interview and proposalsAnswer the open decisions of the plan one at a time, with the protocol sentence and the options in front of you. Proposals arrive in an inbox that you accept, decline or improve.Without AISapling is complete without any AI: the forms, the checks, the decision interview with options, and proposals from the rules and templates. Nothing is sent anywhere.With your AIConnect the AI you already use. It proposes blocks and recommendations, every proposal is compiled before you see it, and you accept, decline or improve. It never approves or decides.For programmers, the specificationsThe SAP says what; the specifications say how. The ADaM and TLF specifications are made from the plan, edited by the programmer and checked against the plan.From the plan to R and SASThe same table written in R and in SAS as the same blocks in the same order, and every number of one compared with the number of the other.DashboardsClick a number and see how it was made: the analysis, the population, the variables, the SAP block and the protocol sentence. A dashboard for R and one in the browser for SAS.Design before the protocolSimulate the statistical design in R before the protocol is final: power, bias against each estimand, multiplicity and interim analyses. The result becomes the protocol's statistical section.Word and PDFThe plan as a PDF, and as a Word file that a reviewer comments on. The plan stays the source; Word is a view.The three toolsSapling SAP writes the plan and the programs. DataStep Studio runs SAS and DataStep Studio for R runs R. Who each is for, and what works without the others.Data and AI: what Sapling does with your filesOne page, plain sentences, each one checkable by a QA or IT person: what stays on your computer and what an AI would be sent.