Home / Guides / How to Organize a Relationship Timeline and Evidence Index

How to Organize a Relationship Timeline and Evidence Index

Published by LovHQ · Content and source check: 10 October 2026. No individual author or professional reviewer is claimed.

A relationship timeline is a dated outline of important events; an evidence index points from each event to the original record that may help you check it. Build both as private planning documents, then compare them with the official instructions for the exact country and route. Neither a timeline nor a collection of messages establishes eligibility or predicts an immigration decision.

What a timeline is for, and what it cannot decide

When two people live in different countries, dates can become hard to reconstruct. Trips, periods apart, visits with family, changes in where someone lived, and shared decisions may sit in separate calendars, email accounts and travel folders. A short timeline lets the couple organize those facts before searching an official application guide. It can also help identify dates that need checking against an original booking, passport record or other source.

The timeline is not an application form, legal opinion, universal proof checklist or substitute for the authority’s current requirements. Immigration routes differ by country and by relationship status. Some applications ask for relationship details; others have particular forms, evidence categories, translation rules, document formats or submission portals. Only the responsible authority's live instructions define what applies to the route you are considering.

Start with a route label before collecting records

Write the destination country, exact route or visa category if known, who would apply, and the date you checked the official page. If you do not know the route yet, label the file “general planning” rather than borrowing another country's evidence list. Keep immigration requirements in one column of your work and private relationship notes in another. That simple separation reduces the chance that a remembered example becomes mistaken for a universal rule.

The differences are substantive. In the United States, USCIS describes a K-1 process for a foreign fiancé(e) of a US citizen, with marriage intended within 90 days after admission and a general prior in-person-meeting requirement; a petition for a spouse is a different route. In the United Kingdom, GOV.UK describes the family partner route and a route-specific way for some couples who cannot live together to show an ongoing relationship. Canada's family-sponsorship guide has its own categories and application package, while Australia's Home Affairs instructions direct applicants to the document list for the relevant family visa. These examples are not interchangeable. Start at the linked authority and read the instructions for the exact route rather than taking a different country's document examples as a checklist.

Build a concise timeline from original records

Use one line for an event or meaningful period, not every message. Helpful fields are: date or date range; place; what happened in plain language; whether both people were present; the original record you used to check it; and a note about uncertainty. Examples of useful milestones include first meeting, when the relationship became committed, visits, time living together if relevant, significant periods apart, meeting important people in each other's lives, engagement or marriage where applicable, and decisions about where to live.

Use “approximately” or a date range when that is more accurate than guessing a day. If the first message was in late spring but the record is not available, write that plainly and mark it to verify. Do not silently convert memory into a precise date. A chronology that distinguishes known, estimated and unconfirmed facts is more useful than a polished story whose precision cannot be explained.

Keep the note factual rather than persuasive. “Visited from 4 to 18 May; flight confirmation in travel folder” is easier to check than “This proves we have a genuine relationship.” The first identifies an event and its source. The authority, not the spreadsheet, decides how a document is treated.

Create a separate evidence index

The timeline answers “what happened when?” The index answers “where is the original record, and what does it relate to?” A compact index can include an item ID, date range, source or file type, event it relates to, route or checklist it was compared against, sensitivity level, language or translation status, and the original storage location. You can add a neutral note such as “confirms travel date” or “shows shared address period.” Avoid writing a conclusion about what an officer must decide.

For example, an entry might say “R-04, 12-20 August, airline itinerary and boarding-pass image, visit to Toronto, original booking in personal email, sensitive travel data, compare with the current IRCC checklist.” That is a fictional format example, not a claim about an actual couple or a promise that the records meet any Canadian requirement. Replace it with your facts and route. You may keep the index on paper or in a file you control; LovHQ does not ask you to upload it.

Preserve the original file wherever practical. If a document needs a working copy, name it as a copy and do not change the meaning, date, surrounding context or source. If a record contains an error, keep the source and explain the correction in a separate note. Never fabricate a document, backdate a note, or edit a screenshot to imply something that did not happen.

Use examples only within their route

Official sources show why the route label matters. For a US spouse petition, USCIS lists examples that can include a marriage certificate, joint property, a joint lease, combined finances, children's birth certificates, third-party affidavits and other relevant records. That is US spousal-petition guidance, not a universal “long-distance visa evidence” list and not the K-1 fiancé(e) standard.

For a UK family partner application, GOV.UK asks applicants to provide information about how the couple met, how often they see each other and how long they have lived together, along with route-specific financial and identity evidence. Its page describes evidence examples for some partners who cannot live together, including regular communication, financial support, care of shared children and time together. Whether a route is available depends on the full official requirements, not one document category.

For Canada, use the current IRCC application package and checklist that matches the applicant's situation and country. IRCC's guide describes multiple relationship categories and country-specific instructions. For Australia, Home Affairs directs family-visa applicants to the step-by-step document list for the visa and tells applicants how to handle documents that are not in English. Those short descriptions are orientation only; they do not replace the current package, subclass page or portal instructions.

Do not use the UK route's two-year relationship language as a rule for another country. Do not turn an example of a US joint lease into an assertion that couples living apart must have a lease. Do not treat one route's translation format, relationship category or supporting statement as universal. The actual question is always: what does the authority ask of this applicant, for this route, at the time they apply?

Choose a small, relevant record set

More files do not automatically make a clearer record. Start with the official checklist, then identify which facts it asks you to document. Select records that are relevant, readable and consistent with the timeline. If you are considering messages or photographs, use a proportionate sample only where it fits the official instructions. Avoid exporting an entire private conversation by default. It may expose unrelated personal, financial, health or family information about either partner and other people.

For each proposed item, ask: Does it relate to a fact the route asks about? Can I explain where it came from? Is it complete enough not to mislead? Is it in the required language or format? Does it contain data about someone who is not part of the application? If you cannot answer these questions, pause and return to the official instructions or seek qualified advice for that jurisdiction.

Privacy review is separate from an authority's evidence rule. You may organize records privately and avoid sending unnecessary material around, but do not redact or remove information in a way that violates the relevant instructions or changes the evidence's meaning. Keep passports, account credentials and originals under the control of their owner. Sharing passwords is not a relationship document.

Check dates and conflicts before relying on the index

Read the timeline beside the source documents. Look for mismatched spellings, travel dates, cities, address ranges, relationship-status dates and periods of living together or apart. A discrepancy does not tell you why it happened; it is a prompt to verify the source and explain what you know. Do not erase an awkward date simply because it does not fit the narrative you expected.

Be explicit about time zones and local dates when a travel itinerary crosses midnight. Keep the original time zone if that is how the record is shown. Separate a ticket's issue date from the date of travel, and an online booking from the actual trip. Record the distinction in your own index so a future reader does not have to guess what the date means.

Give each file a neutral name such as “2026-08-12_to_2026-08-20_travel-confirmation_copy”. Avoid putting passport numbers, full account identifiers, intimate details or another person's name in a filename if it is not necessary. Keep the source file in its original place and use an access-controlled folder of your choosing. The LovHQ Privacy Policy explains what the browser tools do; it is not a secure document vault, and there is no need to enter private documents into the site.

Keep the route check current

Rules and application packages change. Note when you opened a government page and recheck it before acting, especially if the application will be filed later. Use the official source page for a current fee, translation instruction, form edition or document checklist rather than relying on a saved third-party checklist. If a source page sends you to a different form or online account, follow the current official path.

The LovHQ visa preparation checklist can help you list broad planning questions for the US K-1 and UK partner/spouse routes, but it cannot assess eligibility or an application. The marriage documents tool is a separate organizer for questions about a local registry. Neither tool replaces immigration instructions. If visits are part of your chronology, the Days Together Calculator can count dates you choose; it does not verify travel evidence.

A privacy-first workflow you can reuse

1. Choose a destination and exact official route page, or mark the record as general planning if the route is undecided.
2. Draft the timeline from memory with dates, date ranges and confidence labels.
3. Check each milestone against original records and add source locations, not copies of sensitive content.
4. Build the index only for categories the official checklist actually asks you to consider.
5. Review for date conflicts, missing context, duplicate files, third-party information and translation instructions.
6. Keep a note of the source and check date, then re-open the government page before using the organizer for an application.

For a route-neutral approach to organizing visits and records, read how to plan an annual visit budget. If a possible move is part of the story, the transition-planning guide covers household decisions without turning them into immigration tests. The aim here is a clear, private record of what happened, not a claim that a particular outcome will follow.