Parties
Full legal names and entity types for NCSU, its unit, and the counterparty, including organizational addresses and contact persons for notices.
A correctly executed Legal NCSU Agreement clarifies rights and obligations, reduces litigation risk, and supports compliance with applicable electronic-signature law such as the federal ESIGN Act (15 U.S.C. ch. 96, 2000) and state UETA statutes (1999, ULC). Clear terms also simplify administration and records retention.
Typical authors, reviewers, and signers include university contracting officials, departmental administrators, campus legal counsel, and the external counterparty assigned to execute the document.
Use the internal routing and approval process at NCSU to ensure signatures are authorized and supporting documents are attached before finalizing execution.
Authorized institutional signers (contracts office or delegated official) must follow campus signature authority and confirm budget availability, insurance, and compliance with university policy before executing the agreement.
The counterparty signer should be an officer or agent with authority to bind their organization; include job title and corporate authority statement to avoid later disputes about execution authority.
Full legal names and entity types for NCSU, its unit, and the counterparty, including organizational addresses and contact persons for notices.
Clear effective date language and condition precedent wording if performance or funding depends on prior approvals.
Concise description of services, deliverables, milestones, and acceptance criteria, with exhibits or SOW attached where needed.
Payment terms, invoicing instructions, budget references, and any withholding or tax responsibilities.
Ownership and licensing of intellectual property, data rights, publications, and specific confidentiality obligations.
Termination triggers, notice periods, cure rights, indemnities, limitation of liability, and dispute resolution mechanisms.
| Field | Setting |
|---|---|
| Signature Type | eSignature required | Typed, drawn, or PKI |
| Authentication | Email or SMS code | Use stronger MFA for sensitive agreements |
| Conditional Logic | Enable conditional fields | Show based on role or checkbox |
| Retention Policy | Auto-archive executed copy | Retain per records schedule |
Choose a platform that supports required authentication, audit trails, and the file formats used by your office.
Ensure the platform can produce a tamper-evident signed PDF with an audit trail and supports your records-retention workflow.
Set an internal cut-off date for signatures to secure funding or start work.
List due dates for deliverables and acceptance review periods in the SOW.
Specify invoice submission timeline and payment terms to manage cashflow.
Independent-contractor payments may require 1099-NEC reporting by Jan 31.
Retention typically begins on the effective date or final payment date.
Save executed agreements as PDF/A or signed PDF to preserve appearance and audit metadata for long-term records.
Keep prior drafts and a single executed master copy; label versions clearly with date and approver initials.
Retain platform-generated audit trail showing signer, timestamp, IP, and authentication method for evidentiary value.
Include SOW, insurance certificates, budget, W-9 or vendor forms, and any IRB/FERPA approvals as exhibits.
A department engaged a vendor for lab supplies with an attached SOW and insurance
Two institutions agreed on data-sharing and IP terms with publication rights
| 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 | No | No | Yes, limited | Yes, limited |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |