Research Project Move Form
What the Research Project Move Form Is
Why a Clear Move Form Matters
A complete Research Project Move Form minimizes administrative delays, protects human-subjects protections and data privacy, preserves funding continuity, and documents transfer of obligations between institutions under grants and contracts.
Typical Users and Responsibilities
Multiple stakeholders complete or review the form to confirm approvals, funding transfer, and compliance requirements before the move.
- Principal investigator or project lead: submits form, confirms resource needs, and signs to transfer project oversight.
- Institutional official (grants/contracts/technology transfer): verifies sponsor consent, budget adjustments, and IP assignments.
- Research compliance officer or IRB liaison: confirms IRB approvals, data transfer agreements, and privacy safeguards.
Use institutional routing rules to ensure each role signs in the correct order and that required attachments are included before submission.
Step-by-step process to complete and route the form
-
01Prepare: Collect grant, IRB, and equipment inventories for attachments.
-
02Route for Approvals: Send to PI, grants office, IRB liaison, and TTO in role order.
-
03Obtain Sponsor Consent: Notify sponsor as required and attach written approvals.
-
04Finalize: Confirm signatures, update records, and archive executed form.
How to set up a digital routing workflow
| Field | Configuration |
|---|---|
| Signer Order | PI → Grants Office → IRB → Receiving Official |
| Required Attachments | Grant award, IRB approval, equipment list |
| Authentication | Email link with optional SMS code |
| Retention Setting | Archival copy saved to institutional records system |
Typical electronic submission flow
-
Upload: Origin uploads form and attachments.
-
Place Fields: Assign signature, date, and checkbox fields.
-
Send: Route using role-based signer order.
-
Complete: Signed copies and audit trail are stored.
Technical considerations for eSubmission and eSigning
Choose a platform that supports enforceable electronic signatures, secure storage, and institution-level access controls.
- Document formats: PDF and DOCX support
- Integrations: Connectors to Google Workspace, Microsoft 365, and institutional repositories
- Authentication: Email links, SMS codes, or stronger 2FA
Ensure the platform preserves an audit trail (timestamps, IP addresses, signer attribution) and supports your institution's record retention policy.
Key deadlines and processing expectations
Sponsor Notification Deadline:
Follow sponsor terms; many require notice before any substantive change.
IRB Amendment / Approval:
Submit amendment before data transfer or subject contact.
Grant Office Processing:
Allow 2–4 weeks for internal review and budget adjustments.
Payroll / Effort Reporting:
Coordinate before the next payroll cycle to align effort allocations.
Equipment Transfer:
Schedule shipping and inventory reconciliation before handover.
Common pitfalls to avoid when preparing the form
- Missing sponsor approval language: failing to attach written sponsor consent can halt the transfer and delay funding.
- Incomplete IRB documentation: omitting IRB amendments or approvals risks noncompliance with 45 CFR Part 46 obligations.
- Unclear IP or data ownership terms: vague assignment clauses can trigger disputes about future commercialization or data access.
- Incorrect signatory authority: using a person without delegated authority may render the transfer unenforceable or require re-execution.
Consequences of errors or incomplete transfers
eSignature vendor pricing and feature comparison
| 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 | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes (Premium) | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies | Varies | Varies |
Frequently asked questions about form use and legal effect
-
Who can sign to transfer a project?
Authorized institutional representatives must sign; the PI's signature alone may not transfer contractual obligations. Verify delegated signing authority in institutional policy and grant terms.
-
Is an eSignature legally binding?
Yes in most cases under the ESIGN Act (15 U.S.C. ch. 96) and state UETA rules; exceptions include certain testamentary documents and specific court filings.
-
Do I need IRB approval before moving data?
Yes. Amend or transfer the protocol per IRB requirements before data transfer to avoid noncompliance with human subjects protections.
-
When is notarization required?
Notarization is required where the receiving or origin institution or state law demands notarized acknowledgements; check state or institutional rules for signature authentication.
-
How is patient or subject data protected during transfer?
Use encryption in transit and at rest, signed data use agreements, and, when applicable, a HIPAA-compliant BAA per 45 CFR §164.530(j).
-
Can I amend the form after signatures?
Yes, but amendments typically require the same signing sequence and documentation as the original transfer; record the amendment and retain both versions for audits.