Organize responses to an auditor's request list

The auditor's request list, as received:
"""
{{request_list}}
"""

Our team and what each person handles:
"""
{{team}}
"""

Type of audit and period covered: {{audit_type}}
Deadlines: {{deadline}}
Where our records live: {{systems}}
Items I already know are missing or will be late: {{known_gaps}}

Task: Organize this request list into a tracker that our team will work from and that {{coordinator}} will use to manage the audit. The goal is that every request has an owner, a source and a due date, so nothing reaches the deadline unassigned.

Requirements:
- Keep the auditor's own request numbers and wording, so every reply can be matched back to their list.
- Assign each request to one person from the team list, based on what they handle. If no one obviously owns it, write "unassigned".
- Name the likely source for each item (a report from a named system, a contract, a reconciliation), using only the systems I listed.
- Set internal due dates before the auditor's deadline, leaving time for review before anything is sent. Schedule long-lead items first, such as bank or customer confirmations, legal letters and reports that need IT.
- Flag requests that are ambiguous and draft one clarifying question for each, because asking early is cheaper than sending the wrong thing.
- Flag requests that involve personal or payroll data, so the files are redacted or sent through a secure channel the auditor agrees to.
- Never suggest creating, back-dating or editing a document to satisfy a request. If a document does not exist, the tracker should say so, and we will tell the auditor.

Format:
1. The tracker as a table with the columns Request no., Request, Owner, Source, Internal due date, Reviewer, Status, Notes, sorted by internal due date.
2. A summary by owner: each person's items and their first due date.
3. Questions for the auditor, numbered.
4. Risks to the deadline, up to 5 bullets.

If a request's period or scope is unclear, mark it "clarify" in the Status column instead of assuming. Keep the text outside the tables under 250 words.

Your controller or audit lead should review the tracker and every response before it goes to the auditor.