My ImmiReport looks wrong

Most “wrong” reports are one of two things: a report that has not been recalculated yet, or a profile that does not say what you think it says. Neither is a calculation error, and both are things you can check in a minute.

What each number means and where it comes from is in scores and how they are calculated. This page is for when the number is not what you expected.

What this page will not tell you

Whether you should score a particular number under a particular program is an immigration question, not a product one. Lexpoint evaluates the facts in your profile against criteria published by IRCC and the provinces. For the criteria themselves, see immigratic.com, or book a consultation.

I changed my profile and the score did not move

Cause. Nothing recalculates when you save. Saving a profile field marks your report stale; the recalculation is a separate background job. This is deliberate — one recalculation computes every score, every eligibility flag, and every ranking in a single pass, so it runs once after your edits rather than after each keystroke.

You can tell the report knows: a strip appears across the top of every ImmiReport page reading Immireport will refresh in a few minutes, and hovering it says Your profile changed, so this report is queued for recalculation. Scores and eligibility refresh automatically. While the strip is showing, the Up to date freshness badge beside the score disappears, so two competing freshness messages are never on screen at once.

Fix.

1. Confirm the strip is there. If it is, the edit registered and the recalculation is queued.
2. Wait, and reload the page. Automatic recalculation is included on every account, free ones included.
3. If you have ImmiReport Pro, select Refresh now on the strip, or Refresh beside the report title. It recalculates everything at once and reloads the page. On a free account the same controls carry a Pro badge and open the upgrade panel instead of recalculating — Pro buys the timing, not the calculation.

The strip that confirms a profile edit registered and a recalculation is queued.

The strip is not showing, and neither is the change

Cause. Not every profile field feeds the report. A change is only treated as score-affecting when it lands in one of the six areas the report is calculated from: personal info, work history, education history, language tests, job offers, and letters of acceptance. Editing something outside those — a contact detail, a notification preference — correctly changes nothing, so no strip appears.

The second cause is an edit that was never saved. A form left open, or a modal closed before saving, leaves the profile as it was.

Fix. Reopen the profile section and confirm the value is actually stored — go to Profile and read the field back rather than trusting what you typed. If it is correct and no strip appeared, the field does not feed the score. Which fields do is set out in how your profile is used.

Refresh now did not work

Cause. The refresh runs against the database and can fail — a dropped connection, a session that lapsed while the page was open. It says so rather than pretending: a Refresh failed message appears and the button returns to its normal state.

Fix. Reload the page and try again. If it fails a second time, the automatic recalculation still runs on its own, so your report is not stuck — it is only waiting. Report a repeated failure through Help & Support with the time you tried.

A program is missing from my report

Cause. Depending on which program, one of three things:

• It is a program Lexpoint does not assess yet. Those are labelled Coming soon and carry no eligibility answer. The work permit page is the clearest example — Lexpoint shows processing times and says plainly that stream matching is not built.
• It is there, but not eligible, so it does not stand out. A provincial row you cleared no streams on still appears with its count badge — eligible streams over streams evaluated. Zero eligible is a result, not an absence.
• It is a stream inside a family you have not opened. Provincial hubs group streams into sections, and some groups are collapsed. Open the province’s hub and expand the sections.

The full coverage list, province by province, is in provincial programs.

Fix. Open the Permanent Residence hub and read the count badge on the province you are looking for. If the family is listed and the badge reads zero eligible, the program was evaluated. If it is not listed at all, it is not in Lexpoint’s coverage yet, and nothing you change to your profile will make it appear.

A number is not what I expected

Cause. In order of how often it turns out to be the answer:

1. The report is stale. Check for the strip first — you may be reading yesterday’s number.
2. The profile does not say what you think. Every number is derived from what is stored, not from what you meant. A test date, a start or end date on a job, a country field left at its default — each moves a score without looking like it should.
3. You are comparing the wrong scores. The number in a province’s caption is that province’s own ranking score, not your CRS score — an Arrima total for Québec, an expression-of-interest total for Ontario. Comparing a provincial number against a CRS number will always look wrong.
4. A missing fact makes a question undecidable rather than negative. A requirements verdict of Maybe means Lexpoint is missing a fact it needs to decide, not that you failed. Not yet is the negative one.

Fix.

1. Recalculate, or wait for the recalculation, so you are reading a current number.
2. Open the score breakdown and find the component that is not what you expected, then open the profile section that feeds it and check the stored value.
3. If the stored profile values are right and the number still does not make sense, that is a question for a person. Book a consultation — see getting help.

Numbers moved that I did not touch

Cause. Most factors are combinations rather than single fields, so one edit moves several numbers. A recalculation also computes everything at once, which means a change you made days ago and a change you made this morning can land together in the same refresh.

Fix. Nothing to fix. The ImmiReport hub shows a delta chip beside a number a recent recalculation moved, labelled with the date, which is the fastest way to see what actually changed and when. See scores and how they are calculated.

My report was never generated

Cause. Scores unlock only once four profile sections hold data:

1. Personal Info — date of birth, citizenship country, and marital status. All three.
2. Work History — at least one entry.
3. Education — at least one entry.
4. Language — at least one test.

Marital status is the one people miss, because the section looks finished without it.

Once all four are present, Lexpoint creates and calculates the report the next time you open /app/immireport — you do not have to ask for it.

If your account was migrated from Lexpoint’s earlier system, there is a second gate: you are asked to confirm those sections are still accurate, on a card reading Confirm your migrated profile, before scores appear.

Fix. Open ImmiReport and read the card on the page. It names the sections still missing and links to the first of them — Lexpoint never redirects you to the profile without explanation. Fill those in, then return to the report page. See what ImmiReport is.

What to bring to support

Open a ticket at my.lexpoint.io/app/tickets with:

• The exact ImmiReport page URL — the program page, not just /app/immireport.
• The number you are looking at, and the number you expected.
• Whether the stale strip was showing when you looked.
• What you changed in your profile, and roughly when.
• A note that you have already checked the stored profile value.

Support can tell you why the product produced a number. Whether that number is right for your immigration plan is a consultation question, not a ticket.

Related

• What ImmiReport is — unlocking, and when it recalculates
• Scores and how they are calculated — which profile fields feed which number
• Provincial programs — what is covered, province by province
• How your profile is used — which fields reach the report