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.
Some collections are checked automatically 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. Practical guides are published under Siddharth Sharma's byline. The review log records the checks performed during production separately from author attribution; it does not treat an automated check as a person reading a piece.
| Page | Type | Reviewed by | Reviewed | What the review changed |
|---|---|---|---|---|
| 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. |
| Should a law firm pay for per-lead legal marketplaces? | Answer | Answer Production Engine | 2026-08-23 | Removed a comparison of marketplace cost per signed case against paid search cost per signed case. Only one side of that comparison has a sourced figure and publishing the pair would have implied both were established. The page now compares what can be compared — the published lead costs — and directs the firm to compute the signed-case figure from its own records. |
| Should a law firm put an AI agent on first contact? | Answer | Answer Production Engine | 2026-08-23 | The draft compared signing rates before and after AI intake as though a figure existed. It does not — the question of whether AI first contact has changed signing rates is an open research need in this repository, not a settled result. Removed the comparison and replaced it with the denominator defect, which is the reason no such figure can currently be trusted from any firm's own reporting. |
| Should a firm run intake in-house or use a service? | Answer | Answer Production Engine | 2026-08-23 | The draft picked the answering service as the default recommendation. That was not supportable: which structure wins depends on the arrival shape, and the page's own argument is that the shape is unmeasured. Replaced the recommendation with the measurement and the crossing-point logic, and added the authorisation-scope section because it is the most common reason a correctly priced arrangement still fails. |
| Should a manufacturer add machine capacity? | Answer | Answer Production Engine | 2026-08-23 | The draft treated the size-band table as a straightforward count. It is not: cells are suppressed for disclosure and an unclassified residual means the bands do not sum, and a shop that read it naively would draw a confident wrong conclusion about a nearly empty band. Both caveats are now in the body rather than in a footnote, and the quoting-bottleneck test was added because it can invalidate the whole case. |
| Should a manufacturer hire an estimator or buy quoting software? | Answer | Answer Production Engine | 2026-08-23 | The draft compared salary against licence directly, which is the comparison the page argues cannot be settled. Restructured around the missing benefit quantity and the log analysis that produces it. Added the within-part-class control after the first version would have overstated the speed effect, and added the cost-model ownership risk, which is where these implementations actually fail. |
| Should a manufacturer pay for directory listings? | Answer | Answer Production Engine | 2026-08-23 | The draft argued against directories on cost-per-RFQ grounds and missed the stronger case for them, which is structured filterability at the elimination stage. Rebalanced, since the shop's own site usually carries no equivalent. Removed a claimed typical win rate on directory RFQs; no independent measurement of quote win rate by source exists and the page now tells the shop to produce its own. |
| Should a manufacturer publish prices or lead times? | Answer | Answer Production Engine | 2026-08-23 | The draft treated publication as a single choice. Splitting it into the disclosures that survive a shortlist versus the ones that price a job is what makes the answer actionable, and the minimum order value moved from a passing mention to its own section once it became clear it is the only item on the list that improves both sides of the ledger. |
| Should a practice add front-desk staff or automate? | Answer | Answer Production Engine | 2026-08-23 | The first pass argued that automation beats hiring, which the evidence does not support and which is not the finding. Rewrote it around the visibility asymmetry between the two queues, which is what actually decides these in practice, and added the wage-series caveat because the county figure is the number most often reached for and it averages clinicians into the front-desk cell. |
| Should a practice add overflow phone cover? | Answer | Answer Production Engine | 2026-08-23 | Cut an estimate of after-hours call share from the draft. There is no admissible source for it and inventing one would have been the exact failure the page argues against. The outside measurement now carries that weight instead, stated in enough detail to be repeated. Added the protected-information boundary, which belongs in the contract rather than in a later discovery. |
| Should a practice charge a no-show fee? | Answer | Answer Production Engine | 2026-08-23 | Removed a suggested fee range from the draft. Nothing in the evidence supports a number, and publishing one would have reproduced the exact defect the page is about — an unqualified figure detached from specialty and payer mix. Replaced it with the ordered sequence, and moved the payer-mix constraint ahead of the pricing discussion because it can remove the option entirely. |
| Should a practice open online self-scheduling? | Answer | Answer Production Engine | 2026-08-23 | The draft accepted the deflection frame and argued about its size. That was the wrong axis: the deflection claim is unfalsifiable in a saturated practice and the material exposure is on the schedule, not the phones. Restructured around that, and cut a paragraph estimating hours saved, which had no basis and would not have survived the number gate. |
| Should a small business be on social media? | Answer | Answer Production Engine | 2026-08-23 | The draft compared platforms by industry. That advice ages badly and is answerable more reliably by asking the business's own customers, so it was replaced with the one-week method. Added the unmonitored inbox, which is the concrete cost and which the first version treated as secondary to the posting question. |
| Should a small business use an AI receptionist? | Answer | Answer Production Engine | 2026-08-23 | The draft compared the product against a human receptionist, which is the comparison the sales material invites and the wrong one. Rebuilt around the voicemail comparison. Added the pricing-unit section after noticing that per-call and subscription quotes invert with volume, which means most businesses are comparing two numbers that are not comparable. |
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.