# GET FREEWIS ## Request FreeWIS for your jurisdiction Qualifying public child-welfare jurisdictions may request a **versioned FreeWIS source package at no charge** for their own agency use under a separate license. The package is jurisdictionally unconfigured: your agency configures, validates, hosts and operates its implementation. The delivery manifest identifies the application, SQL/database and knowledge-base materials actually included, their versions, dependencies and exclusions. The agency's own employees lead and perform the work, using permitted tools and ordinary infrastructure. Your agency funds staff, AI access, infrastructure, migration, configuration, integration, security, validation and ongoing operations. **State-funded implementation is the expected route.** Federal participation is an optional, separately assessed funding choice, not a condition of requesting FreeWIS. HCT consulting is optional and separately contracted. The source license creates no recurring HCT source-license fee or required HCT services. This is an initial review request. It creates no source license, implementation permission, procurement commitment or promise of approval or delivery. You can make an initial inquiry without authority to bind the agency and identify facts that still need verification. **HCT will not enter a source license or deliver FreeWIS code before November 1, 2026.** Requests may be received and reviewed now. November 1 is the earliest possible date, not a promise of approval or delivery on or after that date. ## The internal implementation requirement For this path, an **Excluded CCWIS Vendor** is a commercial entity other than HCT that has performed compensated CCWIS or SACWIS design, development, implementation, configuration, hosting, maintenance, support, independent verification and validation (IV&V), quality assurance (QA), or advisory work. A provider that supplies only ordinary generally available infrastructure or developer tools without CCWIS-, SACWIS-, or FreeWIS-specific professional services is not excluded merely for that reason. Actual services, personnel access, entity history and involved affiliates must be assessed. An agency does not qualify while it has an ongoing compensated CCWIS or SACWIS engagement with an Excluded CCWIS Vendor, whether or not that vendor is proposed for FreeWIS. Such a vendor also may not participate in the agency's FreeWIS request, restricted evaluation, planning, implementation or support, or receive FreeWIS source, nonpublic delivery materials, modifications, repository/build/deployment access or related credentials. Historical relationships must be disclosed, but an ended relationship alone does not permanently disqualify the agency. Identify dates, any remaining payments, continuing work, support, access and planned involvement so HCT can determine whether the engagement has actually ended. An "ended" label does not resolve those facts. HCT's separately contracted services are permitted. Ordinary generally available computing, storage, networking and security infrastructure are permitted when the provider performs no FreeWIS-specific service and its personnel receive no access to restricted materials. Automated storage, transmission and processing inherent in that ordinary service alone are permitted. Permitted developer and AI tools remain subject to the source license's account, processing-purpose, access and data-protection requirements; a tool label does not authorize provider personnel or outsourced implementation. Legally required disclosure or access is addressed in the license's government and public-records terms. No commercial implementation-partner program is created by this request. Ordinary public PLAY viewing is open to adults, including vendor employees. That permission grants no source or restricted agency-work rights and does not cure a disqualifying agency engagement. Do not interrupt necessary services or breach an existing contract in reliance on an uncertain request. ## What happens next 1. **Request review.** HCT reviews the jurisdiction, requester, proposed use and implementation path, and may ask for clarification. Unknown facts remain pending verification, not automatically approved or deemed false. 2. **Authorized verification.** Before qualification, an authorized agency official confirms eligibility, current vendor status, required access and the agency's internal implementation path. HCT may approve or decline a request. 3. **Complete the source license.** If the request is approved, the parties complete the license's agency, release, rights, funding, public-records, risk and acceptance/delivery particulars. The exact release, package digest and notices are recorded. Both parties execute the license no earlier than November 1, 2026 and before code delivery. 4. **Deliver the recorded package.** Delivery follows the completed license. It includes only the identified version and materials. Hosting, implementation, support, later releases, security patches and knowledge-base updates are included only if separately committed in writing. The source license will address prohibited vendor involvement and access, including applicable suspension, termination, cease-use, source return/destruction, certification and verification remedies, subject to law and the agency's completed government terms. Source removal does not transfer agency data to HCT or perform the agency's transition for it. ## Your agency's responsibility Receiving, evaluating or operating FreeWIS does not establish ACF approval, CCWIS status, federal funding eligibility, reimbursement or a guaranteed reporting result. Your agency remains responsible for its implementation, data, security, operations, applicable requirements, reporting and decisions about real people. If it later proposes federal participation, the relevant work and funding terms must be assessed before the affected commitment or claim. Do not send production data, credentials or access to a production environment through GET. HCT access to real agency data requires the applicable separately signed scope, responsibility and data-protection/security agreements. ## Request form ### Jurisdiction **Jurisdiction or agency legal name** **Jurisdiction type** - State - Tribe - Territory - District of Columbia - County under a state plan - Other public child-welfare entity — describe **State or territory** An entity category starts review; it does not itself establish license eligibility. ### Requester **Your name** **Official work email** **Title or role** **Your role in this request** - I am authorized to request or evaluate software for this jurisdiction. - I am coordinating and can connect HCT with an authorized official. - I am making an initial inquiry. These choices describe the inquiry role, not authority to sign a source license. ### Proposed use and known facts **How does your jurisdiction intend to use FreeWIS?** Describe the agency need at a general level. Do not include real-case or sensitive production information, credentials, secrets, attachments or unnecessary restricted procurement material. **Will agency employees lead and perform the implementation, with any HCT assistance separately contracted?** - Yes — agency employees - Yes — agency employees with optional, separately contracted HCT assistance - No - Not yet determined / I need to verify **Does the agency have a current or ongoing compensated CCWIS or SACWIS engagement with an Excluded CCWIS Vendor, as defined above?** Exclude HCT's own services and ordinary infrastructure that meets the stated exception. - Yes - No, to my knowledge - Unknown / needs authorized verification **Would an Excluded CCWIS Vendor participate in this agency's FreeWIS request, restricted evaluation, planning, implementation or support?** Independent ordinary public PLAY viewing alone is not the participation asked about here. - Yes - No, to my knowledge - Unknown / needs authorized verification **Would an Excluded CCWIS Vendor or its personnel receive direct or indirect access to FreeWIS source, nonpublic delivery materials, modifications, repositories, build/deployment systems or related credentials?** - Yes - No, to my knowledge - Unknown / needs authorized verification **Known current, prior, ongoing or planned CCWIS/SACWIS vendors and engagements** Identify the entity, general work, dates/status (including **ended**) and proposed FreeWIS role/access. Note residual payments, continuing support, access or uncertainty. Enter "None known" only if accurate, or "Needs verification" and describe the missing facts. Do not attach contracts or sensitive records at this stage. History is disclosed for verification; current or planned disqualifying involvement is assessed separately. **Ordinary infrastructure providers** Identify providers if useful. The ordinary-infrastructure exception above applies; source access and FreeWIS-specific services require separate assessment. **Desired evaluation or delivery timeframe** No requested timeframe changes the November 1 earliest-date rule or creates a delivery promise. ### Submission acknowledgement **Required checkbox — accurate inquiry** I confirm that I have provided only the requested professional and administrative information, without real-case or sensitive production data, credentials or secrets. My answers are accurate to my knowledge; I have identified facts needing verification and will correct a known material error. I understand that qualification requires an agency-internal implementation and no disqualifying vendor involvement or restricted access, that an authorized official must verify the required facts before approval, and that this request grants no license or implementation permission. **Required checkbox — personal Terms acceptance** I accept the [FreeWIS Terms of Service](https://freewis.com/terms) for my own use of this request process and acknowledge that the [Privacy Notice](https://freewis.com/privacy) was provided. I am not signing a source license, binding the agency or accepting the Privacy Notice as a contract. ### Review states **Not currently qualified for the no-charge source path:** The answers identify an external implementation path, an ongoing excluded-vendor engagement, proposed excluded-vendor participation or prohibited access. This form cannot submit the request as a qualified no-charge application. Contact **freewis.support@hudsonct.com** for clarification using professional/administrative information only. If the facts later change, a new request remains subject to full review; no approval is promised. **Preliminary inquiry — verification needed:** One or more facts are unknown. You may send this as a preliminary inquiry. HCT cannot approve source access until an authorized official verifies the required information and the agency qualifies. ### Privacy beside the action We send your request to FreeWIS Support through Microsoft 365 and retain necessary correspondence for review, response, the resulting transaction and applicable legal records needs. See the [Privacy Notice](https://freewis.com/privacy). Do not send case data or sensitive attachments. **Button:** Request FreeWIS **Preliminary button:** Send preliminary inquiry **Sending:** Submitting your request… **Submission accepted:** Your request was accepted for submission to FreeWIS Support. This confirms mail-service submission, not approval, delivery or a response deadline. Keep your submission reference. HCT may contact your work email for review. No source license or code delivery will occur before November 1, 2026, and submission promises neither approval nor delivery after that date. **Failure:** We could not confirm submission. Please try again or email **freewis.support@hudsonct.com**, without case data or sensitive attachments.