Analyze your first sermon
Open Import, choose Teaching, add the YouTube link, recording, file, or transcript, and wait until the transcript is usable. Then open the sermon from Safe Library and read the evidence-backed assessment.
Import teaching →
Use the four-step path for a new sermon, search for a specific task, or open Help from any signed-in page for guidance about the screen you are already using. Press ? anywhere outside a form to open contextual help.
Open Import, choose Teaching, add the YouTube link, recording, file, or transcript, and wait until the transcript is usable. Then open the sermon from Safe Library and read the evidence-backed assessment.
Import teaching →Begin with the overall verdict and evidence audit. A useful review identifies exact sermon language, what worked, what needs work, listener impact, assessment impact, delivery coaching, and a concrete revision. Open deeper coaching only after checking the evidence.
The evidence audit checks transcript grounding, paired praise and criticism, specificity, generic wording, and repeated feedback. A weak first pass is automatically sent through a repair pass before it is saved.
Opening prayer, greetings, worship transitions, announcements, and service logistics are not sermon content and are excluded from assessment. A sermon that teaches about prayer remains analyzable.
Open Transcript Center first. If important Scripture, names, sections, or speaker changes are missing, repair the transcript. The durable worker prepares a corrected review automatically while preserving the prior completed report.
Open transcripts →Retry when the source is available but automated processing failed. Use Manual Transcript when you already have reliable text or can correct the transcript yourself. Avoid importing the same source repeatedly.
Open shows the complete private review. Published Review is the share-ready output. Metadata corrects identifying information. Coach opens detailed practice. Transcript repairs source text. Report status shows automatic processing.
Teaching should contain sermons, Bible classes, lectures, workshops, and other material intended for assessment. Research should contain supporting books, podcasts, articles, clips, and documents. Correct the source metadata before relying on reports.
Define theological commitments, audience, behavioral-transformation priorities, communication standards, research sources, and pastoral boundaries. Use separate profiles when the preacher, church, audience, or coaching purpose truly changes.
Manage profiles →Import the source as Research. Preserve its author, source, and citations. Attach it to the appropriate profile or Studio project; do not treat research material as a preached sermon.
Open research →Choose a Studio project, attach the right sermon analysis and research, define the audience and controlling idea, then build one asset at a time. Verify every Scripture interpretation, quotation, and factual claim before use.
Open Studio →Use Classroom or Transformation Training when the same weakness appears in multiple sermons. Choose one pattern, rehearse a correction, use it in the next sermon, and compare evidence instead of relying on memory.
Open Classroom →Start with one question, such as whether application improved over six sermons. Filter the library, choose only the sermons that answer that question, review the selection, and then create the report.
Build a report →A workspace role controls responsibility: owner, administrator, preacher, elder, member, or another church role. A product license separately controls access to Sermon Analyzer, Salt & Light, both, or administration.
Manage workspace →Open Billing to review the plan and trial, start checkout, update payment details, or cancel through Stripe's customer portal. Plan access follows the active Stripe subscription and assigned seats.
Open billing →Use MFA, review sessions, sign out of shared devices, and share only published outputs intended for other people. Do not send passwords, verification codes, private journals, or confidential pastoral material to support.
Open security →Check Import Activity and Transcript Center for the actual state. Retry failed work once. If it repeats, contact support with the source type, page address, approximate time, and a screenshot—never private credentials.
Refresh once after a deployment and make sure the browser is not forcing desktop mode on a phone. If the problem remains, include the exact page, screen size, expected action, and screenshot in a support request.
These actions appear throughout the sermon library and review workflow.
Include what you selected, what you expected, and what appeared. Never send a password, verification code, API key, private journal, or confidential pastoral record.