Automating RFx processes in the public sector means using e-procurement and sourcing software to run requests for information, proposals, and quotations without losing the transparency, fairness, and audit standards that public spending demands.
That caveat is the whole challenge. A private buyer can automate for speed alone. A public buyer has to automate and stay defensible at the same time.
Public procurement is estimated by the World Bank at around $9.5 trillion a year, which is 13 to 20 percent of GDP in most countries. Most of it still moves through manual RFx workflows. Orange County, California, found that the procurement process for a single five-year contract consumed over $86,000 in staff time.
This guide covers what RFx means in a public sector context, the compliance rules automation has to respect, which steps to automate first, where AI fits and where it does not, and how to avoid the pitfalls that lead to bid protests.
What Is RFx in Public Sector Procurement?
RFx stands for “Request for X”. The X is replaced by whatever you are requesting from suppliers.
It is an umbrella term, not a document. You never issue an RFx. You issue an RFI, an RFP, an RFQ, an RFT, or an RFB.
RFx management is the end-to-end handling of those solicitations. It covers requirement definition, document creation, publication, supplier Q&A, response evaluation, award, and the handoff into contract administration.
In the public sector, it does two jobs at once.
It gets the agency what it needs. It also demonstrates, on the record, that the money was spent fairly.
Why Public Sector RFx Is Different
Private sector sourcing is judged on outcome. Public sector sourcing is judged on outcome and process.
Four differences shape everything about automation:
- Mandated transparency. Evaluation criteria and scoring methodology usually have to be documented and published before responses are received.
- Equal access. Every qualified supplier gets the same opportunity, the same documents, and the same answers at the same time.
- Audit and records retention. Decisions must be reconstructable years later, often under public records requests.
- Protest exposure. A losing bidder can formally challenge the award. If you cannot show why they lost, the award can be overturned.
Automation has to strengthen all four, not work around them.
The RFx Types Public Buyers Use
Request for Information (RFI)
An RFI is exploratory. Agencies use it before requirements are fixed, to understand what the market can actually deliver.
Use an RFI to:
- Decide whether a requirement is realistic
- Get indicative price ranges for budget planning
- Get delivery estimates and gauge project length
- Understand supplier capability and interest levels
- Build a qualified shortlist before a formal solicitation
A typical RFI asks for company background, service offerings, relevant public sector experience, certifications, and references.
An RFI is market research. It does not commit the agency to buy.
Example. A state agency issues RFIs to eight vendors before specifying an AP automation platform. It asks about invoice capture accuracy, ERP connectors, hosting model, and security accreditation. Four vendors make the RFP shortlist.
Request for Proposal (RFP)
An RFP is used for higher-value and more complex work, where the requirement is defined but the solution approach may vary.
A public sector RFP includes:
- Detailed functional and technical requirements
- Weighted evaluation criteria, usually published
- Explicit submission instructions, format, and page limits
- Presentation or demonstration requirements
- Terms and conditions, and the process for noting deviations
- A timeline with a formal vendor question window
Submission instructions are not a formality here. Omitting requested information can lead to automatic disqualification, however strong the rest of the bid.
Example. An RFP for a source-to-pay platform covers requisition workflows, supplier onboarding, three-way matching, accessibility compliance, data residency, implementation methodology, and ongoing support.
Request for Quotation (RFQ)
An RFQ is transactional. Agencies use it when specifications are fixed, and price is the deciding factor, typically for lower-dollar procurements.
An RFQ includes:
- Exact specifications
- Required quantities
- Delivery requirements and schedule
- Payment terms
- Submission deadline
- A Statement of Work (SOW) or Performance Work Statement (PWS) where relevant
- The evaluation criteria suppliers must meet
An RFQ is generally not itself a binding contract. For suppliers new to government work, it is the lowest-risk way to learn an agency’s process.
Request for Tender (RFT) and Request for Bid (RFB)
An RFT is standard in construction and public works, particularly outside the United States. It is formal and prescriptive.
An RFB appears where bidding rules are highly formalized, often awarding to the lowest compliant bidder.
Both are heavily rules-bound, which makes them good automation candidates. The logic is explicit, so it can be encoded.
RFI vs RFP vs RFQ: Comparison Table
| Factor | RFI | RFP | RFQ |
|---|---|---|---|
| Purpose | Gather capability and market intelligence | Solicit detailed solution proposals | Obtain pricing against fixed specs |
| Use when | The market or feasibility is unclear | Requirements defined, approach may vary | Specifications clear, price is the key factor |
| Typical timeline | 2 to 3 weeks | 4 to 8 weeks, up to 12 if highly technical | 1 to 2 weeks |
| Evaluation focus | Feasibility and capability screening | Methodology, service levels, quality, pricing | Price against specification |
| Detail required | Low | High | Medium |
| Outcome | Shortlist for RFP or RFQ | Award on weighted scoring | Award to lowest compliant bid |
| Automation potential | Moderate | Partial, evaluation stays human | High |
How to Choose the Right RFx Type
A common mistake is defaulting to one type across every category.
Match the request to risk and value instead.
- High value, complex, or novel. Use an RFP. You need to see approach and capability, not just price.
- Standardized, repeat, low risk. Use an RFQ, or call off an existing framework agreement.
- Unfamiliar market or unclear feasibility. Start with an RFI.
- Public works and formalized bidding. Use an RFT or RFB per the governing framework.
Many sourcing events chain two or three together. An agency sourcing a logistics partner might run an RFI to map the market, an RFP to the shortlist for service design, then an RFQ to standardize lane pricing across qualified vendors.
What to Include in an RFx Template
A standard template is the single biggest lever on response quality, and it is the foundation automation builds on. You cannot automate a document you rewrite from scratch every time.
| Section | Purpose |
|---|---|
| Agency and project overview | Introduces the organization, scope, and sourcing objectives |
| Supplier instructions | Submission format, page limits, deadlines, single point of contact |
| Technical requirements | Specifications, split into mandatory and desirable |
| Pricing structure | Prescribed cost breakdown so responses are comparable |
| Evaluation criteria | How responses will be scored, with published weightings |
| Compliance requirements | Statutory, security, accessibility, insurance, and contractual conditions |
| Timeline and deadlines | Milestones, question window, submission cut-off, award date |
| Terms and conditions | Proposed terms and the process for noting deviations |
Prescribe the pricing format. If suppliers choose their own, you get incomparable numbers and a weak evaluation record.
Build a template library organized by category, value band, and complexity. That library is what lets automated drafting produce something usable.
The Public Sector RFx Process, Step by Step
Six stages. Each produces documentation that supports the award if it is challenged.
Step 1: Define Requirements and Evaluation Criteria
Start inside the agency, not with vendors.
- Identify the need, budget authority, timeline, and technical specifications
- Separate mandatory requirements from desirable features
- Set weighted scoring criteria before any document is published
- Get written sign-off from procurement, legal, finance, and the programme owner
Common failures here are vague requirements, missing stakeholder input, and unrealistic timelines.
Locking criteria early does two things. It allows fair comparison. It also prevents the scope creep that happens when responses arrive, and someone decides a new feature matters.
What to automate. Criteria templates by category, mandatory approval routing, and version control on the requirement set.
Step 2: Create and Publish the Solicitation
Draft from the template library. Cover requirements, evaluation criteria, submission format, and deadline.
Publish to all qualified suppliers at the same moment. Simultaneous release is a legal requirement in most frameworks, not a courtesy.
Include the structured Q&A process in the document. Name the single point of contact and the question window.
Remember that the solicitation and the winning response are often incorporated into the final contract by reference. What you write becomes enforceable.
What to automate. Document assembly from templates, clause libraries for statutory and compliance language, and simultaneous distribution with timestamped proof of publication.
Step 3: Manage Supplier Questions and Track Submissions
Centralize every question. Share questions and answers with all participating suppliers at the same time.
That one rule prevents information asymmetry, which is the most common cause of a successful bid protest.
Also:
- Track deadlines and send automated reminders
- Log receipt and completeness of every submission
- Keep a full communication record for audit and dispute purposes
- Route all supplier contact through the named owner, never through individual stakeholders
If follow-ups depend on one person’s inbox, vacations and staff changes will break the process. Suppliers notice, and your bidder pool shrinks next time.
What to automate. A central Q&A repository, simultaneous answer publication, deadline reminders, receipt confirmations, and a complete communication log.
Step 4: Evaluate Responses Against Published Criteria
Assemble a cross-functional panel and split the work by expertise.
- Procurement evaluates commercial terms and total cost of ownership
- Legal reviews contract clauses, liability, and noted deviations
- Finance validates budget alignment and supplier financial health
- Programme and technical owners assess capability, integration, and fit
Apply the weighted matrix you set in Step 1. Score independently first, then reconcile.
Document the rationale behind each score, not just the number.
Multiple reviewers catch what one reviewer misses. Written rationale is what you present when a losing supplier asks why, or when an auditor asks the same question three years later.
What to automate. Response normalization, scoring calculations, independent reviewer workflows, variance flagging between scorers, and audit-ready scoring reports. The judgement stays human.
Step 5: Award and Negotiate
Take the top-scoring supplier into final negotiation on pricing, deliverables, service levels, and commercial terms. In lowest-compliant-bid processes,s the award follows directly from the scoring.
A competitive process gives leverage. Suppliers know they were compared.
Focus negotiation where the proposal fell short. Do not reopen settled terms.
What to automate. Award notification, debrief letter generation, and the audit package that documents how the decision was reached.
Step 6: Move Commitments Into Contract and Performance Management
Every commitment in a winning response needs to land somewhere it will be tracked.
That means:
- Negotiated pricing and volume breaks recorded against the contract
- Deliverables and SLAs loaded as trackable obligations
- Renewal and notice dates set with automated alerts
- Supplier performance measured against what was promised in the bid
- Awarded pricing pushed into AP so invoices match the contracted rate
Weeks of evaluation are wasted if nobody ever checks whether the supplier delivered what won them the award.
This is where most public sector value leaks out. The solicitation is rigorous. The contract then sits in a shared drive.
How to Automate RFx Without Losing Transparency
Automation and fairness are not in tension, provided three capabilities are in place.
Centralized document management. Every stakeholder and every supplier works from the same version of the same information. No side channels.
Automated workflow routing. The system enforces the evaluation criteria and approval chain you defined, rather than relying on someone remembering them. The rules become structural instead of procedural.
Complete audit trails. Every action is logged, from solicitation creation through to award, including any change to weightings and who made it.
Those three turn automation into a compliance asset. A manual process depends on people following the rules. An automated process makes breaking them difficult and visible.
E-procurement platforms meet public transparency requirements through simultaneous Q&A distribution, automated deadline enforcement, published scoring methodologies, and audit-ready reports.
What the Evidence Says
Research from Cambridge University covering e-procurement reforms across 11 countries found structured electronic procurement reduced prices by roughly 6.75 percent on average, with documented savings ranging from 3 to 25 percent across cases.
McKinsey has put procurement productivity improvement from AI copilots and task-level tools at 25 to 40 percent. Software vendors report RFx cycle time reductions of up to 70 percent from AI-assisted templates and auto-scoring.
Treat vendor figures as directional. Prove them in a pilot before building a business case on them.
What to Automate First
Sequence matters in a regulated environment. Start where the compliance risk is lowest and the time saving is clearest.
- Template and clause libraries. No decision authority changes hands. Immediate consistency gain.
- Publication and distribution. Removes the simultaneity risk entirely.
- Q&A management. Removes the information asymmetry risk entirely.
- Deadline tracking and receipt logging. Pure administration, high failure rate when manual.
- Response normalization and scoring calculation. Mechanical work, with people still assigning the scores.
- Audit pack generation. Turns a week of retrospective assembly into a report.
- Contract and obligation handoff. Where the savings actually get realized.
Evaluation judgment and award authority come last, and in most public frameworks they do not get automated at all.
AI in Public Sector RFx
AI is already changing the mechanics of solicitation work. For public buyers, the useful question is not whether to use it, but how much decision authority it can hold.
Semi-Autonomous RFx: Where Public Buyers Should Operate
AI acts as a co-pilot. It drafts, normalizes, and recommends. People decide.
In practice:
- AI spots signals that sourcing is needed, such as contract expiries, demand spikes, repeated off-contract purchases, or a forecast supply gap
- It proposes the request type and generates a first draft from past solicitations, category strategy, supplier performance, risk indicators, and policy
- Statutory clauses, accessibility requirements, and evaluation criteria are embedded by default
- At evaluation,n it normalizes responses, flags anomalies and omissions, and proposes comparative scoring
People validate assumptions, adjust weightings, confirm compliance, and make the award.
The gain is speed plus consistency. Institutional knowledge gets applied evenly across departments instead of depending on who happens to run the solicitation.
Autonomous RFx: Where It Fits and Where It Does Not
Full autonomy means the system initiates the event, selects suppliers, issues the package, handles clarifications, and awards within set tolerances.
That is appropriate in a narrow set of categories. Look for all five traits:
- High volume, low complexity
- Stable, well-defined specifications
- A large and competitive supplier market
- Low business and reputational risk
- Clear historical patterns in price and performance
Standard MRO items, office supplies, basic IT peripherals, and commoditized logistics lanes fit. Call-offs against an existing framework agreement fit especially well, because the competitive process already happened.
Strategic, novel, or politically visible categories do not. Where requirements evolve, public interest is high, innovation is expected, or trade-offs span cost, resilience, and social value, human involvement stays essential.
Autonomy is not a switch. It varies by category, and by stage within a single event. An agency might let agents run framework call-offs end to end while award approval for anything above a threshold stays with a person.
Core AI Capabilities Across the RFx Lifecycle
Automated drafting. Tailored first drafts from prior solicitations and category strategy, rather than static templates. Fewer omissions and less legal rework.
Multi-dimensional supplier scoring. Cost, delivery performance, financial stability, social value and ESG indicators, cyber and regulatory risk, and compliance history scored together. Weightings adapt by category, because value means something different for MRO than for critical infrastructure.
Scenario and what-if modelling. The most underused capability. It makes trade-offs explicit: lower unit price against higher supply risk, incumbent against diversification, short-term savings against stronger social value outcomes. Surfacing those choices to stakeholders and oversight bodies reduces post-award disputes.
Supplier ranking. In low-risk categories, rankings can trigger awards within predefined thresholds. In complex ones,nes they are decision support only. A ranking is not a decision, and treating it as one erodes trust and invites challenge.
Explainability and auditability. The test is whether you can answer why the system recommended a given supplier to an auditor, an oversight committee, or a protesting bidder. That requires transparent scoring logic, documented data sources, and a full trail of inputs, weightings, and changes.
For public buyers,ers this is not a nice-to-have. Without explainability, automation does not scale past administration.
What AI-Enabled RFx Needs to Work
AI is only as good as the data under it. Algorithms cannot compensate for fragmented or unreliable inputs.
Internal minimum:
- Clean supplier master data
- A usable history of past solicitations and outcomes
- Consistent scoring models
- Reliable supplier performance records
External inputs:
- Supplier risk and financial health indicators
- Compliance, debarment, and sanctions screening
- ESG and social value metrics
These need to be current and attributable to trusted sources.
Integration is the other prerequisite. The sourcing platform has to connect to the ERP, the contract repository, and approval workflows. Otherwise, recommendations ignore real budget and policy, and every output needs rework before it can be executed.
A Worked Example: Mixed Autonomy at an Agency
Consider a large agency sourcing goods, professional services, and capital projects across multiple departments.
Autonomous. For office consumables, standard IT peripherals, and routine maintenance, agents monitor demand signals and contract expiry dates. When thresholds are hit, the system issues RFQs against the approved supplier pool, scores on price, delivery reliability, and compliance, and awards within published tolerance bands with a full audit trail.
Semi-autonomous. For a professional services framework, AI drafts the solicitation, evaluates responses on total value including capacity and social value commitments, and produces a ranked shortlist. The evaluation panel then weighs methodology, delivery risk, and policy alignment. The award is human and documented.
Disruption response. When a key supplier enters administration, AI immediately reassesses exposure across affected contracts, identifies alternatives from the approved supplier universe, and models cost uplift and continuity impact under each option. Leaders choose between higher cost and faster continuity.
The pattern holds. AI does aggregation, modelling, and impact assessment. People make the judgement calls and carry the accountability.
The Biggest Challenges in Public Sector RFx Management
Manual Processes and Scattered Documents
Solicitations sit in email threads. Responses arrive in different formats. Evaluation spreadsheets live on individual laptops.
Teams lose hours consolidating and searching, and the loss compounds when several events run at once.
Knowledge disappears too. Without a searchable record, the next team starts from zero on a category the agency sourced 18 months ago.
Fix it. Centralize documents and responses in one platform. Standardize templates. Keep a searchable archive for benchmarking and for records requests.
Inconsistent Evaluation and Subjective Scoring
Without predefined criteria, evaluators apply their own standards. “Best value” means something different to procurement, legal, and a programme lead.
In the public sector, the consequence is sharper than a weak decision. If you cannot demonstrate objective selection, you are exposed to claims of favoritism and to a sustained protest.
Fix it. Publish weighted criteria before issuing. Use detailed matrices with specific metrics for pricing, experience, timeline, technical capability, and financial stability. Require written rationale. Use multiple reviewers from different functions.
Poor Supplier Communication and Missed Deadlines
Suppliers email different internal contacts. Some get informal guidance; others do not. Deadlines pass without anyone confirming what arrived.
That is both a fairness failure and a market failure. Good suppliers stop bidding, and competition in your next solicitation weakens.
Fix it. One point of contact. Shared Q&A published to all bidders simultaneously. Automated deadline tracking. Written receipt confirmation.
The Gap Between Award and Execution
The contract gets signed and filed. Renewal dates slip past. Negotiated obligations go untracked. Nobody monitors the terms that were evaluated so carefully.
Fix it. Push awarded contracts straight into lifecycle management with obligation tracking, renewal alerts, a central repository, and a feed into AP so invoices match contracted rates.
Common RFx Pitfalls and How to Avoid Them
Ambiguous requirements. The leading cause of RFx failure. Vague specs produce divergent interpretations and incomparable bids. Define precisely before publication.
Inadequate evaluation criteria. Without predefined scoring, evaluation becomes subjective and indefensible.
Poor Q&A administration. Duplicate questions and inconsistent answers extend timelines and create asymmetry. Use one central repository visible to all bidders.
Ignoring total cost of ownership. A $50,000 proposal with hidden implementation costs can cost more than a $60,000 all-inclusive option. Score TCO, not purchase price.
Reusing outdated templates. Old templates carry stale requirements, retired standards, and criteria that no longer reflect policy. Audit them annually.
Lack of internal alignment. If procurement, legal, and the programme owner disagree on requirements, the disagreement surfaces during evaluation. Align before launch.
Unrealistic timelines. Short windows reduce the bidder pool and the quality of what you receive.
Automating without documenting the logic. An automated process whose rules nobody can explain is worse than a manual one. Document the configuration as carefully as the decision.
How to Respond to a Public Sector RFx and Win: 7 Tips for Suppliers
Automation changes the supplier side too. Portals are now the front door, and incomplete submissions get rejected by the system rather than by a person.
1. Understand the requirement properly. Read every attachment and addendum. Map scope, timeline, and evaluation weightings before writing anything. Ask questions through the official channel only.
2. Show relevance, not breadth. Align your response to the agency’s stated priorities. Tie each strength to a specific requirement or evaluation criterion.
3. Emphasize value over price. Underbidding is visible when competitors are similar, and it can get you eliminated rather than shortlisted. Lead on quality, expertise, reliability, and demonstrated public sector delivery.
4. Be clear, complete, and concise. Answer every requirement in the order asked, using their numbering. Skip jargon. Make scoring easy for the evaluator.
5. Use references and past performance. Case studies and testimonials from comparable agencies build credibility faster than claims.
6. Use the question window, then follow up. Submit well before the cut-off, since portals do not grant extensions. Confirm receipt, then clarify and reaffirm interest without pestering.
7. Prepare for negotiation. Know your limits and where you have flexibility on scope, scale, or pricing. This matters most on large RFPs.
Why Automation Matters to Procurement Strategy
RFx is the mechanism that standardizes supplier evaluation across every spend category. Automation is what makes that standard hold under volume.
Without it, teams fall back on informal relationships and inconsistent practice. That produces uneven pricing, unvetted suppliers, and audit exposure.
Operationally, automated RFx shortens sourcing cycles and consolidates supplier communication into one channel.
Strategically, it builds an institutional knowledge base. You can benchmark pricing across events, track supplier performance over time, and identify which suppliers deserve preferred or framework status.
That matters most in categories where supplier decisions carry regulatory, financial, or public safety consequences.
What to Look for in RFx Automation Software
Sourcing software handles the front end. Contract lifecycle management handles what happens after award. The value comes from connecting them.
Capabilities worth requiring:
- A central template and clause library organized by category and value band
- Automated simultaneous publication with timestamped proof
- A central Q&A repository with publication to all bidders at once
- Configurable weighted scoring with independent reviewer workflows
- Full audit logging of inputs, weightings, and changes, with user attribution
- Automated transfer of awarded terms into the contract record
- Obligation tracking against SLAs and pricing commitments
- Renewal and notice date alerts
- A searchable archive of past solicitations for benchmarking and records requests
- Accessibility compliance in the supplier-facing portal
- ERP and AP integration so awarded pricing flows through to invoice matching
That last point is where sourcing discipline either pays off or quietly disappears. If the negotiated price never reaches the invoice matching layer, the savings stay on paper.
Getting Started: A Practical Sequence
This is evolutionary work, not a transformation programme.
- Pick one category. Choose one where data quality is strong, and risk is manageable. Framework call-offs are a good first candidate.
- Audit your current templates. Look for ambiguity, stale clauses, and missing evaluation criteria.
- Build the scoring matrix first. Weight it with the people who will use it, and document the reasoning.
- Automate publication and Q&A next. Highest compliance gain, lowest controversy.
- Run one controlled solicitation end to end. Keep evaluation judgment with the panel.
- Measure. Track cycle time, bidder participation, protest rate, and evaluator time per response.
- Refine governance, then scale. Expand across categories and departments as data and confidence improve.
Most agencies over-engineer routine purchases and under-analyze strategic ones. Automating the routine end is what frees capacity to do the strategic end properly.
Frequently Asked Questions
What is the role of RFx in public sector procurement?
Most public frameworks make a structured RFx process mandatory to ensure transparency, fairness, and accountability for public funds. Agencies publish evaluation criteria, give equal access to qualified suppliers, distribute questions and answers simultaneously, and keep audit trails that demonstrate compliance.
Can public sector RFx processes be automated and still stay compliant?
Yes, and automation usually improves compliance. Simultaneous publication, a central Q&A repository, enforced approval routing, and complete audit logging are easier to guarantee in software than by hand. The rule is that automation handles mechanics and documentation, while evaluation judgement and award authority stay with accountable people.
What is the difference between RFx and RFP?
RFx is the umbrella term for all formal supplier request types, including RFI, RFP, RFQ, RFT, and RFB. An RFP is one specific type, used when requirements are defined but the solution approach may vary. RFx management means handling any or all of them systematically.
How long does the RFx process take?
RFQs typically run 1 to 2 weeks. RFIs run 2 to 3 weeks. RFPs run 4 to 8 weeks, and up to 12 for highly technical evaluations. Add 1 to 3 weeks for evaluation and scoring, and 2 to 4 weeks for contract finalization. Public sector timelines often run longer because of mandated notice periods.
Who manages the RFx process in an agency?
Procurement leads it. Legal reviews terms and statutory compliance. Finance validates budget authority and analyzes pricing. Programme and technical owners assess capability. On larger solicitations, an RFx manager coordinates timelines, enforces the published criteria, and acts as the single point of contact for suppliers.
How do you evaluate RFx responses fairly?
Publish weighted criteria before issuing the solicitation. Use a cross-functional panel that scores independently before reconciling. Apply the same matrix to every response. Document the rationale behind each score, not just the number. Share all clarifications with all bidders at the same time.
Which parts of the RFx process should not be automated?
Final evaluation judgment, award authority, and anything requiring policy interpretation. Automation can normalize responses, calculate scores, and flag anomalies. Deciding what trade-offs are acceptable, and carrying accountability for that decision, stays human.
Is RFx only used for large procurement projects?
No. It is most common in large strategic sourcing, but the framework works for smaller purchases too, wherever structured comparison and transparent evaluation are needed. Scale the document to the spend. A one-page RFQ is still an RFx.
What factors should be included in an RFx evaluation?
Pricing and total cost of ownership, technical capability, compliance posture, service levels, implementation timeline, financial stability, past performance, social value commitments where applicable, and long-term strategic fit. Weight them according to what the category actually requires.
How does RFx automation improve long-term supplier performance?
A structured solicitation sets expectations explicitly at the start: requirements, deliverables, pricing, and timelines. When those commitments flow automatically into a contract system, you can track obligations, monitor SLAs, and measure actual performance against what was bid. That accountability is what makes supplier outcomes predictable.