DTV for Freelancers: Build a Portfolio That Explains Your Work

We recommend building the evidence around a small number of real projects, with a clear connection between the agreement, the work and the payment. This is our preparation method, not an official requirement for a particular number of clients, invoices or pages. The responsible Thai embassy or consulate's current checklist comes first.

The Royal Thai Embassy in London's DTV checklist names a professional portfolio as one possible way to demonstrate relevant professional status. It also lists separate requirements for identity, residence, funds and police clearance. A portfolio therefore solves one part of the application. It does not replace the rest of the file or establish where you may apply.

This guide is for people who already carry out freelance work and need to explain it accurately. It is less useful if the real question is whether an activity qualifies at all. In that situation, start with our Workcation requirements guide. If the problem is the amount or ownership of savings, use the DTV financial-evidence guide. Here we concentrate on the professional file itself.

Decide what the portfolio needs to prove

Start with a plain description of your work. “I provide monthly website maintenance to overseas businesses” is more informative than “I am a location-independent entrepreneur.” The first tells a reviewer what documents might exist. The second leaves almost everything unexplained.

Write down the service, the kind of customer, your personal responsibilities and the normal method of delivery. Then identify which of those statements an independent document can support. A client agreement might identify the service. A dated acceptance email might connect you to a completed milestone. A payment statement might show how the work became income. None needs to prove every aspect of the business on its own.

We find it useful to distinguish five questions. Are you the person named in the work records? Does the work actually exist? Is the relationship with the payer understandable? Does the activity fit the proposed purpose? Are the dates consistent with the story? This is an editorial framework for organising evidence, not a scoring system used by Thai authorities.

You should also be able to explain where the professional activity is anchored. A business can have a foreign name but perform a local role, and an invoice in another currency does not settle a work-authorisation question. If your intended activity includes working for a Thai business or serving Thai customers, describe it accurately and obtain a separate route assessment. Do not expect portfolio design to resolve a legal-purpose mismatch.

Before collecting documents, decide if you are applying as a freelancer, an employee or a business owner who personally works in the business. People sometimes perform more than one role. The answer should follow the facts, with a clear explanation of each relationship, rather than whichever label produces the easiest checklist.

Separate the official checklist from our preparation method

Create two lists. The first reproduces the relevant post's actual requested document categories, with the date you checked them. The second contains the supporting materials you think will make your work easier to understand. Keeping them separate prevents a practical suggestion from becoming an invented rule.

For example, we may recommend connecting an invoice to a bank receipt. That does not mean every DTV applicant must submit every invoice. Nor does a post's request for a professional portfolio mean that a self-written document must be accepted without further evidence. The distinction matters when you decide what to request from a client and what to leave out.

The Washington DTV instructions are a useful example of the detail a particular post can publish. Under its additional-document heading for non-US citizens, the page names a business licence or registration identifying a self-employed applicant. It also warns that unclear files may prompt further requests. That registration instruction has both a post and an applicant-subgroup scope; it is not a requirement to copy into every freelancer's file or another post's checklist.

Filing eligibility deserves its own check before you spend time on presentation. Moscow's September notice describes changed DTV residence and criminal-record documentation effective from 31 August 2026. Old online success stories may predate these changes. Verify the receiving post's current interpretation and your application date, particularly if you live outside your passport country.

Our residence and filing-evidence guide explains the distinctions in more detail. Keep a note of any genuine ambiguity and the authority from which clarification is needed. Do not quietly resolve conflicting instructions by selecting the version that asks for fewer documents.

Choose projects for clarity, not prestige

Your strongest project for a visa evidence file may be an ordinary maintenance contract with tidy records. Your most prestigious project may be difficult to use because the agreement is confidential, the payer is unclear or your personal role cannot be distinguished from a large team's work.

Select examples that show the actual business as it operates now. A recent recurring engagement can explain continuity. A completed project can show delivery. A different kind of assignment can explain the range of your services. You do not need artificial variety if the work is naturally specialised.

We would usually begin by reviewing two or three representative examples, then add more only where they answer a remaining question. This is a working suggestion, not a minimum or maximum imposed by a consulate. If the post requests a different scope or period, follow that request. The aim is a file that can be followed, not a file that happens to contain our suggested number.

Do not choose a client merely because its logo looks impressive. Ask whether you can identify the contracting entity, explain your role, show a real output and connect the payment. If one of those links is missing, another less glamorous project may tell the story better.

Past work can still be relevant, especially in a profession with long projects or infrequent billing. Label its dates clearly. Explain why it illustrates your current professional status instead of allowing the reviewer to assume it is ongoing. A dated archive is useful evidence of history; presenting it as current work creates an avoidable contradiction.

For each possible example, make a private selection table before producing the portfolio:

These are hypothetical examples. The decisions show how we would organise questions; they do not predict an authority's assessment.

Build the agreement-to-payment connection

For each selected engagement, record the parties, service, dates and payment arrangement in a short project summary. Link that summary to the original documents. Think of it as a map through the evidence, not a replacement for the evidence.

Start with the agreement. It may be a formal contract, a platform engagement, an accepted proposal or another genuine record of the commercial arrangement. Do not describe an informal arrangement as a signed contract if no contract exists. Explain the arrangement as it actually works and assess whether the available records are sufficient for the post's request.

Next, identify the delivery evidence. A designer may have an approved design milestone. A translator may have a delivery acknowledgment. A developer may have a release record or a client acceptance message. The purpose is to establish your contribution without disclosing unnecessary customer information. A screenshot with no date, owner or explanation can be difficult to interpret even when it is authentic.

Then follow the billing. Check that the invoice names the correct parties and refers to the relevant service or period. If you invoice through a trading name, explain its connection to you. If the agreement and invoice use different legal entities, do not assume the relationship is obvious. Resolve it with genuine records or a clear explanation.

Finally, connect the receipt. Payment processors, platform fees, currency conversion, instalments and aggregated payouts can make the received amount differ from the invoice. A difference is not automatically a defect. An unexplained difference is simply another question. Show the reconciliation where relevant and keep the original statement intact.

Our preference is a short readable explanation over several disconnected screenshots. For example: “Invoice 014 covers the March maintenance period. The platform deducted its service fee and included the net amount in payout 208, which also contains the final payment for invoice 013.” That is a hypothetical explanation of a reconciliation method, not wording to copy unless it describes your actual records.

Avoid inventing a perfect financial trail after the event. If the records are incomplete, identify the gap. You may be able to obtain a genuine confirmation from the counterparty or download a more complete statement. You should not alter an existing invoice, fabricate an acceptance email or backdate an agreement to make the file look easier to understand.

Explain income patterns without manufacturing stability

Freelance income can be irregular. One large project may produce a deposit, two milestones and a final balance over several months. A retainer may pay consistently, while other clients pay late. The portfolio should describe that pattern accurately instead of pretending that every freelancer receives a salary.

Separate the period when work was done from the date money arrived. A bank credit in May might relate to work delivered in March. A payment received before delivery might be a deposit. If you collapse both dates into one monthly income chart, the result may create a misleading story even though every underlying number is real.

Use a short factual note where timing needs explanation. Keep the note proportional to the issue. A routine delayed payment usually does not need a long defence. Conversely, a substantial unexplained transfer should not be labelled “freelance income” merely because it appears in the same account.

Do not confuse professional evidence with financial eligibility. Your portfolio may show a real business that currently holds little accessible cash. Your savings may meet a published threshold while giving no explanation of professional activity. These are different questions and should have different supporting records.

We would also separate gross billing from money received. Platform revenue, company turnover and personal available funds are not interchangeable. A sole trader and a company director may need different explanations of that relationship. If the legal or accounting structure is unclear to you, clarify it before using a number in the application.

Avoid adding an income requirement that the responsible checklist does not state. Equally, do not announce that an omission from one webpage means income evidence can never be requested. Describe the current published requirement, the evidence you have and any request actually made in your case. That approach is more useful than a broad claim about what all posts always accept.

Handle platforms, trading names and intermediaries

Platform work often creates a naming problem. The client appears in one place, the platform in another, and a payment processor on the bank statement. A reviewer unfamiliar with your workflow may not know how those names connect.

Make the relationship explicit. Explain whether the platform introduces customers, holds payment, processes invoices or acts as the contracting party. Use the platform's genuine account and transaction records where they are relevant. A public profile alone may not show who owns the account or whether a listed project produced paid work.

If a payout combines several jobs, prepare a reconciliation that points back to the underlying transactions. Keep amounts and currencies labelled. State where fees or conversion affect the final receipt. Do not make a single invoice appear to equal a combined payout by changing figures or quietly leaving out other transactions.

A trading name needs similar care. Your website may use one name while the official registration uses your personal name or a different legal name. Explain that relationship with a suitable record. A designed logo is not proof that the business belongs to you.

Working through an agency adds another layer. The end customer may never have signed a contract with you because the agency engaged you. In that case, start with the agency relationship. Do not imply direct employment by a well-known end customer simply because your work contributed to its project.

These explanations should be short enough to fit beside the relevant evidence. If the structure takes several pages to describe, consider whether you have mixed distinct engagements or business models into one story. A separate project note for each arrangement can be clearer than a single complicated diagram for the whole career.

Protect confidentiality without making the evidence unreadable

Clients may have confidentiality restrictions, and professional files can contain information unrelated to the visa question. We recommend identifying those restrictions before selecting work samples. Do not upload confidential customer files to a public portfolio simply because a visa application is important to you.

Ask whether a non-confidential summary, an authorised sample or a confirmation of your role can explain the work. Where permission is needed, obtain it from the appropriate party. You cannot grant yourself permission to disclose a client's material just by adding a watermark.

Keep a distinction between redacting irrelevant confidential details and obscuring the evidence necessary to understand a document. Removing every name, date and payment reference may leave a page that proves very little. If you cannot disclose a material detail, ask the receiving post what form of evidence it can accept. Do not assume an adviser or online commenter can settle that question for it.

A useful internal exercise is to write the purpose of each document before deciding what can be removed. If an agreement is being used to connect you to a contracting party, removing both identities defeats that purpose. If a screenshot is only illustrating the kind of design work you performed, unrelated customer data may be unnecessary. The judgment depends on the document and the actual request.

Maintain an unchanged original and a separately labelled submission copy. Record what was removed and why. Do not edit the original financial or legal record, and do not describe a redacted copy as an untouched original. Where the authority requires complete records, that instruction takes precedence over a preference for a shorter file.

For the initial TVC assessment, begin with a description of the evidence you have. You do not need to upload a passport or bank statements to ask whether your situation merits a closer review. The document stage can follow once the purpose, recipient and agreed handling process are clear.

A portfolio structure we would actually use

We prefer a structure that lets the reader move from a simple explanation to the supporting record. It need not resemble a sales presentation. Strong evidence can be presented in an ordinary, legible document.

Begin with a concise professional summary. Name the activity, your role and the commercial arrangement. Avoid unsupported titles, awards or claims of expertise. If you describe yourself as a consultant, make the service concrete. If you describe a business, clarify whether you own it, work for it or both.

Follow with an evidence index. Each entry should explain what the document is and why it is included. A filename such as “final-final-new.pdf” does not help the reader. A descriptive index can connect the file to the project without changing the original document's content.

Then present the selected project summaries in a consistent order. For each, explain the engagement, your contribution, the relevant dates and the supporting files. Consistency is useful here because it reduces the work of finding information. It should not produce identical paragraphs that conceal meaningful differences between projects.

Add a short explanation of payment flows if the project records do not make them obvious. Place it close to the relevant transaction rather than burying it at the end. Include a separate note for any change of trading name or legal entity that affects several projects.

Finish with unresolved questions for your own review before submission. This is a private preparation list, not necessarily a document to upload. An issue should be resolved, accurately disclosed or deliberately left pending for a reason. It should not disappear because the portfolio now looks polished.

There is no universal page count in this method. A simple business might need little explanation. A more complex business may need more. Follow the official upload requirements and the receiving post's requests, and use additional pages only when they add evidence or necessary context.

What one older Reddit account does and does not show

In a Reddit account of a self-employed DTV application in Austria, the author describes submitting business, partner, accountant and payment records. They also describe a further request for business registration despite having included substantial material. It is a personal report from the early DTV period, not independently verified application evidence or a current official checklist.

The useful question it raises is why a large file can still leave a specific request unanswered. Our answer is to examine the document's function, identity and presentation. The fact that an applicant has included many pages does not establish that the precise evidence requested is present and recognisable.

We would not copy that author's package word for word. The person's business, filing jurisdiction and application date differ from another applicant's. Their reported processing time is not a forecast. Nor does their outcome prove that the same set will be accepted after later changes to residence or clearance requirements.

The practical lesson is narrower: make a requested record easy to identify, and preserve the exact wording of any follow-up request. That is an editorial response to an anecdote, not an inference that a consulate made an error or that more paperwork always improves an application.

Work through a hypothetical incomplete file

Imagine a freelance web developer who works with three overseas customers. One engagement is a monthly retainer, one is a recent completed build, and one is still at proposal stage. The applicant has a polished website, bank statements and a folder of screenshots, but the folder does not connect the records.

We would begin with the retainer because it may show an ongoing relationship. Check the actual agreement, the service period on the invoice and the related receipt. If payment comes through a platform, include an explanation of that link. The aim is to make one complete example understandable before assembling the rest.

For the completed build, identify the applicant's contribution and when the work was delivered. If the project was collaborative, avoid claiming the whole product as personal work. A brief accurate description with an authorised sample is better than an impressive but misleading screenshot.

The proposal-stage project needs a different label. A proposal is not completed work, and an expression of interest is not an existing contract. It might provide context about future business, but should not be presented as evidence of paid activity that has already happened.

Next, compare the professional summary with the documents. If the summary says “monthly income from three clients” but one has never paid and another project has ended, revise the summary. Do not revise the history to fit the summary. This is one of the simplest and most valuable checks in the process.

Finally, return to the official checklist. Does the professional package answer its requirement, and are the separate residence, financial, identity and clearance documents being handled? The portfolio should not consume all the available preparation time while a different necessary item remains unavailable.

Make names, languages and file versions consistent

An international freelance file may use several scripts and naming conventions. Your passport might give a full legal name, a platform might use a shortened name, and an older contract might use a previous surname. Do not assume that the connection will be obvious to someone reading the records for the first time.

Make a private identity list before assembling the final portfolio. Record the name shown in the passport, the names used in professional records and the genuine evidence connecting any material differences. An ordinary shortened display name may need only a clear explanation. A legal change of name may require a formal record. The applicable document and translation requirements must be checked for the receiving post.

Translations should help the reviewer understand an existing record. They should not quietly improve its wording or change an awkward fact. If a contract describes a limited project, the translation should not make it sound like permanent employment. If a payment statement uses a technical accounting label, preserve its meaning and explain it separately if needed.

We recommend keeping the source document, translation and any required certification together in the index. Give each a distinct label. That makes it clear which text is the original evidence and which is a translation or an explanation prepared for the application. It also helps you respond if the post asks about a particular phrase.

Version control matters for less dramatic reasons too. A client may update a confirmation letter, or you may correct a spelling mistake in your own summary. Keep the superseded version in your private history and identify which version belongs in the submission. Do not accidentally attach the old letter because its filename is familiar.

Before submission, compare the completed application answers with the final portfolio rather than with an earlier draft. The activity, employer or client description, income explanation and dates should remain consistent. If the facts changed while you were preparing, make the necessary truthful correction in the appropriate place instead of leaving two incompatible accounts.

This is especially useful when another person helps prepare the file. Agree who checks the final version and how changes are communicated. A polished portfolio that the applicant has never read is a poor result. You should be able to confirm that every statement describes your circumstances, including any explanation written on your behalf.

A final review that catches useful problems

Read the file once as someone who knows nothing about your business. Can you identify the service and your role in the first few paragraphs? Can you follow one project without opening every attachment? Does each important claim point to a genuine record?

Then check identity and dates. Look for inconsistent spelling, a trading-name change, a document addressed to another entity or a period that contradicts the application. Some differences have ordinary explanations. They should still be explained where they matter.

Open the submission files themselves, not just the originals. Check readability, page order, orientation and whether an export has cut off part of a document. A complete record on your computer does not help if the uploaded version contains only its first page. Follow the live portal's permitted formats and size limits instead of relying on an old tutorial.

Review every statement about the future. “I can deliver this service remotely” differs from a promise that a particular customer will retain you for five years. State what is actually agreed and what is your intention. Avoid treating a visa's validity period as a requirement to invent five years of guaranteed business.

Remove duplicated documents where they add no useful context, unless the portal or post requires the same record in more than one category. Keep a final index and a copy of what was submitted. If a further request arrives, that record allows you to answer accurately without guessing which version the authority received.

Questions freelancers ask during preparation

Do I need a personal website?

A website can explain your services and show public work, but it is not a substitute for the responsible post's requirements. We would assess what it actually demonstrates. Does it identify you? Are the examples yours to display? Does it describe current work? A new website filled with unsupported claims may be less useful than an ordinary document supported by real records.

Is one client enough?

Do not invent a minimum number of clients from our selection method. Check the receiving post's current wording and any request made in your case. The practical issue is whether the relationship and professional activity are understandable and adequately evidenced. One clearly documented engagement may explain more than several vague ones, but that observation does not guarantee an eligibility decision.

Can unpaid work appear in the portfolio?

It can illustrate skills if labelled accurately, but it should not be presented as paid commercial activity. Explain why it is included and distinguish it from actual client work. If most of the portfolio is personal practice and the application depends on freelance professional status, the underlying fit needs assessment. Extra design work cannot turn an intended future occupation into an established past one.

What if I do not have formal contracts?

Identify the genuine records that do exist: accepted proposals, platform agreements, invoices, delivery confirmations or other relevant correspondence. Describe the commercial arrangement honestly. Whether the available evidence meets the post's requirement is a separate question. Do not create a backdated contract, and do not ask a client to sign a description that misstates the history.

Should I include tax records?

Use the receiving post's actual requirements and consider whether a genuine tax record helps explain the business or income. A tax document may relate to a different period or measure a different kind of income from a bank receipt. Explain those differences where relevant. We would not recommend submitting an entire tax archive without a reason, or treating the portfolio as a substitute for tax advice.

Can an accountant's letter replace the original records?

A genuine professional confirmation may help explain a complicated arrangement, particularly where the author can accurately describe their role and the records reviewed. It does not automatically replace a document expressly requested by the authority. Avoid asking the accountant to certify facts outside their knowledge. The value of a letter comes from its accuracy and relevance, not merely its letterhead.

What if the file still has a gap?

Name it precisely. “No evidence connecting the trading name to the applicant” is actionable. “The portfolio feels weak” is not. You may need another genuine document, a clearer explanation, an official clarification or a different application strategy. Sometimes the responsible decision is to wait. We would rather identify that before submission than present a polished file whose central claim remains unsupported.

Choose the next step that fits the evidence

If your work is straightforward and the records are consistent, you may be able to assemble the file yourself against the current checklist. If the activity, business structure or filing eligibility is unclear, resolve that issue before spending time on presentation. Professional review is most useful when it answers a specific unresolved question.

Our preferred result is a portfolio you can explain in your own words. You should know what each document establishes, what it does not establish and where the main uncertainties remain. That understanding is useful during preparation, any additional-document request and later questions about your application.

Reader questions in Reddit and Quora-style discussions

These editorial questions focus on practical decisions in DTV for Freelancers: Build a Portfolio That Explains Your Work. They are not quotations from, or claims about, particular Reddit or Quora users. The answers apply the official-source distinctions explained above to this article's facts.

My client agreements are confidential. Can a portfolio still show genuine freelance work?

Usually the first task is to describe the work without disclosing more than the authority needs. A dated, consistent index can connect redacted agreements, invoices, payment evidence and public work samples. Confirm what the responsible mission actually accepts before masking names or amounts; a heavily redacted file with no coherent client-to-payment trail can be harder to assess than a smaller, well-explained one.

Do screenshots of my website prove I work remotely?

They can illustrate an activity, but a website alone does not establish current contracts, your role, payment history or eligibility. Explain the work in your own words and tie independent records to the same period. If the business is new or income varies, say so and identify the strongest genuine evidence rather than manufacturing a stable-looking history.

Reddit and Quora-style common questions are addressed in the community section below.