Design a tracker spreadsheet for a team process

What the tracker is for: {{process}}
Who will enter data and who will read it: {{users}}
App: {{app_and_version}}
Questions people need it to answer: {{questions_to_answer}}
How it is tracked today, if at all: {{current_tracking}}
Roughly how many new rows per week: {{volume}}

Task:
Design a tracker in {{app_and_version}} for the process above, so that {{users}} can enter data quickly and consistently and the questions above can be answered without cleanup. A good tracker has one row per item, one kind of value per column, and as little free text as possible.

Format:
1. Columns: a table with the columns Column name, What goes in it, Type (date, number, drop-down, text or formula), Allowed values or rule, Required (yes or no). Up to 15 columns.
2. Drop-down lists: the values for each, kept on a separate Lists tab, and how to set up the data validation in this app, with menu names, so a list can grow without breaking. If one drop-down should depend on another, show how, or say plainly if the app cannot do it without a script and suggest a simpler layout.
3. Formulas: for each calculated column (for example days open or an overdue flag), the formula for row 2 in a code block and one plain sentence on what it does.
4. Highlighting: up to 3 conditional formatting rules that make problems visible, each with its formula.
5. Summary tab: the formulas that answer each question above, such as counts by status.
6. Check it: three made-up test rows, labeled as test rows, and what each formula should return for them.
7. Rules for users: up to 5 short rules for a Read Me tab.

Requirements:
- Only functions available in {{app_and_version}}; no macros or add-ons.
- Leave out personal data the process does not need, and say if a column could hold sensitive information and who should be able to see it.
- Explanations under 450 words, plus the tables and formulas.

Example of one column row's form only: "Status | Where the request is now | Drop-down | New, In progress, Waiting, Done | Yes"

If a question I listed cannot be answered from the columns, add the column it needs. If the process is unclear, for example whether an item can be reopened, state the assumption you made.