> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://ayuda.peewah.co/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# What the event readiness score tells you

When you open an event, the first thing on **Overview** is its **readiness
score**: a percentage and a summary of what is missing.

Peewah checks your event automatically and flags what is worth fixing before it
starts. Click **See all validations** for the full detail.

---

# The four kinds of notice

| | What it means |
|---|---|
| 🔴 **Critical** | Something that will fail. **Fix these** before you publish or before the day arrives |
| ⚠️ **Warnings** | Will not break the event but will almost certainly cost you — a missing detail, an incomplete setting |
| 💡 **Recommendations** | Improvements, not errors. Things that make the event look and work better |
| ✅ **Complete** | Already fine. Useful for knowing what you do not have to check again |

---

# How to use it

**Do not wait for 100%.** Many recommendations are optional depending on the
event — a virtual event does not need the same things as an in-person one.

**What is worth doing:** arrive at the day of the event with **zero criticals
and every warning read at least once** — even if you decide to leave some as
they are, having read them.

> 💡 **Check it twice:** once when you finish setting up, and again **a few days
> before the event**. Something almost always changed in between — you added
> tickets, moved the date, changed a stage — and the validations update with it.

If you just changed something and it is not reflected, use **Refresh** to run
the check again.

---

# Need help?

Write to us at **soporte@peewah.co** and our team will get back to you.

---