AfterDesk
EN
Apply

The career

Building a portfolio that proves it

Most of your best work belongs to someone else and can never be shown. This course teaches you to prove your skill anyway: synthetic samples that demonstrate the same ability, case studies written without names, a one-page portfolio, certificates and testimonials used honestly, and a work log that becomes your evidence later. You finish with proof you can send tomorrow.

9
lessons
~61
minutes
12
exam questions

Free · No paid tier · No certificate fee

After this course

Everything, and what is in it.

The proof problem

~7 min

Why nobody can see your work

Almost everything good you produce belongs to somebody else. The cleaned list, the research brief, the reformatted deck: the moment you deliver it, it is the client's property and often covered by a confidentiality clause you agreed to. On AfterDesk the rule is absolute. Client work is never yours to show, not as a file, not as a screenshot, not as a redacted extract. That leaves you in a bind nobody warns you about. The people hiring you want to see work. The work you have done is the work you cannot show. Everyone serious faces this, including lawyers, accountants and agency staff. They solved it the same way you will: by building proof that was never a client's to begin with, and by keeping a record of what they did.

What a client is really asking

When somebody asks for samples they are not admiring your craft. They are trying to reduce risk. Three questions sit behind the request. Can you follow instructions exactly. Is your output clean enough to hand to somebody else without fixing it first. Will you disappear, argue or invent excuses when something goes wrong. A sample answers the first two directly. The third is answered by how you behave in the exchange: whether you read the posting, whether you sent what was asked for, whether your file is named sensibly. This changes what you need to build. You do not need an impressive body of work. You need a small number of artifacts that answer those questions faster than a paragraph of claims can. Two good samples beat ten mediocre ones every time.

Three kinds of proof

Proof comes in three forms and you need some of each. Artifacts are things you made and can hand over: a cleaned spreadsheet, a research brief, a formatted document. They show the output a client would receive. Records are your own account of what you have done: a work log, volumes handled, turnaround times, revision rates. They show consistency over time. Signals come from other people: a certificate from a course with a real exam, a testimonial from somebody who worked with you, a profile that has been alive for two years. They show that someone other than you vouches. Artifacts alone look thin. Records alone sound like claims. Signals alone look borrowed. Together they read as a person who actually does this work.

Build it before you need it

The worst time to build a portfolio is the evening you find a posting you want. You rush, you produce something thin, and the temptation to reach for a real client file becomes very strong. Build it in quiet weeks instead. One sample takes two or three focused hours if you plan it. Three samples, a one-page document and a work log is a month of small evenings, and then it is done for a year. Set a fixed slot, an hour twice a week, and treat it as unpaid work that pays later. Keep every file in one folder with a clear structure so you are never hunting. When a good opportunity appears you send in ten minutes what would otherwise have cost you a night and your judgement.

Remember

  • Your best work belongs to the client and can never be used as a sample.
  • Clients ask for samples to reduce risk, not to admire your craft.
  • Proof has three forms: artifacts you made, records you kept, signals from other people.
  • Build your portfolio in quiet weeks, not the night you find a posting.

What you may never show

~7 min

The rule in one sentence

Client data never leaves the task. That is the whole doctrine and it does not bend. On AfterDesk, files you download on a claimed task are for producing that delivery and nothing else. You do not upload them to a third party service, a free online converter, a translation site or an AI assistant unless the brief explicitly tells you to. You do not email them to yourself. You do not keep them once the delivery is approved. And you never use them, in any form, as a portfolio sample. Most clients outside AfterDesk hold the same position even when nobody writes it down, because the data usually is not theirs either. It belongs to their customers, their patients, their suppliers. You are three steps from a person who never agreed to any of this.

A screenshot is still the file

People break this rule believing they have found a safe version of it. A cropped screenshot with the company name blurred. Three sample rows out of four thousand. A PDF with the logo removed. Each one still contains client data, and blurring is weaker than it looks: names show through low-resolution edits, cropped columns still carry unique combinations, and one row of a customer list is still a real person's address. There is also the part you cannot see. Spreadsheets carry hidden sheets, filters, comments and formulas pointing at other files. Documents carry the author name, edit history and tracked changes. Images carry creation data. If your safety plan depends on nobody looking closely, it is not a plan. Treat any file that passed through a client's hands as unusable, in every form.

Keep nothing after approval

When a delivery is approved and paid, your copy stops having a reason to exist. Delete the downloaded source files, the working versions and the exports you made along the way, then empty the recycle bin. Check the places files hide: the downloads folder, the desktop, an automatic cloud sync folder, the email you sent yourself, the phone that opened the attachment. Do this the same day, while you still remember where everything went. If you want to remember the task, write a line in your work log instead: what type of file, how many rows, how long it took, what was difficult. That line is the thing you can keep and use forever. The file is the thing that can end your career if it turns up somewhere it should not.

Refusing is a selling point

This looks like a pure cost until you see it from the client's side. Somebody handing a customer list to a stranger in another country is nervous, and they are right to be. A person who states plainly that they never reuse client work, never store it after delivery and never put it through outside tools is answering the fear before it is spoken. Put one sentence about it in your one-page portfolio. It costs you nothing and it separates you from everyone whose portfolio quietly displays other people's confidential documents. Clients notice those. Some of them think: interesting, so my files will be in there next year. The habit protects you too. You cannot leak what you no longer hold, and you cannot be blamed for a breach you had no copy of.

Where permission fits

Outside AfterDesk there is a narrow path. If a client gives you written permission to show a specific piece of work, and you keep that email, you may show that piece within the limits they set. Vague permission is not permission. Verbal permission you cannot produce later is not permission. And permission from your direct contact does not cover their customers' data. On AfterDesk there is no path at all. You have no contact with clients, so there is nobody to ask, and the answer is fixed anyway. Client work is never a sample. If something about a task itself is unclear, the note you send with your delivery is your channel to the operator. Use it for questions about the work, not for requests to reuse it.

Remember

  • Client data never leaves the task, in any form, including screenshots and sample rows.
  • Blurring and cropping do not remove hidden metadata, comments or unique identifying details.
  • Delete every copy the day a delivery is approved, then check where files hide.
  • Say plainly that you never reuse client work; nervous clients are listening for it.

Samples you build yourself

~8 min

Invent the client, keep the skill

A synthetic sample is work you produce start to finish with data you made up, for a company that does not exist. It is not a lesser version of a real sample. The client cannot verify your real work anyway, so what they are actually reading is the quality of the output in front of them. Start by inventing a plausible situation. A 40-seat dental clinic with three years of appointment records. A small equipment importer whose supplier list arrives in four inconsistent formats. A regional bakery chain that wants competitor pricing. Give it a name that is obviously invented, like Northfield Dental or Harbour Rise Imports, so nobody can mistake it for a real business. Then do the job properly, exactly as you would if somebody were paying for it.

Make your own messy data

Clean data proves nothing, because the skill is in handling mess. Build the mess deliberately. In Google Sheets, generate a few hundred rows, then damage them on purpose: duplicate thirty records with small spelling differences, write dates in three formats, put trailing spaces in half the names, leave some fields blank, mix upper and lower case, stick two values in one cell. Public open data portals and published statistical tables give you realistic names, addresses and categories to start from, free of charge. Three hundred rows is enough. Ten thousand rows only proves you can scroll. Save the damaged version before you touch it, because that raw file is half of what makes the sample convincing. Anyone can hand over something tidy. Few people can show the state it arrived in.

Show the work, not just the result

Structure the sample so a busy person sees what you did in fifteen seconds. Use three tabs. Raw, containing the mess exactly as it arrived. Clean, containing the finished output. Notes, containing what you changed and why: eleven duplicates merged, dates standardised to one format, four rows flagged because the address could not be resolved. That third tab is the one that gets you hired. It shows you make decisions, record them, and flag what you could not settle instead of guessing. Add a line at the top of Notes stating the rules you applied. For a document or a research sample, do the same in a different shape: the brief you worked from, the finished piece, and a paragraph on sources and what you could not confirm.

Label it honestly

Put one line at the top of every synthetic sample: this is a demonstration sample built with invented data for a company that does not exist. Never let a reader assume it is client work, and never answer a question about it in a way that implies a real engagement. This feels like it weakens the sample. It does the opposite. It tells the reader you understand confidentiality, which is precisely the trait they are worried about, and it removes any chance of being caught in an overstatement later. Honest framing also makes the conversation easier. You can talk freely about your choices, walk through the decisions and let them test you, because there is nothing in the file you need to protect or explain away.

Three to five samples, no more

Build one sample for each category of work you actually want to be paid for, and stop. Three is a working portfolio. Five is generous. Beyond that you are maintaining a museum. Choose categories where the work is common and the output is visible: a data cleanup, a research brief, a formatted document, a built list with sources. Each should stand alone and be understandable without you in the room. Give every file a name that reads correctly in a stranger's downloads folder, such as Data cleanup sample, Maria Santos. Revisit them once or twice a year, because your standards rise and last year's work starts to look slow. Replacing one sample properly is worth more than adding two.

Remember

  • A synthetic sample built properly shows the same skill as work you cannot show.
  • Damage your own data on purpose; clean data proves nothing about your judgement.
  • Keep raw, clean and notes together; the notes tab is what gets you hired.
  • Label every sample as invented data, then talk about it freely.
  • Three to five samples is a portfolio; more is a museum.

Sanitising real work safely

~7 min

Sanitised is not anonymous

Removing names is the easy part and it is rarely enough. A record can identify somebody through a combination of details that look harmless on their own: a job title, a city, a purchase date, a company size. Take a list of forty suppliers with the names stripped out, keep the towns and the product categories, and somebody inside that industry can name half of them in ten minutes. The same applies to a document. A distinctive phrase, a product code, a template layout or an unusual date range can point straight back to the source. The test is not whether you removed the obvious identifiers. The test is whether a knowledgeable stranger could work out who this was. If you cannot answer that confidently, the material is not safe to show.

Rebuild, do not redact

Deleting a column and saving under a new name leaves more behind than people expect. Spreadsheets keep hidden sheets, filtered rows, comment threads, named ranges and formulas that reference the original workbook. Documents keep the author name, the company that registered the software, tracked changes and earlier versions. PDF files keep text underneath black rectangles, which can be copied straight out. Image files keep creation data. If you have permission and you genuinely need to show real work, do not clean the original file. Open a blank file and rebuild the structure by hand, typing only what you decided to include. It takes longer and it is the only version you can defend. Then open the result on another device, check the file properties, and read it as a stranger would.

Written permission comes first

None of this applies until you have permission, and permission means an email you can produce two years from now. Ask for something specific: I would like to show the structure of the monthly report I build for you, with all figures replaced by invented numbers and your name removed, in a private portfolio document I send to prospective clients. Name what, name how, name where. If the reply is enthusiastic but vague, write back with the specifics and ask them to confirm. Remember that your contact may not have the authority to grant it, particularly where the data belongs to their own customers. If they hesitate, take that as your answer and build a synthetic sample instead. Nobody has ever lost a contract for being careful with somebody else's information.

When in doubt, build synthetic

Weigh the two outcomes. A well-built synthetic sample costs you an evening and demonstrates the same skill. A sanitising mistake costs you a client, possibly a legal problem, and a reputation that follows you. The gain from using real work is small, because the reader cannot verify it and does not know the client anyway. The downside is not small. So settle the default before you are tired and in a hurry: if there is any doubt about a piece of real work, it does not go in the portfolio, and you build the invented version instead. This rule is worth writing down where you will see it, because the pressure to bend it always arrives at the worst moment, when an opportunity looks perfect and you feel underprepared.

Remember

  • Removing names is not anonymising; combinations of small details still identify people.
  • Rebuild in a blank file rather than deleting from the original, because metadata survives.
  • Permission means a specific written email you can still produce two years later.
  • Any doubt at all means you build the synthetic version instead.

The case study without names

~7 min

Four parts, under 200 words

A case study is a short written account of a job you did. It carries proof a file cannot: it shows how you think. Use four parts and keep the whole thing under two hundred words. The situation, in two sentences. What you were asked to do, in one. What you actually did, in three or four, including the decisions and the problems. The result, in one or two, with a number you can stand behind. Write it in plain past tense with no adjectives about yourself. Not: I meticulously ensured accuracy. Instead: I checked every merged record against the original and flagged nineteen I could not resolve. The second sentence proves the first without claiming it. Three case studies is plenty, and they cost you nothing but honest recall.

Describe the client by shape

Name the type, never the business. A twelve-person logistics company. A solo consultant in the training sector. A regional chain of garden centres. That gives the reader the context they need, which is size and sector, without giving away who it was. Watch for detail that narrows too far. The third largest importer of Italian tile in a small country is a name with extra steps. If your client operates in a thin market, blur one level further: an importer in the building materials trade. When you are unsure whether a description identifies them, ask whether a competitor reading it would know. Do the same for people. Not Sarah in accounts, but the finance lead. Somebody should be able to read your entire portfolio and learn nothing about your clients.

Numbers you can defend

Numbers make a case study credible, and invented numbers destroy it the moment somebody asks a follow-up question. Count things you actually did. Rows processed. Hours taken. Duplicates found. Sources checked. Revisions requested. Turnaround from claim to delivery. Those are yours and you can describe how you arrived at them. Be far more careful with business outcomes. You did not increase their sales by thirty percent; you built a list their sales team used, and you have no idea what happened next. If you do not have the exact figure, round down and say approximately: around four hundred rows, roughly six hours. Nobody minds an approximate number honestly labelled. Everybody notices when a precise-sounding claim collapses under one question, and that is when the rest of your portfolio stops being believed.

Say what went wrong

The strongest case study includes a problem. Somewhere in every real job something did not fit: the source file was worse than described, two columns contradicted each other, a brief was ambiguous, a delivery came back for revision. Write one sentence on it and one sentence on what you did. The source list contained ninety-four records with no country field, so I flagged them in a separate tab rather than guessing from the phone codes. That single line tells the reader more than three paragraphs of confidence. It shows you notice problems, you do not paper over them, and you hand back something the client can act on. Anyone who has hired before knows the smooth job does not exist, and a portfolio of flawless stories reads as inexperience or fiction.

Remember

  • Four parts, under two hundred words: situation, task, what you did, result.
  • Describe the client by size and sector, never by name or unique detail.
  • Count what you did; never claim business outcomes you cannot verify.
  • Include one problem and how you handled it; flawless stories read as fiction.

The one-page portfolio

~7 min

One page, one minute

The person reading you is skimming, probably on a phone, probably with eleven other applicants open. Give them one page they can read in a minute. Top of the page: your name, the three or four things you do, and your working hours expressed in the client's terms rather than yours. Not: I am in the Philippines. Instead: I work 9pm to 5am Manila time, which covers a full US Eastern business day. That sentence answers a question they were going to ask on the second email. Add one line on how fast you typically turn work around, and one on how you handle confidentiality. That is the top third done, and it has already told them more than most portfolios manage in four pages.

The middle: three proofs

Below the header, list three samples. Each gets three lines and no more. What it is: a data cleanup of a 380-row supplier list. What it shows: duplicate detection, date standardisation, and a change log with flagged rows. Where it is: one link. Then a short case study section, two or three of them, each the compressed version from the previous lesson. Then certificates, one line each. Order matters. Put the sample closest to the work they posted first, which means the document changes slightly for each application. Keep a master version and edit the order before you send. Nothing on this page should require the reader to click anything to understand what you do. The links are for people who are already interested.

How you work

Reserve four or five lines near the bottom for the practical facts a client wants and rarely gets. The hours you are genuinely available and how much overlap that gives with their day. Your typical turnaround for a small task. The tools you use, naming the free ones honestly: Google Sheets, Google Docs, whatever else you actually know. What you do when a brief is unclear, which should be that you ask before you guess and flag anything you had to assume. And one line on confidentiality: you do not keep client files after delivery, you do not put client data through outside services, and you never use client work as a sample. State it as fact, not as a promise. It reads better and it is easier to keep.

Build it free, make it open

Write it in Google Docs, then export a PDF. Name the file so it makes sense in a stranger's downloads folder: Maria Santos, virtual assistant portfolio. Keep the samples in one Drive folder with sharing set so anyone with the link can view, then test every link in a private browsing window where you are not signed in. A link that asks the client to request access is worse than no link. Check the whole thing on a phone. If your spreadsheet sample opens as an unreadable wall on a small screen, add a short summary at the top of the first tab. Put the date somewhere on the page and review it every three months. A portfolio dated two years ago tells a story you did not intend.

Remember

  • One page, readable in a minute, on a phone.
  • State your working hours in the client's timezone, not your own.
  • Three samples, three lines each: what it is, what it shows, one link.
  • Test every link signed out; an access request screen is worse than no link.

Certificates and testimonials

~6 min

What a certificate proves

A certificate says that on a specific date you passed a specific exam. That is a real thing and it is worth having. It shows you finished something voluntarily, that a third party set the standard rather than you, and that you knew the material well enough to answer questions under test conditions. It does not say you have done the work for a paying client, and you should never let it imply that. Our Academy certificates are permanent and they are yours, carrying the exam name and the date. Present them as what they are. A client who reads honest framing on a certificate believes the rest of your page more readily. A client who catches a course certificate dressed up as experience stops reading altogether.

Present them without clutter

One line each, near the bottom of the page, in the order that matters for this application. The course name, the issuer, the month and year. Nothing else. Resist the collection instinct. Twelve badges in a grid reads as somebody who has done a lot of courses and not much work, which is the opposite of the impression you want. Three to five relevant ones are stronger than everything you have ever earned. If a certificate is directly relevant to the posting, mention it once in your message as a single clause, not a paragraph. And if you are asked what a certificate covered, be able to answer in two sentences. Not being able to describe your own certificate is worse than not holding it.

How to ask for a testimonial

Ask right after a delivery that went well, while the relief is fresh, and never in the same message as an invoice. Make it easy. Tell them exactly what would help: two or three sentences on what I did, how quickly, and whether the work needed correcting. Offer to draft something they can edit, which most busy people prefer, and keep the draft accurate and modest so editing it feels like agreeing rather than inflating. Ask explicitly what you may publish: their full name and company, or only a first name and an industry. Keep the reply. On AfterDesk this route does not exist, because you have no contact with clients. Here your evidence is your own record and your certificates, and that is fine.

What a good testimonial says

Great to work with is worth nothing, because everybody has one. A useful testimonial names behaviour. She turned around a 600-row cleanup in under a day and flagged the rows she could not verify instead of filling them in. He asked two questions before starting that saved us a rewrite. Those describe someone specific. When you draft one for a client to edit, write that kind of sentence and let them soften it if they want. Two strong testimonials are enough. If you have none yet, say nothing rather than writing something vague, and lean on samples and case studies instead. Absence is normal early on. Padding is noticed, and it makes a reader wonder what else has been inflated.

Remember

  • A certificate proves you passed an exam on a date, not that you have client experience.
  • Three to five relevant certificates beat a grid of twelve badges.
  • Ask for testimonials right after a good delivery, and offer a draft they can edit.
  • A useful testimonial names specific behaviour, not general pleasantness.
  • AfterDesk gives you no client contact, so your record and certificates are the evidence.

The work log becomes your evidence

~6 min

Two minutes at the end

Everything you did last March is gone unless you wrote it down. Not the fact that you worked, but the details that make an application credible: how many rows, how long it took, what went wrong, what you decided. Spend two minutes at the end of every task filling one row in a spreadsheet. Date, category of work, what you produced described by type and volume, hours spent, tools used, one line on the hardest part and how you handled it, and whether it came back for revision. Two minutes. That is the whole discipline. In six months you have a record no interview question can catch out, and a set of honest numbers you can quote without hesitating or rounding upward in panic.

Log the work, not the client

Your log has to survive being read by somebody else, so keep client data out of it entirely. No names of people, no company names you would be uncomfortable seeing repeated, no extracts of the data, no file copies. Use a code for each client, C1, C2, C3, and keep the key somewhere separate if you need one at all. Describe by shape: dental clinic, twelve staff. Describe the work by type and volume: supplier list cleanup, 380 rows, 47 duplicates merged, 9 rows flagged. That is enough to write a case study from and it identifies nobody. Keep the log in your own account, on your own storage, never on a drive a client controls, and back it up somewhere other than the machine you work on.

Track your own error rate

The number most workers cannot state is the one that would impress a client most: how often their work comes back. Log it. Every revision request, what it concerned, and whether it was your error, an unclear brief or a change of mind. After thirty tasks you have a real figure, and you can say something few applicants can. I have delivered around ninety tasks with four revisions requested, three of which were clarifications rather than errors. That is specific, checkable in tone, and honest. It also makes you better. Categorising your own revisions shows you your patterns, and patterns are fixable. Most people fix nothing because they never see the pattern, only the individual bad day.

Turn the log into portfolio lines

Once a month, spend fifteen minutes reading the log and rolling it up. Total tasks by category. Total volume handled. Average turnaround. Revision rate. Add the one or two jobs that would make good case studies, and write them while you still remember the problem. Update your one-page portfolio if the numbers moved meaningfully. This is where the log stops being admin and becomes the reason your application is stronger than somebody with the same skills. They write: I am detail oriented. You write: in the last six months I have cleaned around 14,000 rows across nineteen tasks, with an average turnaround under twelve hours. Same work, entirely different reading, and yours came from a spreadsheet you kept two minutes at a time.

Remember

  • Two minutes per task: date, type, volume, hours, difficulty, revision.
  • Keep client names and data out of the log; use codes and describe by shape.
  • Track revisions and their causes; a known error rate is rare and persuasive.
  • Roll the log up monthly into numbers your portfolio can quote.

Sending proof without dumping links

~6 min

Match the sample to the ask

The most common mistake in an application is sending everything. Five links, three attachments, a full portfolio and a request that they look through it. That is work you have handed to a busy stranger, and busy strangers do not do it. Read the posting properly and pick the single sample closest to what they described. If they want a lead list built, send the list building sample, not the research brief you are prouder of. If nothing matches exactly, pick the one that shares the underlying skill and say which part is comparable. One well-chosen sample answers their question. Five samples ask them to find the answer themselves, and quietly signal that you did not read what they wrote.

Frame it in two lines

Never send a bare link. Two lines around it change how it is read. First, what it is: a 380-row supplier list cleanup, built with invented data as a demonstration sample. Second, what it shows and why it is relevant: it has the duplicate handling and the flagged-row log your posting mentions. Then the link, then stop. Do not explain your whole history, do not apologise for the sample being synthetic, do not add a second link because you are worried the first is not enough. The framing does the work. It shows you understood the posting, it tells them what to look for before they click, and it means the thirty seconds they spend on your file are spent on the right part.

One link, tested

Send one link where possible and two at most, and if you can only send one, make it the one-page portfolio. Do not send zip files, which people will not open. Do not attach large files unless they asked for attachments. Do not link to a folder containing everything, which puts the sorting back on them. Before you send, open the link in a private window where you are not signed in and confirm it loads for a stranger. Check that the file name is professional, that the document has no leftover placeholder text, and that the date on it is current. Most link problems are permissions, and a client who hits an access request screen usually just moves on to the next applicant.

When you do not have what they want

Sometimes they ask for a sample of exactly the thing you have never built. Say so, plainly and briefly, then offer the nearest thing and a way forward. I have not built a CRM migration sample. Here is a data cleanup that shows the matching and deduplication logic, and I am happy to do a small paid test task so you can see the real thing. That is a stronger answer than silence, a stretched claim, or a rushed sample built in an hour that shows your worst work. Never invent experience under pressure. It is the easiest lie to catch, it usually gets caught in the first week of the job, and the version of you that admitted the gap would still have had it.

After you send

Send once, follow up once, then leave it. A single short follow-up after five to seven days is reasonable and often works. Anything beyond that costs you more than it gains. Use the waiting time to fix what you noticed while assembling the application: the sample that took too long to explain, the case study with the vague number, the link that needed a permission change. Keep a short record of what you sent to whom and when, so you do not send the same person a different version of your story three months later. Applications are a numbers game with a quality floor. The portfolio work you did once keeps paying, and every round should leave it slightly better than it was.

Remember

  • Send one sample matched to the posting, not everything you have built.
  • Frame every link with what it is and what it shows, then stop.
  • Test links while signed out; permission errors lose applications silently.
  • Admit a gap and offer a paid test task rather than inventing experience.

Sit the exam

The courses are free. The work is real.

Twelve scenario questions. Pass at ten. Three attempts a day. The bar is the point.

No paid tier. No certificate fee. No upsell. Not now, not later.

Create a free account

You can start the first course tonight.

The curriculum

Everything, and what is in it.