How to Build an RPL Portfolio: Documents, Evidence and Examples

What an RPL portfolio needs to prove

An RPL portfolio is a structured explanation of learning you already possess, supported by evidence. It is not a longer CV or an archive of everything you have produced at work. Its purpose is to help an academic assessor judge whether your learning meets the outcomes of a particular programme or module. Start with those outcomes, not with the documents you happen to have.

The University of St Andrews asks applicants to provide evidence aligned with course outcomes. QAA Scotland's RPL framework similarly connects reflection, identified learning and evidence with an institutional decision. These sources establish useful principles, not a prescribed BAHS portfolio format. Request the instructions for your own route before preparing a submission.

Build the evidence map first

Create a working table with six columns: outcome, learning claim, context, evidence identifier, personal contribution and gap. Copy the official outcome accurately. State the learning claim in your own words. Explain where you developed that learning, identify the supporting document and say which part of the work was yours. Use the final column honestly when a claim still needs support.

For example, an outcome about evaluating business options might be supported by a supplier-selection analysis. Your claim should explain how you compared cost, service reliability and risk. A signed contract alone shows a transaction occurred; it does not explain the reasoning. Read the RPL overview if you are unsure whether you are seeking entry or module credit.

Choose documents that perform different jobs

• Certificates and transcripts document previous assessed study and results.
• Syllabuses and assessment briefs help establish what a previous course actually covered.
• Work products show applied decisions, analysis or outputs.
• Employment records establish dates and responsibilities.
• References independently confirm context and your contribution.
• Reflective accounts explain the learning connecting those items.

Do not ask one document to prove everything. A reference may confirm you supervised a team without demonstrating your understanding of motivation theory. An attendance certificate may show participation without assessed achievement. Identify the limits of each item and combine evidence only where it genuinely strengthens the claim.

Use an evidence index the assessor can navigate

Assign stable identifiers such as E01, E02 and E03. For each item, record its title, date, author or source, permission status and linked outcomes. Use these identifiers in your narrative. If a single document supports several claims, point to the relevant section or page rather than attaching multiple copies with different names.

A practical folder structure might separate academic records, professional evidence, reflective statements and verification. Follow the provider's required arrangement where one exists. Keep a final submission copy so that clarification requests refer to the same version. An assessor should not need to reconstruct your career chronology from inconsistent filenames.

Write reflection that goes beyond description

A useful reflective account answers five questions: What problem did you face? What information and concepts informed your decision? Which alternatives did you consider? What happened? What would you change now? This structure demonstrates reasoning without turning the portfolio into a promotional case study.

Consider an illustrative inventory project. You might explain why you changed reorder points, how you estimated demand and what assumptions affected the calculation. If service levels improved, acknowledge other possible causes. If performance deteriorated, explain what the result taught you. Honest analysis of a disappointing result can demonstrate more learning than an unsupported claim of success.

Make individual contribution visible

Team documents are common in business portfolios. State which analysis you completed, which decisions you recommended and which decisions somebody else approved. Distinguish authorship from participation. Where possible, ask an appropriate referee to confirm your role and the period involved without reproducing private information.

For a shared presentation, identify the slides or research you produced. For a budget, explain whether you built the model, supplied assumptions, interpreted the results or authorised expenditure. Our guide to documenting managerial experience develops this distinction between responsibility and demonstrable learning.

Protect confidential and personal information

Do not assume that owning a copy of a document gives you permission to disclose it. Ask your employer or client where necessary. Remove unnecessary names, account details, personal identifiers and commercially sensitive information. Check whether redaction leaves enough context for an academic judgement.

If the original cannot be shared, ask the institution about verified summaries, an interview or another approved alternative. Do not invent a replacement document that looks official. Label any reconstruction clearly and obtain approval before relying on it. Use the approved submission channel rather than a publicly accessible portfolio link.

Check level, currency and breadth

A detailed document can still be unsuitable if it addresses the wrong academic level or a narrow portion of an outcome. Explain how your reasoning matches the standard sought. For subjects that change quickly, add recent evidence of continued application rather than assuming an old project proves current competence.

Also check coverage across the whole claim. Strong operational evidence may not demonstrate finance, strategy and research methods. Mark those gaps and ask whether a smaller claim, bridging study or a taught module would be more appropriate. A focused portfolio with a defensible scope is often more useful than an ambitious claim with weak coverage.

Before you submit

Use a final check: every outcome has an explanation; every important assertion has evidence; dates and names agree; references can be verified; permissions are recorded; files are readable; and limitations are acknowledged. Ask whether an interview, declaration or additional assessment is required. Our online RPL application guide explains the surrounding process.

Request a BAHS eligibility review before paying for substantial portfolio preparation. Ask Admissions to confirm the assessment scope, charges, awarding arrangements and remaining study. The portfolio supports an academic decision; preparing one does not guarantee admission, credit or a qualification.

Check whether a reader can reproduce your reasoning

Before submission, ask yourself whether an assessor unfamiliar with your organisation could follow each important decision. Define internal abbreviations, explain the data source and identify the evidence supporting your conclusion. If a report relies on an appendix, include the permitted relevant section rather than leaving an unexplained reference. This is a readability check, not permission to have somebody else rewrite your learning claims. Preserve your own voice and keep your explanations consistent with the underlying records.