Billericay RFC
rugby team
Billericay Rugby Football Club is a rugby football club based in Billericay. The club runs three teams on a Saturday with the first XV competing in Counties 1 Essex. To support the club's long term ambitions and sustainability the club is building a youth section and welcome youngsters to come along and take up the game with us. These ambitions are set out within the Whole Club Development Plan, available to any member or interested party upon request.
History
Billericay Rugby Football Club (BRFC) was formed in late 1959 by members of the St Johns Cricket Club with whom BRFC still share the Willowbrook Sports Ground. BRFCs first full fixture took place in February 1960 versus a Brentwood XV and since then the club has built steadily, maintaining an enjoyable but highly competitive outlook both on and off the pitch.
Extracts from a letter from Stan Ball, an early Club President:
"The person who originally had the idea to set up the club (which as you probably know was a section of the St.John's Sports Association Ltd) was Michael Price, uncle of the one and only Frank Price. I am fairly sure that it all started in 1959 and early records show that our first full fixture was against a Brentwood team on 27 February 1960, followed by a game against Billericay School pupils and staff on 19 March 1960. The team sheet from the Brentwood game includes my good self and I have a fixture list for the 1960-61 season.
One piece of useless information that might be of interest is that at one point Billericay RFC had a Barbarian who played occasionally.
This brief starts where responsible research should: with the source description of “Billericay RFC” as rugby team. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as rugby team. Its deeper value depends on whether names, dates, institutions and citations support that framing.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Jul 19, 2026. The linked authority identifier is Q16951730. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1959 and 1960.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Billericay RFC”, its source revision and the description used here.
- Expand the search: follow Billericay RFC primary sources, Billericay RFC archive and Billericay research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Billericay RFC”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Billericay RFC” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.