Intake Information Requests Sample Clauses

Intake Information Requests. Functional Requirement Number Requirement Description Related Reference in Appendix A 001 Ability to develop an online and knowledge base that will provide requester’s the ability to submit request directly into the system 1 002 Ability for City of Austin Law Department’s website to transmit submitted Information Request into system 003 Ability for Intake Staff to input information Request into system 004 Ability for all Information Request to be completely managed by Intake Staff to complete the following but not limited to: • Assignment of one or more PIR Responders • Final correspondence to requester • Add/Remove templates 005 Ability to validate requestor email by sending a confirmation code to the Requester email address 1 006 Ability to attach additional documents and videos with an Information Request. Attachment types to include but not limited to the following: • MSG • JPEG • EXCEL • AUDIO and VIDEO • PDF • WORD 1 007 Ability to indicate requesters preferred pickup method such as but not limited to Web portal, physical pickup, mail to postal service address, or email. 1 : City of Austin Statement of Work Public Information Request System Functional Requirement Number Requirement Description Related Reference in Appendix A 008 Ability to provide requestor confirmation submitted information request with the ability to: • Summarize request • Provide City Contact Information • Anticipated process and/or estimated cost 1 009 Ability to assign unique identifier to each request received (identification number) Refer to Section 2.1 for workflow process. 2 010 Ability to identify duplicate requester and merge 3 011 Ability for internal and external requesters to communicate within the system to complete the following including but not limited to: • Request additional information from requestor • Communicate with requester per preferred communication preference to obtain additional clarity from requester 4, 5 012 Ability to customize unlimited number of rules for automated routing for request and notifications for the following including but not limited to: • Adjust requester response timeframe window • Notify requestor when response timeframe is expiring o Summary of request o New expected date • Send email to PIR Responders • Email notification to the assigned PIR Responder for any change or clarification • Adjust time out period by administrative users • Send additional notification at a set period reminding requester of expected date • Override and/or r...
Sample 1
AutoNDA by SimpleDocs

Related to Intake Information Requests

  • Information Requests The parties hereto shall provide any information reasonably requested by the Servicer, the Issuer, the Seller or any of their Affiliates, in order to comply with or obtain more favorable treatment under any current or future law, rule, regulation, accounting rule or principle.

  • Information Request (a) The Owner Trustee shall provide any information regarding the Issuer in its possession reasonably requested in writing by the Servicer, the Administrator, the Seller or any of their Affiliates, in order to comply with or obtain more favorable treatment under any current or future law, rule, regulation, accounting rule or principle.

  • Information Required Such records must contain the name; Social Security number; last known address, telephone number, and email address of each such worker; each worker's correct classification(s) of work actually performed; hourly rates of wages paid (including rates of contributions or costs anticipated for bona fide fringe benefits or cash equivalents thereof of the types described in 40 U.S.C. 3141(2)(B) of the Xxxxx-Xxxxx Act); daily and weekly number of hours actually worked in total and on each covered contract; deductions made; and actual wages paid.

  • Contracting Information Requirements Contractor represents and warrants that it will comply with the requirements of Section 552.372(a) of the Texas Government Code. Except as provided by Section 552.374(c) of the Texas Government Code, the requirements of Subchapter J (Additional Provisions Related to Contracting Information), Chapter 552 of the Government Code, may apply to the Contract and the Contractor agrees that the Contract can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter.

  • Information Requirements (a) The Company covenants that, if at any time before the end of the Effectiveness Period the Company is not subject to the reporting requirements of the Exchange Act, it will cooperate with any Holder of Registrable Securities and take such further reasonable action as any Holder of Registrable Securities may reasonably request in writing (including, without limitation, making such reasonable representations as any such Holder may reasonably request), all to the extent required from time to time to enable such Holder to sell Registrable Securities without registration under the Securities Act within the limitation of the exemptions provided by Rule 144 and Rule 144A under the Securities Act and customarily taken in connection with sales pursuant to such exemptions. Upon the written request of any Holder of Registrable Securities, the Company shall deliver to such Holder a written statement as to whether it has complied with such filing requirements, unless such a statement has been included in the Company's most recent report filed pursuant to Section 13 or Section 15(d) of Exchange Act. Notwithstanding the foregoing, nothing in this Section 7 shall be deemed to require the Company to register any of its securities (other than the Common Stock) under any section of the Exchange Act.

  • Information Requirement The successful bidder's shall be required to advise the Office of Management and Budget, Government Support Services of the gross amount of purchases made as a result of the contract.

  • Documentation Required The certificates and endorsements shall be received and approved by the District before Work commences. As an alternative, the Contractor may submit certified copies of any policy that includes the required endorsement language set forth herein.

  • Data Submission Requirements As part of its registration and sponsorship of Registered Names in the Registry TLD, Registrar shall submit to the Registry System complete data as required by technical specifications of the Registry System that are made available to Registrar from time to time. Registrar hereby grants Registry Operator a non-exclusive, royalty free, non-transferable, limited license to such data for propagation of and the provision of authorized access to the TLD zone files and as otherwise required for Registry Operator to meet its obligations to ICANN and/or for Registry Operator’s operation of the Registry TLD.

  • Publication Requirements Those seeking to include renderings of more than 10 images from the UND Biometrics Database in reports, papers, and other documents to be published or released must first obtain approval in writing from the UND Principal Investigator. In no case should the face images be used in a way that could cause the original subject embarrassment or mental anguish.

  • Special Formalities and Information Requirements 1. Nothing in Article 10.3 shall be construed to prevent a Party from adopting or maintaining a measure that prescribes special formalities in connection with covered investments, such as a requirement that investors be residents of the Party or that covered investments be legally constituted under the laws or regulations of the Party, provided that such formalities do not materially impair the protections afforded by a Party to investors of the other Party and covered investments pursuant to this Chapter.

Time is Money Join Law Insider Premium to draft better contracts faster.