One contact for your purchasing review
DistrictProof is a brand of Salt Technologies, Inc., a Delaware corporation and the contracting company for DistrictProof engagements. Our services focus on document and website accessibility for U.S. public K–12 districts and service partners. Delivery is based in Pune, India. Discuss contracting, delivery-location requirements, and vendor onboarding together so the proposed arrangement fits your district.
Email info@districtproof.io with your district name, the service you need, purchasing timeline, and required vendor documents. We use the same contact for scope questions and procurement coordination.
| Company detail | Purchasing reference |
|---|---|
| Contracting company | Salt Technologies, Inc. |
| State of incorporation | Delaware, United States |
| US mailing address | 9450 SW Gemini Dr Suite 89020 Beaverton, OR 97008 United States |
| Delivery location | Pune, India |
| Procurement contact | info@districtproof.io |
From first enquiry to an agreed project
Start with public examples and the outcome you need. For a document backlog, share a public website URL or an existing inventory. For website testing, identify the pages, templates, and family tasks that matter. For recurring work, describe the publishing volume and meeting calendar. Keep student records, credentials, and confidential files out of the initial enquiry.
- Review the starting material. Identify representative files, source quality, priorities, and district responsibilities.
- Define the work. Separate the initial project, website tasks, and recurring service so each has clear outputs.
- Review a fixed quote. Confirm the included volume, methods, schedule, assumptions, and treatment of changes.
- Complete purchasing and data review. Agree on the contracting parties, order process, payment terms, access, and file handling.
- Approve the scope and begin. Establish intake, named contacts, review milestones, and acceptance before production starts.
What the statement of work should make clear
The statement of work connects the price to the actual work. A page count alone does not describe a scan, an interactive form, a complex table, or a combined board packet. Representative samples help establish the mix and the review effort.
| Scope item | What to agree |
|---|---|
| Coverage | Named files, versions, page allowances, templates, website tasks, and any exclusions. |
| Deliverables | Returned documents or source files, findings, delivery manifest, review records, and publication checks where included. |
| Review and acceptance | Criteria, automated and human review coverage, district approval, correction process, and acceptance procedure. |
| Schedule | Intake dates, milestones, required source material, revision windows, and any urgent-work arrangement. |
| Commercial terms | Fixed price, invoice milestones, payment terms, recurring allowances, and approval of additional work. |
| Responsibilities and data | Content owner, posting owner, vendor dependencies, authorized access, processing locations, retention, and deletion. |
Vendor onboarding documents
A W-9, certificate of insurance, and standard service agreement, statement of work, and data-processing agreement are available on request for purchasing review. Send your district’s checklist early so we can confirm the documents, coverage requirements, and any district-specific terms before the order is approved.
Tax and insurance records belong in the appropriate purchasing exchange. They are not published here. A request for a document should include your district’s requirements and submission route; sensitive records should not be placed in a marketing form.
Purchase orders, invoicing, and payment
We accept district purchase orders. Payment terms are Net 30, or alternative terms agreed per project. Confirm the purchasing route and any vendor registration, board approval, invoice fields, or payment requirements before work begins. The quote and agreement identify the applicable arrangement.
For a phased project, identify the first approved tranche and quote later work separately. Recurring Care or Board Packet work should state its allowance, revision process, and billing period. Changes to volume, complexity, or timing need an agreed price and schedule before additional work proceeds.
Regional agencies and purchasing arrangements
Regional agencies, service partners, and buying groups can contact us about a shared scope or coordinated delivery. Confirm the applicable contract route and your district’s purchasing requirements before relying on a cooperative arrangement. A service description on this website does not establish contract eligibility.
Evidence your team can review at handoff
The proposed delivery record should identify the file or page version, review date, methods, coverage, and open actions. Automated checks, human review, and verification of the published version are separate review states. Agree which are included and who owns any remaining posting or content decisions.
Use the quality and evidence guide to prepare acceptance questions, and the security and data-handling page for technology review. To begin, email info@districtproof.io with your proposed scope and required documents.
Bring a scope your team can review
Use the project scoping worksheet (plain text) to organize your request. It is a planning aid, not a contract or a price commitment. Include your purchasing requirements and public examples, then agree on any non-public file transfer separately.
The fictional sample delivery report gives your team a concrete evidence format to discuss alongside the statement of work.