Product and editorial standards
About CueKit
CueKit is built and maintained by the CueKit Product Team. It is a browser teleprompter workflow we build and test against the product people can use today.
Last reviewed:
Current product boundaries
Camera and microphone are available only after your browser grants permission. CueKit cannot turn either device on without that permission.
Current browser recording is designed for local preview and a local .webm download. The current flow is not designed to upload raw video to CueKit servers.
AI processes submitted script or prompt text only when you choose an AI action. A request may include the draft and instructions needed to generate or rewrite the response.
How guides are reviewed
We review guides against the current product UI, controls, permission prompts, outputs, and browser behavior. Reviews check that the instructions match the workflow available on the review date.
Numeric claims link to an external source or the first-party methodology documented on this page. Product-specific claims are checked against the current CueKit interface and documented behavior.
Pacing review method
For pacing guidance, we use the same word-count and ETA calculation shown in CueKit: estimated minutes equal script word count divided by the selected WPM. The calculation is repeated at each cited WPM setting.
We read a short spoken script and a denser explanatory script aloud at the cited settings. We check punctuation pauses, emphasis, and whether the script needs fewer words; when a read feels rushed, the method calls for shortening the script instead of increasing speed.
These figures are CueKit Product Team starting ranges, not a population benchmark, user study, or promise that one pace fits every speaker.
Corrections and questions
Product behavior can change as browsers and CueKit change. Contact the CueKit Product Team when a guide no longer matches the interface, a permission prompt, or an output.