FaeWorks sample  ·  a real deliverable, on a fictional portal faeworks.com
Sample · fictional portal
FaeWorks · Forms Audit & Consolidation

Forms Audit & Consolidation

Northwind B2B · 11 live forms · 187,353 all-time submissions · audited 2026-09-03 · every form in the portal, what depends on it, and what replaces it

This is the workbook, rendered for reading. Download the .xlsx ↓ to see it as delivered.

1

What's in the Portal

Eleven forms doing four jobs — and what that has cost you.
11
live forms
4
jobs they actually do
4
standard forms replace all 11
4
forms with no automation attached
1
form never routed anywhere
100
page placements to update

Talk to Sales — Pricing Page has taken 311 submissions since it was created and routed none of them. It has no workflow, no list, no notification. Those people filled in a form on your pricing page and nothing happened.

2

Every Form Today

What exists, how much it's used, and — the column that matters — what automation depends on it.

Swipe the table sideways for the rest of the columns →

FormJobStatusSubmissionsConv.PagesLast submissionBuilt byAutomation depending on it
Request a DemoDemo requestKeep4,8203.1%492026-09-02MarketingWF: MQL routing · WF: Demo alert · List: Demo requests 90d
Get Started — HomepageDemo requestConsolidate1,2042.4%32026-08-28Web teamWF: MQL routing
Talk to Sales — Pricing PageDemo requestConsolidate3111.9%12026-08-19Sales opsNone — never wired up
Contact UsContact usKeep9183.4%12026-09-01MarketingWF: Contact us notification
Contact Us — SecurityContact usConsolidate6970.6%12025-11-14LegacyNone
2026 Benchmark ReportContent downloadConsolidate1,3899.0%22026-08-30MarketingList: Content downloads
Webinar — Scaling OpsContent downloadConsolidate7913.4%12026-06-11MarketingList: Content downloads
Guide — Attribution 101Content downloadArchive31631.0%02025-09-02MarketingNone
Subscribe to BlogNewsletterConsolidate174,6100.1%42026-09-03LegacyList: Blog subscribers
Footer — Email SignupNewsletterConsolidate2,2401.1%382026-09-03Web teamList: Blog subscribers
Event — Booth Scan 2025Event registrationArchive570.0%02025-06-11MarketingNone

Redundant here means same job, not same fields. Forms doing the same work were built by different people at different times, so their fields drifted apart. A form with no automation attached is either safe to archive or evidence its submissions have been going nowhere — both worth knowing before anything is switched off.

3

Where Each One Goes

Every form, the pages it sits on, and the form that replaces it. web team executes from this table.

Swipe the table sideways for the rest of the columns →

Current formPlacement / pageActionReplaced byWeb team notes
Request a Demo/request-a-demo (+48 CTA placements)KeepDemo RequestBecomes the standard. Check styling on every placement.
Get Started — Homepage/ (homepage hero)ConsolidateDemo RequestHero styling differs — verify render before go-live.
Talk to Sales — Pricing Page/pricingConsolidateDemo RequestConfirm hidden fields populate; this page loads JS late.
Contact Us/contactKeepContact UsBecomes the standard.
Contact Us — Security/securityConsolidateContact UsRoute to the same inbox before swapping.
2026 Benchmark Report/resources/benchmark-2026ConsolidateContent DownloadAsset delivered by workflow, not by form. Verify after swap.
Webinar — Scaling Ops/resources/webinar-scaling-opsConsolidateContent Download
Guide — Attribution 101not on a live pageArchiveNo page action needed.
Subscribe to Blog/blog (+3)ConsolidateNewsletter SignupHighest-traffic form on the site. Swap last, watch closely.
Footer — Email Signupsite-wide footerConsolidateNewsletter SignupAppears on 38 pages — the styling risk lives here.
Event — Booth Scan 2025not on a live pageArchiveNo page action needed.
4

The Standard Field Sets

One canonical form per job, so the next request lands on a form that already exists.

Swipe the table sideways for the rest of the columns →

FormFieldRequiredHiddenNotes
Demo RequestFirst nameYes
Demo RequestLast nameYes
Demo RequestWork emailYesBlock free-mail domains.
Demo RequestCompanyYes
Demo RequestWhat are you interested in?YesShort fixed list — drives routing.
Demo RequestSource / campaignHiddenIf the JS fails this arrives empty and attribution breaks silently.
Demo RequestPage URLHiddenRemoves the need for a per-page form.
Contact UsFirst nameYes
Contact UsWork emailYes
Contact UsReason for contactYesFixed list. Absorbs Security, Partner and Media — no separate form needed.
Contact UsMessageNo
Contact UsSource / campaignHidden
Content DownloadFirst nameYes
Content DownloadWork emailYes
Content DownloadCompanyNoProgressive profiling candidate.
Content DownloadAsset requestedHiddenThis is what removes the need for one form per asset.
Content DownloadSource / campaignHidden
Newsletter SignupWork emailYesEmail only. Anything more suppresses conversion.
Newsletter SignupSource / campaignHidden

A hidden field carrying the asset or the page is what lets one form serve many pages. It is also the thing that fails silently when the JavaScript doesn't run — which is why it appears again in the hand-off below.

5

What To Do With This

Two hand-offs: what you archive, and what your website team ships.

A · What to archive

Nothing has been disabled. Archiving is your call, and these are ordered by how safe they are to do.

1
Archive now — Guide — Attribution 101 and Event — Booth Scan 2025. Neither is on a live page, neither has automation attached, and neither has taken a submission in over a year. No dependency to break.
2
Archive after the inbox is confirmed — Contact Us — Security. 0.6% conversion, nothing since November 2025. Point /security at the standard Contact Us and confirm those messages land in the same inbox first.
3
Archive only after the swap ships and test submissions pass — Get Started, Talk to Sales, 2026 Benchmark Report, Webinar — Scaling Ops, Subscribe to Blog, Footer — Email Signup. Each is still live on a page. Archiving one before its replacement is confirmed working takes the page down with it.
4
Decide separately what happens to Talk to Sales' 311 orphaned submissions. They were never routed. They are still contacts in your portal and nobody has ever followed up.

B · What to hand to the website team

Section 3 is the sheet they work from. Page building is theirs; nothing below requires portal access.

1
Place the four standard forms and swap 9 forms across 100 placements, in the order given in section 3.
2
Swap the footer and the blog last. Footer — Email Signup appears on 38 pages and Subscribe to Blog is the highest-traffic form on the site. Everything else is a smaller blast radius.
3
Test-submit on every page after each swap and open the contact record to confirm the hidden fields populated — not just that the form submitted.

Two things that go wrong after hand-off

stylingA consolidated form now appears on more pages than the one it replaced. Styling that held on one page won't necessarily hold on all of them. Visible, so it gets caught — but only if someone looks at every placement.
silentThe JavaScript fails and the hidden fields arrive empty. The form still submits. The contact is still created. Everything looks healthy. Source and campaign are blank, and attribution degrades from that moment with nothing to surface it. This is why the test in B3 is opening the record, not watching the form submit.

FaeWorks — Forms Audit & Consolidation · sample workbook · fictional portal · illustrative data · 2026-09-03