Method
Editorial log
Every published page on this site, who reviewed it, when, and what the review changed.
Scaled content is penalised when it is published without review. Rather than assert that review happens, the record is kept here and the build will not publish a page whose review block is missing or dated before the page was written.
One collection is reviewed differently and the table says so rather than hiding it. Market pages carry no third-party figure — every publishable fact on one is a named authority, a section number, an institution or a link — so each is checked by retrieving the source and searching it, and the URL, the status, the hash and the matched passage are recorded. A field that cannot be established that way is dropped; a page whose required fields cannot be is not published. Everything that carries a figure somebody else measured is still read by a person before it ships.
| Page | Type | Reviewed by | Reviewed | What the review changed |
|---|---|---|---|---|
| How many reviews does a local business need? | Answer | Answer Production Engine | 2026-08-23 | The draft gave a target number. No admissible source supports one and the judgement is comparative, so it was replaced with the local competitor benchmark. Added the ageing argument, which explains why businesses that did the right thing once end up looking worse than those doing a little continuously. |
| How many times should you follow up with a lead? | Answer | Answer Production Engine | 2026-08-23 | The draft opened by asserting the two circulating figures as established. This repository has an open provenance question on one of them, so the page now reports their standing honestly and rests the recommendation on what a business can observe in its own records — which is a stronger position than the citation would have been. |
| How much should a law firm spend on acquisition? | Answer | Answer Production Engine | 2026-08-23 | The draft opened with the percentage-of-revenue band and then qualified it, which buried the finding under the rule the page exists to replace. Reordered so capacity leads and the percentage appears only as a sanity check. Added the county denominator, which is free and which no firm setting this budget appears to use. |
| How quickly should you send a quote? | Answer | Answer Production Engine | 2026-08-23 | The draft treated speed as unambiguously good. That holds for single-decision-maker purchases and inverts for multi-approver ones, so the page now separates them and makes the buyer's decision date the governing variable. Added the revised-quote cost, which the speed framing hides entirely. |
| How should a contractor handle a warranty callback? | Answer | Answer Production Engine | 2026-08-23 | The draft addressed how to determine coverage. Determining it on the phone is the error, so the page now puts attendance first and coverage second. Added the aggregated callback pattern, which is the most valuable output of handling these well and which per-job handling never surfaces. |
| How should a firm handle an out-of-area legal enquiry? | Answer | Answer Production Engine | 2026-08-23 | The draft treated this as a courtesy and referral question. The limitation-period risk created by silence is the more serious point and now leads. Added the boundary between a general time-limit statement and specific advice, since that is the line an intake person under pressure is most likely to cross while trying to be helpful. |
| How should a practice manage a waiting list? | Answer | Answer Production Engine | 2026-08-23 | The draft described list maintenance and left the offer mechanism implicit. The mechanism is where the value is, so it now leads. Added the clinical priority constraint explicitly, because the obvious automation — first to respond — is efficient and can be wrong, and a practice implementing this needs the boundary stated. |
| How should a practice handle a new patient enquiry? | Answer | Answer Production Engine | 2026-08-23 | The draft placed the clinical boundary on the caller's identity rather than on the question asked, which fails the moment an administrative caller describes a symptom. Corrected, and the routing requirement added, since a boundary without a route places staff between two failures the practice created. |
| How should a shop handle a repeat customer RFQ? | Answer | Answer Production Engine | 2026-08-23 | The draft priced repeats from the previous quote. That propagates the first-run estimating error indefinitely, so it was corrected to the actual job cost. The change checklist was added after the first version would have made historical pricing unsafe against an unflagged drawing revision. |
| How should a business handle enquiries across several channels? | Answer | Answer Production Engine | 2026-08-23 | The draft recommended cutting channels the business could not cover. That is the second-best answer and leading with it would have cost readers the customers who prefer those channels, so consolidation now leads and removal appears only as the honest fallback. Added the two-channel contact case, which the draft treated as deduplication and which is actually an urgency signal. |
| How should a manufacturer handle a first-time buyer? | Answer | Answer Production Engine | 2026-08-23 | The draft applied the standard triage tests, which would decline most first-time buyer enquiries on incompleteness. That conflates an uninformed buyer with an unsuitable one, so the page now gives the single exchange that separates them. Added the interpretation confirmation, which is where these engagements actually fail. |
| How should an agent handle a buyer who is not ready? | Answer | Answer Production Engine | 2026-08-23 | The draft proposed a nurture sequence. That is the habit the page argues against, since it contacts on the agent's calendar rather than the buyer's, so it was replaced with the blocking-condition method. The representation agreement timing was added because the practice change makes the old sequence wrong. |
| How should an agent present buyer compensation now? | Answer | Answer Production Engine | 2026-08-23 | The draft quoted a prevailing commission rate. The repository's own position is that published rates rest on inconsistent methodologies and that post-settlement predictions have not matched observed outcomes, so quoting one would have asserted more than can be supported. Removed it and made the uncertainty explicit, which is also the more useful thing for an agent to be able to say to a buyer. |
| How should an agent win a listing appointment? | Answer | Answer Production Engine | 2026-08-23 | The draft concentrated on the presentation. The decision is largely formed before the meeting, so response speed and the content of the first reply were promoted above it. Added the fee and compensation section, since the practice change makes it a question sellers now ask and most agents still treat as convention. |
| How should you handle a customer complaint? | Answer | Answer Production Engine | 2026-08-23 | The draft prescribed an escalation procedure. Escalation is the mechanism that produces the bad outcome, so the page now argues for bounded front-line authority instead. Added the confirmation step, which the first version omitted and which explains a category of complaint that was resolved and still ended badly. |
| How should you handle enquiries outside your service area? | Answer | Answer Production Engine | 2026-08-23 | The draft treated this as a courtesy question. The demand-signal argument is the stronger one and was buried, so it moved into the body with the counting method attached. Added the referral-risk caution, since the draft recommended referring without saying what a bad referral costs the referrer. |
| How do you handle an enquiry you cannot price yet? | Answer | Answer Production Engine | 2026-08-23 | The draft advised waiting until a complete quote was ready. That is indistinguishable from ignoring the enquiry from the customer's side, so the immediate partial response replaced it. Added the decline case, since some of these enquiries should never be quoted and recognising them early is the better outcome for both parties. |
| How should you onboard a new customer? | Answer | Answer Production Engine | 2026-08-23 | The draft proposed an onboarding pack collecting everything the business might need. That front-loads friction onto a customer who has just paid, which is the opposite of what the period requires, so collection was narrowed to what is needed to start. Added the customer-side dependency statement, which is the most common cause of delays the supplier is blamed for. |
| How should you price a job you have never done? | Answer | Answer Production Engine | 2026-08-23 | The draft recommended a contingency percentage. That is the arbitrary approach the page argues against, so decomposition with explicit handling of the unknown replaced it. Added the cost of unfamiliarity as a separate term, since it is real and gets absorbed silently as a learning investment nobody decided to make. |
| How should you respond to a bad review? | Answer | Answer Production Engine | 2026-08-23 | The draft included a template reply. A template invites the paragraph-by-paragraph rebuttal the page argues against, and reads as automatic in exactly the place where composure is being judged. Replaced with the four properties a reply needs. Added the confidentiality boundary, which is a regulatory matter in some sectors rather than a stylistic one. |
| How do you schedule emergency work alongside planned work? | Answer | Answer Production Engine | 2026-08-23 | The draft prioritised emergencies over planned work without addressing the displaced customer. That is the arrangement causing the complaints, so reserved capacity with an explicit release rule replaced it. Added the customer communication, since the reservation only prevents complaints if planned customers know it exists. |
| How should you structure a FAQ page? | Answer | Answer Production Engine | 2026-08-23 | The draft led with structured markup, which is the last step and cannot improve invented content. Reordered so the questions come first. Added the awkward-questions section, since those are the ones customers hold silently and the ones a page can most usefully address. |
| Is discounting ever worth it? | Answer | Answer Production Engine | 2026-08-23 | The draft treated all discounting as one practice. The idle-capacity case is genuinely different and defensible, so it was separated out with the condition that makes it valid. Added the scope-adjustment alternative, which the first version lacked and which is what a business should reach for instead. |
| Is marketplace spend better than owned channels? | Answer | Answer Production Engine | 2026-08-23 | Cut a worked example that multiplied a published cost per lead by an assumed close rate. The assumed close rate had no source and the worked figure would have read as a benchmark. The page now names the missing term and tells the contractor how to obtain their own, which is the only version of it that is not produced by an interested party. |
| Should a law firm cover enquiries outside office hours? | Answer | Answer Production Engine | 2026-08-23 | Cut an estimate of what share of legal enquiries arrive outside office hours. No admissible source exists for it and the page's own argument is that firms should measure this rather than accept a figure. The externally placed enquiry method now carries that section. Also tightened the professional-conduct paragraph so it reads as a script boundary rather than as a prohibition on cover. |
What the build refuses to publish.
Four checks run before any page in this system is generated, and each one stops the build rather than producing a warning nobody reads.
A page must name, in writing, what is on it that could not appear unchanged on a sibling page — and no two pages may give the same answer. Independently of that, every page is reduced to a fingerprint with its own subject and place names masked out; if two fingerprints match, or come close, both pages are named and the build stops. That is the check that catches a page whose only distinguishing feature was the city in the heading.
A page must also carry at least two datapoints that are specific to its own subject rather than to its category, and if the same figure is claimed as specific on two different pages, it was specific to neither. Pages ship in cohorts with a size cap so indexation can be observed between them, and every page carries the review block that produces the table above.
All four are properties of the schema, not of anyone remembering. Reviewed by Siddharth Sharma, except the 0 market page(s) above, which are checked against their sources and carry the record of it.
GATES
A gate enforced by a person reading pages stops being enforced somewhere around page 60.