A carrier signs your underwriting workbench, and the next question arrives fast: how does a submission get into our Guidewire PolicyCenter? Your product already captures the account, the exposures, and the loss runs. What it lacks is a route into a system your engineers have never built against.
Guidewire expects its own structure. The account must exist first, a short set of fields is required to create the submission, and a quote fails when the job lacks the data rating needs. Each carrier also configures its own products, so a route built for one instance does not carry over cleanly to the next.
This guide explains what PolicyCenter requires, where the effort in a custom connector goes, and how building, hiring, and using a prebuilt gateway compare.
What Does It Take to Get a Submission Into Guidewire?
Getting a submission into Guidewire means creating an account and a submission job in PolicyCenter, filling that job with coverage and contact content, and leaving it ready to quote. Every step expects Guidewire's data shape, not yours.
What a Workbench Owns and What It Does Not
An underwriting workbench supports the work that happens before a policy exists: intake, triage, risk review, and pricing. The carrier's policy administration system, PolicyCenter for a carrier on Guidewire, owns the policy once it is created.
The Submission Handoff Path
We call the route from your system into PolicyCenter the Submission Handoff Path. It has four steps, and each raises a question your team has to answer.
Step | What happens in PolicyCenter | Question for the vendor |
|---|---|---|
1. Account | The account that owns the submission exists first | Does your payload create the account or find it? |
2. Job | A submission job is created with a status of Draft | Which required fields does your payload supply? |
3. Content | Coverages, contacts, questions, and risk data are added | Which of your fields map to which structures? |
4. Quote readiness | A quote call succeeds only when rating data is present | What happens to a submission that is not quote-ready? |
What Does PolicyCenter Require Before It Accepts a Submission?
PolicyCenter accepts a submission only when the account already exists and the request carries five fields: account, base state, job effective date, producer code, and product. Guidewire's Cloud API documentation lists these as the minimum creation criteria for the 2025 release of PolicyCenter for Guidewire Cloud. Carriers on other releases confirm the equivalent requirements with their own Guidewire team.
The Account Comes First
A vendor sends the insured as an account first, then the submission against it. Guidewire documents a composite request that creates the account, creates the submission, adds content, and quotes the job in a single call.
Five Fields Every Submission Carries
The base state is the jurisdiction of the account's primary location. The job effective date sets when the policy starts, and the producer code ties the submission to the agency or MGA that placed it. The product field takes the product's ID, which the carrier's own product configuration defines.
What Fails at Quote
A submission can be created and still not be ready to quote. When the job lacks information that rating requires, the quote call fails. Guidewire's example from the base Personal Auto product is a covered vehicle with no driver.
Where Does the Effort in a Custom Guidewire Connector Go?
The effort in a custom Guidewire connector goes into three places: learning Guidewire's structures, matching each carrier's configuration, and maintaining the connector after every change.
Learning Guidewire and Matching Each Carrier
Guidewire's Cloud API is organized around jobs, lines of business, coverables, coverages, questions, and modifiers. Your engineers learn how a job moves from Draft to Quoted before they write the first mapping.
The product ID then comes from each carrier's own configuration, so your payload needs a lookup against every instance, not a fixed value.
Keeping Up After Go-Live
A connector you build is a connector you maintain. Each carrier you add is another point-to-point connection to patch when something upstream changes.
Build, Hire, or Use a Prebuilt Gateway
Carriers hit the same wall from the other direction, because scaling partner underwriting stalls on custom engineering per partner.
Question | Build in-house | Hire an integrator per carrier | Prebuilt gateway the carrier runs |
|---|---|---|---|
Who holds the Guidewire knowledge? | Your engineers | The integrator | The gateway |
Who writes the mapping? | Your team, field by field | The integrator, per engagement | A draft is generated, and your administrator confirms it |
What repeats for each carrier? | The whole build | The engagement | The mapping, on shared tooling |
Where does the data sit? | Wherever you host it | Depends on the build | Inside the carrier's environment |
What Does Payload Mapping Do in a Submission Handoff?
Payload mapping matches each field in a sender's data to the field Guidewire expects, so a submission or claim lands in the right place on the first send.
Confirm the Producer Code Before You Send
The producer code is a required field, so a vendor needs the carrier's valid codes before the first send. Checking the code in your system first keeps a submission from reaching the carrier without a valid placing producer.
Send Loss History and Prior Policies
PolicyCenter stores loss history and prior policies as risk analysis information that underwriters use, and both can be edited during a submission. Mapping your extracted loss runs into them puts the data where the underwriter looks.
Log Every Request and Response
Every send needs a record of the request, the response, and any error, so your team and the carrier's read the same facts. Reliable insurance data exchange depends on that shared record.
How InsOps Helps
InsOps builds an insurance-trained AI that assists with moving submission data into Guidewire. LiLa, our insurance-trained LLM, drafts the mapping from your payload to the carrier's Guidewire structure, and a person on your team reviews and confirms every mapping before data moves.
InsOps is a Guidewire technology partner with prebuilt connectors to Guidewire's core products. The InsOps Integration Gateway handles authentication, validation and request logging, so your engineers spend their time on your product instead of on Guidewire APIs.
A vendor that serves several carriers gets tenant-specific mappings, so each carrier's Guidewire structure has its own confirmed mapping. For a submission, you check the producer code first, and the gateway flags incomplete data before it reaches an underwriter.
The gateway and LiLa run inside the carrier's own environment, so PII and PHI stay in controlled infrastructure. If you are evaluating how to exchange submission data with a carrier's Guidewire instance without building your own connector, contact us to talk through what this looks like for your operation.
Frequently Asked Questions
What is an underwriting workbench?
An underwriting workbench is a centralized system that brings together the data, tools, and workflows an underwriter uses to assess and price a risk before a policy exists.
Does an underwriting workbench replace a policy administration system?
No. The workbench supports intake, triage, and pricing, while the policy administration system, such as PolicyCenter, issues and services the policy.
What does Guidewire PolicyCenter require to create a submission through the API?
The account must exist first, and the request carries the account, base state, job effective date, producer code, and product ID. The product ID comes from the carrier's own product configuration.
Why does a quote call fail after a submission is created?
Rating needs specific content on the job, so the quote call fails when that content is missing. Guidewire's example is a covered vehicle submitted without a driver.
What should a vendor track to know the handoff is working?
Track how many submissions reach Draft without correction, how many are quote-ready on first send, and which fields cause rejected sends.
How does the InsOps Integration Gateway help?
It gives a sender a prebuilt route into the carrier's Guidewire products, with LiLa drafting the mapping from the sender's payload. A person at the sender reviews and confirms every mapping before any data moves.