Correcting submitted data
Fix a typo in a submitted value without losing what the visitor originally sent, and see how the fix reaches the person.
Visitors mistype their own details. They write “jhon@” instead of “john@”, leave the phone field blank and give you the number on the call, or pick the wrong day for an appointment.
You can correct any submitted value on the lead, and PageFork keeps the original.
Corrections are a Pro feature. On a Basic site submitted values are read-only. See Basic and Pro plans.
Making a correction
- Open the lead page.
- In the timeline, click the submission card to expand it. Every field the visitor sent is listed.
- Click the pencil next to the field’s name.
- Edit the value.
- Click Save. Cancel or Escape leaves the value as it was.
Long values, and values with line breaks, open in a larger box.
Fields the visitor left blank are listed too, shown as a dash, so you can fill them in after a phone call.
You can only correct fields the submission already has. Corrections fix values. They don’t add new fields to a form.
The original is never overwritten
A correction is stored on top of what the visitor sent. The original submission is kept exactly as it arrived.
That’s what makes corrections safe. Any destination that already received this submission received the original. Rewriting it afterwards would leave PageFork and your other tools quietly disagreeing about what the visitor said.
Correcting a value doesn’t re-send anything. If another tool already has the wrong email, fix it there too.
How a correction reaches the person
A submission is a record of what was sent. The person is the record your team actually works with. When you correct a submission, PageFork carries the fix over to the person where that’s clearly what you meant.
Name, email, phone and company. If the corrected field is the one PageFork read the person’s name, email, phone or company from, the person is updated as well, as long as their current value is still the one from the submission or empty.
Custom fields. If the corrected field feeds one of the person’s custom fields, that field is updated under the same rule.
Details someone has edited are left alone. If a teammate has already changed the person’s phone number by hand to something else, correcting the old submission doesn’t overwrite their edit.
An example. A visitor submits jhon@example.com, and the person is
created with that email.
| You do | Submission shows | Person’s email |
|---|---|---|
Correct the submission to john@example.com | john@example.com | john@example.com |
Edit the person’s email by hand to j.smith@example.com, then correct the submission | john@example.com | j.smith@example.com, unchanged |
Two more details:
- Clearing an identity value in a submission doesn’t blank the person’s name, email, phone or company. Remove those on the person directly if you need to.
- Clearing a value that feeds a custom field does clear that custom field, under the same “still the submitted value” rule.
When the corrected email belongs to someone else
If you correct an email to an address that another person on the site already has, the correction is refused and nothing is changed. Moving a submission from one person to another isn’t something a typo fix should do silently.
If the two really are the same person, merge them instead.
What a correction changes
| Place | Shows |
|---|---|
| The submission card on the lead | The corrected value |
| The submission’s preview line | Rebuilt from the corrected values |
| The person’s details | Updated when the rules above apply |
| The calendar | The booking moves if you corrected the form’s booking date field |
| CSV export | The person’s details, so the fix is included once the person is updated |
| Destinations that already received it | The original. Nothing is re-sent |
| The lead’s timeline | Both, old value → new value |
Correcting a booking date
If the field you correct is the form’s
booking date field, the appointment is re-read
from the new value and moves on the calendar. Enter it the way the
form sends it, for example 2026-08-05 or 2026-08-05T14:30. A value
that can’t be read as a date removes the booking from the calendar.
The trail
Every correction is recorded in the lead’s timeline as “corrected”, with the field name, the old value, the new value, who did it and when. Long values are shortened there.
When the correction also updated the person, a second line records that too, for example “changed Email”.
So the original is never lost from view. It’s one scroll away.
Good to know
Can I undo a correction? Correct the field again and type the original value back. Both changes stay in the timeline.
The person didn’t update. Their current value was different from what the submission originally said, so PageFork treated it as a deliberate edit and left it. Change the person’s details directly in the Person panel.
Saving did nothing. The value you entered is the same as the current one, so there was nothing to correct.