A deal can stall after verbal agreement because the customer's procurement team will not issue a purchase order until the supplier is registered in its portal. Sales support often learns about the portal late, when the customer asks for a vendor number or sends a registration link. The intake record looked complete because it captured the contact, the need, and the budget, but it missed the path the order must travel. This protocol describes a bounded test of whether sales support intake captures a customer procurement portal requirement before the quote moves forward.
Research question and scope
The research question is whether a sales support intake record captures the customer's procurement portal requirement, including the portal name, the registration status, the owner, and the next deadline. The scope is one team and one intake path during a fixed review window, not a comparison across sectors or procurement systems. The test asks whether the intake gives the coordinator a usable next step, not whether the customer will award the business. It does not measure win rates or payment timing, because those outcomes need a separate review. Keep the frame narrow so the finding can support one concrete change to the intake fields.
Population and unit of analysis
Begin with every intake record created during the review window that reached a quote or a handoff. Record the intake identifier, the account, the owner, the source channel, the deal type, and whether a procurement portal was mentioned. The unit is one intake record, so an account with several requests can contribute several rows. Include inbound forms, rep referrals, and event follow-ups if they use the same queue. Exclude records that were duplicates or spam, and note each exclusion with a reason so the denominator stays visible.
Set the review window
Choose a window that covers a normal intake workload, such as four to six weeks. Freeze the start and end dates before coding and keep them fixed after the first result appears. If the intake form or the procurement policy changes during the window, split the result at that date or note the change beside the finding. A stable window keeps the comparison honest and makes a later repeat measurement useful. Write the window in the report so a reader can judge whether the result still applies to the current quarter.
Define a procurement portal requirement
A procurement portal requirement exists when the customer will not issue a purchase order, contract, or payment unless the supplier registers, updates its profile, or submits documents through a named system. Define the term before coding and list the signals that count, such as a registration link, a vendor number request, a supplier onboarding packet, or a portal name in the customer's message. Record whether the requirement was stated by the customer or inferred by the team. An inference is a lead, not a confirmed requirement, until someone points to the customer message or portal record that supports it.
Build the evidence dictionary
Each row needs the intake identifier, the account, the owner, the source channel, the deal type, and the portal name if one exists. Add the registration status, the portal identifier, the customer contact who owns the process, the next deadline, and the evidence message. Record whether the requirement was captured at intake, added later, or never recorded. The dictionary should let a later reviewer reproduce the coding without asking the original analyst what a category meant. Keep a short note field for portals that serve several customers or require a third-party administrator.
Test design
Use a census when the intake volume is small and a documented sample when it is large. Freeze the intake export before coding so edits made during the test do not move the target. Have one reviewer code every record and a second reviewer check a subsample without seeing the first result. Record every disagreement and resolve it against the written definition rather than personal preference. If a record mentions a portal but the reviewer cannot find the registration status or owner, mark it incomplete rather than passing.
Compare the intake date with the portal request date
The core comparison is between the date the portal requirement entered the record and the date the customer first raised it. Calculate the difference in days and note whether the team captured it at intake, after the quote, or only when the customer asked for a purchase order. A late capture is not automatically a failure if the customer raised the issue late, so record who introduced the requirement. Report the distribution rather than only an average, since one long delay near a quarter close can distort the picture. The result should show where the team can intervene earlier.
Check the registration status and the owner
A portal requirement without a status and an owner is a note, not a plan. Check whether the record shows whether the supplier is unregistered, in progress, active, or blocked. Identify the person responsible for the registration, including whether it sits with sales support, finance, legal, or the customer. Record the next deadline, such as a registration approval date or a purchase order cutoff. If the status is blank, mark the record incomplete even when the portal name is present, because the team cannot act on a name alone.
Code by intake channel
Different channels carry different portal risks. An inbound form may omit procurement details because the form does not ask, while a rep referral may carry them in a message that never reaches the queue. Assign the source channel before coding and compare completeness by channel. A team with strong event follow-up and weak inbound forms may still lose time where the volume is highest. Report the channels beside the result so the reader can see where the repair belongs. Do not merge channels just to raise the overall share.
Resolve disagreements before counting
Reviewers often disagree about whether a general mention of procurement counts as a portal requirement or whether a customer's vendor form is enough evidence. The answer depends on the team's written rule, not on the reviewer's preference. Write the rule before coding, apply it consistently, and recode rows classified under an older rule. Record the rule change and its effective date so the next test remains comparable. A short calibration on ten records before the full review prevents most disputes and saves a second pass.
Fix the intake fields
Most missing portal requirements come from a form that does not ask for them. Add a dedicated field for the portal name, a status field, an owner field, and a date field for the next registration step. Put the fields near the customer and deal details so the preparer sees them before routing the request. Add a short prompt that asks whether the customer requires supplier registration before a purchase order. Pair the change with the billing contact checklist so the vendor record and the invoice record stay aligned.
Limitations and next action
The result can support a change to the intake form, the routing rule, or the handoff to finance. It cannot prove that the customer will issue a purchase order or that the portal registration will be approved. A high completeness share can hide records where the portal was named but the status was never confirmed. Pair the test with a short review of customer messages and a check that the owner acknowledged the next step. Report presence, status, and ownership separately so the repair matches the gap.
Report the result
Report the number of intake records, the share with a portal name, the share with a registration status, and the share with a named owner and deadline. Add one short example of a strong record and one weak record with identifying details removed. Show the gap by intake channel so the reader can see where the repair belongs, then compare it with the order form reconciliation to confirm the vendor details survive the handoff. State the limitation beside the numbers rather than in a separate appendix. The output should end with one field change, one owner, and one recheck date.
Review cadence
Run the test before a peak intake period, after a form change, and at least once every three months. A monthly check helps during a busy week when requests arrive quickly and procurement details are easy to skip. Keep the same definitions so results remain comparable across cycles. End each review with one change, one owner, and one recheck date. Archive the intake export, the customer messages, and the coding sheet beside the finding.
Sources
The sources below offer general context on business operations, recordkeeping, and selling to larger organizations. They do not describe a local intake result or a benchmark for this team, and they were checked on November 12, 2026. Use them as background only and keep the local observation separate from any external claim. The list is not a substitute for the customer's procurement instructions or the finance review.
- U.S. Small Business Administration: Business guide: https://www.sba.gov/business-guide
- U.S. Small Business Administration: Manage your business: https://www.sba.gov/business-guide/manage-your-business
- IRS: Recordkeeping: https://www.irs.gov/businesses/small-businesses-self-employed/recordkeeping
- NIST Cybersecurity Framework: https://www.nist.gov/cyberframework
- U.S. Census Bureau: Small Business data: https://www.census.gov/programs-surveys/susb.html