Five things people actually do with it

Five common capture jobs, start to finish — the question you ask, the evidence you check, and the action you take at the end.

Each job below starts with a question you would ask a colleague and ends with something you actually do — a call, a number in a pricing sheet, a name on a task. Pick the one that matches the decision in front of you.

Every job also has a boundary: the thing FedScope cannot settle for you. Read it. It is usually the part that costs money if you skip it.

Find out who is doing the work today

You want to know: Is this work likely to come up for rebid, and who holds it now?

Ask: Who appears to be doing similar work for this agency, and which awards show it?

Describe the work. Say the agency, the type of work, the industry code, and roughly when the work was performed. Plain sentences are fine.

Compare the companies that come back. Look at who was paid, how much, which contract they used, and what changed recently.

Open the strongest records. Read the actual awards behind the answer, then confirm them at the official government source.

Write down the other explanations. If two companies or two contracts could both cover this work, note that — a lead you can defend beats a guess you cannot.

You end with: a short list of likely performers, each backed by a record you can point to in a capture review.

Boundary

Similar past awards do not prove a company is the incumbent on a specific upcoming notice. Treat the result as a research lead you still have to confirm.

Sanity-check a price before you commit to it

You want to know: Is my early price or labor rate in the right neighborhood?

Ask: What comparable federal awards or rates can frame this estimate?

Narrow the comparison. Same kind of work, same customer, same region, same contract type, similar time period. A loose comparison produces a useless number.

Keep two numbers apart. What the government has actually paid out so far is not the same as the contract's maximum value. Do not mix them, and do not compare unlike contracts.

Look at the awards, not just the range. Open the records underneath the summary figure so you know what is driving it.

Record your assumptions. Note what you assumed about scope, staffing, and location, so the number survives someone questioning it later.

You end with: a defensible planning range, with the awards behind it and your assumptions written down. See labor-rate benchmarks.

Boundary

Public award values rarely show the full staffing mix, overhead rates, discounts, or bidding strategy. A benchmark is a planning reference — not a bid price and not a certified cost estimate.

Catch a rule change before it catches you

You want to know: Did something change that my capture, proposal, or compliance people need to act on?

Ask: Which recent federal changes could affect our pursuits, certifications, or reporting?

Filter to your world. The agencies, programs, and requirements you actually work in.

Read the source and note the dates. When it takes effect, when comments close, and what the transition rules say.

Tell proposed apart from final. A proposed rule is a heads-up. A final rule is an obligation. They are not the same, and FedScope labels which is which.

Give it an owner. Interpretation and implementation happen in your company, not in FedScope.

You end with: a named owner and a due date for each change that touches you. See regulatory watch.

Boundary

FedScope organizes public information. It does not give legal advice and cannot decide whether a rule applies to your specific company or contract.

Decide whether a partner is worth a phone call

You want to know: Should I reach out to this company for this pursuit?

Ask: Which firms have real, evidenced experience in this scope, with this customer, in this role?

Name the gap. Be specific about what the partner has to bring that you do not have.

Compare the evidence. Past awards, which agencies they served, industry codes, where they work, and what their small-business status has been on real contracts.

Open the awards and check status at the source. A past set-aside award does not mean the company holds that certification today. Confirm current registration and certification at the official source.

Call them. Availability, interest, conflicts, capacity, and whether you can stand working together are things only a conversation settles.

You end with: a short outreach list where every name has a record behind it. See company profiles.

Boundary

A ranked match is not an endorsement and not a certification decision. It does not say the company is available, responsible, or eligible for a particular procurement.

Get ready for a compliance review

You want to know: What evidence do we have, what is missing, and who is fixing it?

Ask: Which records support our readiness, and where are the gaps?

Name the review. Which obligation or review are you preparing for? Everything else follows from that.

Gather the evidence. Public records, plus any contractor-controlled material you are authorized to use.

Sort it into three piles. Confirmed evidence, unconfirmed claims, and missing material. Keeping those apart is the whole point of the exercise.

Assign the fixes. Remediation happens outside FedScope. Keep the authoritative source for every conclusion you write down.

You end with: a gap list with owners, and a source citation next to each conclusion. See subcontracting compliance.

Boundary

A complete-looking picture in FedScope does not establish that you are compliant. Your company and its advisers make that call.

What a defensible answer looks like

Before you act on anything FedScope tells you, you should be able to say all six of these out loud:

The questionWhat you actually asked
The filtersHow you narrowed it
The recordsWhich official records support it
The assumptionsWhat you took on faith
The gapsWhat the record does not cover
The next actionWho does what, by when

If one of those is blank, you have a lead, not an answer. See how FedScope decides what to show you and what FedScope cannot tell you.

On this page