On this page
A transition agreement can have service-specific limits
Exhibit B to the October 2022 RCM Technologies–TalentHerder agreement defines reciprocal services through a schedule, with transitional duties and service-specific end terms. It is a filed form for that deal, not evidence that every service or extension is available.
Plan one replacement for each function
Original fictional exercise: assume the seller will process the buyer’s first two payroll runs and host an order database for six weeks under agreed terms. These invented periods do not come from the filed example.
| Temporary function | Buyer replacement dependency | Evidence before exit |
|---|---|---|
| Payroll processing | Buyer employer/payroll set-up and trained administrator | An authorised reconciliation of a trial payroll and actual handoff |
| Order database | Permitted export, usable receiving system and trained users | Open-order reconciliation and authorised cutover test |
| Supplier purchasing support | Buyer accounts and purchasing authority | Confirmed ordering route for the required inputs |
An end date is not a replacement test
Assign each replacement an owner and test date early enough to act on a failure. Establish any notice, extension, additional-service or early-termination route from the actual agreement; do not assume the seller must keep helping because the buyer’s system is late.
Compare the service being provided with the replacement test. A successful data export does not prove payroll tax registration, supplier credit or the lawful use of customer information. Keep those separate dependencies visible.
Use Launch dependencies to connect replacement tasks and tested cutover. Keep the service schedule, costs, access permissions and test evidence in the business’s controlled transaction records.
Scope
- Selected historical filed transition-service form and original fictional periods only. No actual service scope, cost, availability, extension or completion is established.
- No payroll, privacy, employment or technical cutover is approved by the worksheet.
Next step
Use Launch dependencies for service replacements and cutover tests. Keep the service/scope/cost/period/replacement/exit register separately.
Terms used here
- Transition service
- Temporary assistance under the actual transaction arrangements, rather than permanent operating capacity.
- Service recipient
- The party receiving a particular service; a reciprocal arrangement can put each party in both roles for different services.
Sources & review notes
RCM Technologies; SEC-filed agreement
Passage, dates and research notes
company-filed-agreement · APA preamble and 7.12; Exhibit B TSA preamble,1.01(a)–(e),1.02–1.03,2.01–2.04,3.01–3.03 and4.01; schedule precedence, transitional nature, service-specific termination, confidentiality
Historical named deal only; clauses and original fictional owner worksheet do not establish actual completion, enforcement, payment or ordinary-market terms. Selected historical filed transition-service form and original fictional periods only. No actual service scope, cost, availability, extension or completion is established.
Bookmark this guide or mark it as read.
Progress privacy
Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.
This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.