The useful moment in a document-preparation workflow is often the pause before filing. EasySuit's small-claims intake can create an internal matter and produce a draft statement of claim, but the draft still needs factual and procedural review.1 This walkthrough explains what to check at that boundary.
The example is fictional and uses Colorado as the proposed state. It does not establish that Colorado is the correct venue for a real dispute, that the claim is timely, or that a generic statement is the form your court requires.
Begin in the filing intake
Sign in, open EasySuit, select File a claim, and choose the small-claims category. The seven-question flow asks who the claim is against, the kind of dispute, your name, the amount, an approximate incident date, a proposed state and a court if known.
Read each question carefully. The other party's name is not necessarily the signer's personal name or a storefront's trade name. Use your records to identify the actual contracting or responsible party, and preserve any uncertainty for review. A state entered in a form is your proposed jurisdiction, not the software's legal approval of it.
In our fictional test, Pine Studio entered a $900 claim against Cedar Workshop, selected money owed, entered Colorado and left the court and incident date unknown. The resulting internal matter was marked Started. That stage described work inside EasySuit; it did not mean anything had been submitted to a court.
Generate, then read the entire draft
The matter offered Draft my statement of claim. The resulting text had a draft warning, a caption, factual allegations, the $900 amount, requested relief and a signature block. It also contained placeholders for the court, the date, the circumstances and contact details.
That is a starting document, not a complete factual story. The brief intake had not captured why the money was owed. A sentence saying a defendant owes money still needs the underlying agreement, performance, payments and disputed facts. Do not fill those gaps by accepting a plausible AI narrative.
Keep the draft label visible while reviewing. Do not sign or certify it merely to unlock another control. The product presents review certification separately; only make an attestation when you understand it and can truthfully make it.
Check parties and the amount against records
Use a factual review table before proceeding:
| Draft item | Supporting material | Review question |
|---|---|---|
| Plaintiff's name | Contract and entity information | Who owns this claim? |
| Defendant's name | Signature block and reliable entity records | Is this the correct person or legal entity? |
| Amount requested | Invoice, payments and credits | Can each dollar be explained? |
| Statement of facts | Dated records and your knowledge | Which facts are disputed or missing? |
| Requested relief | Legal advice and court limits | Is this remedy available in this court? |
For Pine Studio, $1,200 billed minus $300 paid supports the arithmetic of $900. It does not by itself prove breach or entitlement to recover. If Cedar disputes delivery, the draft should not silently turn acceptance into an established fact.
Verify the court process independently
Consult the intended court's current instructions before treating the draft as filing-ready. Colorado's Judicial Branch publishes a small-claims guide with procedural directions, including party and service considerations.2 Use the official guide and local clerk or self-help resources to check the actual case; do not apply Colorado's procedure to another state.
Your review needs to address the court's authority, appropriate county or venue, the current monetary limit, the right forms, fees or fee-waiver procedure, any prerequisite notice and service requirements. A generic statement cannot establish those answers merely by containing a court caption.
Service is a separate legal step from creating a document. Sending a courtesy email, printing a draft or recording a status inside software does not prove valid service. Identify who can serve, what must be served, how, when and how proof is recorded using the applicable rules.
Keep a filing-readiness log
Create a small checklist with an owner and a source for each unresolved item: “court form confirmed,” “proper defendant reviewed,” “all blanks completed,” “amount reconciled,” and “service instructions checked.” Mark unresolved items open. Keep the original records separate from the editable draft.
If a lawyer reviews only the draft, clarify whether that review also covers jurisdiction, deadlines and filing/service. Limited document review should not be mistaken for an agreement to handle the entire case. If you already have court papers or an expiring limitation period, seek timely advice; drafting does not stop the clock.
Open the small-claims intake when you have the basic facts ready. For a related preparation task, the existing contract-review guide explains a different document entry point.
LawSensai is not a law firm. Its preparation tools do not decide your legal rights or guarantee a filing, service, judgment or recovery. Consult qualified counsel when you need advice about the claim or procedure.
Sources and references
-
LawSensai, EasySuit filing intake, synthetic intake and draft checked October 26, 2026. Internal matter creation and draft generation are distinct from court filing and service. ↩
-
Colorado Judicial Branch, Guide to Small Claims, checked October 26, 2026. Official Colorado instructions; use current local requirements for the actual proceeding. ↩