View all submitted checklists for date range?

Hi Fatima, happy to help with this! Great question for audit purposes.

Yes, there is a dedicated path for this. Here's what I recommend:

Option 1: Built-in Checklist Report (Recommended)

1. Navigate to Reports → Checklist Responses
2. Select your date range using the Date Filter dropdown
3. Optionally filter by Checklist Template, Technician, or Job Type
4. Click Export to CSV for your audit documentation

This report includes: checklist name, submission timestamp, technician, job reference, completion status, and individual question responses in a flattened format suitable for analysis.

Option 2: API (if you need deeper integration)

The endpoint is GET /v2/checklist-responses with start_date and end_date parameters. Rate limit is 100 requests/minute; paginate with limit=100 and offset. For 2,400 records, you'd need ~24 calls—well within limits.

See this article for full steps on viewing submitted checklist responses.

Pro tip: if you're doing this quarterly, save yourself the clicks and bookmark the filtered report URL once you set it up. The date range won't persist but your other filters will, so it's just two dropdowns each quarter.

Also, if your auditors want photos attached to checklist items, those export separately—make sure you grab the Attachments Report from the same menu and cross-reference by job ID.

I would like to clarify one point regarding the API approach. The endpoint Priya mentioned returns checklist responses at the response level, not the individual question-answer level. If your auditors require granular visibility into which specific safety questions were answered affirmatively versus negatively, you will need to use GET /v2/checklist-responses/{id}/answers for each response ID.

This increases your API call volume significantly. For 2,400 jobs with an average of 15 checklist items each, you are looking at approximately 36,000 calls. I would recommend negotiating a temporary rate limit increase with FieldPulse support rather than stretching this across multiple days.

Additionally, it is worth noting that the CSV export from the UI does flatten this structure automatically, which may be preferable for your use case.

Thank you, Anita. This clarification is precisely what I needed. The flattened CSV will suffice for our current audit cycle; however, the granular API structure is noted for future automation requirements.

I have confirmed that the Reports → Checklist Responses interface provides the necessary data. I will proceed with the manual export for Q4 2025.

```bash curl -H "Authorization: Bearer $TOKEN" \ "">api.fieldpulse.com/.../checklist-responses ```

Response omits job.customer_id in nested object—known issue if you need to join customer data. Flatten yourself or use the CSV export.

From a data retention perspective, i.e., how long are these checklist responses maintained in the system? Our compliance framework requires 7-year retention for safety documentation. Is the API export the authoritative source, or should we be archiving the CSV outputs separately?

Additionally, are there any provisions for tamper-evident or digitally signed exports that would satisfy SOC 2 Type II audit requirements?

Checklist response data is retained according to your account's Data Retention Settings under Admin → Security & Compliance. Default is indefinite; however, you may configure automated archival or deletion per your policies.

For audit trails, enable Audit Logging (requires Enterprise tier) which captures export events with user attribution and timestamp. The CSV itself is not cryptographically signed; for that requirement, you would need to implement client-side hashing or use the API to populate a WORM storage system.

Audit Logs: Viewing Account Activity covers the event logging in detail.