Permitting and licensing software RFP template
Requirements written so that a vendor's answer can be checked, grouped the way a small permitting office works, with columns for your priority and the vendor's response.
This is the requirements part of a request for proposals, not the whole document: your purchasing office supplies the instructions, terms and evaluation method. The requirements are vendor-neutral. Delete the ones that do not apply, and add the ones your codes, your state and your other systems call for.
The accessibility rows follow 28 CFR part 35, subpart H, which applies WCAG 2.1 Level A and AA to web content and mobile apps a public entity provides through contractual, licensing or other arrangements [2].
How to use it
- Set a priority for each row before the RFP goes out: must, should or could. Evaluators score the musts first.
- Ask vendors to answer every row with one of: available now, available by configuration, planned (with a date), or not offered, and to explain in the notes.
- Ask for a demonstration of the musts using your own permit types, and keep the vendor’s written answers as part of the contract.
The template
Download as CSV Opens in Excel, Numbers or Google Sheets. To print, use your browser’s Print command.
| Requirement | What the vendor should show | Priority (must, should, could) | Vendor response | Notes |
|---|---|---|---|---|
| Applicants | ||||
| Applicant guide | Permit and license types, required documents and fees shown in everyday wording before an applicant starts, maintained by your staff without the vendor. | |||
| Online application | Applications, uploads and payments online, on a phone as well as a computer. | |||
| Applying in person | Counter staff can enter an application on behalf of someone who cannot or prefers not to apply online. | |||
| Status for applicants | Applicants can see where their application is and what is waiting on them, without calling. | |||
| Notices | Emails when an application is received, needs corrections, is issued, denied or withdrawn, and when an inspection is scheduled or resulted; wording your department can set. | |||
| Accessibility (28 CFR part 35, subpart H) | ||||
| WCAG 2.1 Level A and AA | Conformance of every applicant-facing page, form, document and mobile app the vendor provides, and the date of the last test. | |||
| Evidence | An accessibility conformance report based on testing, naming the pages tested, the method (automated and manual, with assistive technology) and the open issues. | |||
| Documents applicants use | Forms, receipts and issued permits produced by the system are accessible, or the vendor says which are not and when they will be. | |||
| Fixing what is found | A contract commitment to fix conformance defects, with response times, at no extra charge. | |||
| Intake and review | ||||
| Completeness checks | Required documents and information checked before an application reaches staff. | |||
| Parcel and zoning | How parcel number and zoning district reach each application: typed by staff, looked up, or sent from your GIS. | |||
| Parallel review | Building, zoning, fire and other disciplines review at the same time, with one set of comments to the applicant. | |||
| Resubmittals | Each round's documents kept separately, with each discipline's earlier comments visible to reviewers. | |||
| Conditions | Standard and custom conditions of approval printed on the issued permit. | |||
| Fees and payments | ||||
| Fee calculation | Fees calculated from your schedule, including flat, valuation-based and per-unit fees, shown by calculating sample applications from your own schedule. | |||
| Staff adjustments | Staff can adjust or waive a fee, with the reason and the person recorded. | |||
| Payments | Which payment processors are supported, who holds the merchant account, and how payments, receipts and refunds are recorded against each fee. | |||
| Card security | Which party is responsible for PCI DSS compliance for card payments, and how card data is kept out of the permitting system. | |||
| Accounting | Exports or reports that map fees to your general ledger accounts. | |||
| Inspections and licenses | ||||
| Inspection requests | Applicants or contractors request inspections online; staff schedule them. | |||
| Field results | Inspectors record results, notes and photos on a phone or tablet, including where coverage is poor. | |||
| Licenses and renewals | Business and trade licenses tracked to expiry, with online renewal. | |||
| Records, data and security | ||||
| Public records requests | How staff find and export an application's full record, including documents and comments. | |||
| Retention | How records are kept and disposed of under your retention schedule. | |||
| Data migration | What the vendor will migrate from your current system, in what condition, and what stays as reference only. | |||
| Your data at the end | How and in what format you get all your data back if the contract ends, and when the vendor deletes it. | |||
| Sign-in and roles | Single sign-on for staff, roles that limit who can approve, adjust fees or issue, and an audit trail of changes. | |||
| Implementation and support | ||||
| Implementation plan | Who configures permit types, documents and fees, how long it takes, and what your staff must provide. | |||
| Training | Training for counter staff, reviewers, inspectors and administrators, and materials you keep. | |||
| Support | Support hours, response times and how issues are reported. | |||
| Pricing | All costs for the term: subscription, implementation, payment processing, integrations and storage, and how prices change at renewal. | |||
Whether a product conforms to WCAG 2.1 is shown by testing. Ask how and when it was tested, by whom, and against which pages; a conformance report is only as good as that testing.
This is general information, not legal advice. For what a rule requires of your organization, read the rule itself or ask your counsel.