Establishing secure connection…Loading editor…Preparing document…

Request for Proposal P20GB001

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

ASSUMPTION OF RISK, WAIVER, RELEASE, AND CONSENT FOR NON-STUDENT MINOR PARTICIPATION

ARIZONA BOARD OF REGENTS FOR AND ON BEHALF OF NORTHERN ARIZONA UNIVERSITY

Contracts, Purchasing and Risk Management

("PROGRAM")

928-523-4557

RETURN TO:

NAU-Insurance@nau.edu

PO Box 4067

Flagstaff, AZ 86011

Revised 01/30/2020

Program Information

THIS DOCUMENT HAS LEGAL CONSEQUENCES. IT MUST BE COMPLETED AND SIGNED PRIOR TO PARTICIPATION. PLEASE READ IT CAREFULLY BEFORE SIGNING.

Program Description and Dates:

Department Contact (name, e-mail, phone):

Program Location:

Specific Potential Risks to Participants:

Minor’s Information

Minor’s Name: Age:

Parent(s)/Legal Guardian(s):

Address:

City: State: Zip:

Phone: Cell: Work:

Emergency Contact: Relationship:

Phone:

Emergency Contact: Relationship:

Phone:

Authorized Pick-Up

Minor will be picked up at the end of the Program or for any authorized time spent off of campus by:

Name: Relationship:

Phone number(s):

Identification will be required to be shown to Program staff by the person who is picking up the Non-Student Minor. If the parent(s)/legal guardian(s) listed above is not the person picking up the Non-Student Minor, add name(s), relationship(s), and phone number(s) of other authorized individuals below.

IN ADDITION TO THE PARENT(S)/LEGAL GUARDIAN(S) LISTED ABOVE, THE FOLLOWING INDIVIDUALS ARE AUTHORIZED TO PICK UP NON-STUDENT MINOR:

Parent/Guardian Agreement

I affirm that I am the adult parent or legal guardian of , a Non-Student Minor under the age of eighteen (18), and I consent to their participation in this Program.

1. Acknowledge and understand the risks associated with participation in the Program.

2. Assume all of the foregoing risks and accept personal and financial responsibility for damages.

3. Agree not to sue and waive claims to the fullest extent allowed by law.

4. Grant permission for photography and use of likeness so long as the Image Release Form is signed.

5. Understand medical treatment limitations and financial responsibility.

6. Consent to emergency medical services as needed.

7. Agree to review Program rules and ensure compliance.

8. Waive and release claims arising when the minor is not under direct supervision.

9. Acknowledge the right to decline, decrease, or cease participation for illness or injury.

10. Understand participation may be reduced or stopped in the interest of safety.

11. Acknowledge reading and understanding the waiver and giving up substantial rights by signing it.

12. No oral or written representations can alter the contents of this document.

Parent/Legal Guardian Signature:

Date:

Medical Information

Provide a complete and accurate statement of the physical factors that may affect participation in the Program.

Local Physician preferred (if possible): Phone:

Insurance Company (if additional to Program insurance):

Policy: Group Number: Phone:

Please indicate any and all special medical conditions Northern Arizona University may need to know about:

List any allergies, to include but not limited to, any medications, food, insect bites, and stings, and describe allergic reactions:

List any and all medication(s) taken on a regular basis for any reason, to include but not limited to, medication taken for illness(es), allergies, pain and injuries (use additional paper if necessary):

List any additional medical/physical information that Northern Arizona University should be aware of, to include but not limited to fitness level, ability to swim, and mobility or sensory limitations:

Enter text✕

What the Request for Proposal P20GB001 Is

Request for Proposal P20GB001 is a procurement solicitation template used to invite competitive bids for goods, services, or projects under a defined scope of work. The document defines objectives, technical requirements, submission instructions, evaluation criteria, and contractual terms so prospective vendors can prepare compliant proposals. Agencies and organizations use an RFP of this form to standardize procurement, compare offers on the same basis, and create a transparent record of the award decision. It is typically published with a deadline, Q&A schedule, and delivery instructions for electronic or physical submissions.

Why Using a Standardized P20GB001 RFP Matters

A clear RFP reduces ambiguity, improves vendor comparability, and documents the procurement process for audit and compliance purposes.

Why Using a Standardized P20GB001 RFP Matters

Who Prepares and Responds to the P20GB001

Typical roles that create, manage, or respond to this RFP are listed below.

  • Procurement officers and contract managers preparing requirements and evaluation criteria for vendor selection.
  • Vendors and suppliers completing technical and commercial proposals to meet the stated scope of work.
  • Legal counsel and compliance teams reviewing terms, insurance requirements, and contract clauses.

Each role should follow organization policies for approvals and recordkeeping throughout the RFP lifecycle.

Stepwise Process to Prepare and Issue P20GB001

Follow these sequential steps to create, publish, and manage responses to the RFP.

  • 01
    Define Requirements: Draft scope, deliverables, and mandatory qualifications.
  • 02
    Set Evaluation: Establish scoring method and minimum thresholds.
  • 03
    Publish RFP: Post on procurement portal and notify vendors.
  • 04
    Collect & Evaluate: Accept proposals, score responses, and document decisions.

How Submissions and Evaluations Flow

A consistent submission workflow preserves evidence and supports a defensible award.

  • Upload: Vendors submit proposals to the stated portal or email.
  • Acknowledge: System sends receipt and timestamp to the submitter.
  • Preliminary Review: Procurement staff confirm completeness and mandatory forms.
  • Scoring: Evaluators score using published criteria and record notes.

Digital Workflow Settings to Configure

Configure the e-submission workflow before opening the RFP to ensure secure, auditable receipt of proposals.

Field Configuration
Authentication Method Email link or Multi-factor (SMS or SAML)
Submission Format PDF/A preferred; allow DOCX if redaction needed
Evaluation Rubric Numeric scores with required comment fields
Notifications Automate receipts and status updates to stakeholders

Technical Requirements for Electronic Submission

Verify platform capabilities before accepting electronic proposals to avoid compatibility issues.

  • File Formats: PDF, DOCX, XLSX supported
  • Integrations: Works with Google Drive and Box
  • Authentication: Email, SMS, or SSO available

Typical RFP Dates and Timing Considerations

RFP schedules differ by procurement type; publish clear dates and time zones to prevent disputes.

Issue Date:

Date the RFP is published and vendor outreach begins.

Question Deadline:

Deadline for vendor questions, often 10–14 days after issue date.

Submission Deadline:

Final date and time for proposals; late offers are usually rejected.

Evaluation Period:

Timeframe for scoring, clarifications, and reference checks.

Award Notice:

Date when the selected vendor is notified and contract negotiations begin.

Key Milestones from Release to Award

Track these milestones sequentially to maintain procurement integrity and audit readiness.

01

RFP Release

Publish document and post instructions for questions.

02

Q&A Window

Collect and answer vendor questions; issue amendments if needed.

03

Proposal Close

Lock submissions and generate timestamped receipts.

04

Award Decision

Score, rank, and authorize award or debriefings.

Common Preparation and Submission Errors to Avoid

  • Unclear scope of work leading to inconsistent proposals and excessive vendor questions.
  • Missing or mismatched solicitation number or attachments causing proposals to be routed incorrectly.
  • Failure to publish amendment notices resulting in noncompliant submissions and vendor disputes.
  • Not specifying submission format or authentication causing compatibility or receipt problems.

Consequences of Errors in the RFP Process

Bid Rejection: Noncompliant proposals may be disqualified
Procurement Delay: Missing information can delay award decisions
Debarment Risk: Serious procurement violations can trigger sanctions
Contract Disputes: Ambiguity increases litigation or protest likelihood
Financial Exposure: Incorrect pricing can lead to loss or penalties
Audit Findings: Incomplete records invite negative audit results

Security and Compliance Considerations

Encryption in Transit: TLS 1.2 / TLS 1.3
Encryption at Rest: AES-256 encryption
Compliance Reports: SOC 2 Type II available
International Standards: ISO 27001 certified
HIPAA Support: BAA required for PHI workflows
FDA Compliance: 21 CFR Part 11 supported

eSignature Vendor Pricing Snapshot for RFP Workflows

Compare common pricing and feature dimensions to match procurement volume and compliance needs; signNow is shown first per vendor ordering rules.

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 Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No envelope cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Real-World Examples of Electronic Procurement and Signatures

Organizations across sectors use eSignature workflows to speed approvals, maintain audit trails, and reduce paper handling.

Tech Data (Enterprise)

Tech Data standardized digital signing across internal and external contracts to speed revenue recognition.

  • Bulk send and template features supported high-volume procurement processes.
  • The company reported faster internal approvals and consistent audit trails after centralizing digital signature workflows across teams and systems.

Xerox (Integration)

Xerox integrated signing into NetSuite for procurement and vendor contracts.

  • API-based workflows automated signature capture and storage.
  • Integration reduced manual reconciliation and improved document format consistency while enabling programmatic access to signed contract records for reporting.

Frequently Asked Questions about P20GB001

Answers to common questions about electronic submission, signatures, and procurement compliance.


Need help? Contact support

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