Establishing secure connection…Loading editor…Preparing document…

Legal Request LTB PIN

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

LEGAL REQUEST LTB PIN

This Legal Request for issuance of a Landlord and Tenant Board Personal Identification Number ("LTB PIN") is entered into on the day of , by and between Applicant Name: of Address: (the "Applicant") and Recipient Name: of Address: (the "Recipient").

RECITALS

WHEREAS the Applicant is a party to one or more matters before the Landlord and Tenant Board and requires an LTB PIN to access electronic services and filings in relation to the Applicant's matters, including but not limited to filings, case management, and communications;

WHEREAS the Recipient is authorized to request issuance of an LTB PIN on behalf of the Applicant or to act as an intermediary in the transmission of credentials to the Applicant under the Recipient's security controls;

WHEREAS the Parties wish to set out the terms and conditions under which the LTB PIN will be requested, issued, used, and revoked.

NOW THEREFORE, in consideration of the mutual covenants contained herein and other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, the Parties agree as follows:

1. REQUEST FOR LTB PIN

The Applicant requests that the Recipient submit an application for issuance of an LTB PIN in respect of the Applicant's access to the Landlord and Tenant Board electronic services for the following matter(s): File Number(s): . The Recipient agrees to submit such request in accordance with the Board's procedures and in compliance with the representations and warranties set forth in this document.

2. AUTHORIZATION; REPRESENTATIONS

The Applicant hereby authorizes the Recipient to act on the Applicant's behalf to request and receive an LTB PIN. The Applicant represents and warrants that all information provided to the Recipient for the purpose of requesting the LTB PIN is true, accurate and complete, and that the Applicant is authorized to seek access for the matter(s) identified above.

3. IDENTITY VERIFICATION

The Applicant shall provide satisfactory identification documentation to permit issuance of a PIN. Type of identification provided (check all that apply):

Identification details: ID Number: Issuing Authority: .

4. USE, SECURITY AND CONFIDENTIALITY

The Applicant shall use the LTB PIN solely for the purposes of accessing the Applicant's LTB matter(s) and related electronic services. The Applicant acknowledges and accepts responsibility for maintaining the confidentiality and security of the LTB PIN and for all activity that occurs under the Applicant's account. The Applicant shall implement commercially reasonable administrative, technical and physical safeguards to prevent unauthorized access, use or disclosure of the PIN.

If the Applicant knows or reasonably suspects that the PIN has been compromised, lost or used without authorization, the Applicant shall immediately notify the Recipient in writing and request revocation of the PIN.

5. LIMITATIONS ON USE

The PIN is personal to the Applicant and shall not be assigned, transferred, sold or otherwise disclosed to any third party except as expressly permitted in writing by the Recipient. Use of the PIN by persons other than the Applicant in violation of this provision constitutes a material breach of this Request.

6. LIABILITY AND INDEMNITY

The Applicant acknowledges that the Recipient does not create, control or guarantee the security of the Board's systems. To the maximum extent permitted by law, the Applicant releases and holds harmless the Recipient from any loss, liability, claim or expense arising from issuance, use, misuse, suspension or revocation of the LTB PIN, except to the extent caused by the Recipient's gross negligence or willful misconduct.

The Applicant agrees to indemnify and defend the Recipient against all claims, damages, losses and expenses (including reasonable legal fees) arising from the Applicant's breach of this Request or misuse of the PIN.

7. TERM; REVOCATION

This Request remains in effect until revoked in writing by either Party. The Recipient may suspend or revoke the PIN immediately upon reasonable belief of misuse, compromise, or upon request by the Applicant. Revocation does not relieve the Applicant from obligations or liabilities incurred prior to revocation.

8. NOTICES

All notices, requests and other communications under this Request shall be in writing and delivered to the addresses set out below:

9. AMENDMENTS; WAIVER

No amendment to this Request shall be effective unless in writing and signed by both Parties. Waiver of any provision or breach shall not constitute waiver of any other provision or subsequent breach.

10. GOVERNING LAW

This Request shall be governed by and construed in accordance with the laws of the province or territory in which the Applicant's primary address is located, without regard to rules governing choice of law.

11. ENTIRE AGREEMENT

This Request constitutes the entire agreement between the Parties with respect to the subject matter hereof and supersedes all prior agreements, understandings and negotiations, whether written or oral.

12. SEVERABILITY

If any provision of this Request is held to be invalid, illegal or unenforceable for any reason, the remaining provisions shall continue in full force and effect to the fullest extent permitted by law.

13. COUNTERPARTS

This Request may be executed in counterparts, each of which shall be deemed an original, and all of which together shall constitute one and the same instrument. Signatures transmitted by electronic means shall be effective as originals.

14. ADDITIONAL INFORMATION

Applicant:

By:

Date:

Recipient:

By:

Date:

Enter text✕

What the Legal Request LTB PIN Is and why it exists

The Legal Request LTB PIN is a standardized request form used to obtain a secure Personal Identification Number (PIN) linked to a legal matter or case reference. It documents the requester, the purpose for the PIN, the identity of the recipient, and any time limits or conditions on use. The form is intended to create an auditable record that supports secure transmission, authentication, and traceability of a PIN in legal workflows, including internal counsel requests, client authorizations, and government-facing submissions. Proper completion improves acceptance and reduces administrative delay.

Why a formal Legal Request LTB PIN matters

A formal request creates a clear chain of custody for a PIN, documents authorization and purpose, and reduces disputes about who requested or received access. It standardizes information needed by receiving parties and supports later audits or investigations.

Why a formal Legal Request LTB PIN matters

Who typically completes or receives this request

The Legal Request LTB PIN is used by internal teams and external parties that require controlled access to a legal account, file, or portal. Use the examples below to match your role to the correct fields.

  • In-house counsel and paralegals responsible for case access and evidence retrieval; they include case ID and authorization scope.
  • Compliance and security teams issuing temporary access for investigations or vendor support; they attach approval records.
  • External attorneys or authorized agents requesting access on behalf of clients; they provide engagement letters or power of attorney.

If your role is not listed, follow the step-by-step fill instructions and include organizational authorization documentation with the request.

Representative signers and submitters

Corporate Counsel

General counsel or delegated legal staff may sign to request a PIN on behalf of the company. Include a line showing delegation (title) and attach an authorization memo if the requestor is not the named client representative.

Authorized Agent

Outside counsel, a registered agent, or another authorized representative must attach proof of representation such as a signed retainer, limited POA, or court order that specifically authorizes the PIN request.

Security, compliance and technical details to include

Encryption: AES-256 at rest; TLS 1.2/1.3 in transit
Authentication: Multi-factor recommended (SMS, email, KBA)
Audit Trail: Timestamp, IP, signer actions
BAA Availability: Required for HIPAA workflows
Regulatory Coverage: ESIGN and UETA compliant
Accessibility: WCAG 2.0 Level AA support

Key risks and potential consequences of errors

Access Delays: Missing data can delay PIN issuance
Rejection: Incomplete authorization may be rejected
Regulatory Fines: Data breaches can trigger HIPAA/CCPA penalties
Legal Challenge: Incomplete records weaken evidentiary value
Tax/Reporting Penalties: Incorrect info can trigger filing penalties
Operational Risk: Unclear scope leads to misuse of credentials

Common preparation pitfalls to avoid

  • Omitting firm or client authorization details, which causes processing delays.
  • Using informal signatures without intent evidence or audit trail for electronic submissions.
  • Providing inconsistent name or ID data that prevents identity verification.
  • Failing to attach required supporting documents such as engagement letters or powers of attorney.

Step-by-step: completing the Legal Request LTB PIN

Follow these steps in order to prepare and submit a complete request that supports verification and timely processing.

  • 01
    Identify Requestor: Enter your full legal name and official title
  • 02
    Specify Recipient: Provide the exact account or case identifier
  • 03
    Purpose & Scope: Describe why the PIN is needed and duration
  • 04
    Attach Authorization: Include retainer, POA, or internal approval

How to set up an electronic workflow for PIN requests

Configure an eSubmission workflow that captures identity proofing, attachments, and an audit trail to simplify approvals and recordkeeping.

Field Configuration
Requestor Field Required; auto-validate email domain
Attachment Slot PDF required; max 10 MB
Authentication Email + SMS code recommended
Approval Route Role-based sign-off chain

Digital signing and eSubmission considerations

Choose a platform that provides secure eSigning, an audit trail, and appropriate authentication for the sensitivity of the PIN transaction.

  • File Formats: PDF and DOCX supported
  • Integrations: CRM and document storage integrations
  • Authentication: SMS, email, or KBA options

Typical eSubmission flow for PIN requests

This sequence shows a standard online submission and approval path to obtain a PIN while preserving verification artifacts.

  • Prepare Request: Complete form fields and attach authorizations
  • Submit: Send to the receiving authority or portal
  • Verify Identity: Recipient confirms identity per policy
  • Issue PIN: PIN delivered and logged with audit trail

Core information elements every professional request should include

A complete Legal Request LTB PIN includes administrative, identity, purpose, and verification elements so the recipient can approve and record the issuance with confidence.

Requestor Identity

Full legal name, role, organization, and contact information.

Recipient Identifier

Exact case, account, or system ID to which the PIN will apply.

Purpose Statement

Clear explanation of why access is requested and for how long.

Authorization Proof

Engagement letter, power of attorney, or internal approval document.

Authentication Details

Requested authentication method for delivery (SMS, email, secure portal).

Retention Note

Statement of how the request and PIN will be stored and for how long.

Download, save, and supporting documents to attach

Prepare supporting files in standard formats; include only what is necessary to verify authority and identity.

Accepted Formats

PDF preferred; DOCX accepted for drafts; maximum attachment size often specified by recipient.

Required Attachments

Engagement letter, POA, or signed authorization that names the requester and scope.

Optional Evidence

Photo ID scanned copy, corporate resolution, or billing authorization when requested.

Save Copies

Keep signed PDF and audit certificate in secure records for retention compliance.

Practical tips for accurate and efficient completion

Small changes to how you prepare requests reduce delays and rejections—follow these best practices consistently.

Use precise identifiers
Match case or account numbers exactly and avoid abbreviations that impede lookups.
Attach proof early
Include authorization documents with the initial submission to prevent hold-and-request cycles.
Prefer electronic signatures
Ensure signatures include intent and an audit trail compliant with ESIGN/UETA standards.
Log follow-ups
Record submission dates and any communication to track processing timelines effectively.

Timelines, expected processing times, and deadlines

Processing times and deadlines depend on recipient policies; plan ahead and document the requested delivery timeframe in the request.

Typical Review Time:

3–10 business days depending on verification needs

Urgent Requests:

Mark as urgent and supply immediate contact info

Extension Requests:

State why an extension is needed and who approved it

Audit Retention:

Retain request and response for the prescribed retention period

Follow-up Window:

If no response within 10 business days, recheck submission and delivery logs

eSignature pricing and capability comparison for processing PIN requests

Comparing common eSignature providers helps select a platform that meets security, compliance, and volume needs. signNow is listed first for reference.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial Yes Yes Yes Yes
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
Envelope Cap No cap 100 env/user/yr Varies Varies Varies

Use-case examples showing how organizations request and receive PINs

These short examples show real-world scenarios and how a complete request supports a smooth issuance.

Case Study 1

A corporate legal team requested a portal PIN to retrieve client records for litigation on behalf of the company.

  • The request included an engagement letter and ID verification.
  • The recipient approved the PIN within three business days after validating the attached authorization and audit trail.

Case Study 2

A healthcare practice needed a temporary PIN for a vendor to access billing records for reconciliation.

  • The submission included HIPAA authorization and BAA confirmation.
  • The secure eSubmission with audit logs allowed the vendor limited access and provided the practice with a retained record for compliance.

Frequently asked questions and troubleshooting for Legal Request LTB PIN

Answers to common questions about required fields, authentication, and what to do when a request is delayed or rejected.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users