What Makes an Evidence Package Stronger?

When an account is restricted, a payout is frozen, or a profile is suspended, the immediate instinct is often to upload everything.

Business owners may pull together years of tax returns, transaction records, customer conversations, screenshots, emails, licences, and anything else they think might help.

The thinking is understandable: if I provide enough information, the platform will eventually see that my business is legitimate.

But more evidence does not automatically make a stronger case.

A reviewer needs to understand what the evidence establishes, why it matters, and how it relates to the issue being reviewed. A large collection of poorly organised or irrelevant files can make that harder.

A stronger evidence package is not necessarily a larger one.

Relevance, structure, consistency, and clarity matter more than volume.

01The Five Tests of Strong Evidence

Before adding a document to a case package, run it through five simple tests.

Relevant: Does the document establish something important to the specific issue being reviewed? For example, if a platform is reviewing fulfilment, an old tax certificate may establish that the business exists, but it may not address the fulfilment question. Evidence should have a purpose.

Authentic: Can you stand behind the document as a genuine, unaltered record from its original source? Do not edit, manipulate, or manufacture evidence to make it fit the case. If a document has been legitimately redacted to protect unnecessary sensitive information, make sure the remaining information still accurately represents the original record.

Consistent: Does the document agree with the rest of the case? Check it against account or profile information, business documents, website information, other evidence, your timeline, and your written explanation. A document that appears useful on its own can create a problem if it contradicts something else in the package.

Understandable: Can someone unfamiliar with the case quickly understand what the document shows? A reviewer shouldn't have to guess why a file was included. Clear file names, short descriptions, and an evidence index can make a significant difference.

Necessary: Does the document add something useful, or does it simply duplicate evidence you already have? If three documents establish the same fact and a fourth adds nothing, the fourth may not improve the package.

The goal isn't to submit everything you have. It's to submit the evidence that helps establish the important facts.

02Volume Is Not the Same as Strength

Consider two different approaches.

A weaker evidence package looks like this: 47 files uploaded without explanation, duplicate screenshots, unclear file names, several unrelated documents, different versions of the same record, no evidence index, no timeline, and no explanation of what individual documents establish.

A reviewer then has to work out what each file is supposed to demonstrate and which documents actually matter.

A stronger evidence package looks like this: a smaller collection of relevant documents, clear descriptive file names, documents organised logically, a timeline showing important events, an evidence index, important gaps identified, inconsistencies addressed, and each important claim connected to supporting evidence.

The difference isn't simply the number of files. It's the amount of work the package requires the reviewer to do.

A strong evidence package makes the important information easier to find, understand, and verify.

03The Core Elements of an Organised Case

A structured evidence package looks beyond individual documents and considers how the entire submission fits together.

Evidence index: create a master list showing each item, what it supports, and its status. For example:

The purpose is simple: give the reviewer a clear map of the evidence.

Clear document names: use names that explain what the file is. Lease-Agreement-June-2025.pdf is more useful than Document_1.pdf. A good file name can provide context before the document is even opened.

Timeline: a timeline shows when important events happened and connects those events to the supporting records. This can reveal both well-supported events and gaps in the case.

Gap identification: don't hide missing evidence. If you don't have current proof of an address, say so. If you cannot establish the exact date of an event, don't invent one. A known gap can be addressed. An undisclosed gap can become a credibility problem later.

Contradictions: look for differences between legal and trading names, addresses, business descriptions, website information, account information, dates, business categories, service areas, and ownership information. Not every difference means there is a problem. Some have legitimate explanations. The important thing is to identify them and determine whether they need clarification.

Remove unnecessary documents: more files don't automatically make the case stronger. If a document doesn't help establish a relevant fact, doesn't answer a platform request, and doesn't add useful context, consider leaving it out.

Protect sensitive information: evidence can contain information that isn't relevant to the case, such as full bank account numbers, personal identification numbers, unnecessary customer information, private contact details, and other sensitive information. Where appropriate, unnecessary information can be redacted while keeping the information needed to establish the relevant fact visible. The goal is to provide useful evidence without unnecessarily exposing private information.

04Facts, Claims, Evidence, and Unknowns

One of the most important distinctions when preparing a case is understanding the difference between what you know, what you say, what you can support, and what you simply don't know.

At Casiflo, this distinction is central to how we think about evidence.

A fact is an objective statement that can be established from a reliable record. For example, the business was registered on June 12, 2024, and a business registration document may establish this date.

A claim is a statement you make about the business or what happened. For example, we ship physical goods within 48 hours of receiving an order. That may be true, but the statement itself isn't evidence.

A claim becomes evidence-supported when relevant records establish it. For example, the business states that orders are shipped within 48 hours, supported by order records and carrier pickup timestamps. The evidence gives the reviewer something they can actually examine.

An unknown is something you currently cannot establish from the records available to you. For example, the exact date of the address change cannot currently be established from the available records. That isn't necessarily a failure. It is simply an unresolved part of the case.

The dangerous step is turning an unknown into a fact. That can happen when someone guesses a date, assumes why a platform took an action, treats an unrelated document as proof, fills a gap from memory, or makes a claim that the available evidence cannot support.

It's better to identify an unknown than to present an unsupported assumption as a fact.

Once a gap is identified, you can look for additional records, explain the limitation, or reconsider how the claim should be presented.

05Connect Claims to Evidence

A strong package doesn't just contain documents. It shows how those documents relate to the important claims in the case.

For example: claim, the business operates from 123 Main Street. Evidence: Utility Bill.pdf and Lease.pdf. Status: supported.

Or: claim, the business is licensed to provide the stated service. Evidence: none. Status: evidence missing.

This distinction matters.

A folder containing a licence, utility bill, website screenshot, and registration document may look impressive.

But the more useful question is: what does each document actually establish?

That's the difference between document collection and evidence preparation.

06Look for Consistency Before You Submit

Evidence should not be reviewed in isolation.

Compare the important information across the entire case:

The exact fields will vary depending on the platform and case.

The purpose is to identify anything that needs explanation before the package is submitted.

For example, a legal entity might have one name while operating under a legitimate trading name. That isn't automatically a problem.

But if the difference isn't explained and the evidence uses several different names without context, a reviewer may have difficulty understanding the relationship.

Consistency doesn't mean every document has to look identical. It means legitimate differences should be understandable and supported.

07Use the Evidence to Find the Gaps

Once the package is organised, ask: what important fact is currently unsupported? Which platform question hasn't been answered? Is there a document I expected to have but don't? Does a claim in the explanation go further than the evidence allows? Are there dates I still cannot establish? Is there an inconsistency that needs an explanation?

These questions can reveal weaknesses before the platform does.

And sometimes the right answer is not to find another document.

Sometimes the correct answer is to change the explanation so that it accurately reflects what the evidence can establish.

That is an important part of evidence preparation.

08A Simple Final Review

Before submitting an evidence package, work through the following checklist.

Evidence quality: ☐ Is each important document relevant? ☐ Is the document authentic and unaltered? ☐ Does it agree with the rest of the case? ☐ Can a reviewer understand what it shows? ☐ Does it add something useful?

Case structure: ☐ Is there an evidence index? ☐ Are files clearly named? ☐ Is there a timeline where one is needed? ☐ Are important claims connected to evidence? ☐ Have unnecessary duplicates been removed?

Gaps and inconsistencies: ☐ Have missing documents been identified? ☐ Have conflicting dates been checked? ☐ Have differences in business information been reviewed? ☐ Have unsupported claims been removed or clarified? ☐ Are unknowns clearly identified rather than guessed?

Sensitive information: ☐ Have unnecessary private details been removed or redacted where appropriate? ☐ Is the information being shared actually necessary for the case?

Finally, ask: if someone unfamiliar with the business opened this package, could they understand what the important evidence establishes without having to guess?

If the answer is yes, you've moved beyond simply collecting documents. You've built an evidence package.