Vessel maintenance deferrals referral brief template: a fill-in handoff for marine ERP consultants

Short answer

A company introduction about vessel maintenance deferrals is a short handoff the technical director can forward without editing: the company and fleet, the systems, years of closed deferrals, rough volumes, who keeps the records, who can authorize a licensing discussion, and any documented access deadline. It contains no defect reports, approvals, screenshots, ship names or exports, only metadata about them.

Visual briefFull-size diagram
Eight empty brief fields in a two-column grid that fill in one after another with Illustrative values: 240 staff ashore and at sea, 12 vessels, maintenance system plus document control, closed deferrals since 2017, about 700 deferrals a year, technical director as owner, MD plus owner's representative as contacts, and a contract end for four vessels.
Illustrative. A fictional ship manager's brief; every value is a count, a span of years, a system type or a role.

The template belongs to the vessel maintenance deferrals guide, which explains what a deferral chain holds. Use it after one conversation with the technical director, then check your draft against the completed example.

Fill-in brief: eight fields for the technical director

Copy the fields and replace each bracket with a short phrase, a count, a role or "to be confirmed".

  • Company: [Ship manager, owner-operator or both; staff ashore; seagoing staff and whether employed directly]
  • Fleet: [Number of ships; ship types; owned versus managed for third parties]
  • Systems: [Planned maintenance system; document control or safety management system; where shore approvals are recorded]
  • Years of history: [Oldest closed deferral readable today; any archived database for older years]
  • Record volumes: [Deferrals a year across the fleet, roughly; share closed with a linked sign-off, if known]
  • Records owner: [Who maintains the history day to day]
  • Authorized contact: [Who can approve a licensing discussion for the manager; owner's representative where relevant]
  • Open question and deadline: [The one thing nobody can confirm; any documented access end date, with its source]

End every brief with: Not included: defect reports, approvals, crew or ship names, screenshots, exports or any estimate of value.

Field notes for marine fleets

Company and fleet are two fields on purpose. The introduced company needs 50+ full-time employees at peak, contractors excluded, so the company field counts people and states how seafarers are employed. The fleet field counts ships. A large fleet run by a small office and a small fleet run by a large owner-operator read very differently.

Owned versus managed decides the authority field. The ISM Code's "Company" can be the owner or a manager that has taken on responsibility for operating the ship, so the people who keep the records may not be the people who own them. BIMCO's SHIPMAN 2024 added provisions on owners' access to and ownership of ship data in the manager's information system. If any ships are managed for others, the authority field should name the owner's representative as well; the who-can-license decision tree shows how to work it out.

Years of history are counted per system. Ask when the current planned maintenance system was installed and whether older data sits in an archived database. A ship keeps its IMO number for life, through changes of name, flag and owner, but internal job and equipment numbers often change with each new system, so older years may be harder to join.

The deadline must have a source. A management contract end, a license expiry or a server shutdown, each with the document it comes from. If there is none, write "none set". The retention timeline explains which records disappear first in a handover.

Completed brief (Illustrative): a manager losing four ships

Illustrative wording for a fictional manager. Every count and date is invented.

FieldEntry
CompanyShip manager with about 90 staff ashore and 150 seafarers on direct contracts
FleetTwelve offshore supply ships; eight owned by the group, four managed for one third-party owner
SystemsPlanned maintenance system; document control; superintendent mailboxes for approvals
Years of historyClosed deferrals back to 2017 in the current system; older history in an archived database
Record volumesAbout 700 deferrals a year across the fleet; most closed against the same job number
Records ownerTechnical director
Authorized contactManaging director for the group's ships; owner's representative to be confirmed for the four managed ships
Open question and deadlineWhether the management agreement assigns records for the four ships to the owner. Outgoing system access for them ends when the management contract ends

Not included: defect reports, approvals, crew or ship names, screenshots, exports or any estimate of value.

The open question is deliberately one sentence. It tells SourceX where the rights review should start, and it tells the managing director why the owner may need to join the call.

The message you send with it

A brief travels with two or three sentences on top. Something like:

"I'd like to introduce SourceX, which licenses approved business data directly from companies for AI training and evaluation. The note below describes our deferral history at summary level only. SourceX would review fit, rights and what could be included, and nothing is shared until we agree."

If you send it yourself rather than the technical director, disclose that you may receive a referral reward. The company is paid under its own agreement with SourceX and the reward is funded separately, so it never reduces that payment. Illustrative only: if SourceX paid the company $250,000, the default reward would be $62,500. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.](/rewards) shows the rule.

For tone, the warm introduction brief covers a first message to an owner. ERP consultants working in marine systems will find role-specific advice on the ERP consultants page and in MCP for ERP consulting, and the client opportunity brief generator can produce a first draft from your notes.

Before it goes out: a final check

  • Every field is metadata, and the closing "not included" line is present.
  • The authority field names a decision-maker, not only the records owner, and flags any third-party owner.
  • The company meets the basics: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English.
  • You have signed the Channel Partner Agreement. The first valid introduction within the 90-day window is credited when the company submits a verified application.

What stays unknown until SourceX reviews it: buyer interest in deferral records, how crew and ship identifiers would be treated, the owner-manager rights split and any offer. Other sectors are on the industries hub.

Next step

Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

When all eight fields are filled with metadata and the authority field names who can say yes, register as a partner, confirm the company on who qualifies and read the terms before the brief is forwarded.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardYour 25% of the actual supplier payout. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Should vessel names or IMO numbers go in the brief?

No. A fleet count and vessel type are enough. Vessel identities can come up in SourceX's review if the company wants to continue, and leaving them out keeps the brief easy to forward.

Do seafarers count toward the 50-employee threshold?

The test is 50+ full-time employees at peak, contractors excluded. Seafarers supplied by a crewing agency are not the company's full-time employees, so they do not count; only the company's own full-time staff do. Write the employment basis in the company field.

What if the technical director cannot say who owns the records?

Write 'to be confirmed' in the authority field and name both the manager's MD and the owner's representative. That is a normal state for a first brief.

Sources

  1. imo.org/en/OurWork/HumanElement/SafetyManagement/Pag…
  2. imo.org/en/ourwork/msas/pages/imo-identification-num…
  3. bimco.org/insights-and-information/contracts/20240325-…
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 90% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment