FLPPR
Florida Private Provider Registry

Electronic Signature Statements

Version v0.1
Effective 2026-08-14

DRAFT v0.1 — for review, not yet in force

This document holds the operative statement texts shown at each signing moment on the Platform. Each statement is versioned independently; the e_signatures evidence record stores the statement version signed, the signer's typed signature, name, title, capacity, timestamp, IP address, user agent, and a content hash of the statement text as displayed.

Statement texts are immutable once in force — changes create a new version, and prior signatures always reference the version actually signed.

1. Electronic Signature Consent (shown before every signing act)

Version: consent-v1.0

By typing your name below, you are signing electronically. You agree that your typed signature, together with your name, title, and the recorded date and time, has the same legal effect as a handwritten signature, consistent with section 553.791(1)(g), Florida Statutes, and Florida's Uniform Electronic Transaction Act, section 668.50, Florida Statutes. You consent to conducting this transaction by electronic means and to FLPPR's retention of the signing record, which will be available to you on request.

Do not sign unless you are the named individual and you are authorized to make this statement.

2. Jurisdiction Enrollment Statement

Version: jurisdiction-enrollment-v1.0 Capacity: jurisdiction_official · Subject: jurisdiction_enrollment Shown at: participation activation, together with the Jurisdiction Participation Agreement (v-current) and the Terms of Service (v-current), both displayed in full or by link with version identifiers.

I, [full name], [title], am an authorized official of [jurisdiction name] with authority to bind it to the FLPPR Jurisdiction Participation Agreement (version [X]).

On behalf of [jurisdiction name], I:

  1. Adopt FLPPR as an electronic method for [jurisdiction name] to receive and maintain private provider registrations under section 553.791(4), Florida Statutes;
  2. Accept each active registration maintained on FLPPR, and each update to it, as a registration submission received by [jurisdiction name] while its participation is active;
  3. Agree to the Jurisdiction Participation Agreement (version [X]) and the FLPPR Terms of Service (version [Y]).

Typed signature: ______________ Date/time: [recorded automatically]

3. Firm Engagement Affirmation — Base Statement

Version: engagement-affirmation-v1.0 Capacity: firm_officer · Subject: engagement_affirmation Shown at: creating an engagement, or changing its relationship type or roster role. Bracketed clauses are included conditionally based on the engagement's facts.

I, [full name], [title], am an officer or authorized signer of [firm name] and am authorized to make this affirmation on its behalf.

I affirm that [professional name], license [license number(s)], is engaged by [firm name] as a [qualifier / duly authorized representative] and that their relationship to the firm is: [employee / agent / officer / partner].

[Included when roster role = duly authorized representative performing inspections:] I further affirm that [professional name] is an employee of [firm name] entitled to receive reemployment assistance benefits under chapter 443, Florida Statutes, as required by section 553.791(9), Florida Statutes, for a duly authorized representative who performs inspections.

[Included when the professional holds only a provisional certificate:] I further affirm that [professional name] performs services under the direct supervision of [supervisor name], a licensed building code administrator engaged by [firm name], as required by section 553.791(1)(f), Florida Statutes.

I understand that participating jurisdictions rely on this affirmation as part of [firm name]'s registration, that a false affirmation may result in suspension or termination of the firm's registry access and correction or withdrawal of registration information delivered to jurisdictions, and that this affirmation must be renewed if the relationship type or roster role changes.

Typed signature: ______________ Date/time: [recorded automatically]

4. Assembly Rules (for implementation)

  • Render the consent block (§1) above the operative statement at every signing moment; both texts' versions and hashes go into the e_signatures row.
  • Substitute all bracketed fields from live data before display; the hash is computed over the text as displayed to the signer.
  • Conditional clauses in §3 are included or omitted per the engagement's roster_role, relationship_type, and license class — never shown grayed-out.
  • Any wording change, however small, is a new version (v1.1, v2.0, …) with a changelog entry here. Old versions are never edited.