Skip to main content

Someone wanted to learn this too, so Grasp built them a personal learning path.

You can keep exploring this one or create your own

Mapping Stakeholders, Jobs, Incentives, and Constraints in Customs Filing

Hello! Last lesson turned a proposed customs-filing integration into a problem statement: filing specialists sometimes have to clarify manufacturer or country-of-origin information before an Importer Security Filing (ISF) draft is ready. The illustrative sample—31 paused drafts out of 120—described a problem, but it did not explain who could resolve each pause.

This lesson widens the view. You will map the people and organizations around a U.S. ocean-import filing, the jobs they perform, what success means to them, and what limits their actions. The result is a stakeholder map you could use to evaluate an integration proposal without assuming that everyone who touches a shipment has the same responsibilities.


Set the boundary of the workflow

“Customs filing” can refer to several related activities. An ISF occurs before a U.S.-bound ocean shipment arrives; customs entry and release involve other information and decisions. A useful map therefore names its boundary. For our running example, the focal job is getting an ISF draft ready and submitted with supportable information, while noting downstream entry work where it explains a stakeholder’s interest.

Watch how an import shipment brings together the importer, supplier, broker, customs authority, and other parties. Focus on the handoffs rather than the video’s specific timing or penalty figures; requirements should be checked against current guidance for a real shipment.

US Customs Brokerage Training – Import Process

Watch US Customs Brokerage Training – Import Process from Scarbrough Global for a practical account of who supplies documents, who prepares filings, and who responds when information is questioned.

Start with shipment context, from the purchase order through ISF and the broker's need for commercial documents. Then watch broker interactions to see how the broker works with the importer and CBP. In agency roles and cargo coordination, notice that some parties become relevant only for particular goods or shipment arrangements.

The CBP diagram below shows why it is worth setting that boundary. It depicts a broader ACE collections life cycle, including entry, release, collection, and post-entry activities. It is not a step-by-step ISF map, and its segments should not be read as a path every shipment follows.

CBP’s ACE collections diagram depicts activities around arrival, entry, release, collection of duties and fees, liquidation, bills, and refunds. It provides broader import context; the ISF preparation problem in this lesson sits outside much of this collections view.

For a product decision, begin with a narrower question: When a filing specialist finds conflicting manufacturer information, whose information is it, who can check it, and who can act on the answer? That question exposes stakeholders more reliably than a list of organizations involved in international trade.


Map jobs across organizational boundaries

A stakeholder is a person or organization that performs work, supplies something the work depends on, makes a relevant decision, or bears a consequence. Their job is what they are trying to accomplish in this workflow—not their job title. An incentive is a reason a particular result matters to them; a constraint is something that limits what they know, may do, or can change.

A service blueprint offers a helpful way to look beyond the person using the proposed integration. It distinguishes customer-visible work from supporting work behind the scenes and makes dependencies between them visible.

Service Blueprints: Definition - NN/G

Read Nielsen Norman Group’s Service Blueprints: Definition to learn a compact method for separating the filing specialist’s actions from the work of suppliers, brokers, administrators, and systems.

In “Key Elements of a Service Blueprint,” read the four action types. In “Lines,” read the boundaries, paying particular attention to what the customer can and cannot see. Under “Secondary Elements to Include in a Service Blueprint,” find “Regulations or Policy” and “Metrics”; read policy constraints and operational measures.

For an integration product, the filing specialist’s screen may show a missing field or an unresolved discrepancy. Behind that screen, a supplier may hold the source document, an importer’s compliance lead may need to judge the information, and a broker may be preparing the submission. Labeling all of this “the filing process” hides the critical handoffs.

One distinction is especially important: a freight forwarder primarily coordinates cargo movement, while a customs broker performs customs-related work for its client. The same business might offer both services, but the jobs remain distinct.

Freight Forwarder vs. Customs Broker: What's the Difference?

Watch Freight Forwarder vs. Customs Broker: What’s the Difference? from Shipping Solutions to sharpen that distinction before assigning work on the map.

Watch distinct roles. Notice the forwarder’s transport coordination, the broker’s customs function, and why a combined service provider should not make you collapse the two responsibilities into one box.


Build the stakeholder map

Return to the illustrative paused ISF drafts from last lesson. The table below is a starting map for one possible shipment arrangement, not a claim that every shipment uses these parties in exactly this way. The incentives are plausible hypotheses to check with the people involved.

Stakeholder Job in or around the filing What success may mean to them Important constraint or dependency
Overseas supplier or manufacturer Provide product and shipment facts, and clarify disputed source information. Send accurate information without repeated requests or disruption to shipping plans. May not see the importer’s filing draft or know which detail needs clarification.
Importer’s filing specialist Assemble information, resolve discrepancies, and track readiness for filing. Complete an accurate filing with enough time to address exceptions. Cannot verify a fact that has not been supplied; may see conflicting records without knowing which is authoritative.
Importer’s trade-compliance lead Set review practices and resolve or escalate compliance questions. Maintain defensible decisions and dependable operations. Must weigh speed against the need for supportable information; may oversee many shipments.
Customs broker, if engaged Review supplied information, prepare or transmit filings within its authorized role, and handle questions. Submit workable, accurate filings and avoid repeated clarification cycles. Depends on the importer and other parties for facts; its ability to act is bounded by authorization and applicable rules.
Freight forwarder Coordinate transportation and communicate relevant shipment milestones or documents. Keep cargo movement predictable. May know transport status but not be the authority for a product fact such as its manufacturer.
Carrier Operate the transport service and provide carrier-controlled shipment information. Move cargo while meeting its own operational and reporting obligations. Controls different information from the importer or broker.
CBP Receive and evaluate required submissions and administer customs requirements. Receive compliant, usable information for its responsibilities. Does not resolve the importer’s missing supplier data on the importer’s behalf.
Integration provider and customer account administrator Move permitted data between systems and manage who can use the connection. Reliable exchange, appropriate access, and manageable support effort. A technical connection does not create missing facts, grant unlimited access, or make customs decisions.

Other stakeholders are conditional, not forgotten. A partner government agency may matter when the goods fall under its requirements; a surety may matter in a bond-related part of the arrangement. Add them when the scoped workflow gives them an actual job or decision, rather than filling the map with every possible trade participant.

Notice also that doing work and bearing responsibility are not the same thing. A broker can help prepare a filing, while the importer still has important obligations concerning the information supplied. Conversely, the person expected to answer a question may lack the source record needed to answer it. A good stakeholder map shows both facts.


Find the handoff that an integration might change

Suppose the filing specialist sees one manufacturer value in a supplier message and another in the draft. “Sync the manufacturer field” sounds useful, but the map reveals several different situations:

  1. The correct value exists in a trusted source but was copied incorrectly. Better transfer or validation might help.
  2. Two sources disagree and no one has resolved why. Transferring either value faster could spread the error; a review and decision are needed.
  3. The supplier has not yet provided the information. A connection between the importer’s and broker’s systems cannot supply a fact neither possesses.

For each disputed piece of information, record four things on the map: where it originates, who can verify it, who needs it next, and what prevents a timely handoff. Add the artifact involved—a message, document, draft field, or filing status—so the map describes observable work rather than vague “communication.”

Document requirements can make these handoffs consequential. In the following short segment, listen for which records the broker needs and why receiving them early changes what can be checked.

US Customs Brokerage Training – Import Process

Return to US Customs Brokerage Training – Import Process for the document handoff. This segment concerns customs entry more broadly, so use it to understand stakeholder dependencies—not to treat every document mentioned as an ISF field.

Watch document dependencies. Notice the different purposes of the invoice, packing list, bill of lading, and documents that depend on the goods. The closing question about when to send files reinforces the value of lead time.

Some constraints are about access, not the accuracy of the underlying information. CBP’s ACE Portal account structure distinguishes a company’s business-activity views from individual user profiles and their permissions.

Introduction to an ACE Secure Data Portal Account | U.S. Customs and Border Protection

Read CBP’s Introduction to an ACE Secure Data Portal Account to see why “the importer has access” is too imprecise for a workflow or integration design.

At the beginning of the page, read the account overview, including the definitions of top accounts, sub-accounts, and user profiles. Then find “Overview of Account Management Features by User Profile.” Starting at the permissions table, compare who can add business activities, create users, and manage access. Distinguish these portal permissions from responsibility for the accuracy of a shipment’s information.

In a product map, do not turn portal access into a blanket claim that a person—or an integration—may read or change every record. Specify the action needed and the relevant authorization. Likewise, a filing status visible to one party is not necessarily evidence that another party has reviewed or agreed with the underlying value.

The map now suggests sharper discovery questions: Was the manufacturer value unavailable, copied incorrectly, or disputed? Who noticed first? Who had authority and evidence to resolve it? Those questions identify where an integration could remove work and where it would merely move uncertainty to another screen.


Takeaway

A customs-filing stakeholder map connects people to jobs, incentives, constraints, information, and decisions. It keeps the supplier, importer, broker, transport parties, authorities, and product provider distinct, even when their work overlaps. Most importantly, it shows the difference between moving a value and establishing that the value is ready to use.

Next, you will distinguish product outputs, user outcomes, and business impacts. This map will help you ask whether a proposed integration merely transfers data—or actually improves the filing specialist’s work without shifting risk elsewhere.

Can't find a good explanation? Sign up and we'll make it for you

Sign up