# The Fixed-Fact Match Standard, Six Artifacts Graded Before Each Send

*Grade one outgoing application's 10 to 12 fixed facts across six artifacts as Match, Allowed Variance, or Mismatch, and block the send on any Mismatch.*

- Canonical URL: https://www.refolk.ai/candidates/guides/fixed-fact-match-before-submit
- Pillar: Applying at volume
- Format: Standard
- Published: 2026-11-15
- Last reviewed: 2026-11-15
- Reading time: 21 min
- Keywords: application form dates don't match resume, resume and LinkedIn dates different, applying to multiple jobs same company different resume, job application consistency check before submit, workday autofill wrong work history, does the ATS keep my old application

## Key takeaways

- Grade every fixed fact against a ledger built from W-2s, payslips, or offer letters, never against another artifact, because two documents written from memory can agree with each other and both be wrong.
- Month-year employment dates get zero Allowed Variance: screening reports flag any mismatch, and the 2 to 3 month tolerance some employers allow is their decision, not something a candidate can assume.
- The employer's candidate record counts as a sixth artifact, because Workday reuses your most recent application to prefill the next one and Greenhouse keeps every past resume and overwritten field on one candidate record.
- Use one email per employer: Workday and Greenhouse both key identity on email, so a changed email splits your history and a reused one auto-merges into the oldest profile.
- In Refolk's index, 1,297 US recruiters list Workday as a skill against 295 for Greenhouse, a ratio of 4.4 to 1, so Workday's prefill flow is the default case to plan for.
- Run the gate before submit, because candidates cannot edit a submitted Workday application and later profile edits never change an earlier submission.

This standard is for people sending a separately tailored resume, cover letter, and set of form answers to every posting, across many employers at once. Before you click submit, it lets you confirm that the fixed facts (names, titles, dates, location, contact details, work authorization, pay figure) say the same thing everywhere this employer will look. That includes what the portal prefilled and what you sent them last time. You get a ledger of 10 to 12 facts, three grades with written rules, an eight-step procedure, and a send gate that blocks on any Mismatch.

## What does the fixed-fact match standard check?

It checks that 10 to 12 fixed facts in one outgoing application are either identical across six artifacts or differ only within written limits. Anything outside those limits is a Mismatch, and the application does not send until it is fixed.

Three terms, defined once:

- **Fixed fact:** a fact with one true value in your records, whichever posting you apply to. Your start month at a past employer is fixed. Which achievements you lead with is not.
- **Ledger:** one written record of each fixed fact's true value and the document that proves it.
- **Artifact:** any place this employer will read a fixed fact.

The six artifacts graded for every application:

1. The attached resume.
2. The portal's work-history and profile fields, including anything it prefilled.
3. The cover letter.
4. The screening answers.
5. Your public profile.
6. Earlier submissions sitting in this employer's candidate record.

Each fact in each artifact gets one of three grades:

| Grade | Meaning | Send? |
|---|---|---|
| Match | Same as the ledger in substance | Yes |
| Allowed Variance | Differs, but the difference is on the written variance list | Yes |
| Mismatch | Any other difference from the ledger | No |

**What a clean grade proves:** your application agrees with your ledger. **What it does not prove:** that your ledger is right. If the ledger came from memory, a perfect score only means you repeated the same mistake six times. That is why step one builds the ledger from payroll documents.

The sixth artifact is the one generic proofreading lists leave out, and it matters most on the platform you are most likely to meet.

**4.4x - More US recruiters list Workday as a skill than Greenhouse**

In Refolk's index of professional profiles, 1,297 US recruiters and talent acquisition specialists or partners list Workday, against 295 who list Greenhouse.

## Which facts belong in the ledger?

The ledger holds the facts employer-side fraud checklists say they cross-check (dates, locations, titles, employer names, contact details), plus the answers you type into forms: work authorization, pay figure, and education. That comes to 12 facts for most people, and fewer if you have no degree to report.

Employers say plainly what they compare. Glider's candidate-fraud checklist calls "mismatched dates or locations across the resume, LinkedIn profile, and application form" an early signal. Interviewer Signal's checklist has a line for "resume dates compared with the application and public profile." Brainner adds contact details: "email addresses created recently, phone numbers with no carrier history, or VoIP numbers that do not match the candidate's claimed location." Background screening works from the same facts, at month-year precision, using the title "as it appears in your employment contract or HR records."

### Identity, contact, and form answers

| Fact | Source of truth | Allowed Variance |
|---|---|---|
| Name | Government ID or payroll name | None in name fields |
| Email | The one address used for this employer | None |
| Phone | Your active number | None |
| Location | Where you live now | None in location fields |
| Work authorization | Your actual status | None, typed by hand |
| Pay figure | Your written target for this role | None within one application |

### Work and education history

| Fact | Source of truth | Allowed Variance |
|---|---|---|
| Employer of record | W-2, payslip, or offer letter | Structure fixed per role |
| Start month-year | First payslip or offer letter | None |
| End month-year | Last payslip or separation letter | None |
| HR title | Contract or HR records | Parenthetical market title |
| Institution and degree | Diploma or transcript | Standard abbreviation |
| Graduation date | Diploma | None |

Relocation plans go in the cover letter, never in a location field. Once a location field has a value, that value is a fixed fact.

## How do you grade a fact Match, Allowed Variance, or Mismatch?

Grade every fact against the ledger, never against another artifact. A fact is a Match if it equals the ledger. It is Allowed Variance only if the difference appears on the written variance list below. Everything else is a Mismatch, including a fact that reads the same in all six artifacts but disagrees with the ledger.

### The written variance list

These differences between tailored versions are allowed:

- **Bullet order and selection** inside a role.
- **Emphasis and wording** of accomplishments.
- **A parenthetical market title** after the HR title, for example the HR title followed by the title the market uses for that work in brackets.
- **Summary and skills content**, which are presentation and not fixed facts.
- **Standard abbreviations** of a degree or institution, provided the abbreviation is unambiguous.

Nothing else may vary. That list includes employer names, month-year dates, email, phone, location, the authorization answer, and the pay figure inside one application.

> **Rule:** Zero drift on month-year dates
>
> Employment and graduation dates get no Allowed Variance, ever. Screening reports "flag any mismatch; the report doesn't distinguish lying from rounding," and any tolerance belongs to the employer, who does not tell you what it is.

The reasoning: InCheck reports that "employers may allow for a two- to three-month discrepancy on employment dates, while diploma dates usually need to be accurate." Notice the "may." That tolerance is the employer's setting, the screening provider publishes no threshold, and you cannot see it from outside. Octagnt's screening guide says "when dates shift between the resume and LinkedIn, even by a single month, that inconsistency is almost never accidental." If you cannot know the tolerance, the only rule you can defend is zero.

Year-only dates are a Mismatch in this standard. Verification works at month level, so "2019 to 2022" on a resume next to month-year dates on the form reads as two different claims.

### Titles: the case the evidence does not settle

No published checklist says an internal-versus-external title difference, or a promotion partway through a tenure, is not a fraud signal. That is not established publicly. The closest statement is noon.ai's "no single red flag is conclusive," and that is not permission. So decide titles in advance:

- The **HR title** from your contract or HR records goes in every title field and on the resume line.
- A **business title** may appear only as a parenthetical, and that counts as Allowed Variance.
- A **promotion** is two ledger rows with their own month-year dates, never one row carrying the later title for the whole tenure.

### Pay figure across applications

Inside one application, the pay figure must be identical in the cover letter, the screening answer, and any form field. Against an earlier submission to the same employer for a different role, I grade a different figure as Allowed Variance only when the role level is different and the log says why. Without that note it is a Mismatch, because a recruiter looking at both records sees two numbers and no explanation.

#### Grading a fixed fact

Horizontal axis runs from Agrees with payroll record to Disagrees with payroll record. Vertical axis runs from Same wording everywhere to Wording varies across artifacts.

| Quadrant | What it means |
| --- | --- |
| Allowed Variance or Mismatch | Allowed only if the difference is on the written variance list |
| Mismatch | Fix the artifact that departs from the ledger, then fix the rest |
| Match | Send |
| Hidden Mismatch | Correct the ledger from payroll, then regrade all six artifacts |

*The dangerous quadrant is the bottom right, where every artifact agrees and all of them are wrong.*

## Why does the employer's own record count as an artifact?

The employer keeps your earlier applications, uses them to prefill new ones, and can show a recruiter old values next to new ones. Whatever you sent this employer last quarter is still in its system beside today's tailored resume, and that is why "does the ATS keep my old application" deserves a yes.

### Workday

- **Identity:** "Workday uses the candidate's email address as an identifier. This identifier helps reduce duplicate candidates in the system."
- **Reuse:** "If a candidate applies to at least one job, Workday uses the information from the most recent job application for any subsequent job applications."
- **Start routes:** Autofill with Resume, Apply Manually, and Use My Last Application. The last one lets you "edit all fields and add or replace documents," but "you cannot change your application after submission."
- **Prefilled fields:** "name, contact and location, education, and work experience." The share of standard fields that get prefilled is not established publicly.
- **Profile edits:** changes to a Workday Candidate Profile "never impact a previously submitted job application," and there is "no cross-tenant sharing of individual application histories." In practice, each employer's record stands alone.
- **After submit:** recruiters can edit your "Experience and/or Application Materials." You cannot.
- **Reactivation:** a recruiter can reactivate a declined application, and you show up in the last stage you reached before being dispositioned. The disposition reason "is recorded for the employer, not shown on your status."

### Greenhouse

- **Duplicate tag:** fires when a profile "matches on at least one of your duplicate tagging criteria (name, email, phone number, or LinkedIn URL)." Greenhouse's Chrome extension "always checks all four criteria," whatever the in-app setting.
- **Auto-merge:** stricter than the tag. One help article says "only candidates and prospects with identical email addresses are merged," even when the names differ. Employers can now choose which criteria must match, so look at Greenhouse's current release notes before assuming the default.
- **Which profile survives:** auto-merge "will prioritize the oldest candidate profile," and "candidate profiles cannot be un-merged."
- **What survives the merge:** "deprecated fields will always be listed on the candidate Activity Feed after a merge."
- **Stored files:** the anonymize option covers "all attachments and resumes for all applications associated with the candidate," which shows every past resume is kept on the one record.
- **Retention:** set by the employer "per office, and separately for rejected and (if enabled) hired candidates," with the timer starting "when a candidate is rejected on all job applications." No fixed period is published.

| Platform | Identity keys | Auto-merge | Prior data kept |
|---|---|---|---|
| Greenhouse | Name, email, phone, LinkedIn URL (tag) | Yes, criteria configurable | Overwritten fields on activity feed |
| Workday | Email | Not documented | Most recent application reused |

No time window for duplicate detection is published for either platform.

### Which platform to plan for

| ATS skill | US recruiters | Sample employers |
|---|---|---|
| Workday | 1,297 | Boeing, Siemens, Lenovo, Takeda |
| Greenhouse | 295 | Meta, Snowflake, Warby Parker |
| Ratio | 4.4 : 1 | |

Source: Refolk's index, covering the titles Recruiter, Technical Recruiter, TA Specialist, and TA Partner. Employers come from a 25-profile sample. One caveat: "Workday" listed as a skill may mean the HR system rather than Workday Recruiting, so read the ratio as direction, not as market share. The same index shows 70 UK recruiters and TA specialists or partners listing Workday. Either way, a US job seeker applying to large enterprises should treat Workday's prefill flow as the default.

#### How a fixed fact gets frozen

1. **Prior record** - The employer holds your most recent application, keyed to your email
2. **Prefill** - The portal loads name, contact, location, education, and work experience
3. **Your edits** - You correct or replace fields and documents, or leave them as loaded
4. **Submit** - Your copy locks and later profile edits do not reach it
5. **Stored** - The recruiter sees it, can edit it, and can compare it with past files

*Whatever is in the portal fields at the moment you click submit becomes the employer's record, and only a recruiter can change it afterwards.*

> Prefill freezes the facts at the moment you submit, so the gate has to run before the click.

## The pre-submit grading procedure

Run these eight steps for every application. Steps 1 and 2 happen once and get reused. Steps 3 to 8 happen per send. No source publishes timings. As a desk estimate I have not verified, building the ledger takes about an hour once, and listing prior applications takes about five minutes per employer.

#### Grade one application before it sends

1. **Build the ledger from payroll records** - Write each employer of record, month-year start and end, and HR title from a W-2, payslip, or offer letter, then add contact, location, education, authorization, and pay facts. Done when every one of the 10 to 12 facts names its source document.
2. **Fix one structure per agency or contract role** - For each agency or contract role, choose agency-as-employer or client-with-"via" and record it in the ledger. Done when that structure is the only one used in any artifact.
3. **Sign in and list prior applications** - Sign in to this employer's portal with the email you used before, list active and inactive applications, and pull your own saved copies of what you sent. Done when you know the email on file and what the record holds.
4. **Choose the start route deliberately** - Pick Upload new resume, Apply Manually, or Use my last application on purpose, knowing the last option brings in the previous tailored resume and old answers. Done when the route was a decision and not a default.
5. **Grade every prefilled portal field** - Before you move past the work-history page, compare each prefilled name, contact, location, education, and work experience field against the ledger. Done when every field is marked Match, Allowed Variance, or Mismatch.
6. **Grade resume, cover letter, and screening answers** - Grade the attached resume, the cover letter, and every screening answer against the ledger, and type salary and work authorization by hand. Done when every fixed fact in every artifact has a grade.
7. **Grade the public profile** - Compare employer names, titles, and month-year dates on your public profile against the ledger. Done when the profile has no Mismatch, or the Mismatch was fixed before submit.
8. **Block on any Mismatch, fix, and log** - Do not submit while any Mismatch remains; fix the artifact where the error lives, regrade, then log the role, date, and email used. Done when the Mismatch count is zero and the log line exists.

### Notes on the steps

- **Step 3, when you cannot see the record.** Workday's Candidate Home lets you "view their active and inactive job applications." Whether you can see the full contents of each one depends on the employer's setup, and I have not found that documented. If you cannot see what you sent, your own sent log is the only copy you control. Keep the exact files, not just their names.
- **Step 4, where sources disagree.** One autofill guide says autofill first, then check. UW guidance says Apply Manually gives "more control over what to include." A Workday resume guide treats autofill as a first draft. My position: any route works if step 5 grades every field. Only choose Use my last application when you plan to replace the documents, because it "sends the resume you tailored for a different posting."
- **Step 6, the two hand-typed answers.** Salary and work authorization never come from autofill. They change between employers more than anything else, and a wrong stored answer is costly.
- **Where tailoring adds risk.** Every tailored version you build by hand is another chance for a date or title to drift. [Refolk](/candidates) writes each tailored resume and cover letter from your one stored history, so the fixed facts are not retyped for each version and only the emphasis changes. You still grade the portal fields, the profile, and the employer's record yourself, because those live outside any document you write.

**Fixed-fact grading sheet, one application**

```
EMPLOYER: ____________   ROLE / REQ ID: ____________   DATE: ________
EMAIL USED FOR THIS EMPLOYER: ____________   PRIOR APPLICATIONS ON FILE: ___
START ROUTE: Upload new resume / Apply Manually / Use my last application

FACT                  | LEDGER VALUE | SOURCE DOC | RESUME | PORTAL | COVER | SCREENING | PROFILE | PRIOR
1  Name               |              |            |        |        |       |           |         |
2  Email              |              |            |        |        |       |           |         |
3  Phone              |              |            |        |        |       |           |         |
4  Location           |              |            |        |        |       |           |         |
5  Employer of record |              |            |        |        |       |           |         |
6  Start month-year   |              |            |        |        |       |           |         |
7  End month-year     |              |            |        |        |       |           |         |
8  HR title           |              |            |        |        |       |           |         |
9  Institution/degree |              |            |        |        |       |           |         |
10 Graduation date    |              |            |        |        |       |           |         |
11 Work authorization |              |            |        |        |       |           |         |
12 Pay figure         |              |            |        |        |       |           |         |

GRADES: M = Match | AV = Allowed Variance (write which rule) | X = Mismatch | n/a = not present
X COUNT: ___      SEND ALLOWED ONLY IF X COUNT = 0
LOG: role ________ | date sent ________ | email used ________ | resume file ________ | pay figure ________
```

*Copy once per application. Fill the ledger column from source documents, then grade each artifact column M, AV, or X.*

Repeat rows 5 to 8 for each role you list. A typical history fills most of a page, and that is fine.

## How does the fact match go wrong?

Seven failure modes account for most bad sends. Each one either produces a Mismatch you never see or produces a false Match, where the grade says clean but the facts would fail verification.

### 1. Dates rounded to the year

- **How it fails:** verification works at month level, so year-only dates read as a mismatch.
- **The false positive:** checking your resume against your own LinkedIn treats one remembered timeline as verified when both came from the same memory. This is the classic "resume and LinkedIn dates different" problem in reverse: they agree, and both are wrong.
- **The check:** grade against payslip or W-2 months.

### 2. A title Match that later fails verification

- **How it fails:** a Blind user reported a yellow flag after listing their official business title, because the check "pulled an internal administrative title."
- **The check:** keep both titles in the ledger and decide in advance which one is Allowed Variance. An unverified secondary source says payroll-based verification returns a payroll title plus first and last payroll dates. If that is true, the payroll title is the one being matched.

### 3. Client named as employer for agency work

- **How it fails:** a payroll lookup returns the agency, so verification fails even though every artifact agrees.
- **The check:** the employer of record is whoever paid you. See the structure rules in the next section.

### 4. Email changed between applications

- **How it fails:** a new email creates a second Greenhouse profile and splits your history, so your prior-submission artifact disappears from view and the grade for that column is meaningless.
- **The reverse failure:** reusing an email auto-merges into the oldest profile, where overwritten values stay visible on the activity feed. That is not a reason to switch emails. It is a reason to grade the old record before you send.
- **The check:** one email per employer, recorded in the log.

### 5. Use my last application

- **How it fails:** it brings the previous tailored resume and old form answers into the new application. This is the usual cause behind "workday autofill wrong work history" searches.
- **The check:** replace every document and regrade every field, or start a different way.

### 6. Editing the portable profile and assuming the employer's record changed

- **How it fails:** profile edits "only apply to future applications." The submission you are worried about still holds the old values.
- **The check:** treat every past submission as frozen, and ask the recruiter for a correction if it matters.

### 7. Fixing it after submit

- **How it fails:** candidates cannot edit a submitted Workday application. Only the recruiter can, and asking costs a little goodwill and a little time.
- **The check:** the gate runs before the click. Every step in the procedure exists to avoid this one.

> **Watch out:** Agreement is not accuracy
>
> The most common false pass is a set of artifacts that all agree because they were all copied from one stale source. If the ledger cites no payroll document for a fact, grade that fact Mismatch until it does.

Interviewer Signal's note on date mismatches cuts both ways: a mismatch is "often an old resume; sometimes dates stretched to cover a dismissal or a job left off." A reviewer cannot tell which from the outside, and the screening report will not tell them either. Whatever the reason behind the drift, it looks the same from where they sit.

## Which situations force a structure choice before you grade?

Agency contracts, temp-to-perm roles, concurrent jobs, and multiple roles at one employer all need a structure decision recorded in the ledger before you grade anything. Once decided, the structure is a fixed fact, and switching it between applications counts as a Mismatch.

| Situation | Ledger rule | Evidence |
|---|---|---|
| Agency contract | Agency as employer, or client "(Contract via Agency)" | Sources agree |
| Temp-to-perm | Client as employer for whole period | One guide |
| Concurrent jobs | State freelance or part-time | Thin |
| Several roles, one employer | One row per title, own dates | Not established |
| Boomerang stint | One row per stint, own dates | Not established |

What the sources say:

- **Agency contracts:** advice agrees that you should "never hide the agency, because employment verification will show it." Another guide says "do not switch structures to improve appearances." Either structure passes. Switching between them does not.
- **Temp-to-perm:** "list the client company as the employer for the entire period." Check this against your own payslips. If the agency paid you for the temp stretch, record that in the ledger and decide how it appears before your first application, not partway through your search.
- **Concurrent jobs:** the only advice found is to say whether the second role was freelance or part-time. Make that label a fixed fact.
- **Several roles at one employer, and boomerang stints:** I found no recommended form wording. Those two rows are my own rule. They follow from verification working at month-year level against payroll dates, but treat them as a reasoned default, not settled practice. If an employer's form only allows one row per employer, use the first start and last end month-year with the HR title you left with, and record that choice in the ledger.

## Before you click submit, and how to keep the ledger current

Run the checklist below on every application. Then keep the ledger current by changing facts in one direction only: ledger first, then public profile, then portal profiles, so no artifact ever gets ahead of the record it is graded against.

#### Send gate for one application

- [ ] Every fact in the ledger names a payroll, offer, diploma, or ID document as its source.
- [ ] Every agency, contract, and temp-to-perm role uses the structure recorded in the ledger.
- [ ] I signed in with the one email I use for this employer and listed prior applications.
- [ ] The start route was chosen on purpose, and any reused documents were replaced.
- [ ] Every prefilled portal field is graded, including education and location.
- [ ] All employment and graduation dates are month-year and match the ledger exactly.
- [ ] Every title field shows the HR title, with any business title only in parentheses.
- [ ] Salary and work authorization were typed by hand and match the cover letter.
- [ ] My public profile shows the same employers, titles, and month-year dates as the ledger.
- [ ] The fact set matches what I sent this employer before, or each difference is on the variance list and explained in my log.
- [ ] The Mismatch count is zero.
- [ ] I have a log of the role, date, and email used.

### Keeping it current

- **When a fact changes** (new job, move, new phone), update the ledger the same day, then the public profile, then every saved portal profile you still use. Profile edits reach future applications only.
- **When you find a Mismatch in something already sent**, decide whether it matters enough to raise. A wrong month-year date, employer name, or authorization answer does. Recruiters can edit Experience and Application Materials after submission, so ask once, plainly.
- **When an employer comes back months later**, assume your old record is still there and regrade against it. Retention is the employer's choice, and no fixed period is published.

**Correction request after submit**

```
Subject: Correction to my application for [Role], Req [ID]

Hi [Name],

I submitted my application for [Role] on [date] using [email]. One field is wrong: my [start/end date at Employer / title at Employer / work authorization answer] reads [wrong value] and should read [correct value], as shown on my [W-2 / offer letter / payslip].

I can't edit the application after submitting, so I'd be grateful if you could update it. Everything else in the application stands.

Thank you,
[Name]
[Phone]
```

*Send to the recruiter or the address on the requisition. Change only the bracketed facts and keep it this short.*

When the same correction keeps coming back across several applications, the cause is upstream: a stale saved profile, a reused last application, or a tailored resume that drifted from the ledger. Fix the source rather than patching each send. Because Refolk generates every tailored version from the same history, a fix made once in that history carries into every version you produce afterwards. Portal profiles and past submissions still have to be checked one employer at a time.

## Frequently asked questions

### Does the ATS keep my old application?

Yes. How long it keeps it is up to the employer, and no fixed period is published. Workday uses the details from your most recent application to prefill later ones. Greenhouse lets each employer set retention per office, and the timer starts only once you are rejected on every application. Greenhouse also stores the attachments for all your applications on one candidate record, so plan on a recruiter being able to see what you sent before.

### What do I do if my application form dates don't match my resume after I already submitted?

Write to the recruiter, because on Workday you cannot edit a submitted application yourself. Recruiters can edit Experience and Application Materials after submission. Give the correct month-year dates, name the document they come from, and keep the note short. Then fix whatever caused the error, usually a stale portal profile or a reused last application, so the next submission is clean. Editing your portable profile will not change the application you already sent.

### Can I send different resumes to multiple jobs at the same company?

Yes, as long as only the presentation changes and the fixed facts stay the same. Bullet order, emphasis, and a parenthetical market title can vary between tailored versions. Employer names, month-year dates, contact details, and your authorization answer cannot. Treat every earlier submission to that employer as an artifact you grade against, because the employer's record can put the old resume next to the new one.

### Why did Workday autofill put the wrong work history in my application?

Autofill reads whatever source you picked and sometimes drops information into the wrong fields. Use my last application also brings in the resume you tailored for a different posting, plus your old form answers. Before you leave the work-history page, grade every prefilled field against your ledger. Fix stale entries there, not after you submit.

### Do my resume and LinkedIn dates need to match exactly?

Yes, to the month. One fraud-screening guide says a shift of even a single month between resume and LinkedIn is almost never accidental, and screening reports flag any mismatch without telling rounding apart from lying. Some employers tolerate two to three months, but you cannot see that setting. Grade both documents against your payslip or W-2 months, not against each other.

### Should I use my official title or my business title on applications?

Put the title from your employment contract or HR records in every title field, and add the business title in parentheses if it helps. No published checklist says an internal-versus-external title difference is excused. One candidate reported a verification flag because the check pulled an internal administrative title. Write both titles in your ledger and decide in advance which one counts as Allowed Variance.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/candidates/guides/fixed-fact-match-before-submit*
