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

  1. Set a priority for each row before the RFP goes out: must, should or could. Evaluators score the musts first.
  2. 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.
  3. 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.

Permitting and licensing software requirements, with your priority and the vendor's response
RequirementWhat the vendor should showPriority (must, should, could)Vendor responseNotes
Applicants
Applicant guidePermit and license types, required documents and fees shown in everyday wording before an applicant starts, maintained by your staff without the vendor.
Online applicationApplications, uploads and payments online, on a phone as well as a computer.
Applying in personCounter staff can enter an application on behalf of someone who cannot or prefers not to apply online.
Status for applicantsApplicants can see where their application is and what is waiting on them, without calling.
NoticesEmails 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 AAConformance of every applicant-facing page, form, document and mobile app the vendor provides, and the date of the last test.
EvidenceAn accessibility conformance report based on testing, naming the pages tested, the method (automated and manual, with assistive technology) and the open issues.
Documents applicants useForms, 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 foundA contract commitment to fix conformance defects, with response times, at no extra charge.
Intake and review
Completeness checksRequired documents and information checked before an application reaches staff.
Parcel and zoningHow parcel number and zoning district reach each application: typed by staff, looked up, or sent from your GIS.
Parallel reviewBuilding, zoning, fire and other disciplines review at the same time, with one set of comments to the applicant.
ResubmittalsEach round's documents kept separately, with each discipline's earlier comments visible to reviewers.
ConditionsStandard and custom conditions of approval printed on the issued permit.
Fees and payments
Fee calculationFees calculated from your schedule, including flat, valuation-based and per-unit fees, shown by calculating sample applications from your own schedule.
Staff adjustmentsStaff can adjust or waive a fee, with the reason and the person recorded.
PaymentsWhich payment processors are supported, who holds the merchant account, and how payments, receipts and refunds are recorded against each fee.
Card securityWhich party is responsible for PCI DSS compliance for card payments, and how card data is kept out of the permitting system.
AccountingExports or reports that map fees to your general ledger accounts.
Inspections and licenses
Inspection requestsApplicants or contractors request inspections online; staff schedule them.
Field resultsInspectors record results, notes and photos on a phone or tablet, including where coverage is poor.
Licenses and renewalsBusiness and trade licenses tracked to expiry, with online renewal.
Records, data and security
Public records requestsHow staff find and export an application's full record, including documents and comments.
RetentionHow records are kept and disposed of under your retention schedule.
Data migrationWhat the vendor will migrate from your current system, in what condition, and what stays as reference only.
Your data at the endHow and in what format you get all your data back if the contract ends, and when the vendor deletes it.
Sign-in and rolesSingle sign-on for staff, roles that limit who can approve, adjust fees or issue, and an audit trail of changes.
Implementation and support
Implementation planWho configures permit types, documents and fees, how long it takes, and what your staff must provide.
TrainingTraining for counter staff, reviewers, inspectors and administrators, and materials you keep.
SupportSupport hours, response times and how issues are reported.
PricingAll 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.

Related Moraph software

If you would rather keep this in software

The templates work on their own, on paper or in a spreadsheet. Each product page lists what the product does, what it does not do, and how to arrange a demonstration.

More free templates: Free templates. Evaluating software? Buyer’s guides and How to buy.