A principal may work with ten agents across ten ports and still have no reliable way to compare their performance.
Each agent reports differently. PDA formats vary. FDA timing varies. Supporting documents arrive through separate email chains. Some agents raise a cost change before committing the expense. Others explain it when the final account arrives.
Over time, the principal develops a general sense of which agents are dependable. That judgment often comes from memory, recent problems, and feedback from operations or finance.
A consistent set of port agent KPIs gives the review more substance.
In this guide, we break down the ten KPIs principals can use to compare agents across ports, explain how to calculate each one, and show what strong performance looks like. We also cover how principals gather this information today, where manual reviews tend to break down, and how a shared operational record makes the process easier.
10 KPIs for Comparing Agents Across Ports
The first step is deciding what should actually count as strong port agent performance.
That cannot be reduced to one number. An agent may keep everyone updated but submit weak financial backup. Another may close the FDA quickly while reporting berth changes too late.
The ten KPIs below give principals a more complete view of how each agent handles the appointment.
| KPI | What It Measures | What Good Performance Looks Like |
|---|---|---|
| PDA-to-FDA variance | The difference between estimated and final port-call costs | Material changes are limited, raised early, explained by line item, and supported |
| DA accuracy rate | The share of disbursement account lines accepted without correction | Rates, quantities, currencies, descriptions, and supporting records are correct |
| FDA turnaround time | The time required to submit the final disbursement account | The FDA arrives within the agreed period, with any delay tied to a clear cause |
| First-pass FDA acceptance | The share of FDAs approved without correction or reissue | Finance can review and approve the account with limited follow-up |
| Exception and rebill rate | The frequency of corrected, disputed, or reissued charges | Exceptions are infrequent and supported by a clear resolution record |
| Response latency | The time between a principal request and the agent’s response | Critical matters receive prompt acknowledgment and a useful answer |
| Update timeliness | The gap between an operational event and the related update | Important changes are reported while they can still support a decision |
| SOF timestamp discipline | The completeness and reliability of statement of facts records | Events are recorded consistently, sourced, and ready for later review |
| Supporting-document completeness | The share of costs and events with the required evidence | Quotes, invoices, receipts, approvals, and service records are attached |
| Cost exception control | How the agent handles costs outside the approved estimate or scope | Material costs are raised before commitment whenever conditions allow |
While these measures should be applied consistently across agents, it is important to remember the targets can vary by appointment.
A tanker call with significant port costs may place more weight on PDA-to-FDA variance and DA accuracy. A husbandry appointment involving crew changes, transportation, and cash to master may place more weight on response latency, update timing, and document completeness.
Port conditions also belong in the review.
A terminal delay does not automatically indicate weak agent performance. The principal can still assess how quickly the delay was reported, how well it was documented, and what action the agent took.
Compare Port Agents With the Records Behind the Results
How to Calculate the KPIs
the next step is calculating them the same way across every agent and port.
The formulas below create that consistency, so each result can be compared across appointments without relying on different reporting methods or individual judgment.
1. PDA-to-FDA Variance
Formula:
(FDA total - PDA total) ÷ PDA total × 100
PDA-to-FDA variance measures how closely the final disbursement amount matched the original estimate.
The total percentage gives the principal a quick view. The line-item explanations show why the amount changed.
Common causes include:
- A principal-requested service
- A berth or schedule change
- Additional launch or transport hours
- A port authority requirement
- A local vendor rate difference
- A currency movement
- A cost missing from the PDA
- An estimating error
The agent should connect each material variance to a source record, especially when the difference between the PDA and FDA comes from added scope, vendor rates, or a schedule change.
A larger variance can be reasonable when the scope changed and the principal approved the added work. A smaller variance can still raise concern when it contains duplicated or unsupported charges.
The review should answer two questions:
- Could the agent have predicted the cost?
- Did the principal learn about the change before the FDA arrived?
The variance explains how the estimate changed. DA accuracy shows whether the final account can support approval.
2. DA Accuracy Rate
Formula:
Accepted DA lines ÷ total submitted DA lines × 100
DA accuracy measures how many disbursement account lines the principal accepts without correction.
Each line should match the underlying service and record.
The review may check:
- Vendor
- Service description
- Quantity
- Rate
- Currency
- Exchange-rate treatment
- Tax treatment
- Contract or tariff
- Invoice or receipt
- Principal approval
- Vessel and call allocation
The review should also identify duplicated charges, omitted pass-through costs, and undocumented adjustments.
3. FDA Turnaround Time
Formula:
FDA submission date - agreed closeout start date
The principal should define the closeout start date in advance.
Common options include:
- Vessel departure
- Completion of the agent’s scope
- Receipt of the final vendor invoice
- A date stated in the agency agreement
Many principals will benefit from tracking two periods:
- Vessel departure to FDA submission
- Final vendor document received to FDA submission
The first period shows the principal’s full wait. The second shows how quickly the agent completed the account after receiving the required vendor records.
This distinction matters when a launch provider, terminal, or local supplier submits its invoice late. The scorecard can capture the vendor delay and the agent’s own processing time separately.
Tracking both periods gives the principal a clearer view of the financial close and the wider port call turnaround time.
Submission time tells only part of the story. The FDA still needs to pass the principal’s review.
4. First-Pass FDA Acceptance
Formula:
FDAs accepted on first submission ÷ total FDAs submitted × 100
First-pass FDA acceptance measures how often finance approves the account without requiring correction or reissue.
Each FDA can be classified as:
- Accepted
- Accepted with minor clarification
- Returned for correction
- Reissued
- Formally disputed
The classification rules should remain the same across agents.
An FDA may arrive within the agreed period and still include missing invoices, an incorrect exchange rate, or a duplicated charge. Those issues extend the true closeout period.
A strong first-pass acceptance rate usually reflects careful cost capture throughout the appointment. It also points to stronger approval records and supporting documents.
When an FDA returns, the reason should be categorized.
5. Exception and Rebill Rate
Formula:
Corrected, disputed, or rebilled lines ÷ total billed lines × 100
The exception and rebill rate measures how often charges require additional work after submission.
Useful exception categories include:
- Duplicate charge
- Wrong rate
- Wrong quantity
- Missing approval
- Missing supporting document
- Unsupported charge
- Currency correction
- Tax correction
- Scope dispute
- Late vendor invoice
- Principal-requested change
The category should reflect the seriousness of the issue.
A corrected description carries less financial risk than a large unapproved cost. Principals may assign severity levels or track the total value attached to each exception.
Patterns deserve close attention. The same correction across several calls may point to an outdated rate record, weak handoff, or missing review step.
These first five KPIs focus on the financial side of the appointment. The next two show how the agent communicates while the vessel call is active.
6. Response Latency
Formula:
Response timestamp - request timestamp
Response latency measures how long the agent takes to acknowledge and address a principal request.
Acknowledgment time and resolution time should be recorded separately.
An agent may confirm receipt within ten minutes and provide the complete answer an hour later. Both timestamps tell the principal something useful.
Requests can be grouped by priority:
- Critical operational event
- Time-sensitive cost approval
- Routine status request
- Document request
- Post-call finance query
Median response time often gives a more reliable picture than the average. A few unusual delays can heavily affect an average when the call sample is small.
The response also needs substance. A brief acknowledgment confirms that the request was received. Resolution time shows when the principal received the information needed to act.
Direct requests create one set of communication records. Proactive updates create another.
7. Update Timeliness
Formula:
Update timestamp - operational event timestamp
Update timeliness measures the gap between an operational event and the related update to the principal.
Relevant events may include:
- ETA or ETD change
- Berth change
- Pilot ordered
- Tug confirmed
- All fast
- Cargo started
- Cargo completed
- Operational stoppage
- Service failure
- Vessel departure
The principal should define which events require immediate communication and which can appear in a scheduled update.
Accuracy belongs in the review as well. A fast update with uncertain details may create confusion for operations, chartering, or finance.
Good performance means the principal receives reliable information while it can still support planning, approval, or escalation.
Many of these events later appear in the statement of facts. That record needs its own performance measure.
8. SOF Timestamp Discipline
Formula:
Required SOF timestamps completed ÷ total required SOF timestamps × 100
The maritime Statement of Facts (SOF) records the key events of a vessel call.
Principals may use it during laytime calculations, claims, incident review, and post-call analysis. Missing or conflicting times can create questions long after the vessel leaves port.
The scorecard should review:
- Required events recorded
- Source of each time identified
- Local time and UTC handled consistently
- Corrections preserved
- Conflicting times reconciled
- Delay reasons included
- Supporting messages or records attached
- Missing periods explained
The agent should separate verified event times from estimated times.
A complete SOF gives the principal a defensible sequence of events. It also provides a stronger record for reviewing where time was lost.
The SOF supports the operational timeline. Supporting-document completeness covers the evidence behind financial and service records.
9. Supporting-Document Completeness
Formula:
Items with all required evidence ÷ total items requiring evidence × 100
Required evidence may include:
- Vendor quote
- Principal approval
- Purchase order
- Vendor invoice
- Receipt
- Tariff
- Rate agreement
- Written instruction
- Service completion record
- Currency support
- Credit note
Each item can be classified as:
- Complete at submission
- Complete after follow-up
- Incomplete
- Unsupported
- Evidence not required
These classifications help finance record the quality of the submission consistently.
They also show where documents tend to go missing. The issue may sit with a local vendor, an internal shift handoff, or a service ordered outside the usual approval process.
Supporting documents show what happened. Cost exception control shows how added expenses were handled before commitment.
10. Cost Exception Control
Formula:
Material exceptions raised before commitment ÷ total material exceptions × 100
Cost exception control measures how the agent handles expenses outside the PDA, contract, tariff, or approved scope.
Examples include:
- Additional services
- Costs above an approval threshold
- Rates above contract
- Added hours or quantities
- Emergency spending
- Vessel-requested services
- New authority requirements
- Costs caused by a schedule change
The principal should define a materiality threshold. Small routine changes may follow one process. Large or unusual costs may require written approval.
Some situations require immediate action. Safety concerns, authority instructions, and urgent vessel needs may leave little time for advance approval.
The agent should still record:
- What happened
- Why action was required
- Who was informed
- When the information was sent
- Which document supports the final charge
Download the Port Agent Scorecard Template
Now that you know which KPIs to track and how to calculate them, you can put them into practice with the Port Agent Scorecard.
Use the scorecard to review one agent, compare performance across ports, or assess a group of appointments. Choose a review period with enough vessel calls to reveal patterns. Quarterly, semiannual, and call-volume-based reviews can all work, depending on how often the agent handles your vessels.
Download the Port Agent Performance Scorecard
How Principals Usually Gather Port Agent Performance Data Today
One common issue we see when principals are trying to gather information is that the needed records are spread across several places.
A typical review may require the principal to:
- Collect PDAs and FDAs from separate email threads
- Standardize different account formats
- Compare estimated and final costs manually
- Search for vendor invoices and principal approvals
- Review messages to calculate response times
- Compare the SOF with vessel or terminal records
- Ask finance which FDAs were returned
- Ask operations which agents required repeated follow-up
- Categorize corrected and disputed charges
- Enter the results into a spreadsheet or review deck
The team also has to settle basic record questions.
Which FDA version is final? Which email contains the approval? Which timestamp came from the vessel? When did the agent receive the final vendor invoice? Was the cost raised before or after the service was completed?
Each answer may require another search.
Different formats also affect the comparison. An agent with a polished report may appear stronger even when its underlying records contain gaps. An agent working in a more complex port may score poorly unless the review captures local conditions and third-party delays.
The process becomes harder as the number of ports and agents grows.
That is where Base Connect changes the process.
How Base Connect Cuts Out the Work
Base Connect gives principals and appointed agents a shared place to work across separate organizations.
Updates, messages, approvals, costs, and documents can remain tied to the same job or project. The principal can view the records shared for the appointment without rebuilding the call from emails and attachments.
The work removed from the review becomes easier to see when the manual process and the shared process are placed side by side.
| Manual Review Work | How Base Connect Cuts Out the Work |
|---|---|
| Collect PDA and FDA files from email | Keeps the financial record connected to the shared call |
| Compare separate account versions | Maintains the call history and related records in one place |
| Search for approvals | Preserves approvals with the cost or activity they support |
| Find invoices and receipts | Keeps supporting documents attached to the related record |
| Reconstruct response times | Records messages and activity with timestamps |
| Compare event updates manually | Keeps operational activity connected to the job or project |
| Ask each agent for status | Gives the principal scoped visibility into shared activity |
| Rebuild the money trail | Connects charges, supporting evidence, and approvals |
| Assemble the scorecard from several systems | Provides much of the source data required for the calculation |
Base Connect cuts work from several parts of the scorecard process. Here’s how:
✓ Communication Records Are Created During the Call
Response times and update timing can be measured from activity that already carries a timestamp.
The principal can refer back to the original request, update, or message. The agent can see the same source record during the review.
This reduces debates over when information was requested or shared.
✓ Financial Records Stay Connected to the Appointment
PDA and FDA lines can remain connected to the service, approval, and supporting document.
That gives the principal a clearer money trail for:
- PDA-to-FDA variance
- DA accuracy
- First-pass FDA acceptance
- Exception analysis
- Cost exception control
Finance can review the charge in context instead of searching through separate folders.
✓ Supporting Evidence Stays With the Related Cost or Event
Quotes, invoices, receipts, approvals, and service records can stay with the item they support.
This makes document-completeness reviews more direct. It also shows which records were available during the call and which arrived after follow-up.
✓ Principals Receive Cross-Organization Visibility
The agent and principal can remain in separate organizations while sharing the agreed call information.
Role-based permissions control access. Each party can see the records relevant to its role and the appointment.
For principals managing several agents, this creates a more consistent source of port-call information across ports.
✓ The Scorecard Becomes a Review Layer
Base Connect captures and organizes much of the source data required for the Port Agent Scorecard.
The scorecard still defines the performance standard. It tells the principal which results to calculate and how to interpret them.
Base Connect removes much of the record gathering behind that calculation.
The result is a review based on call data produced during the work. The principal can spend more time examining patterns and assigning actions.
Learn more about how Base Connect supports shared port-call visibility across organizations.
Conclusion: A Shared Standard Needs a Shared Port-Call Record
Principals need a consistent way to review port agent performance across calls and ports.
The Port Agent Scorecard brings financial accuracy, FDA closeout, communication, operational records, supporting evidence, and cost control into one review. It helps principals see where an agent is performing well, where the same issues keep appearing, and where port conditions affected the outcome.
Base Connect supports that review by keeping the source record tied to the appointment as the call moves forward. Updates, cost changes, approvals, messages, and documents stay connected to the same job.
This gives principals stronger evidence for agent reviews and gives agents clearer feedback tied to specific appointments. Over time, both sides gain a more reliable view of performance, recurring exceptions, and the areas that need attention.
The scorecard defines the measures. Base Connect keeps the records needed to evaluate them.
See how Base Connect supports performance visibility across port agents.
Key Takeaways
- Port agent performance should be reviewed across financial accuracy, responsiveness, operational discipline, and call closeout.
- The same KPI definitions should be applied across agents, with local conditions recorded as part of the review.
- PDA-to-FDA variance and FDA timing should be reviewed with accuracy, evidence, and first-pass acceptance.
- Email, spreadsheets, and separate files create significant work when principals compare agents across several ports.
- Base Connect captures much of the shared call data required to support a credible Port Agent Scorecard.
Frequently Asked Questions About Port Agent Performance
What KPIs should principals use to measure port agent performance?
A balanced port agent scorecard should include PDA-to-FDA variance, DA accuracy, FDA turnaround time, first-pass FDA acceptance, exception rate, response latency, update timeliness, SOF timestamp discipline, supporting-document completeness, and cost exception control.
Together, these measures cover financial accuracy, communication, operational records, and closeout quality.
How do you calculate PDA-to-FDA variance?
Use the following formula:(FDA total - PDA total) ÷ PDA total × 100
The percentage should be reviewed alongside the line-item explanations. Each material change should connect to an approval, invoice, tariff, instruction, or documented event.
How should a principal account for delays outside the agent’s control?
Each material delay can be classified as agent-controlled, partly agent-controlled, or outside agent control.
The original delay may sit outside the agent’s responsibility. The principal can still measure the timing of the update, the quality of the documentation, and the actions taken in response.
What is a good FDA turnaround time?
The principal should define the start date and target period in advance. Tracking both departure-to-FDA time and final-vendor-document-to-FDA time provides a clearer result.
The right target depends on the agency agreement, port, vendor billing practices, and appointment scope.
How often should principals review port agent performance?
Quarterly reviews work well for principals with regular call volume. A review after a defined number of calls may work better when appointments are less frequent.
New agency relationships and corrective-action periods may require more frequent reviews.
