Preliminary Asset Audit

Data Asset Audit & Intake Form

This preliminary audit helps Input Frontier evaluate the scope, continuity, and technical footprint of your historical operational archives. Complete the questions and include one small, representative sample for our direct review.

Your Contact Details

Full Name

Work Email

Data Sources & Footprint

Which systems still hold your organization's records.

6. Which primary communication and collaboration tools does your organization maintain archives for?

Check all that apply.

Internal Messaging (Slack, Microsoft Teams, Discord, Mattermost)Cloud Storage & Documents (Google Workspace, Microsoft 365, Box, Dropbox)Knowledge Bases & Wikis (Notion, Confluence, Coda, Basecamp)Project / Task Management (Jira, Asana, Linear, Trello, Monday.com)Financial & Operational Models (Excel workbooks, QuickBooks/NetSuite exports, ERP records)Other Structured Archives

7. For each checked system, what primary business functions / teams are represented?

Example: "Slack covers Engineering, Executive Leadership, Product, and Customer Support channels; Google Drive holds Financial Forecasts, HR policies, and Board Decks."

Scale, Date Range & Temporal Continuity

Rough approximations are completely acceptable.

8. Historical Timeframe — Start (MM / YYYY)

End (MM / YYYY)

Organization is still active / records continue to present

9. Continuity of Records

Unbroken historical record across the full timeframeMostly continuous (minor gaps during tool transitions)Fragmented / Sporadic archives

10. Estimated Volume & Scale

Relational Coherence & Metadata

How your systems reference one another — and what context survives.

11. Do the different systems cross-reference one another?

Example: Does a Slack product discussion link to a Notion PRD, which references an Excel financial model and a set of Jira sprint tickets?

Highly integrated (teams regularly linked files, tickets, and discussions across tools)Moderately integratedDisconnected / Siloed (tools used independently without shared links or context)

12. What metadata is preserved in these archives?

Check all that apply.

Exact timestamps (creation, last edited, message delivery)Message threading and reply parent-child relationshipsConsistent author/user IDs or role tagsVersion history across documents and spreadsheetsFolder hierarchy and directory organizational trees

Technical Feasibility & Export Readiness

Where the data lives today, and how we can help prepare it. Needing export or anonymization support does not reduce eligibility.

13. What is the current technical state of this data?

Already exported / backed up to local drives or cloud bucketsStill live in active accounts; can be exported internally by our teamStill live, but our team lacks the bandwidth or administrative access to run full exportsFrozen / Archived in an inactive account (requires administrative reactivation or API assistance)

14. Would your team require technical or engineering assistance to execute a clean export?

No, our internal technical team can handle complete exportsYes, we would like extraction playbooks, scripts, or hands-on assistance

Rights, Privacy & Governance Check

A quick legal and privacy sanity check before your sample is reviewed.

15. Does the organization hold exclusive ownership and legal authority to license these internal operational records?

Yes — the organization holds exclusive ownership and legal authority to license these recordsUnsure — requires legal or board review

16. Does this archive focus strictly on internal organizational operations rather than bulk third-party consumer personal records?

e.g., internal chats, working drafts, strategy, financial planning — not end-user credit card numbers, HIPAA medical files, or consumer lists.

Yes, strictly internal operational recordsContains mixed customer/user data that would require redaction or filtering

17. Are there any specific files, proprietary algorithms, or highly sensitive assets that must be explicitly excluded from this package?

Representative Sample

One small sample helps us assess structure and context alongside your answers.

See what a strong sample looks like

Review a fictional package showing the level of detail, structure, and metadata that is most useful for evaluation.

View sample submission

Upload your sample

Required · PDF, Word, Excel, CSV, JSON, TXT, or ZIP · 10 MB max

Submit only a small representative fragment, such as 5–10 spreadsheet rows or a 1–2 page document excerpt. Do not include customer personal data, credentials, or proprietary source code. If we proceed after evaluation, we will work with your team to anonymize sensitive fields and prepare the full archive. Your sample is stored privately and is not publicly accessible.

Next Steps Once Submitted

1.We review your answers and draft an anonymized, standardized Corpus Summary Profile.
2.We evaluate your submitted sample's structure, metadata, and functional context before determining next steps.
3.If we move forward, we agree on scope and help your team anonymize, export, and securely prepare the approved archive.

Your answers and sample are submitted securely to Input Frontier for our direct review. We will follow up at the email address you provided.