How long it takes

A schedule, by component

What makes one market slower than another

Competitive density is the largest variable. A city where several established defense firms have invested for years is harder ground than one where the incumbents have neglected their profiles, and identical work produces different curves.

The firm's starting position matters as much. A practice with an unclaimed profile and no charge pages has a great deal of correctable ground, and correctable ground moves fast. A practice already doing most things properly will move more slowly for the same spend.

Geography sets a ceiling that time does not lift. Proximity is a direct input to local ranking, so a single office in a large metro is bound past a certain radius however long the work runs. A grid scan shows where that boundary sits before any money is committed.

When to judge it

A firm evaluating an agency at week four is measuring the wrong thing at the wrong time. The work with the shortest latency has barely landed and the work that matters most has not started producing.

The first informative comparison is a grid rescan against the baseline at ninety days, which shows whether profile and technical work moved anything. Content is properly judged at six months. The question of whether enquiries and signed matters rose is a twelve-month question, and and that number lives with the firm.

What has actually been measured

Every case study published across this network reports a window of under ninety days, measured on a grid scanned before the work and rescanned afterwards on the identical grid.

Those figures describe six specific markets. They are first-party, they measure visibility and not cases signed, and a large percentage from a low base is a smaller absolute movement than the number suggests. Competitive density varies enough between cities that the same work produces different curves, which the spread in that table shows.

Chapter assignment

The assignment for How long it takes is to turn the chapter's advice into a decision record that states the firm's market, scope and present constraint. Begin with the question that caused the reader to open this chapter. Write it in one sentence and name the person who can approve the answer. The chapter premise is: Asking how long SEO takes is asking about several activities with very different latencies. Averaging them produces a number that describes none of them, which is why this chapter gives a schedule per component instead.

For How long it takes, define completion before doing the work. A task is complete when the firm can inspect the changed asset, recover the starting state and repeat the check without relying on memory. Activity counts and dashboard labels do not satisfy that rule. The retained deliverable is a dated assumption sheet and the next question to resolve.

Set up the working file

Create the How long it takes folder under the market and observation date. Put the baseline or source copy first. Add a short manifest that names the asset owner, operator, approver, measurement unit and next review date. Link to firm-controlled credentials through the approved credential system; never place a password in the workbook.

The How long it takes file records unknown fields as unknown. An empty value is a prompt for the owner, not permission to infer. If two sources disagree, save both and open a conflict row before choosing one. For public legal text, identify the attorney who will check the statement. For measurement, identify the instrument and settings. For vendor work, identify the export and exit right.

Execution pass

1. Observe. Save the present state and note why it matters to the firm's criminal defense work.
2. Diagnose. Separate the visible symptom from its possible causes. Choose the smallest change that tests the diagnosis.
3. Approve. Obtain factual, attorney or commercial approval at the point required by the asset.
4. Change. Make one attributable revision and record the operator and time.
5. Verify. Repeat the original check under the same scope. Capture the result even when it failed.
6. Hand off. Store the files under firm control and assign the next review.

The How long it takes failure to guard against is starting work before the baseline or decision owner is known. If it occurs, stop the release. Preserve the failed state and decide whether the work, source or instrument caused the problem. A new method needs a new baseline and version; it should not be spliced into the previous series.

Decision points

Continue the How long it takes assignment when the starting record is complete, the owner is known and the acceptance rule can be tested. Pause when access is disputed, a legal statement awaits attorney review, the measured unit has changed or a source conflicts with the proposed wording. Cancel the task when it does not match a real charge, market, reader question or business decision.

Prioritize How long it takes by dependency. Ownership comes before optimization. A baseline comes before a change report. A charge brief comes before prose. Crawl access comes before answer testing. A defined intake event comes before a return calculation. This order prevents later work from resting on an unknown or disputed input.

Quality review

For How long it takes: Review the premise against the firm's actual matters and retained records. Then ask whether a new operator could reproduce the check from the handoff. Confirm that page headings name the reader's question, local claims name the correct market, and measurement statements retain their units. Verify that no confidential matter fact or unsupported outcome entered a public file.

Check source control for How long it takes as well. A statement on the firm's own page is first-party. A publisher-owned sibling domain is still the same origin. An award citation must keep the issuer's qualification. A vendor screenshot is useful evidence of a recorded state, but the firm should also retain an export when one is available.

Field exercise

Choose one live example for How long it takes from the firm's current operation. Use a real market and a real service the firm accepts. Save the present public view before discussing improvements. Ask the asset owner to describe the problem without offering a solution. That account becomes the problem statement and gives the later review something concrete to test.

Now complete the How long it takes assignment on that single example. Keep a side log of assumptions and evidence requests. When an assumption is confirmed, replace it with the source. When it is rejected, note the effect on the proposed work. Do not expand to a second asset until the first has passed its acceptance rule. This narrow trial exposes access problems and approval delays while the recovery cost is low.

Have a second person review the How long it takes handoff without verbal explanation. Ask that reviewer to locate the baseline, identify the change, repeat the test and find the approval. Any answer that depends on the original operator's memory is a documentation gap. Repair the file and repeat the review.

Finally, write two How long it takes report sentences. The first states the observable result in its native unit. The second states the limit or next decision. Remove any causal language that the record cannot support. Store the approved pair with the deliverable so the monthly report does not have to reconstruct meaning from a chart.

Handoff record

The How long it takes handoff contains the starting record, work completed, approval, final check, open limitations and next action. Give each item a stable filename. The receiving owner should be able to say what changed, why it changed, who approved it and where the proof sits.

End the How long it takes file with a plain decision: accepted, accepted with a named limit, returned for repair or stopped. A partially completed task should remain open. Carry the unresolved field into the next work cycle instead of hiding it inside a broad progress label.

Acceptance record for How long it takes

Reopen How long it takes with a dated assumption sheet and the next question to resolve in view. Apply this review: Review the premise against the firm's actual matters and retained records. Record whether the file answers “Asking how long SEO takes is asking about several activities with very different latencies. Averaging them produces a number that describes none of them, which is why this chapter gives a schedule per component instead.” at its stated market and date. A different question gets a new assignment and cannot borrow the approval attached to How long it takes.

Return How long it takes when it shows starting work before the baseline or decision owner is known. Keep the rejected copy and name the record needed for another pass. Acceptance means the firm controls a decision record that states the firm's market, scope and present constraint, can recover the earlier state and has dated the next check.

Related chapters6. Setting a baseline · 41. The search grid · 46. What a monthly report should contain