A public form is an open door. That’s the point — anyone with the link can submit without an account — but an open door with no structure behind it lets in duplicates, typos, anonymous entries and answers nobody can act on.
“Governed” intake means keeping the door open while making sure what comes through is usable. Atlas builds that governance into every public form on the Advanced and Enterprise tiers.
Control 1: Know who is asking
Before an Atlas public form starts, it asks two things of its own: a name and an email address. That’s what attaches the answers to a person, so a submission is never anonymous to you, even though the page is open to anyone.
Identity capture changes the character of public intake. Every submission has someone to follow up with, and a submission that looks suspicious can be checked against a real contact.
Control 2: Validate at the source
Every section of a public form is one of the data schemas the form attaches, and every field keeps the type, format and required rule defined in that schema. An email field with the Email Address format only accepts a real email address. Required fields are marked with an asterisk and must be filled in.
Because the form is generated from the same schema Atlas stores, what a customer sees and what Atlas will accept can’t drift apart. Validation happens before the data exists, not in a cleanup pass afterwards. See Data quality starts at the point of entry.
Control 3: Review before submit
The last step of every public form is a review: every answer in one place, before anything is sent. Atlas is clear that this is the moment to fix things, because a submission can’t be edited afterwards.
A review step does two things. It reduces mistakes, because people catch their own typos. And it makes the submission a deliberate act, so what arrives is what the respondent meant to send.
Control 4: Set expectations up front
The public page shows your organization’s name, the form and what it’s for, and lists every step down the side — details, each section, and a final review. People know who they’re submitting to and how long it will take before they start, which reduces abandoned and half-hearted submissions.
Control 5: Land in one secure place
Submissions arrive in Data Collection, connected to the form they came from, rather than in an inbox. Access to Atlas is controlled, so public submissions are visible to your team rather than to whoever happens to be copied on an email. On Enterprise, security policies go further, controlling who can discover, read, write, archive and manage each part of your data.
Atlas’s documentation describes a further step for teams that need it: holding public submissions for review, so a person can approve, correct or reject them before they’re committed as records — the governance step that keeps public intake from polluting your data.
Why governance helps conversion, too
It’s tempting to think every control makes a form harder to complete. In practice, clear structure helps respondents: they know who they’re talking to, what will be asked, and that they’ll get a chance to check their answers. Good governance and a good experience point in the same direction.
What can still go wrong, and what to do
Governance reduces risk; it doesn’t eliminate it. A few situations worth planning for:
Someone submits on behalf of someone else. Identity capture records who filled in the form, not who the form is about. If that distinction matters, ask for it explicitly on the form.
A respondent mistypes their email. Format validation catches malformed addresses, not wrong ones. The review step helps, and a confirmation message tells people what to expect.
Duplicate submissions. People sometimes submit twice if they’re unsure it worked. A clear confirmation reduces this; a convention for handling duplicates handles the rest.
Unwanted submissions. A public link is public. Because every submission carries a name and email, unwanted entries are identifiable, and you can review what’s asked and where the link is published.
Governance checklist for a public form
- Does the page show who the form belongs to?
- Does it say what the form is for and how long it takes?
- Are identity details captured before the questions begin?
- Does every field have the right type, format and required rule?
- Is there a review step before submission?
- Do submissions land in one controlled place rather than an inbox?
- Does someone check them on a known schedule?
- On Enterprise, do security policies limit who can reach the data?
Balancing openness and control
The instinct when public intake goes wrong is to close it down — add approvals, restrict the link, require accounts. That usually costs more than it saves, because it makes it harder for the people you want to hear from.
A better balance is the one Atlas implements: keep the door open, but know who came through it, insist the information is well-formed, and give people a chance to check their answers. Most quality problems disappear at that point, and the ones that remain are visible and attributable.
Related concepts
Governed intake is one part of a broader practice. See Data governance for teams without a data team for ownership, definitions and access, and Data quality starts at the point of entry for the quality principles behind it.
