Start your research with clarity. This one-page guide shows researchers how to capture key choices about creation, storage, access and reuse in a compact, usable form.
Think of the document as a living checklist. It records ownership, back-up routines, file formats, version control and who is responsible for each task. Early planning reduces the chance of privacy breaches and lost work, and it keeps your team aligned with the Australian Research Council’s expectations.
Use this template to turn broad requirements into repeatable steps. Link to institutional resources, note hardware needs, and make sharing or archiving decisions clear. When everyone knows the workflow, the project runs smoother and outputs are easier to reuse.
Keep it simple, keep it useful. A short, well-kept plan becomes an asset for publications, translation and long-term impact across Australian research projects.
Key Takeaways
- Treat the DMP as a practical one-page guide for your research team.
- Plan early to avoid breaches and loss, and to meet ARC expectations.
- Define clear roles, back-ups, naming and versioning workflows.
- Connect the plan to institutional repositories and ARDC guidance.
- Use the template for onboarding, compliance checks and milestones.
Why a DECRA data management plan matters for Australian research success
A short, clear approach to handling project assets saves time and prevents costly mistakes.
Good stewardship at the start makes research more reliable and easier to publish. Robust research data management prevents loss, reduces privacy risks and keeps your team aligned with ARC and NHMRC expectations.
Early thinking about storage, backup and access wins back valuable time. It replaces rushed fixes near deadlines and keeps workflows smooth during peak activity.
Funding and compliance become easier when you can show clear commitments to responsible practice. Many institutions and ARDC offer templates and tools to help researchers create a concise one-page document at project initiation.
- Make findings findable and secure so outputs can be reused across projects.
- Clarify roles and access so everyone knows what to do and when.
- Use simple, repeatable patterns to scale good practice across teams.
- Keep the guide live — update it as the work evolves to retain relevance.
Aligning with ARC, NHMRC and the Australian Code for the Responsible Conduct of Research
Set out how your team will meet ARC and NHMRC expectations before fieldwork begins. This helps reviewers and administrators see you have used institutional infrastructure and discipline standards.
ARC requires a one-page record to be in place prior to project commencement. It does not require submission, nor does it mandate open access. The focus is on sound stewardship and encouraged reuse when feasible.
ARC expectations
Reference institutional storage, repository and publishing pathways. Make responsibilities explicit so researchers know who approves access and who handles security.
NHMRC and the Australian Code
Follow the Australian Code for the Responsible Conduct of Research to protect participants and support ethical access and reuse. Describe embargo rules and repository deposit on acceptance.
“Responsible conduct underpins trust in research and makes outputs reusable where appropriate.”
| Requirement | Action | Who | Timing |
|---|---|---|---|
| Pre-commencement record | Document storage and access routes | Project lead & institution IT | Before start |
| Ethics and privacy | Describe safeguards and embargoes | HREC & data custodian | During set-up |
| Publication pathway | Repository deposit on acceptance | Researcher & library | At publication |
| Cross-institution work | Ensure compatible storage and metadata | Collaborating institutions | Planning phase |
How to create an ARC-ready DECRA data management plan
Begin with a clear inventory of existing material, then state what new outputs the project will produce.
Define your research outputs: types, volume, formats and standards
Note current files and list new research outputs with expected sizes and formats. Name any discipline standards or schemas you will follow.
Assign roles and responsibility across the project team
Make each task explicit: access approvals, quality checks, metadata capture and repository deposit. Attach a single owner to each task for swift decisions.
Plan storage, backup and secure access from day one
Specify primary and secondary storage locations, backup cadence and testing schedules. State who has access and how credentials are granted and revoked.
Set naming conventions, version control and collaborative writing practices
Use a short, consistent pattern: Project_Year_Subject_Version.ext as an example. Adopt simple version rules and a single collaborative editing tool for manuscript work.
Document ownership, licensing, sharing and embargoes
Record legal ownership, preferred licences and any embargo periods so publication and archiving proceed without delay.
Describe metadata, documentation and provenance for reuse
List core metadata fields and provenance notes you will capture. Link to discipline metadata standards to boost discoverability and reuse.
Detail transfer, synchronisation and hardware needs
Plan secure transfer routes, checksums and synchronisation intervals. Note any large-storage hardware or encrypted drives required and who will maintain them.
Budget time, tools and infrastructure for curation
Estimate hours for curation, repository fees, hardware refresh cycles and reference-management tools. Build these costs and tasks into project timelines.
| Area | Action | Owner | Timing |
|---|---|---|---|
| Inventory & formats | Survey existing files; list new outputs and standards | Project lead | Pre-start |
| Storage & backup | Define primary/secondary locations; test backups monthly | IT lead & sysadmin | Setup & ongoing |
| Access & security | Assign access roles; set credential process | Data custodian | Before access |
| Metadata & documentation | Choose schema; capture provenance fields | Researcher & librarian | During collection |
| Sharing & licensing | Record ownership, licence and embargo rules | Project lead | At submission |
ARDC-backed essentials to include in your one-page DMP
Begin by listing legacy assets and the new outputs your project will produce, so reviewers see the full lifecycle at a glance.
Existing survey and outputs
Capture a short inventory of existing files and a clear outline of outputs you will create. Note file types, volumes and any legacy formats that need conversion.
File formats and metadata
Prefer open, durable formats where possible. Add concise metadata fields that match your discipline to improve discoverability and reuse.
Security, privacy and destruction
State ownership, access controls and safeguards for sensitive material. Include explicit end‑of‑life destruction rules and retention triggers.
Publication, archiving and tooling
Map repository routes, licences and sharing pathways so deposit is straightforward at publication. Embrace machine-actionable DMP tools to automate provisioning and reduce admin.
“Make the one-page record practical: clear owners, simple rules and tested storage paths.”
| Essential | Action | Owner | Timing |
|---|---|---|---|
| Existing survey | Inventory legacy files and formats | Project lead | Pre-start |
| Formats & metadata | Choose durable formats; capture core metadata | Researcher & librarian | During setup |
| Security & destruction | Define access rules; add destruction steps | IT & custodian | Before collection |
| Archiving & tooling | Record repositories, licences and tools | Project lead | At publication |
Ethics, institutions and funding: keeping your DMP compliant
A concise compliance record, lodged promptly, smooths ethics review and funding release.
HREC alignment and timing for human research projects
Prepare your record early for HREC submissions so consent wording, retention and secure handling meet the National Statement on Ethical Conduct in Human Research. Macquarie University now asks many cohorts to lodge submissions in the FoRA DMP Portal. Using FoRA early helps show reviewers you have default safeguards in place.
Using university portals and policies to reduce risk
Adopt institutional defaults where available. FoRA provides templates and settings that lower risk and speed approvals; any variation should be clearly justified. ARC and NHMRC awards also require a detailed record before funds are released, so schedule approvals to avoid start‑up delays.
Practical governance and researcher support
Assign a custodian who maintains the document, approves amendments and links changes to ethics forms and access controls. Train HDR candidates to update their entry within six months and at annual milestones so compliance stays current.
- Embed simple procedures for secure access, storage and destruction.
- Cover multi‑site transfers and cross‑institution storage early.
- Plan milestone checks to confirm ongoing fitness for purpose.
| Requirement | Action | Who | Timing |
|---|---|---|---|
| HREC submission | Provide treatment of sensitive material and consent language | Researcher & ethics lead | Before application |
| Institutional lodging | Use FoRA defaults; justify deviations | Project lead | Pre-start |
| Funding release | Supply detailed record for ARC/NHMRC checks | Research admin | Prior to funds |
| HDR compliance | Complete entry within six months; update annually | Candidate & supervisor | Ongoing |
One-page DECRA template overview: structure, example prompts and resources
This one‑page template gives researchers a quick way to record essential choices and approvals for any project.
Top‑of‑page checklist for compliance and approvals
Start with approvals, storage locations, roles and repository targets. Tick boxes for ethics, institutional clearance and sponsor requirements so reviewers see readiness at a glance.
Concise sections for storage, access, sharing and retention
Use short prompts to capture primary storage, backup cadence, who may access files and intended sharing routes. Add embargo dates and licences to keep compliance visible.
Links to policies, ARDC guidance and repositories
Embed links to your university policy, ARDC guidance and preferred repositories. This saves time and guides researchers to trusted resources and tooling.
Quick extras:
- Lightweight metadata and naming rules box.
- Mini workflow for version control and collaborative writing.
- Short risk register with mitigations for backup failure and staff change.
| Section | Prompt | Who | Outcome |
|---|---|---|---|
| Checklist | Approvals, storage, roles, repository | Project lead | Ready for review |
| Storage & Access | Primary/secondary, cadence, credentials | IT & custodian | Secure access |
| Sharing & Retention | Licence, embargo, retention trigger | Researcher & librarian | Clear publishing route |
| Risks & Reviews | Backups, staff turnover, third‑party links | Project lead | Mitigated risks & review dates |
Conclusion
Make the final step practical: set one owner, one review date and clear access rules for the team.
Commit to the Australian Code and responsible conduct research in practice. Record storage, security and access choices so your australian research meets expectations from the research council and funders.
Use institutional tools and ARDC resources to speed work and cut friction. See the ARC guide for practical templates and examples.
Keep the document live: update it as projects evolve, prioritise simple workflows, robust backups and clear responsibility so your project stays ready for publication and reuse.
FAQ
What is a one‑page DECRA DMP and why use it?
A one‑page DECRA DMP is a concise, ARC‑ready summary that captures essentials — types of research outputs, storage and access, roles, ethics and sharing. It helps researchers meet ARC expectations quickly, supports NHMRC and institutional requirements, and guides teams to keep projects reproducible and discoverable.
When should I prepare the DMP for a DECRA project?
Prepare the DMP before your project starts. ARC expects a clear plan at commencement to show how you will handle records, protect participant privacy, meet HREC conditions and enable future reuse. Early planning avoids delays and protects research integrity.
What are the core elements reviewers look for in an ARC‑ready DMP?
Reviewers expect a brief summary of the kinds of research outputs, storage and backup arrangements, assigned responsibilities, metadata and standards, access and sharing pathways, and any ethics or legal constraints. Practical detail on budgets, timelines and repository choices strengthens the case.
How do I align the plan with the Australian Code for Responsible Conduct of Research?
Show how you will meet the Code’s principles: responsible record keeping, clear ownership, appropriate access, verifiable provenance and fair recognition of contributors. Include procedures for data retention, sharing, and responding to misconduct or requests for reuse.
What about human research and HREC approvals?
If your project involves human participants, include HREC reference numbers, consent processes for future use, de‑identification methods and secure storage details. Your one‑page summary should make it easy for ethics panels to see compliance at a glance.
How should I describe storage, backup and security in one page?
Use short, specific statements: primary storage location (institutional servers or ARDC services), backup frequency, encryption or access controls, and retention period. Note any sensitive data protections and destruction timelines where required.
What metadata and documentation are essential for reuse?
Identify minimal metadata fields, chosen standards or schemas, README files and provenance notes. Explain how you will capture experimental conditions, software versions and file formats so others can interpret and reuse outputs reliably.
How do I handle licensing, embargoes and repository selection?
State preferred licences (such as Creative Commons), any planned embargo periods, and target repositories for long‑term access. If legal or commercial constraints apply, explain who may approve releases and the process for requesting access.
Can a DMP include budget and infrastructure needs?
Yes. Briefly list required tools, storage costs and curatorial time. Align costs with institutional or ARDC services where possible to demonstrate feasibility and reduce funding risk during assessment.
How often should the DMP be reviewed or updated?
Review the plan at key project milestones or when project scope changes. Keep updates concise and track versions. Many institutions encourage an annual check; treat the one‑page DMP as a living prompt for good practice.
What roles and responsibilities should be named?
Name a responsible lead for stewardship, a point person for access requests, and who handles backups and metadata. Clear accountability reduces risk and ensures timely compliance with NHMRC and institutional policies.
Is machine‑actionable DMP integration necessary for DECRA?
Not always mandatory, but noting plans for machine‑readable elements or integration with ARDC tools adds value. It demonstrates forward‑thinking stewardship and can simplify reporting and compliance.
Where can I find templates and guidance tailored to Australian funders?
Use institutional DMP portals, ARDC guidance and ARC or NHMRC resources. These sources align with the Australian Code and help you craft a one‑page statement that meets funder expectations and institutional policy.
