I Am The Petitioner Co Petitionerrespondent Other Identify Relationship Form
Use a I Am The Petitioner Co PetitionerRespondent Other identify Relationship template to make your document workflow more streamlined.
What this relationship form identifies
This form identifies whether the person completing it is the petitioner, co-petitioner, respondent, or another participant, and records that person’s relationship to the matter. Because the title does not identify an issuing agency, case type, or filing program, the required fields and legal effect depend on the accompanying application or proceeding. In signNow, a sender can upload the form, review detected fields, assign each field to the correct participant, send it for signature, and retain the completed copy with its audit trail. Confirm agency-specific instructions before filing.
Who should complete this relationship form
Petitioners
A petitioner or co-petitioner uses the form to identify their role in a filing, then checks the completed relationship entry against the underlying case or application before signing.
Other participants
A respondent or other identified participant uses the form to state their relationship accurately. The receiving agency, court, or organization—not this generic title—determines whether the form is sufficient and where it must be submitted.
Business types that can use this form
The form is most useful where several participants must state and confirm their relationship to one petition, case, or application.
Solo immigration practitioners can use a reusable relationship-form template to identify each petitioner, co-petitioner, or respondent before assembling the client’s filing packet. Legal-services teams can route the form by role, preserve the signer’s completed relationship entry, and attach the audit trail to the matter record. Government-facing organizations can collect participant acknowledgments electronically while applying their own agency instructions for identity proofing, filing, and records retention.
These tasks are executed by both individual contributors and centralized administrators depending on organizational policy and required controls.
Complete the relationship form online
Prepare the document, identify every participant, and verify the relationship entry before sending it for signature.
Upload:
Upload the relationship form to signNow. Check fields:
Review detected fields and add missing fields. Assign roles:
Assign each field to the correct participant. Send:
Send the form or create a signing link. Verify:
Review the signed copy and audit trail.
Best ROI. Our customers achieve an average 7x ROI within the first six months.
Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
Intuitive UI and API. Sign and send documents from your apps in minutes.
Choose a method for sending and signing
- Use the signNow web app when preparing the relationship form, assigning petitioner or respondent fields, and checking the completed document on a larger screen.
- Use the signNow mobile app when a participant needs to review and sign the relationship form from an iOS or Android device.
- Use kiosk mode when several participants complete the same relationship form at one supervised location and each person must sign in sequence.
- Use a shareable signing link when the responsible participant needs access without receiving a separate email invitation for this relationship form.
How the audit trail records this form
The audit trail connects the relationship selection, signer activity, timestamps, and completed document for later review.
Signer access:
Identity record:
Timestamp capture:
Document history:
Audit retrieval:
Secure export:
Recommended workflow configuration
Use role-specific routing, an accessible signature method, and preserved audit evidence while applying the governing filing and retention rules.
| Setting | Recommendation |
|---|---|
| Authentication method | Email invitation with SMS verification |
| Signature type | Typed or drawn electronic signature |
| Audit trail | Capture timestamps and signer actions |
| Document retention | Follow the receiving authority’s schedule |
| Encryption | TLS 1.2/1.3 and AES-256 |
Security controls for this form
Transport encryption:
Stored-data encryption:
Security reporting:
Information security:
U.S. eSignature framework:
Health information:
Relationship and disclosure pitfalls
Selecting “other” without explaining the relationship can leave the receiving reviewer unable to connect the signer to the underlying petition or case. Entering a relationship that conflicts with the main filing may trigger a request for clarification or delay review of the complete submission. Sending the form to the wrong participant can produce an accurate signature on the wrong person’s role and weaken the filing record. Failing to retain the signed form and audit trail can make it harder to demonstrate who selected the relationship and when.
Record-keeping practices for this form
Accurate role matching, controlled access, and a preserved audit trail make the completed relationship form easier to review and retrieve.
Confirm the underlying filing instructions
Reconcile participant roles before sending
Export the signed record and audit trail
Apply the correct retention rule
Troubleshoot this relationship form
These answers address role assignment, electronic consent, privacy, and signNow workflow issues without replacing the receiving authority’s filing instructions.
The title does not identify an issuing agency or case type. Treat it as a template label, confirm the underlying filing instructions, and verify required fields before using signNow’s upload and field-detection workflow.
signNow can route petitioner, co-petitioner, respondent, or other-participant fields to named signers. The sender must still confirm that each assigned signer matches the underlying petition or application.
A signNow Business plan includes legally binding eSignatures, templates, and audit trails. The plan does not determine whether an agency accepts this particular form; that question depends on the receiving authority’s rules.
For consumer-facing electronic records, ESIGN requires disclosure of the right to paper, electronic-access capability, and a withdrawal process under 15 U.S.C. §7001(c). Apply those requirements when this form is used with consumers.
If the relationship form contains protected health information, signNow identifies HIPAA compliance as requiring a BAA. Confirm that the organization has the required BAA and applies its own privacy and access controls.
If a recipient cannot sign, check the invitation address, resend the request, or provide a signing link. The sender should not change the participant’s relationship merely to complete the workflow.
Key performance indicators that demonstrate SignNow's proven track record.
BE READY TO GET MORE
Get this form now!
If you believe that this page should be taken down, please follow our DMCA take-down process.