Executive Summary
Summarize purpose, high-level objectives, key deliverables, major assumptions, and acceptance criteria. Provide a one-page overview suitable for funders and institutional leadership to approve next steps without technical detail.
A Research Scoping Study clarifies objectives, scope, resource needs, and risks before major investment. It reduces uncertainty in design, supports realistic budgeting, identifies compliance needs, and improves alignment between stakeholders and sponsors for stronger proposal and project outcomes.
Typical users who prepare or rely on a Research Scoping Study include project leads, institutional administrators, and external funders seeking early project clarity.
Use the study to brief leadership and secure approvals before committing to detailed protocols or significant expenditures.
Summarize purpose, high-level objectives, key deliverables, major assumptions, and acceptance criteria. Provide a one-page overview suitable for funders and institutional leadership to approve next steps without technical detail.
List prioritized research questions and hypotheses, indicate primary and secondary endpoints, and specify measurable outcomes. Tie questions directly to methodology choices and data needs to avoid misalignment during execution.
Describe study design options, sampling frames, analytic approaches, and validation plans. Note feasibility considerations, required expertise, and any pilot or phased approaches that reduce risk.
Identify datasets, ownership, licensing restrictions, expected formats, security requirements, and any institutional approvals or data use agreements needed before analysis can begin, with estimated timeframes for access approval.
List internal and external stakeholders, their roles, decision rights, contact information, and escalation paths. Include sponsors, data custodians, legal counsel, and operational leads and timeline responsibilities.
Provide an itemized budget aligned to tasks, assumptions for cost estimates, milestone schedule, contingency, critical path items, and responsible parties for each milestone that may affect delivery dates.
| Field | Configuration |
|---|---|
| Signature Authentication | Use email, SMS, or SSO; enable 2FA for HIPAA |
| Conditional Sections | Show or hide fields based on prior answers |
| File Attachments | Allow upload of datasets, IRB approvals, and DUAs |
| Retention Policy | Set read-only archival PDF retention and access roles |
Choose secure distribution channels that preserve signed PDFs, audit trails, and access controls appropriate to data sensitivity.
| 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 trial, no credit card | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes (Business Premium) | Yes | Yes | Yes | Yes |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes (BAA) | Yes (BAA) | Yes (BAA) | No | No |
A university team used a scoping study to define multi-site data sharing needs and IRB dependencies before grant submission.
A hospital research office completed a scoping study to assess PHI access requirements and BAA needs for a pilot analytics project.
Allow 1–3 weeks for internal administrative review and route approvals.
Expect 4–12 weeks depending on review type and amendments.
Plan 2–8 weeks for DUAs, licensing, and security reviews.
Budget and scope negotiations typically take 2–6 weeks.
Allow several business days for signatures and archival procedures.
Prepare initial draft with objectives, methods, and stakeholder list.
Circulate to institutional offices for feedback and risk assessment.
Obtain IRB clearance, DUAs, and any required data approvals.
Execute signatures, save READ-ONLY PDFs, and record version history.