A good telecom expense management (TEM) RFP defines your scope and spending baseline, sends vendors your real carrier invoices, and asks for a scored proof of concept instead of yes-or-no answers. It also separates software from managed services, asks exactly how savings are calculated and verified, and sets out what happens to your data when the contract ends.
If you’re the procurement lead running a TEM sourcing event, this guide gives you the sections the RFP needs, 10 tips for getting answers you can compare, an example scorecard, the red flags to watch for, and the Canadian requirements to include.
Key takeaways
- A TEM RFP that asks “do you support X” gets the same answer from every vendor. Ask vendors to show the capability on your own invoices instead.
- Baseline your telecom spend before you write the RFP. Without a baseline, no vendor’s savings claim can be checked.
- Separate TEM software from managed services in the RFP. Pricing and accountability differ, and bundled answers hide both.
- Score TEM responses against weights agreed before the responses arrive. It keeps the evaluation fair and defensible.
- Canadian TEM RFPs need Canadian requirements. Ask about Canadian carrier invoice formats, French-language reporting and how invoice data is handled outside Quebec or Canada.
What a telecom expense management RFP needs to cover
A telecom expense management RFP needs to cover what the vendor will do, how well it does it on your data, and what happens to your data and costs over the contract. The two tables below list the sections to include, what to ask in each, and what a weak answer looks like.
TEM RFP sections on scope and capability
The capability sections of a TEM RFP test what the vendor actually does with your invoices and lines.
| RFP section | What to ask | What a weak answer looks like |
|---|---|---|
| Scope | Which services and carriers are covered (wireless, wireline, IoT) | “All of them” with no list |
| Invoice processing | How invoices are loaded, read and validated, and how fast | No mention of Canadian carrier formats |
| Inventory | How lines are matched to users, devices and cost centres | Relies on you to keep the inventory current |
| Optimization | How unused lines and poor-fit plans are found and reported | A savings promise with no method |
| Disputes and carrier management | Whether the vendor files disputes and negotiates, or only reports | Unclear who contacts the carrier |
| Reporting | Standard reports, custom reports and who can see them | Screenshots instead of sample reports |
TEM RFP sections on data, language, pricing and exit
The commercial sections of a TEM RFP test how your data is handled and what the contract really costs.
| RFP section | What to ask | What a weak answer looks like |
|---|---|---|
| Integration | Links to your finance, HR and device management systems | “Custom integration available” with no price |
| Security and data handling | Where invoice data is stored and processed, and who can access it | No answer on location or subcontractors |
| Language | Whether reports and the interface are available in French | “On the roadmap” |
| Pricing | Price per comparable unit, plus every fee outside it | Percentage of savings with no cap or definition |
| Exit | How you get your data back and how long it takes | No commitment on format or timing |
10 tips for writing a TEM RFP that gets comparable answers
A TEM RFP gets comparable answers when it removes the room vendors have to answer in their own terms. The 10 tips below each close one of those gaps.
1. Baseline your telecom spend before you write the TEM RFP
A TEM RFP needs a spending baseline, meaning your current monthly cost by carrier, service and line count. Without it, you can’t check any vendor’s savings estimate. If you don’t have a baseline, a wireless audit before the RFP gives you one.
2. Define the TEM scope by service and carrier
The TEM scope should list exactly which services are included, such as wireless only, or wireless plus wireline and IoT, and which carriers. Vendors price and staff very differently for each, so a vague scope produces proposals you can’t compare. See what TEM software covers if you’re deciding scope.
3. Send sample carrier invoices with the TEM RFP
Sample carrier invoices, with personal information removed or under a confidentiality agreement, let vendors show their invoice processing on your real formats. Include at least one invoice from each carrier and service type in scope.
4. Ask for a TEM proof of concept on your own data
A TEM proof of concept on your own invoices is the strongest test in the RFP. Ask shortlisted vendors to process your sample invoices and return their findings, then score the findings, not the presentation.
5. Separate TEM software from managed services
TEM software and TEM managed services are different purchases. Software gives your team the analysis, while a managed service has the vendor’s staff act on it, for example by filing disputes or cancelling lines. Ask vendors to price and describe each separately so you can see what you’re paying people to do.
6. Ask how TEM savings are calculated and verified
TEM savings claims are only useful if the method is clear. Ask how savings are defined, what baseline they’re measured against, whether they’re one-time or recurring, and who confirms them. Tie this to the TEM KPIs your CFO will track.
7. Test how the TEM vendor handles Canadian carrier invoices
Canadian carrier invoices have their own formats, taxes and line items. Ask vendors which Canadian carriers they process today and confirm it in the proof of concept rather than taking it on trust.
8. Ask about French-language TEM reporting
French-language reporting matters if your TEM users or finance teams work in Quebec. Ask whether the interface, reports and support are available in French today, not on a roadmap.
9. Define TEM data handling and exit terms
TEM data handling and exit terms should say where your invoice data is stored and processed, which subcontractors touch it, and how you get it back when the contract ends. Ask for the export format and timeline in writing.
10. Price TEM proposals on a comparable unit
TEM proposals are only comparable when priced on the same unit, such as per line, per invoice or per billing account per month. Ask every vendor to quote on the unit you choose, and list every fee outside it, including setup, integration and custom reports.
How to score TEM vendor responses
Score TEM vendor responses against criteria and weights you agree internally before responses arrive. The example scorecard below shows one way to weight a TEM evaluation. The weights are an example only, so adjust them to your priorities, and keep the same scale for every vendor so no one is judged on criteria the others weren’t asked about.
| Criterion | Example weight | What a 5 looks like | What a 1 looks like |
|---|---|---|---|
| Proof of concept findings | 25% | Specific, accurate findings on your invoices | Generic findings or none |
| Invoice coverage | 15% | Every in-scope carrier and service processed | Gaps in carriers or services |
| Savings method | 15% | Clear definition, baseline and verification | Promise with no method |
| Reporting and usability | 10% | Reports your team would use monthly | Reports need rework before use |
| Data handling and security | 10% | Locations, access and subcontractors stated | Vague or missing answers |
| Language and Canadian fit | 10% | French available today, Canadian formats proven | English only, formats untested |
| Price on the comparable unit | 15% | All fees disclosed on your unit | Fees outside the unit or uncapped |
Red flags in telecom expense management proposals
Telecom expense management proposals carry a few red flags worth marking before scoring. A savings guarantee with no stated method or baseline can’t be checked, so treat it as marketing until the vendor explains it.
Contingency pricing, where the vendor takes a share of savings, needs a cap and a clear definition of what counts as a saving. Long or unstated data export timelines make it hard to leave. And proposals that answer every requirement with “yes” but decline a proof of concept deserve a closer look.
TEM RFP requirements for Canadian organizations
TEM RFPs for Canadian organizations should include requirements a US template won’t. Telecom invoices carry personal information, such as user names and phone numbers, so data handling belongs in the RFP. Treat the points below as what to ask your privacy and legal teams to review.
Under PIPEDA, the Office of the Privacy Commissioner says the transferring organization is accountable for the information it sends to a service provider, and should use contractual or other means to protect it. If you operate in Quebec, Law 25 requires a privacy impact assessment before personal information is transferred outside Quebec, so ask where vendors store and process invoice data.
Quebec’s Charter of the French language also gives workers the right to carry out their activities in French, as the Office québécois de la langue française explains. If Quebec staff will use the TEM platform, ask about French-language software and reports. Public-sector buyers should also confirm their own procurement rules before issuing the RFP.
When a formal TEM RFP isn’t the right first step
A formal TEM RFP isn’t the right first step if you don’t yet know your baseline or your fleet is small. In those cases, an audit of your current invoices tells you how much there is to find and which services are worth including.
A smaller fleet may get what it needs from TEM software without a full sourcing event. Compare the options in our guide to TEM companies.
Where PiiComm fits in a TEM evaluation
PiiComm’s ClearSight TEMs AI analyzes the carrier invoices you upload and surfaces unusual charges, zero-use lines and plan changes worth making. You can run it on your own invoices before an RFP to set a baseline, or alongside one to check what vendors report. If your RFP also covers devices, our managed mobility services team handles the device side.
It doesn’t fit everyone. ClearSight doesn’t file carrier disputes or negotiate with carriers for you, so if you want a vendor to take on that work, a full-service TEM provider is the better fit.
Questions procurement teams ask about TEM RFPs
What should a TEM RFP include?
A TEM RFP should include your scope, spending baseline, sample invoices, a proof-of-concept request, and questions on invoice processing, inventory, optimization, disputes, reporting, integration, data handling, language, pricing and exit. Ask vendors to price software and managed services separately, on the same comparable unit.
How long does a TEM RFP process take?
A TEM RFP process length depends on your approval rules and whether you run a proof of concept. Allow time to build a baseline, give vendors enough time to respond, and leave room to process sample invoices with shortlisted vendors. A proof of concept adds time but gives the most useful evidence.
How do you compare TEM pricing models?
Compare TEM pricing models by asking every vendor to quote on the same unit, such as per line, per invoice or per billing account per month. Then add every fee outside that unit, including setup, integration and custom reporting. For contingency pricing, ask for a cap and a definition of savings.
Should a TEM RFP include a proof of concept?
Yes, a TEM RFP should include a proof of concept for shortlisted vendors. Processing your own sample invoices shows how well a vendor handles your carriers, formats and services. Score the findings rather than the presentation, and use the same invoices for every vendor.
How do you verify TEM savings claims?
Verify TEM savings claims by agreeing a baseline before the contract starts and defining what counts as a saving. Ask whether savings are one-time or recurring and who confirms them. Then check reported savings against your invoices over the following months rather than accepting the vendor’s report alone.
What data should we share with TEM vendors during an RFP?
Share with TEM vendors only what they need to respond, usually sample invoices and line counts, with personal information removed where possible or under a confidentiality agreement. Ask your privacy team to review what’s shared, especially if invoice data will be processed outside Quebec or Canada.
Should TEM and managed mobility be in the same RFP?
TEM and managed mobility can be in the same RFP if you want one provider for expenses and devices, but score them as separate sections. Many vendors are strong in one and partner for the other. Read how to evaluate a managed mobility services provider for the device side.
Where to start with a TEM RFP
Build your telecom spending baseline first, then define scope by service and carrier and agree your scoring weights internally. Write the RFP around sample invoices and a proof of concept, and add Canadian requirements for invoice formats, French-language reporting and data handling. That gives you answers you can compare.
Know your telecom baseline before you issue the RFP.
ClearSight TEMs AI analyzes your Canadian carrier invoices and shows unusual charges, zero-use lines and plan changes worth making.
References
- Office of the Privacy Commissioner of Canada, Guidelines for processing personal data across borders (2009). The transferring organization remains accountable for information sent to a service provider.
- Office québécois de la langue française, Entreprises (updated October 23, 2026). Businesses must respect workers’ right to carry out their activities in French.